DOP-C02 Question 111
Single answerYou are managing a CI/CD pipeline for a high-traffic e-commerce application hosted on AWS. The application uses Amazon ECS with Fargate for container orchestration. The development team wants to implement a deployment strategy that minimizes downtime and ensures that new deployments can be rolled back quickly if issues are detected. Which deployment strategy should you choose?
- A
Blue/Green deployment using AWS CodeDeploy
- B
Rolling update using ECS service scheduler
- C
All-at-once update using ECS service scheduler
- D
Recreate deployment strategy using AWS CloudFormation
Show answer and explanation
Correct answer: A
Explanation
The Blue/Green deployment strategy using AWS CodeDeploy is the most appropriate option for minimizing downtime and ensuring quick rollback capabilities. It allows the new version (green) to be tested in parallel with the existing version (blue) before traffic is fully shifted, ensuring the high-traffic e-commerce application remains available and stable during deployments.
- A. Correct.
Blue/Green deployment using AWS CodeDeploy is the best choice here as it minimizes downtime by running two separate environments (blue and green) and allows traffic to be shifted gradually or instantly. This also makes rollback quick and easy if any issues are detected.
- B. Incorrect.
Rolling update using ECS service scheduler updates tasks in batches but can still cause partial downtime and does not provide as straightforward a rollback mechanism as Blue/Green deployments.
- C. Incorrect.
All-at-once update using ECS service scheduler replaces all tasks at once, leading to downtime and no easy rollback mechanism, which is unsuitable for high-traffic applications.
- D. Incorrect.
Recreate deployment strategy using AWS CloudFormation deletes the existing resources before creating the updated ones, which causes significant downtime and is not ideal for minimizing impact.