AZ400-Q: keep runbooks current
A deployment runbook often differs from the pipeline. How should it be maintained?
- A) Store it only in one engineer’s notebook.
- B) Version it with the service and review documentation changes through pull requests. ✓
- C) Update it annually after incidents.
- D) Generate it from production logs with no review. Answer: B. Docs-as-code makes changes reviewable and close to the implementation. Why not the others: Private, delayed, or unreviewed documentation drifts.