DOP-C02 Question 64
Single answerYou are managing an AWS environment for a company that uses a CI/CD pipeline to deploy applications to Amazon ECS. The deployment process needs to ensure zero downtime and rollback capabilities in case of failures. Which deployment strategy should you choose to meet these requirements?
- A
Rolling update
- B
Blue/green deployment
- C
All-at-once deployment
- D
Canary deployment
Show answer and explanation
Correct answer: B
Explanation
Blue/green deployment is the most suitable deployment strategy for achieving zero downtime and enabling rollback capabilities. It allows you to test the new version in isolation (green environment) and provides a seamless way to revert to the previous version (blue environment) if issues are detected.
- A. Incorrect.
Rolling updates incrementally replace tasks in the service with new ones. While this minimizes downtime, it doesn't inherently provide an easy rollback mechanism, making it less suitable for zero-downtime requirements.
- B. Correct.
Blue/green deployment creates a new environment (green) while the old environment (blue) continues serving traffic. After testing, traffic is switched to the green environment. This ensures zero downtime and provides an easy rollback option by switching traffic back to the blue environment if needed.
- C. Incorrect.
All-at-once deployment replaces all tasks in the service simultaneously. This is the fastest deployment method but results in downtime and lacks built-in rollback capabilities.
- D. Incorrect.
Canary deployment gradually shifts traffic to a new version, testing it with a subset of users before full rollout. While it minimizes risk, it doesn't inherently ensure zero downtime or provide a straightforward rollback mechanism compared to blue/green deployment.