Gunicorn quiz

Test your Gunicorn knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.

How does Gunicorn typically fit into a common production deployment stack alongside Nginx?

1. How does Gunicorn typically fit into a common production deployment stack alongside Nginx?
2. How does Gunicorn typically pick up code changes after a deployment, in terms of worker restarts?
3. Why can't Python's built-in development server (e.g. Flask's `app.run()`) typically be used directly in production?
4. Why is having Nginx (or another reverse proxy) buffer slow client connections in front of Gunicorn's sync workers considered good practice?
5. What role does Gunicorn's master process play in this architecture?
6. How does Gunicorn typically handle logging of access and error information?
7. What is the purpose of Gunicorn's worker timeout setting (`--timeout`)?
8. What does it mean for Gunicorn to be described as "unopinionated" about the choice of web framework it runs?
9. Why does Gunicorn's documentation commonly recommend a rule of thumb like `(2 x $num_cores) + 1` for the number of sync workers?
10. What is the key limitation of Gunicorn's default "sync" worker class regarding concurrent requests within a single worker?
11. What is a common alternative WSGI server to Gunicorn in the Python ecosystem, and how do they broadly compare?
12. What does Gunicorn's `--max-requests` setting do, and why might a team configure it?

More quizzes