SAP-C02 Question 152
Single answerA media company wants to deploy a new video streaming application across multiple AWS Regions to ensure low latency for its global user base. The company also requires zero downtime during deployments, the ability to roll back quickly in case of issues, and minimal manual intervention. Which deployment strategy should you recommend to meet these requirements?
- A
Use a rolling deployment strategy with Amazon EC2 Auto Scaling groups.
- B
Implement a blue/green deployment strategy using AWS Elastic Beanstalk.
- C
Use a canary deployment strategy with AWS Lambda and Amazon API Gateway.
- D
Set up a multi-region active-active architecture with manual deployments to each region.
Show answer and explanation
Correct answer: B
Explanation
The blue/green deployment strategy using AWS Elastic Beanstalk is the most appropriate solution because it allows for zero downtime by separating the production and staging environments. Traffic can be shifted seamlessly to the new version once testing is complete, and rollback is fast and straightforward. This approach also supports automation, ensuring minimal manual intervention. Other options do not fully meet the business requirements of zero downtime, global deployment, and quick rollback.
- A. Incorrect.
Rolling deployments update instances gradually, but they may cause downtime if an error occurs during the process. This strategy is less suitable for zero-downtime requirements and quick rollback.
- B. Correct.
A blue/green deployment strategy creates two separate environments: one for the current version and another for the new version. This approach ensures zero downtime, allows quick rollback by switching traffic back to the previous environment, and can be automated using AWS Elastic Beanstalk.
- C. Incorrect.
Canary deployments work well for serverless architectures, but they are more suited for testing small portions of traffic rather than achieving zero downtime for globally distributed applications.
- D. Incorrect.
A multi-region active-active architecture ensures high availability, but manual deployments to each region increase the risk of errors, downtime, and delays. This approach does not meet the requirements for automation and zero downtime.