Why settings configuration matters in Django - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is DEBUG mode important in Django settings?

What happens when you set DEBUG = True in Django settings during development?

A Django disables all error messages and logs nothing.

B Django shows detailed error pages with debug information when errors occur.

C Django automatically deploys the app to production servers.

D Django encrypts all database connections by default.

💡 Hint

Think about what helps developers find problems easily.

When DEBUG is True, Django shows detailed error pages that help developers understand what went wrong. This should only be used during development, not in production.

❓ component_behavior

intermediate

Effect of ALLOWED_HOSTS in Django settings

What will happen if you set ALLOWED_HOSTS = [] in production?

A Django will automatically add localhost to ALLOWED_HOSTS.

B Django will accept requests from any host without restriction.

C Django will reject all incoming requests with a 'Bad Request' error.

D Django will redirect all requests to HTTPS.

💡 Hint

Think about security and which hosts Django trusts.

When ALLOWED_HOSTS is empty, Django does not trust any host and returns a 'Bad Request (400)' error for all requests. This prevents host header attacks.

📝 Syntax

advanced

Identify the correct way to configure DATABASES in Django settings

Which option correctly configures a PostgreSQL database in Django settings?

A DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql', 'NAME': 'mydb', 'USER': 'user', 'PASSWORD': 'pass', 'HOST': 'localhost', 'PORT': '5432' } }

B DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql', 'NAME': 'mydb', 'USER': 'user', 'PASSWORD': 'pass' } }

C DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'mydb', 'USER': 'user', 'PASSWORD': 'pass' } }

D DATABASES = { 'default': { 'ENGINE': 'postgresql', 'NAME': 'mydb', 'USER': 'user', 'PASSWORD': 'pass' } }

💡 Hint

Check the exact engine string Django expects for PostgreSQL.

Django requires the engine string 'django.db.backends.postgresql' for PostgreSQL. Other options either use wrong engine names or different databases.

❓ state_output

advanced

What is the effect of STATIC_URL setting in Django?

If STATIC_URL = '/static/' is set, what URL will Django use to serve static files?

A Static files will not be served at all.

B Static files will be served from the root URL '/' only.

C Django will serve static files from '/media/' URL.

D URLs starting with '/static/' will be used to serve static files.

💡 Hint

STATIC_URL defines the base URL path for static files.

The STATIC_URL setting tells Django the URL prefix to use when serving static files. Setting it to '/static/' means static files are accessed via URLs starting with '/static/'.

🔧 Debug

expert

Why does changing SECRET_KEY in production cause errors?

If you change SECRET_KEY in a running Django production app, what problem might occur?

A User sessions and password reset tokens become invalid causing login failures.

B The database connection will fail immediately.

C Django will automatically generate a new SECRET_KEY and continue working.

D Static files will stop loading on the website.

💡 Hint

SECRET_KEY is used to sign important data like sessions.

The SECRET_KEY is used to sign cookies and tokens. Changing it invalidates existing sessions and tokens, causing users to be logged out and password resets to fail.