Setting and getting session data in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Django view when session key 'count' is not set?

Consider this Django view that tries to read a session key 'count' and increments it:

def my_view(request):
    count = request.session.get('count', 0)
    count += 1
    request.session['count'] = count
    return HttpResponse(f"Count is {count}")

What will the response content be on the first visit?

Django

def my_view(request):
    count = request.session.get('count', 0)
    count += 1
    request.session['count'] = count
    return HttpResponse(f"Count is {count}")

A Count is None

B Count is 0

C Count is 1

D KeyError: 'count'

💡 Hint

Remember the default value used in get when the key is missing.

The session key 'count' is not set initially, so get('count', 0) returns 0. Then it increments to 1 and saves back. So the response shows 'Count is 1'.

📝 Syntax

intermediate

Which option correctly sets a session variable 'user' to 'alice' in Django?

Choose the correct code snippet to set the session key 'user' to the string 'alice' inside a Django view.

A request.session.add('user', 'alice')

B request.session['user'] = 'alice'

C request.session.set('user', 'alice')

D request.session.user = 'alice'

💡 Hint

Think about how Python dictionaries are used to set session data.

Session data in Django behaves like a dictionary. You set values by assigning to keys with square brackets. Methods like set or add do not exist on session objects.

🔧 Debug

advanced

Why does this Django view fail to save session data?

Look at this Django view:

def view(request):
    request.session['visits'] = request.session.get('visits', 0) + 1
    return HttpResponse(f"Visits: {request.session['visits']}")

After calling this view multiple times, the visit count does not increase. What is the most likely reason?

Django

def view(request):
    request.session['visits'] = request.session.get('visits', 0) + 1
    return HttpResponse(f"Visits: {request.session['visits']}")

A Session middleware is not enabled in settings

B The view does not call request.session.save() explicitly

C HttpResponse does not support f-strings

D The session key 'visits' is read-only

💡 Hint

Check if the session system is properly activated in Django.

If the session middleware is missing from MIDDLEWARE in settings, session data won't persist. The view code is correct and does not require explicit save calls.

❓ state_output

advanced

What is the session data after this sequence of requests?

Assume a user makes these requests to a Django view that manages session data:

def counter(request):
    if 'count' not in request.session:
        request.session['count'] = 0
    request.session['count'] += 2
    return HttpResponse(str(request.session['count']))

What will be the session value for 'count' after the third request?

Django

def counter(request):
    if 'count' not in request.session:
        request.session['count'] = 0
    request.session['count'] += 2
    return HttpResponse(str(request.session['count']))

A 6

B 2

C 3

D 0

💡 Hint

Count how much the value increases each request.

Initially 'count' is set to 0. Each request adds 2. After 3 requests: 0 + 2 + 2 + 2 = 6.

🧠 Conceptual

expert

Which statement about Django session data is true?

Choose the correct statement about how Django handles session data.

A Session data is stored client-side in cookies by default

B Session data requires explicit saving by calling request.session.save() after modification

C Session data is automatically encrypted and cannot be read by the server

D Session data is stored server-side and linked to the client via a session cookie

💡 Hint

Think about where Django keeps session data and how it identifies clients.

Django stores session data on the server side (database, cache, or file). The client only holds a session ID cookie to link to that data. The server can read session data. It does not require explicit save calls.