Answer-first summary for fast verification
Answer: Utilize AWS Elastic Beanstalk with a secondary staging environment for the CI/CD pipeline, deploying by swapping staging and production environment URLs.
The correct answer is B. Utilizing AWS Elastic Beanstalk with a secondary staging environment for the CI/CD pipeline allows for rapid deployment and quick rollback by simply swapping the staging and production environment URLs. This approach meets the requirements of allowing multiple releases per hour and ensuring quick rollbacks. Other options, such as using AMIs with EC2 instances or updating user data with AWS Systems Manager, do not provide as efficient a mechanism for frequent updates and quick rollbacks.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
A company is refactoring a monolithic application into a modern design and needs to upgrade its CI/CD pipeline on AWS to meet the following criteria: frequent releases (several times per hour) and rapid rollback capability. Which deployment strategy should they adopt?
A
Implement a CI/CD pipeline using AMIs for the application and its configurations, deploying by replacing EC2 instances.
B
Utilize AWS Elastic Beanstalk with a secondary staging environment for the CI/CD pipeline, deploying by swapping staging and production environment URLs.
C
Employ AWS Systems Manager to re-provision infrastructure for each deployment, updating EC2 user data to fetch the latest code from S3, and using Route 53 weighted routing to direct traffic to the new environment.
D
Deploy application updates through an Auto Scaling event with prebuilt AMIs, adding new instances with updated AMIs and gradually removing instances with the previous AMI version using a configured termination policy.
No comments yet.