SAP-C02 Question 390
Single answerYou are designing a CI/CD pipeline for a microservices-based application deployed on an Amazon ECS cluster. The application must have zero downtime during deployments, and you need to ensure that any issues with the new version can be rolled back quickly. Which deployment strategy should you use in this scenario?
- A
Blue/Green deployment using AWS CodeDeploy
- B
Rolling deployment using AWS CodeDeploy
- C
All-at-once deployment using AWS CodePipeline
- D
Canary deployment using AWS CodeDeploy
Show answer and explanation
Correct answer: A
Explanation
Blue/Green deployment is ideal for scenarios where zero downtime and quick rollback are critical. By creating a completely separate environment for the new version, it allows extensive testing and validation before shifting traffic to the updated version. This ensures that if any issues are detected, you can easily revert to the previous version without impacting users or service availability.
- A. Correct.
Blue/Green deployment using AWS CodeDeploy is the best choice for zero downtime and quick rollback. It creates a new environment for the updated version, and traffic can be shifted to the new environment only when it is fully validated.
- B. Incorrect.
Rolling deployment updates the application incrementally across instances, but it does not guarantee zero downtime and can make rollback slower since a portion of the fleet may already be running the new version.
- C. Incorrect.
All-at-once deployment updates all instances simultaneously, which can lead to downtime if the deployment fails and does not support a smooth rollback process.
- D. Incorrect.
Canary deployment introduces the new version to a small subset of users before rolling it out more widely, but it does not inherently guarantee zero downtime and requires careful monitoring to determine when to proceed or rollback.