Session framework configuration in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the default session engine in Django?

Django supports multiple session engines. Which one is used by default if you do not change any settings?

A django.contrib.sessions.backends.signed_cookies

B django.contrib.sessions.backends.db

C django.contrib.sessions.backends.file

D django.contrib.sessions.backends.cache

💡 Hint

Think about where Django stores session data by default.

The default session engine stores session data in the database using the django.contrib.sessions.backends.db backend.

❓ component_behavior

intermediate

What happens if SESSION_COOKIE_AGE is set to 0?

In Django settings, if you set SESSION_COOKIE_AGE = 0, what will be the behavior of the session cookie?

A The session cookie will expire immediately and not be saved.

B The session cookie will last for the default 2 weeks.

C The session cookie will never expire.

D The session cookie will expire when the browser is closed.

💡 Hint

Think about what a zero age means for cookies.

Setting SESSION_COOKIE_AGE to 0 makes the session cookie a browser-length cookie, which expires when the browser closes.

📝 Syntax

advanced

Identify the correct way to configure a cache-based session engine

Which of the following settings correctly configures Django to use the cache session engine?

A SESSION_ENGINE = 'django.contrib.sessions.backends.cache'

B SESSION_ENGINE = 'django.contrib.sessions.cache_backend'

C SESSION_ENGINE = 'django.sessions.backends.cache'

D SESSION_ENGINE = 'django.contrib.cache.sessions'

💡 Hint

Check the exact module path for the cache session backend.

The correct setting for cache-based sessions is django.contrib.sessions.backends.cache.

🔧 Debug

advanced

Why does session data not persist across requests?

A developer sets SESSION_ENGINE = 'django.contrib.sessions.backends.signed_cookies' but notices session data is lost after each request. What is the most likely cause?

A The SECRET_KEY setting is missing or not set properly.

B The database migrations for sessions were not run.

C The cache backend is not configured.

D The SESSION_COOKIE_AGE is set too high.

💡 Hint

Signed cookies require a secret to sign the data.

Signed cookie sessions require a properly set SECRET_KEY to sign and verify session data. Without it, session data cannot persist.

❓ state_output

expert

What is the output of this Django session code snippet?

Consider this Django view code snippet:

def view(request):
    request.session['count'] = request.session.get('count', 0) + 1
    return HttpResponse(str(request.session['count']))

If a user visits this view 3 times in the same browser session, what will be the output on the third visit?

Django

def view(request):
    request.session['count'] = request.session.get('count', 0) + 1
    return HttpResponse(str(request.session['count']))

A 1

B 2

C 3

D Error: 'count' key not found

💡 Hint

The session stores the count and increments it each visit.

Each visit increments the 'count' in the session by 1. On the third visit, the count will be 3.