What information should a typical FOSSE runbook contain?

• A. Only steps
• B. Purpose, scope, prerequisites, step-by-step procedures, rollback steps, validation checks, contacts, and post-incident steps
• C. Only contacts
• D. Only rollback steps

Answer: (B)

The main idea tested is that a runbook should be a complete, ready-to-use guide that covers not just how to perform an operation, but when, why, and what to expect throughout the process. A typical FOSSE runbook includes several essential elements that together ensure actions are safe, repeatable, and auditable.

It should state the purpose and scope so anyone knows when this runbook applies and what it covers. Prerequisites list the necessary conditions, tools, access, and environment readiness before starting. The step-by-step procedures provide the exact actions in the correct order. Rollback steps describe how to undo changes if something goes wrong, offering a safe exit path. Validation checks define how to confirm the operation succeeded and what success looks like. Contacts identify who to notify or escalate to for coordination and support. Post-incident steps outline what to do after the operation, such as documentation updates, metric collection, and lessons learned.

This combination is crucial because runbooks in a FOSSE environment must be actionable, safe, and auditable. Focusing only on steps misses the safety nets and context (prerequisites, rollback, validation) that protect systems. Focusing only on contacts or rollback steps misses the actual procedures and verification needed to complete the task.