SAP-C02 Question 386
Single answerA company is using AWS CodePipeline to deploy a web application hosted on Amazon ECS. They want to minimize downtime during deployments and ensure a quick rollback in case of issues. Which deployment strategy should they use in this scenario?
- A
All-at-once deployment
- B
Rolling deployment
- C
Blue/green deployment
- D
Canary deployment
Show answer and explanation
Correct answer: C
Explanation
Blue/green deployment is the best choice for this scenario as it minimizes downtime by creating a parallel environment for the new version and allows quick rollback by switching traffic back to the previous environment if needed. This deployment strategy is highly suitable for applications requiring high availability and minimal disruption during updates.
- A. Incorrect.
All-at-once deployment replaces all instances simultaneously, leading to potential downtime and no easy rollback mechanism. This does not meet the requirements to minimize downtime and ensure quick rollback.
- B. Incorrect.
Rolling deployment updates instances in batches. While it minimizes downtime, rolling back to the previous version can be complex and slower compared to blue/green deployments.
- C. Correct.
Blue/green deployment creates a separate environment (blue) for the new version while keeping the old version (green) intact. Traffic can be shifted to the new environment with minimal downtime, and rollback is quick as traffic can be reverted to the old environment.
- D. Incorrect.
Canary deployment shifts traffic incrementally to the new version to test it with a small percentage of users before full rollout. While it minimizes risk, it does not prioritize quick rollback as effectively as blue/green deployments.