Uvicorn quiz

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

Why might a production deployment run multiple Uvicorn worker processes rather than a single one?

1. Why might a production deployment run multiple Uvicorn worker processes rather than a single one?
2. What is Uvicorn?
3. Why would enabling Uvicorn's access logging be useful in production, and what is a common reason to disable or reduce it under very high load?
4. What is a common command to run a FastAPI app in development using Uvicorn?
5. What does the `--workers` flag do when running Uvicorn directly (without a separate process manager like Gunicorn)?
6. What does Uvicorn's `--reload` flag do, and why is it typically only used in development?
7. What does it mean that Uvicorn is described in its own documentation as a "server," not a full web framework?
8. What role does Python's `asyncio` play underneath Uvicorn's request handling?
9. Why does FastAPI documentation commonly recommend running a FastAPI app with Uvicorn?
10. What does Uvicorn's support for HTTP/1.1 and WebSockets specifically enable that a plain WSGI server generally cannot handle natively?
11. Why is a single Uvicorn worker (using asyncio's cooperative concurrency) potentially problematic for a handler that performs a long, blocking, synchronous CPU-bound operation?
12. What is a practical reason a team might choose Uvicorn specifically over Gunicorn's default sync workers for a new Python API service?

More quizzes