Only 5% of citizens should see the new UI first while metrics are watched before a wider rollout. Which deployment strategy matches this plan?
Select an answer to reveal the explanation.
Short Explanation
Canary is the "try it on a few birds before the whole flock" approach. Five percent of citizens get the new UI while you watch error rates and latency — if it sings, you widen the slice. That small-subset exposure is canary, not an all-at-once blue-green flip.
Full Explanation
A canary release routes a limited percentage of users or traffic to the new version while the majority remains on the stable build, enabling observation of real metrics before broader rollout. Instant 100% environment swaps describe blue-green; overnight host-wide binary replacement is in-place; retiring the old system without progressive validation is a risky big-bang cutover.