A citizen-facing fee API must cut over with minimal downtime and a quick path back if errors spike. The team is choosing among blue/green, canary, and rolling for the next release. Which selection best matches a risk profile that needs an instant cutover with an idle prior environment ready?
Select an answer to reveal the explanation.
Short Explanation
Blue/green is the spare runway: stand up the new strip, land traffic there, and keep the old strip warm if you need to bounce back. Rolling chews through instances in place; canary sips traffic first. For "flip hard, undo fast," blue/green is the civic API's friend.
Full Explanation
Blue/green deployments provision a new environment (green), validate it, then shift traffic from blue while retaining the prior environment for rapid rollback. Canary gradually shifts a percentage of traffic to limit blast radius before full promotion. Rolling replaces capacity in batches on the existing fleet and does not inherently keep a full idle prior environment for an instant environment-level cutover. Matching strategy to risk profile is a core DVA-C02 deployment skill.