Answer-first summary for fast verification
Answer: Deploy the new version to a separate environment via Blue/Green Deployment, and then swap Route 53 records of the two environments to redirect traffic to the new version
Overall explanation Correct option: Deploy the new version to a separate environment via Blue/Green Deployment, and then swap Route 53 records of the two environments to redirect traffic to the new version With deployment policies such as 'All at once', AWS Elastic Beanstalk performs an in-place update when you update your application versions and your application can become unavailable to users for a short period of time. You can avoid this downtime by performing a blue/green deployment, where you deploy the new version to a separate environment, and then swap CNAMEs (via Route 53) of the two environments to redirect traffic to the new version instantly. In case of any deployment issues, the rollback process is very quick via swapping the URLs for the two environments.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A retail company operates its IT infrastructure on AWS Cloud using Elastic Beanstalk. The development team is preparing to release the next version of an application. Their primary concerns are to achieve minimal application downtime during the deployment process and to have the ability to quickly rollback to the previous version if the deployment encounters any issues.
As a Developer Associate, which of the following options would you recommend to the development team?
A
Deploy the new application version using 'Rolling' deployment policy
B
Deploy the new application version using 'All at once' deployment policy
C
Deploy the new application version using 'Rolling with additional batch' deployment policy
D
Deploy the new version to a separate environment via Blue/Green Deployment, and then swap Route 53 records of the two environments to redirect traffic to the new version