SOA-C02 Question 143
Single answerYour organization is running a web application on Amazon ECS using the Fargate launch type. You need to deploy a new version of the application with minimal disruption to users while being able to quickly roll back if any issues occur. Which deployment strategy is best suited for this scenario?
- A
Blue/Green deployment using AWS CodeDeploy
- B
Rolling deployment with ECS service scheduler
- C
Canary deployment using AWS App Runner
- D
Recreate deployment by terminating old tasks and launching new ones
Show answer and explanation
Correct answer: A
Explanation
Blue/Green deployments are designed to reduce disruption by keeping the old version live while the new version is being tested. AWS CodeDeploy integrates with ECS to support blue/green deployments, ensuring traffic can be gradually shifted or instantly rolled back, making it ideal for minimizing downtime and mitigating risk during updates.
- A. Correct.
Blue/Green deployment using AWS CodeDeploy is the best option as it allows traffic to be shifted between the old and new versions, providing minimal downtime and enabling quick rollback in case of issues.
- B. Incorrect.
Rolling deployment is not ideal for this scenario as it replaces tasks incrementally, which can result in partial downtime and makes rollback more challenging if issues occur.
- C. Incorrect.
Canary deployment is not natively supported by ECS or CodeDeploy in this context, and AWS App Runner is not relevant for this ECS Fargate use case.
- D. Incorrect.
Recreate deployment involves terminating all old tasks and launching new ones, leading to downtime and is not suited for minimizing disruption.