User model overview in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the default User model in Django.

Django

from django.contrib.auth.models import [1]

Drag options to blanks, or click blank then click option'

AUser

BProfile

CAccount

DMember

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to import Profile or Account instead of User.

Importing from the wrong module.

The default User model in Django is named User and is imported from django.contrib.auth.models.

2fill in blank

medium

Complete the code to create a new User instance with username 'alice'.

Django

user = User.objects.[1](username='alice')

Drag options to blanks, or click blank then click option'

Acreate

Bget

Cfilter

Dall

Attempts:

3 left

💡 Hint

Common Mistakes

Using get() which retrieves existing users.

Using filter() which returns a queryset, not a single user.

To create a new User instance in Django, use create() on the model manager.

3fill in blank

hard

Fix the error in the code to check if a user is staff.

Django

if user.[1]:
    print('User is staff')

Drag options to blanks, or click blank then click option'

Astaff

Bis_staff

CisStaff

Dstaff_member

Attempts:

3 left

💡 Hint

Common Mistakes

Using camelCase like isStaff.

Using incorrect attribute names like staff or staff_member.

The correct attribute to check if a user is staff is is_staff.

4fill in blank

hard

Fill both blanks to filter users who are active and have email ending with '@example.com'.

Django

users = User.objects.filter(is_active=[1], email__[2]='@example.com')

Drag options to blanks, or click blank then click option'

ATrue

BFalse

Cendswith

Dstartswith

Attempts:

3 left

💡 Hint

Common Mistakes

Using False instead of True for active users.

Using startswith instead of endswith for email filtering.

To filter active users, use is_active=True. To filter emails ending with a string, use email__endswith.

5fill in blank

hard

Fill all three blanks to update a user's first name and save the changes.

Django

user = User.objects.get(username=[1])
user.first_name = [2]
user.[3]()

Drag options to blanks, or click blank then click option'

A'alice'

B'Alice'

Csave

Dupdate

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around string values.

Using update() method on the instance instead of save().

Get the user by username 'alice', set first_name to 'Alice', then call save() to save changes.

Practice

1. What is the primary purpose of Django's built-in User model?

easy

A. To manage static files like CSS and JavaScript

B. To handle database migrations automatically

C. To create HTML templates for user profiles

D. To store and manage user accounts including authentication

Solution

1. Step 1: Understand the role of the User model

   The User model in Django is designed to handle user accounts, including login and authentication.

2. Step 2: Compare options with User model functions

   Options B, C, and D relate to other Django features, not user management.

3. Final Answer:

   To store and manage user accounts including authentication -> Option D

4. Quick Check:

   User model = user account management [OK]

Hint: User model = user accounts and login management [OK]

Common Mistakes:

• Confusing User model with template or static file handling
• Thinking User model manages database migrations
• Assuming User model creates HTML pages

2. Which of the following is the correct way to import Django's default User model?

easy

A. from django.contrib.auth.models import User

B. import django.auth.User

C. from django.models import User

D. from django.contrib.auth import UserModel

Solution

1. Step 1: Recall the correct import path for User

   Django's default User model is located in django.contrib.auth.models.

2. Step 2: Check each option's syntax

   from django.contrib.auth.models import User matches the correct import syntax. Options A, C, and D are incorrect or invalid imports.

3. Final Answer:

   from django.contrib.auth.models import User -> Option A

4. Quick Check:

   Correct import path = from django.contrib.auth.models import User [OK]

Hint: User model is in django.contrib.auth.models [OK]

Common Mistakes:

• Using incorrect module paths
• Trying to import User directly from django.models
• Confusing User with UserModel

3. What will be the output of this code snippet?

from django.contrib.auth.models import User
user = User.objects.create_user(username='alice', password='pass123')
print(user.is_active)

medium

A. False

B. None

C. True

D. Raises an error

Solution

1. Step 1: Understand create_user default behavior

   The create_user method creates a user with is_active set to True by default.

2. Step 2: Check the printed attribute

   Printing user.is_active will output True unless explicitly changed.

3. Final Answer:

   True -> Option C

4. Quick Check:

   Default is_active = True [OK]

Hint: create_user sets is_active True by default [OK]

Common Mistakes:

• Assuming is_active is False by default
• Expecting None or error without context
• Confusing create_user with create_superuser

4. Identify the error in this code snippet that tries to create a user:

from django.contrib.auth.models import User
user = User.objects.create(username='bob', password='secret')

medium

A. Username must be an email address

B. Using create() instead of create_user() for password hashing

C. Password field cannot be set during user creation

D. Missing import for User model

Solution

1. Step 1: Check method used for user creation

   The create() method does not hash passwords; create_user() should be used instead.

2. Step 2: Analyze the impact of using create()

   Using create() stores the password as plain text, which is insecure and incorrect.

3. Final Answer:

   Using create() instead of create_user() for password hashing -> Option B

4. Quick Check:

   Use create_user() to hash passwords [OK]

Hint: Use create_user() to hash passwords, not create() [OK]

Common Mistakes:

• Using create() which stores raw passwords
• Forgetting to import User
• Thinking username must be email

5. You want to extend Django's default User model to add a 'birth_date' field. Which approach is recommended?

hard

A. Create a separate model with OneToOneField to User and add birth_date there

B. Directly add birth_date field to the built-in User model

C. Override User model by copying all fields and adding birth_date

D. Add birth_date as a global variable in settings.py

Solution

1. Step 1: Understand Django's recommended user extension

   Django suggests extending User by creating a profile model linked with OneToOneField.

2. Step 2: Evaluate options for adding fields

   Directly modifying built-in User or copying it is discouraged; settings.py cannot hold model fields.

3. Final Answer:

   Create a separate model with OneToOneField to User and add birth_date there -> Option A

4. Quick Check:

   Extend User via OneToOneField profile model [OK]

Hint: Extend User with OneToOneField profile model [OK]

Common Mistakes:

• Trying to modify built-in User model directly
• Copying User model instead of extending
• Adding model fields in settings.py