User model overview in Django - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the User model in Django?

The User model in Django represents a person who can log into the website. It stores information like username, password, email, and permissions.

intermediate

Name two ways to customize the User model in Django.

You can customize the User model by either extending AbstractUser or by creating a completely new model using AbstractBaseUser.

beginner

What fields are included by default in Django's built-in User model?

The default User model includes username, password, email, first_name, last_name, is_staff, is_active, and date_joined.

beginner

How does Django handle password security in the User model?

Django stores passwords in a hashed format using strong algorithms, so the actual password is never saved in plain text.

intermediate

What is the role of the AUTH_USER_MODEL setting in Django?

AUTH_USER_MODEL tells Django which User model to use. It allows you to replace the default User model with a custom one.

Which Django model is used by default to represent users?

A django.contrib.admin.models.AdminUser

B django.db.models.Model

C django.contrib.sessions.models.Session

D django.contrib.auth.models.User

The default user model is django.contrib.auth.models.User.

Which method is recommended to create a fully custom user model?

A Extend AbstractBaseUser

B Extend AbstractUser

C Use the default User model without changes

D Create a model unrelated to AbstractBaseUser

Extending AbstractBaseUser allows full control over the user model.

What does the is_staff field indicate in the User model?

A If the user is active

B If the user can log in to the admin site

C If the user has a verified email

D If the user is a superuser

is_staff means the user can access the Django admin interface.

How are passwords stored in Django's User model?

A Plain text

B Encrypted with reversible encryption

C Hashed with a secure algorithm

D Not stored at all

Passwords are hashed securely to protect user data.

What setting do you change to use a custom User model?

A AUTH_USER_MODEL

B USER_MODEL

C CUSTOM_USER

D USER_AUTH_MODEL

AUTH_USER_MODEL tells Django which user model to use.

Explain the difference between extending AbstractUser and AbstractBaseUser when customizing the User model.

Think about how much you want to change the default user.

Describe how Django ensures password security in the User model.

Focus on how passwords are saved safely.

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