Practice runbook vocabulary: prerequisites sections, numbered procedures, decision trees, review dates, and runbook accuracy testing.
0 / 5 completed
1 / 5
A runbook template starts with 'a prerequisites section.' What should this section contain?
The prerequisites section prevents the on-call engineer from getting halfway through a runbook and discovering they lack access or a required tool. It lists everything needed upfront: permissions, CLI tools, environment setup, and pre-conditions — saving critical time during incidents.
2 / 5
Your runbook uses 'numbered steps for the procedure.' Why is numbered formatting important?
During incidents, engineers are under pressure and may be handling multiple communications. Numbered steps provide clear position tracking ('done through step 5'), enable handoff between engineers ('pick up from step 8'), and reduce the cognitive load of tracking where you are in the procedure.
3 / 5
An advanced runbook includes 'a decision tree that guides the on-call engineer.' When is a decision tree more useful than a linear list of steps?
Decision trees shine when the procedure diverges based on observed conditions. A linear runbook handles this awkwardly with 'if/else' prose; a visual or structured decision tree makes the branching obvious, reduces errors, and is faster to follow under pressure.
4 / 5
A runbook header says 'Last reviewed: 2024-01-15.' Why does the review date matter?
Runbooks that are never reviewed become dangerous — systems change, services are renamed or retired, credentials expire, and procedures evolve. The review date helps the on-call engineer assess how much to trust the runbook and flags runbooks that need updating. Many teams require quarterly reviews.
5 / 5
Your team says 'The runbook test verifies the steps are accurate.' What does runbook testing involve?
Runbook testing (often done during game days or scheduled drills) involves actually executing the procedure to verify it works. This finds stale commands, missing environment setup, incorrect API endpoints, and confusing wording — ensuring the runbook is reliable before it's needed under pressure.