Why production setup differs in Django - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set DEBUG mode off for production.

Django

DEBUG = [1]

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

ATrue

B"False"

CNone

DFalse

Attempts:

3 left

💡 Hint

Common Mistakes

Setting DEBUG to True in production exposes sensitive info.

In production, DEBUG must be set to False to avoid showing detailed error pages to users.

2fill in blank

medium

Complete the code to add allowed hosts for production.

Django

ALLOWED_HOSTS = [[1]]

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

A"example.com"

B"localhost"

C"127.0.0.1"

D"*"

Attempts:

3 left

💡 Hint

Common Mistakes

Using '*' allows all hosts, which is insecure in production.

In production, ALLOWED_HOSTS should list the real domain names your site uses, like "example.com".

3fill in blank

hard

Fix the error in the static files setting for production.

Django

STATIC_ROOT = [1]

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

Aos.path.join(BASE_DIR, 'static')

Bos.path.join(BASE_DIR, 'staticfiles')

CBASE_DIR + '/static/'

D'/static/'

Attempts:

3 left

💡 Hint

Common Mistakes

Setting STATIC_ROOT to the same folder as STATICFILES_DIRS causes conflicts.

In production, STATIC_ROOT should be a directory where static files are collected, commonly 'staticfiles'.

4fill in blank

hard

Fill both blanks to configure secure cookies in production.

Django

SESSION_COOKIE_SECURE = [1]
CSRF_COOKIE_SECURE = [2]

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

ATrue

BFalse

C"True"

D"False"

Attempts:

3 left

💡 Hint

Common Mistakes

Leaving these as False exposes cookies over insecure connections.

In production, setting SESSION_COOKIE_SECURE and CSRF_COOKIE_SECURE to True ensures cookies are sent only over HTTPS.

5fill in blank

hard

Fill all three blanks to configure database settings for production.

Django

DATABASES = {
    'default': {
        'ENGINE': [1],
        'NAME': [2],
        'USER': [3]
    }
}

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

A'django.db.backends.postgresql'

B'mydatabase'

C'myuser'

D'sqlite3'

Attempts:

3 left

💡 Hint

Common Mistakes

Using SQLite in production is not recommended for scalability.

Production often uses PostgreSQL with proper database name and user instead of default SQLite.

Practice

1. Why should DEBUG be set to False in a Django production setup?

easy

A. To speed up the development process

B. To enable automatic database migrations

C. To allow Django to serve static files directly

D. To prevent detailed error messages from being shown to users

Solution

1. Step 1: Understand the role of DEBUG in Django

   When DEBUG is True, Django shows detailed error pages with sensitive information.

2. Step 2: Consider security implications in production

   Showing detailed errors publicly can expose security risks, so DEBUG must be False in production.

3. Final Answer:

   To prevent detailed error messages from being shown to users -> Option D

4. Quick Check:

   DEBUG False hides errors [OK]

Hint: Remember: DEBUG False hides errors from users [OK]

Common Mistakes:

• Thinking DEBUG False speeds development
• Believing DEBUG controls static file serving
• Confusing DEBUG with database migrations

2. Which of the following is the correct way to specify allowed hosts in Django's settings.py for production?

easy

A. ALLOWED_HOSTS = ['yourdomain.com', 'www.yourdomain.com']

B. ALLOWED_HOSTS = ['localhost', '127.0.0.1']

C. ALLOWED_HOSTS = []

D. ALLOWED_HOSTS = '*'

Solution

1. Step 1: Understand ALLOWED_HOSTS purpose

   ALLOWED_HOSTS lists domain names your Django app can serve to prevent host header attacks.

2. Step 2: Choose correct production domains

   In production, you must list your real domain names, not localhost or empty list.

3. Final Answer:

   ALLOWED_HOSTS = ['yourdomain.com', 'www.yourdomain.com'] -> Option A

4. Quick Check:

   Production domains in ALLOWED_HOSTS [OK]

Hint: Use real domain names in ALLOWED_HOSTS for production [OK]

Common Mistakes:

• Leaving ALLOWED_HOSTS empty disables host checking
• Using '*' is insecure and not allowed
• Including only localhost for production

3. Given this production setting snippet:

DEBUG = False
ALLOWED_HOSTS = ['example.com']
STATIC_ROOT = '/var/www/static/'

What happens when you run python manage.py collectstatic?

medium

A. Static files are copied to '/var/www/static/' directory

B. Static files are served automatically by Django

C. An error occurs because DEBUG is False

D. Static files remain in app folders without change

Solution

1. Step 1: Understand collectstatic command

   It gathers all static files from apps and copies them to STATIC_ROOT for serving.

2. Step 2: Check STATIC_ROOT setting

   STATIC_ROOT is set to '/var/www/static/', so files copy there on collectstatic.

3. Final Answer:

   Static files are copied to '/var/www/static/' directory -> Option A

4. Quick Check:

   collectstatic copies files to STATIC_ROOT [OK]

Hint: collectstatic copies files to STATIC_ROOT folder [OK]

Common Mistakes:

• Thinking Django serves static files in production automatically
• Believing DEBUG affects collectstatic behavior
• Assuming static files stay in app folders

4. You deployed your Django app with DEBUG = False and ALLOWED_HOSTS = []. When accessing the site, you get a 400 Bad Request error. What is the likely cause?

medium

A. DEBUG must be True to allow requests

B. ALLOWED_HOSTS is empty, so Django blocks all hosts

C. Static files are not collected

D. Database settings are incorrect

Solution

1. Step 1: Analyze ALLOWED_HOSTS effect

   An empty ALLOWED_HOSTS means no hosts are allowed, causing 400 errors.

2. Step 2: Understand DEBUG role

   DEBUG False is correct for production; it does not cause 400 errors by itself.

3. Final Answer:

   ALLOWED_HOSTS is empty, so Django blocks all hosts -> Option B

4. Quick Check:

   Empty ALLOWED_HOSTS causes 400 error [OK]

Hint: Empty ALLOWED_HOSTS blocks all requests [OK]

Common Mistakes:

• Thinking DEBUG True fixes 400 errors
• Blaming static files for 400 errors
• Assuming database issues cause 400 Bad Request

5. In production, why is it recommended to serve static files using a web server like Nginx instead of Django's development server?

hard

A. Because Django cannot serve static files at all

B. Because Nginx automatically sets DEBUG to False

C. Because Django's server is not optimized for static file delivery and can slow down the app

D. Because static files are not needed in production

Solution

1. Step 1: Understand Django's development server purpose

   Django's built-in server is for development only and is not efficient at serving static files.

2. Step 2: Recognize production server advantages

   Web servers like Nginx are optimized to serve static files quickly without slowing the app.

3. Final Answer:

   Because Django's server is not optimized for static file delivery and can slow down the app -> Option C

4. Quick Check:

   Use Nginx for static files in production [OK]

Hint: Use Nginx or similar for static files in production [OK]

Common Mistakes:

• Believing Django cannot serve static files at all
• Thinking Nginx changes DEBUG setting
• Assuming static files are unnecessary in production