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 5 · Production Deployment & Observability
›
Health probes — shallow vs deep
quiz
83 / 105
🇺🇸
EN
▼
↗
Share
⋯
More
+100 XP
📋
Task
📖
Theory
🤖
AI Help
Task
📝 **Question:** Why must liveness be a shallow check? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Quiz
Question
📝 **Question:** Why must liveness be a shallow check? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
A
Performance only — every liveness probe runs on the request thread, so deep checks add measurable latency to every nearby user-facing call inside the same pod
B
If liveness checks the DB, any transient DB problem kills every pod in the deployment, and the cold-start storm during restart further hammers the DB
C
Kubernetes requires it — the kubelet enforces a 1-second timeout on `livenessProbe` and any deep check that touches a network dependency will fail the spec validation step
D
Deep liveness checks are slower than readiness checks — kubelet polls liveness every 200ms by default and any query against Postgres exceeds the strict per-probe budget
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…