Cookie-based sessions vs database sessions in Django - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Difference in data storage location

Where is session data stored when using cookie-based sessions compared to database sessions in Django?

A Cookie-based sessions store all session data on the client inside cookies; database sessions store session data on the server in the database.

B Cookie-based sessions store session data in the database; database sessions store data inside cookies on the client.

C Both cookie-based and database sessions store session data only in server memory.

D Cookie-based sessions store session data in temporary files; database sessions store data in browser local storage.

💡 Hint

Think about where the session data physically lives in each method.

Cookie-based sessions keep all session data inside the user's browser cookies, while database sessions save session data on the server side in the database.

❓ component_behavior

intermediate

Session size limits impact

What happens if you try to store a large amount of data in a cookie-based session in Django?

A The data will automatically be split across multiple cookies without issues.

B The session data will be truncated or cause errors because cookies have size limits.

C The session data size is unlimited in cookie-based sessions.

D Django will store the extra data in the database automatically.

💡 Hint

Consider browser cookie size limits.

Cookies have size limits (usually around 4KB). Storing too much data in cookie-based sessions can cause truncation or errors.

🔧 Debug

advanced

Session data loss troubleshooting

A Django app using cookie-based sessions loses session data unexpectedly after a user logs in. Which of the following is the most likely cause?

A The session cookie is not marked as secure and is blocked by the browser.

B The database storing sessions is down.

C The session data exceeds the cookie size limit and is truncated.

D The server's cache is full.

💡 Hint

Think about cookie size limits and how that affects cookie-based sessions.

When session data is too large for cookies, it can be truncated, causing data loss in cookie-based sessions.

📝 Syntax

advanced

Configuring database sessions in Django

Which setting correctly configures Django to use database-backed sessions?

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

B SESSION_ENGINE = 'django.contrib.sessions.backends.signed_cookies'

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

D SESSION_ENGINE = 'django.contrib.sessions.backends.file'

💡 Hint

Database sessions use the 'db' backend.

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

❓ state_output

expert

Session data persistence after server restart

In a Django app using database sessions, what happens to session data after the web server restarts?

A Session data persists only if the server cache is warmed up.

B Session data is lost because it is stored only in server memory.

C Session data is lost because cookies are cleared on server restart.

D Session data persists because it is stored in the database.

💡 Hint

Think about where the session data lives and what survives a server restart.

Database sessions store data in the database, which persists across server restarts.

Practice

1. What is the main difference between cookie-based sessions and database sessions in Django?

easy

A. Both store data only on the server but in different database tables.

B. Cookie-based sessions store data on the client browser, while database sessions store data on the server.

C. Both store data only on the client browser but use different encryption methods.

D. Cookie-based sessions store data on the server, while database sessions store data on the client browser.

Solution

1. Step 1: Understand where session data is stored

   Cookie-based sessions keep the session data inside the user's browser cookies. Database sessions keep the data on the server side in a database.

2. Step 2: Compare storage locations

   Since cookie sessions store data client-side and database sessions store data server-side, this is the key difference.

3. Final Answer:

   Cookie-based sessions store data on the client browser, while database sessions store data on the server. -> Option B

4. Quick Check:

   Storage location = client vs server [OK]

Hint: Remember: cookies = browser, database = server [OK]

Common Mistakes:

• Confusing client and server storage
• Thinking both store data only on server
• Assuming cookie sessions use server database

2. Which setting in Django controls whether sessions use cookies or the database?

easy

A. SESSION_ENGINE

B. SESSION_COOKIE_NAME

C. SESSION_SAVE_EVERY_REQUEST

D. SESSION_EXPIRE_AT_BROWSER_CLOSE

Solution

1. Step 1: Identify session-related settings

   Django uses several settings for sessions, but the one that controls the backend storage is SESSION_ENGINE.

2. Step 2: Understand SESSION_ENGINE role

   Changing SESSION_ENGINE switches between cookie-based sessions and database sessions.

3. Final Answer:

   SESSION_ENGINE -> Option A

4. Quick Check:

   Session backend = SESSION_ENGINE [OK]

Hint: SESSION_ENGINE sets session storage type [OK]

Common Mistakes:

• Choosing cookie name instead of engine
• Confusing save frequency with storage
• Mixing expiration with storage setting

3. Given this Django setting: SESSION_ENGINE = 'django.contrib.sessions.backends.signed_cookies', what happens when you store a large amount of data in the session?

medium

A. The data is stored securely on the server database.

B. The data is split between cookie and database automatically.

C. The session will raise an error and not save any data.

D. The data is stored in the user's browser cookie, which may cause size issues.

Solution

1. Step 1: Identify the session backend

   The setting 'signed_cookies' means session data is stored in browser cookies, signed for security.

2. Step 2: Consider cookie size limits

   Browser cookies have size limits (usually around 4KB). Storing large data can cause issues or truncation.

3. Final Answer:

   The data is stored in the user's browser cookie, which may cause size issues. -> Option D

4. Quick Check:

   Signed cookies = client storage, watch size limits [OK]

Hint: Signed cookies store data client-side, watch size limits [OK]

Common Mistakes:

• Assuming data is stored server-side
• Thinking Django splits data automatically
• Expecting error instead of silent truncation

4. You switched SESSION_ENGINE to use database sessions but your session data is not saving. Which is the most likely cause?

medium

A. You set SESSION_COOKIE_NAME incorrectly.

B. You did not clear browser cookies before testing.

C. You forgot to run migrations to create the session table.

D. You used the wrong database engine in settings.

Solution

1. Step 1: Understand database session requirements

   Database sessions require a database table to store session data, created by migrations.

2. Step 2: Identify missing migration impact

   If migrations are not run, the session table does not exist, so session data cannot be saved.

3. Final Answer:

   You forgot to run migrations to create the session table. -> Option C

4. Quick Check:

   Database sessions need session table migration [OK]

Hint: Run migrations after switching to database sessions [OK]

Common Mistakes:

• Blaming cookies instead of database setup
• Changing cookie name unrelated to saving
• Confusing database engine with session table

5. You want to store sensitive user data in sessions and ensure it is not exposed to the client. Which session backend should you choose and why?

hard

A. Use database sessions because data is stored server-side and not exposed to the client.

B. Use cookie-based sessions because they are encrypted and secure.

C. Use cookie-based sessions because they are faster and store data locally.

D. Use database sessions but also store data in cookies for backup.

Solution

1. Step 1: Consider data sensitivity and storage location

   Sensitive data should not be stored in client-accessible places like cookies, even if encrypted.

2. Step 2: Choose backend that keeps data server-side

   Database sessions store data on the server, protecting it from client access and tampering.

3. Step 3: Evaluate options

   Use database sessions because data is stored server-side and not exposed to the client. correctly chooses database sessions for sensitive data security.

4. Final Answer:

   Use database sessions because data is stored server-side and not exposed to the client. -> Option A

5. Quick Check:

   Sensitive data = server storage [OK]

Hint: Sensitive data? Store server-side with database sessions [OK]

Common Mistakes:

• Assuming cookie encryption is enough
• Mixing speed with security needs
• Trying to duplicate data in cookies and DB