Blue/green deployment runs two environments — the current (blue) and the new (green) — and shifts traffic to green once it’s verified, so releases have near-zero downtime and instant rollback.
How AWS does it
Services like CodeDeploy, Elastic Beanstalk, ECS, and Lambda (with weighted aliases) support blue/green. If the new version misbehaves, you shift traffic back to blue instantly — far safer than an in-place update. The tell is “deploy with zero downtime and easy rollback.”
Test yourself
A team wants to release a new app version with zero downtime and the ability to roll back instantly if problems appear. Which deployment strategy?
- In-place deployment
- Blue/green deployment
- Manual deployment during a maintenance window
- Deleting and recreating the environment
👉 Click to reveal the answer & explanation
Correct answer: B. Blue/green runs the new version alongside the old and shifts traffic once verified, giving zero downtime and instant rollback. In-place (A) risks downtime and harder rollback; a maintenance window (C) means downtime; delete/recreate (D) is disruptive.
Related topics
AWS CodeDeploy · Route 53 routing policies · AWS Elastic Beanstalk
Ready to pass the AWS Solutions Architect Associate (SAA-C03)?
Stop guessing whether you’re ready. Our full-length, exam-realistic practice exams put you through the exact question style you’ll face — with a detailed explanation behind every answer, so you learn why, not just what.
- ✓ 6 full-length practice exams
- ✓ A detailed explanation for every single question
- ✓ Realistic, scenario-based questions — not memory dumps
- ✓ Lifetime access, kept current for 2026
Get the SAA-C03 Practice Exams →or try 25 free questions first