Skip to main content
🔒 Preview mode. The first 15 Foundations lessons are free; this one is Pro. Start a 7-day trial to unlock the editor, AI hints and the rest of the curriculum. Card required, cancel any time in Dashboard.
Start 7-day trial →
⚡
← Courses
›
FastAPI Production
›
Module 6 · Real-World Patterns
›
Connection pools: sizing
quiz
94 / 105
🇺🇸
EN
▼
↗
Share
⋯
More
+100 XP
📋
Task
📖
Theory
🤖
AI Help
Task
📝 **Question:** 10 pods, Postgres max=200. Safe pool_size per pod? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Quiz
Question
📝 **Question:** 10 pods, Postgres max=200. Safe pool_size per pod? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
A
100 per pod — saturates the Postgres connection slot table on day one.
B
~15 (leaves headroom for admin/migrations); PgBouncer transaction-pooling beyond that.
C
Default 5 per pod — wastes capacity and starves request workers under load.
D
Disable the pool and open a fresh connection per request from the handler.
Submit answer
💬 Discussion
Be the first to ask a question or share a tip.
Sign in
to join the discussion. Reading is free.
Loading discussion…