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
›
Sentry, error budgets, sampling
quiz
81 / 105
🇺🇸
EN
▼
↗
Share
⋯
More
+100 XP
📋
Task
📖
Theory
🤖
AI Help
Task
📝 **Question:** Why is traces_sample_rate=1.0 in production a bad default? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Quiz
Question
📝 **Question:** Why is traces_sample_rate=1.0 in production a bad default? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
A
Sentry rejects the SDK init — Sentry's ingest tier hard-caps traces_sample_rate at 0.5 and returns 429 on any envelope sent above that ceiling
B
Full trace sampling generates massive Sentry costs and floods dashboards with redundant traces
C
It creates a measurable per-request performance hit on the app — sampled span finalization adds ~15ms of synchronous serialization on every endpoint at the SDK layer
D
It is actually fine for production — Sentry's adaptive sampler down-samples server-side when ingest volume is high, so the requested 1.0 rate never reaches the dashboard intact
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…