Rollout strategies: free-recall review
Free-recall prompts across the rollout unit. Answer each from memory first, then reveal the model answer and compare.
Retrieval beats re-reading. For each prompt, say or write a full answer from memory before you open the model answer — the effort of recall is what makes the material stick.
Reconstruct the unit’s core mechanisms — the three tradeoff axes, maxSurge/maxUnavailable, why readiness gating is load-bearing, canary metric gates, and schema-safe rollback — without looking back at the lesson.
- 01Name the four rollout strategies and the three axes you trade between when choosing one.
- 02What do maxSurge and maxUnavailable control, what are their defaults, and what is the zero-downtime setting?
- 03Why is a readiness probe load-bearing during a rolling update, and how does it differ from a liveness probe?
- 04What makes canary lower-risk than blue-green, and what single thing must be in place for that benefit to be real?
- 05Why does blue-green's 'instant rollback' fail on a schema change, and how does expand-contract fix it?
- 06When is recreate the right choice despite its downtime, and why can't the other strategies substitute?
If you could reconstruct each answer from memory, you hold the unit’s spine: four shapes traded across blast radius, resource cost, and rollback speed; maxSurge/maxUnavailable plus a readiness probe for zero-downtime rolling; an automated metric gate (progressive delivery) for canary; expand-contract so rollback survives a schema change; and recreate reserved for workloads where versions cannot coexist. Observability is the lever that decides which strategy you can actually trust. Now when you see a rollout choice on a real service, you have the three-axis frame to reason it through — not just a name to recite.
Something unclear?
Ask a question about this lesson. Questions are anonymous and go straight to the author to make the lesson better.