How to run production systems reliably, as Google's SRE books and common industry practice describe it: reliability targets and error budgets, alerting, incident response, postmortems, capacity, resilience patterns and chaos testing.
You’re reading a free preview. Sign up to see every topic and question — and to play this deck as games.
What SRE is, what counts as toil and why it is capped, and how an error budget turns a reliability target into a rule for when to ship.
39 total questions
Card #1
Site Reliability Engineering (SRE)
Card #2
Toil
Card #3
Engineering work (in SRE)
1. A service with a 99.9% SLO has spent its whole error budget by day 20 of the window. Under a typical error budget policy, what happens next?
2. Which of these tasks is NOT toil?
3. Which measurement best shows that an SRE team's automation work is paying off?
1. Google's SRE book describes SRE as what happens when you ask a software ___ to design an operations team.
Hint: a job title for someone who writes code
2. Meetings, hiring and training are counted as ___, not toil, because they are not tied to running the service.
Hint: general admin work
3. Google's SRE teams aim to keep toil below ___ percent of each engineer's time.
Hint: a round number
