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
›
Senior Deep-Dives
›
Module 4 · Memory + profiling · Recap
›
On-call: runbook is the contract
quiz
101 / 161
🇺🇸
EN
▼
↗
Share
⋯
More
+100 XP
📋
Task
📖
Theory
🤖
AI Help
Task
📝 **Question:** Alert with no runbook? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Quiz
Question
📝 **Question:** Alert with no runbook? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
A
Page anyway — on-call engineers should grow institutional knowledge by solving novel alerts under pressure.
B
Don't page. Either add the runbook or downgrade to a non-paging notification.
C
Page the author of the alert — git-blame the PagerDuty rule and route the page to whoever first added the threshold.
D
Escalate to the SRE team — they own the alert taxonomy and will write the runbook reactively during the incident.
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…