DEBUG mode behavior in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when DEBUG is set to True in Django?

In a Django project, if you set DEBUG = True in settings.py, what is the expected behavior when an error occurs during a request?

A Django disables all middleware and serves static files only.

B Django shows a detailed error page with stack trace and local variables.

C Django silently logs the error and shows a generic 500 error page to the user.

D Django redirects the user to the homepage without any error message.

💡 Hint

Think about what helps developers find bugs during development.

When DEBUG is True, Django shows a detailed error page with the stack trace and local variables to help developers debug issues.

📝 Syntax

intermediate

Which setting causes Django to serve static files automatically?

In Django, when DEBUG is set to True, which of the following is true about serving static files during development?

A Django disables static file serving when DEBUG is True.

B Django requires manual configuration of static file serving regardless of DEBUG.

C Django automatically serves static files using <code>django.contrib.staticfiles</code> app.

D Django serves static files only if <code>STATIC_ROOT</code> is empty.

💡 Hint

Think about what makes development easier without extra setup.

When DEBUG is True, Django serves static files automatically using the django.contrib.staticfiles app, simplifying development.

🔧 Debug

advanced

What error occurs if DEBUG is False but ALLOWED_HOSTS is empty?

In Django, if DEBUG = False and ALLOWED_HOSTS = [], what happens when you try to access the site?

A Django serves the site normally without any error.

B Django redirects all requests to the admin login page.

C Django shows the detailed debug error page with stack trace.

D Django raises a <code>DisallowedHost</code> exception and returns a 400 Bad Request error.

💡 Hint

Think about security restrictions when DEBUG is off.

When DEBUG is False, Django requires ALLOWED_HOSTS to be set. If empty, it raises a DisallowedHost exception and returns a 400 error.

❓ state_output

advanced

How does DEBUG mode affect template caching in Django?

When DEBUG is True, how does Django handle template loading compared to when DEBUG is False?

A Templates are reloaded on every request to reflect changes immediately.

B Templates are cached and never reloaded until the server restarts.

C Templates are compiled to bytecode and stored permanently on disk.

D Templates are disabled and replaced with plain HTML files.

💡 Hint

Think about what helps developers see changes quickly.

With DEBUG=True, Django reloads templates on every request so developers see changes immediately without restarting the server.

🧠 Conceptual

expert

Why should DEBUG never be True in production?

Which of the following is the main reason to never set DEBUG = True in a production Django environment?

A It exposes sensitive information like secret keys and database credentials in error pages.

B It disables all middleware, causing security holes.

C It automatically deletes user data after errors occur.

D It prevents the server from handling HTTPS requests.

💡 Hint

Think about what information error pages show when debugging is on.

DEBUG=True shows detailed error pages that can reveal sensitive data, which attackers could exploit. This is why it must be off in production.