Part 6 of 6 · 2 min read
Exercises
Easy
Easy 1: Mitigate or fix (20 minutes)
Sort six actions into mitigation or root-cause fix: roll back, add an index, scale out, rewrite a query, switch off a flag, patch a library.
Done when: a six-row table.
Hint
Ask whether users stop being hurt right away.
Easy 2: Budget used (20 minutes)
A 30-day SLO of 99.9 percent. An outage of 22 minutes. Compute the share of budget used and say whether it needs a postmortem under a 10 percent rule.
Done when: one percentage and a decision.
Hint
0.1 percent of 43,200 minutes.
Easy 3: Rewrite a blaming sentence (20 minutes)
Rewrite "Sam deleted the wrong table" as a blameless finding with two system questions.
Done when: one sentence and two questions.
Hint
Ask what safeguard was missing.
Medium
Medium 1: Timeline (30 minutes)
Write a made-up timeline for a bad release, with at least seven timestamps from alert to close.
Done when: a timeline with detection, mitigation and recovery times.
Hint
Include acknowledgement and the rollback.
Medium 2: Update message (30 minutes)
Write two status updates for the same incident, 20 minutes apart, for support staff.
Done when: two short messages that each state impact, action and next update time.
Hint
Say what users see, not internal detail.
Medium 3: Chain of causes (30 minutes)
Use the GitHub case to list five contributing factors and a repair item for each.
Done when: a five-row table.
Hint
Think failover, counters, caches and permissions.
Hard
Hard 1: Full postmortem (45 minutes)
Write a postmortem for a made-up outage of a payment service, in the layout of section 3.
Done when: a one-page document with at least three repair items.
Hint
Put owners and dates on every repair item.
Hard 2: Design a game day (45 minutes)
Plan a game day for a three-service system: the failure, what teams should notice, what could go wrong, and how to stop it.
Done when: a plan with a stop condition.
Hint
Start with a small failure in a safe hour.
Hard 3: Incident policy (50 minutes)
Write a short policy: severity levels, who is paged, when roles are named, and when a postmortem is required, tied to error budget burn.
Done when: a policy of one page.
Hint
Use burn rate to set severity.