Cookie-based sessions vs database sessions in Django - Quick Revision & Key Differences

Recall & Review

beginner

What is a cookie-based session in Django?

A cookie-based session stores all session data directly inside the user's browser cookie. Django signs the cookie to prevent tampering but does not store session data on the server.

beginner

How does a database session work in Django?

A database session stores session data on the server in the database. The user's browser only keeps a session ID cookie that references the stored data.

intermediate

Name one advantage of cookie-based sessions.

They reduce server load because session data is stored on the client side, so the server does not need to read or write session data for each request.

intermediate

What is a key security concern with cookie-based sessions?

Since session data is stored on the client, it can be exposed if not properly secured. Although signed, sensitive data should not be stored in cookies to avoid leaks.

intermediate

Why might you choose database sessions over cookie-based sessions?

Database sessions allow storing larger and more complex data securely on the server, and they avoid exposing session data to the client.

In Django, where is session data stored when using cookie-based sessions?

A In a server-side file

B Inside the user's browser cookie

C In the server's database

D In the server's memory only

Cookie-based sessions store all session data inside the user's browser cookie.

What does Django store in the user's cookie when using database sessions?

A Only a session ID

B No cookie is stored

C User's password

D The entire session data

Django stores only a session ID in the cookie, which references the session data stored in the database.

Which session type reduces server storage needs?

A Cookie-based sessions

B File-based sessions

C Database sessions

D Cache-based sessions

Cookie-based sessions store data on the client side, reducing server storage needs.

What is a risk of storing sensitive data in cookie-based sessions?

A Server load increases

B Data can be lost if the server crashes

C Cookies expire too quickly

D Data can be tampered with or exposed

Sensitive data in cookies can be exposed or tampered with despite signing, so it is risky to store it there.

Which session type is better for storing large amounts of data securely?

A Cookie-based sessions

B URL-based sessions

C Database sessions

D Local storage sessions

Database sessions store data securely on the server and can handle larger data sizes.

Explain the main differences between cookie-based sessions and database sessions in Django.

Think about client vs server storage and what each session type keeps in the cookie.

When would you choose to use cookie-based sessions over database sessions in a Django project?

Consider performance and data sensitivity.