Part 7 of 7 · 2 min read
Exercises
Easy
Easy 1: Order the stages (20 minutes)
Put in order: build, review, canary, pre-production, full rollout. Say what each checks.
Done when: an ordered list with one line each.
Hint
Cheap tests early, expensive ones later.
Easy 2: Canary or blue-green (20 minutes)
Choose one for each case and say why: a payment service with heavy state, a stateless web page, a recommendation algorithm.
Done when: three choices with reasons.
Hint
Think about idle capacity and traffic routing.
Easy 3: Spot the unsafe change (20 minutes)
Which of these cannot be rolled back safely: add an optional field, rename a database column in place, change a message format. Explain.
Done when: a classification with a reason each.
Hint
Ask whether the old version can read the new data.
Medium
Medium 1: A rollout plan (30 minutes)
Plan a release to 120 instances in 3 regions. Give stages, percentages, bake times and the signals checked.
Done when: a table of stages with a stop rule.
Hint
Start with the smallest region.
Medium 2: Three-step change (30 minutes)
A service stores a date as text "12/05/2026" and must switch to ISO "2026-05-12". Write the prepare, activate and cleanup steps.
Done when: three steps, each safe to roll back.
Hint
The reader must accept both formats first.
Medium 3: Capacity during rollout (30 minutes)
A fleet of 20 instances runs at 70 percent load. The rollout takes 4 down at a time. Compute the load on the rest and say if it is safe.
Done when: one number and a decision.
Hint
Divide the same load by 16 instead of 20.
Hard
Hard 1: Design a pipeline (45 minutes)
Draw the pipeline for a service with a database. Show tests, environments, health signals, bake times and who is paged.
Done when: a labelled diagram.
Hint
Every arrow needs a check.
Hard 2: Flag lifecycle (45 minutes)
Write a policy for feature flags: creation, rollout, review, and removal. Say how SLO burn rate gates each step.
Done when: a one-page policy with measurable rules.
Hint
Put an owner and a date on every flag.
Hard 3: Post-release failure (50 minutes)
A release passed every stage and failed at peak hour on Friday. List what bake time, health signals and rollout steps would you change, and why.
Done when: a list of five changes tied to the cause.
Hint
Peak-only issues need a bake that covers peak.