Session framework configuration in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable sessions in Django settings.

Django

INSTALLED_APPS = [
    'django.contrib.admin',
    'django.contrib.auth',
    'django.contrib.contenttypes',
    'django.contrib.sessions',  # [1]
    'django.contrib.messages',
    'django.contrib.staticfiles',
]

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

A'django.contrib.messages.middleware.MessageMiddleware'

B'django.contrib.sites'

C'django.contrib.sessions.middleware.SessionMiddleware'

D'django.contrib.sessions'

Attempts:

3 left

💡 Hint

Common Mistakes

Adding middleware instead of app in INSTALLED_APPS

Forgetting to add the sessions app

You must add 'django.contrib.sessions' to INSTALLED_APPS to enable session support.

2fill in blank

medium

Complete the code to add session middleware in Django settings.

Django

MIDDLEWARE = [
    'django.middleware.security.SecurityMiddleware',
    'django.contrib.sessions.middleware.[1]',
    'django.middleware.common.CommonMiddleware',
    'django.middleware.csrf.CsrfViewMiddleware',
]

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

ASessionMiddleware

BMessageMiddleware

CAuthenticationMiddleware

DLocaleMiddleware

Attempts:

3 left

💡 Hint

Common Mistakes

Using AuthenticationMiddleware instead of SessionMiddleware

Forgetting to add session middleware

The session middleware is 'django.contrib.sessions.middleware.SessionMiddleware'. It manages session data on requests.

3fill in blank

hard

Fix the error in the session engine setting to use database-backed sessions.

Django

SESSION_ENGINE = [1]

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

A'django.contrib.sessions.backends.db'

B'django.contrib.sessions.backends.file'

C'django.contrib.sessions.backends.signed_cookies'

D'django.contrib.sessions.backends.cache'

Attempts:

3 left

💡 Hint

Common Mistakes

Using cache or file backend instead of db backend

Missing quotes around the string

To use database-backed sessions, set SESSION_ENGINE to 'django.contrib.sessions.backends.db'.

4fill in blank

hard

Fill both blanks to configure session cookie settings for security.

Django

SESSION_COOKIE_SECURE = [1]
SESSION_COOKIE_HTTPONLY = [2]

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

ATrue

BFalse

C'True'

D'False'

Attempts:

3 left

💡 Hint

Common Mistakes

Using string 'True' instead of boolean True

Setting these values to False reduces security

Setting SESSION_COOKIE_SECURE and SESSION_COOKIE_HTTPONLY to True helps protect session cookies.

5fill in blank

hard

Fill all three blanks to create a session dictionary comprehension filtering keys starting with 'user_'.

Django

filtered_sessions = {k: v for k, v in request.session.items() if k[1]'user_') and v[2] 0 and isinstance(v, [3])}

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

A.startswith(

B>

Cint

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' instead of '.startswith(' for key check

Using wrong comparison operators

Using wrong type in isinstance

This comprehension keeps session items where the key starts with 'user_', the value is greater than 0, and the value is an integer.

Practice

1. What is the main purpose of Django's session framework?

easy

A. To store static files like images and CSS

B. To handle database migrations automatically

C. To remember user data between different pages

D. To manage user authentication only

Solution

1. Step 1: Understand session framework role

   Django sessions store data to keep track of users as they move between pages.

2. Step 2: Compare options with session purpose

   Only To remember user data between different pages describes remembering user data between pages, which is the session's job.

3. Final Answer:

   To remember user data between different pages -> Option C

4. Quick Check:

   Sessions remember users = B [OK]

Hint: Sessions remember users across pages, not files or migrations [OK]

Common Mistakes:

• Confusing sessions with static file storage
• Thinking sessions only handle login
• Mixing sessions with database migrations

2. Which setting in settings.py specifies the backend storage for sessions?

easy

A. SESSION_ENGINE

B. SESSION_COOKIE_AGE

C. SESSION_SAVE_EVERY_REQUEST

D. SESSION_EXPIRE_AT_BROWSER_CLOSE

Solution

1. Step 1: Identify session backend setting

   The setting that controls where sessions are stored is SESSION_ENGINE.

2. Step 2: Review other options

   Other options control cookie age, saving behavior, or expiration, not storage backend.

3. Final Answer:

   SESSION_ENGINE -> Option A

4. Quick Check:

   Backend storage = SESSION_ENGINE [OK]

Hint: SESSION_ENGINE sets storage backend, not cookie or expiration [OK]

Common Mistakes:

• Confusing SESSION_ENGINE with cookie age
• Mixing save behavior with storage backend
• Assuming expiration settings control storage

3. Given this settings.py snippet:

SESSION_ENGINE = 'django.contrib.sessions.backends.cache'
SESSION_COOKIE_AGE = 1209600  # 2 weeks
SESSION_EXPIRE_AT_BROWSER_CLOSE = False

What happens when a user closes and reopens their browser?

medium

A. The session cookie is deleted but data remains in cache

B. The session expires immediately on browser close

C. The session is stored in the database and expires on logout

D. The session is kept for 2 weeks and user stays logged in

Solution

1. Step 1: Analyze SESSION_EXPIRE_AT_BROWSER_CLOSE

   It is set to False, so session cookies do not expire when browser closes.

2. Step 2: Check SESSION_COOKIE_AGE

   Set to 2 weeks, so session lasts that long unless user logs out.

3. Final Answer:

   The session is kept for 2 weeks and user stays logged in -> Option D

4. Quick Check:

   Expire at close = False means session kept [OK]

Hint: False expire at close means session lasts cookie age [OK]

Common Mistakes:

• Assuming session expires on browser close by default
• Confusing cache backend with database storage
• Thinking cookie deletion removes session data immediately

4. You set SESSION_ENGINE = 'django.contrib.sessions.backends.file' but get errors about missing directories. What is the likely cause?

medium

A. The session file directory does not exist or lacks write permission

B. SESSION_ENGINE value is invalid and causes syntax error

C. You forgot to add sessions to INSTALLED_APPS

D. SESSION_COOKIE_AGE is set too low causing session loss

Solution

1. Step 1: Understand file backend requirements

   The file backend stores sessions in files, needing a writable directory.

2. Step 2: Identify cause of errors

   If directory is missing or not writable, errors occur when saving sessions.

3. Final Answer:

   The session file directory does not exist or lacks write permission -> Option A

4. Quick Check:

   File backend needs writable directory [OK]

Hint: File backend needs writable folder, else errors occur [OK]

Common Mistakes:

• Assuming SESSION_ENGINE value syntax is wrong
• Forgetting sessions are built-in, no INSTALLED_APPS needed
• Blaming cookie age for file write errors

5. You want sessions to expire when the user closes the browser but also want to keep sessions for 1 hour if the browser stays open. Which settings combination achieves this?

hard

A. SESSION_EXPIRE_AT_BROWSER_CLOSE = False and SESSION_COOKIE_AGE = 3600

B. SESSION_EXPIRE_AT_BROWSER_CLOSE = True and SESSION_COOKIE_AGE = 3600

C. SESSION_EXPIRE_AT_BROWSER_CLOSE = True and SESSION_COOKIE_AGE = None

D. SESSION_EXPIRE_AT_BROWSER_CLOSE = False and SESSION_COOKIE_AGE = None

Solution

1. Step 1: Understand SESSION_EXPIRE_AT_BROWSER_CLOSE

   Setting it to True makes the session expire when browser closes.

2. Step 2: Understand SESSION_COOKIE_AGE

   Setting it to 3600 seconds (1 hour) limits session lifetime if browser stays open.

3. Final Answer:

   SESSION_EXPIRE_AT_BROWSER_CLOSE = True and SESSION_COOKIE_AGE = 3600 -> Option B

4. Quick Check:

   Expire at close True + 1 hour age = A [OK]

Hint: Expire at close True + cookie age limits session time [OK]

Common Mistakes:

• Setting expire at close False when wanting session to end on close
• Using None for cookie age disables expiration
• Confusing cookie age with session storage backend