How often should runbook tests be conducted to ensure readiness?

• A. Monthly
• B. Quarterly
• C. Annually
• D. Only after incidents

Answer: (B)

Regular runbook testing keeps incident response ready by confirming that the documented steps, automation, and escalation paths still line up with the current environment and team structure. Quarterly testing provides a practical cadence: it’s frequent enough to catch drift from software updates, new teammates, or changing dependencies, while not imposing excessive overhead.

Testing too rarely—like once a year—lets drift accumulate and muscle memory fade, making the runbook less reliable in a real incident. Waiting until after an incident is reactive and misses opportunities to refine procedures before they’re needed. In some high-risk contexts, more frequent tests might be appropriate, but quarterly is a solid default that balances readiness with practicality.