WhiteNoise for static files in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

How does WhiteNoise serve static files in Django?

When using WhiteNoise in a Django project, what is the main way it serves static files?

A It serves static files directly from the Django development server without needing a separate web server.

B It requires configuring Nginx or Apache to serve static files separately.

C It uploads static files to a cloud storage service automatically.

D It disables static file serving and expects the browser to cache files permanently.

💡 Hint

Think about how WhiteNoise simplifies static file serving in production.

WhiteNoise allows Django to serve static files directly, even in production, without needing a separate web server like Nginx. This simplifies deployment.

📝 Syntax

intermediate

Correct way to add WhiteNoise middleware in Django settings

Which option shows the correct way to add WhiteNoise middleware in the Django MIDDLEWARE list?

A WhiteNoise middleware should be added inside INSTALLED_APPS, not MIDDLEWARE.

B 'whitenoise.middleware.WhiteNoiseMiddleware' should be added at the bottom of the MIDDLEWARE list.

C 'whitenoise.middleware.WhiteNoiseMiddleware' should be added at the top of the MIDDLEWARE list.

D 'django.middleware.security.SecurityMiddleware' should be replaced by 'whitenoise.middleware.WhiteNoiseMiddleware'.

💡 Hint

Middleware order matters for WhiteNoise to work properly.

WhiteNoise middleware must be placed near the top of the MIDDLEWARE list, usually right after SecurityMiddleware, to serve static files correctly.

🔧 Debug

advanced

Why are static files not served with WhiteNoise in production?

Given this Django production setup with WhiteNoise configured, static files are not loading. What is the most likely cause?

Django

MIDDLEWARE = [
    'django.middleware.security.SecurityMiddleware',
    'whitenoise.middleware.WhiteNoiseMiddleware',
    # other middleware
]

STATIC_ROOT = '/var/www/static/'

# collectstatic has been run

# DEBUG = False

A WhiteNoise middleware is placed after SecurityMiddleware, which is incorrect.

B STATICFILES_STORAGE is not set to 'whitenoise.storage.CompressedManifestStaticFilesStorage'.

C DEBUG is set to True, so WhiteNoise does not serve static files.

D STATIC_ROOT is missing trailing slash, causing path errors.

💡 Hint

Check if static files are compressed and cached properly in production.

In production, WhiteNoise requires STATICFILES_STORAGE to be set to 'whitenoise.storage.CompressedManifestStaticFilesStorage' to serve compressed and versioned static files correctly.

❓ state_output

advanced

What happens when you run collectstatic with WhiteNoise?

After configuring WhiteNoise and running 'python manage.py collectstatic', what is the expected state of the static files?

A Static files are copied to STATIC_ROOT with compressed and hashed filenames for caching.

B Static files remain in their original app directories without changes.

C Static files are uploaded to a CDN automatically.

D Static files are deleted from the project to save space.

💡 Hint

Think about how WhiteNoise helps with caching static files.

WhiteNoise works with Django's collectstatic to copy static files into STATIC_ROOT, adding hashes to filenames for cache busting and compressing files for faster delivery.

🧠 Conceptual

expert

Why choose WhiteNoise over a separate static file server?

What is the main advantage of using WhiteNoise to serve static files in a Django app compared to using a separate web server like Nginx?

A It automatically scales static file serving across multiple servers without extra setup.

B It encrypts static files during transfer for better security.

C It improves static file delivery speed beyond what Nginx can provide.

D It simplifies deployment by removing the need to configure and maintain a separate static file server.

💡 Hint

Think about deployment complexity and maintenance.

WhiteNoise allows Django apps to serve static files directly, reducing deployment complexity by avoiding separate static file server setup and maintenance.