A Retail Company Wants to Use AWS Elastic Beanstalk to Host

Multiple Choice

A retail company wants to use AWS Elastic Beanstalk to host its online sales website running on Java. Since this will be the production website, the CTO has the following requirements for the deployment strategy: Zero downtime. While the deployment is ongoing, the current Amazon EC2 instances in service should remain in service. No deployment or any other action should be performed on the EC2 instances because they serve production traffic. A new fleet of instances should be provisioned for deploying the new application version. Once the new application version is deployed successfully in the new fleet of instances, the new instances should be placed in service and the old ones should be removed. The rollback should be as easy as possible. If the new fleet of instances fail to deploy the new application version, they should be terminated and the current instances should continue serving traffic as normal. The resources within the environment (EC2 Auto Scaling group, Elastic Load Balancing, Elastic Beanstalk DNS CNAME) should remain the same and no DNS change should be made. Which deployment strategy will meet the requirements?

A) Use rolling deployments with a fixed amount of one instance at a time and set the healthy threshold to OK.
B) Use rolling deployments with additional batch with a fixed amount of one instance at a time and set the healthy threshold to OK.
C) launch a new environment and deploy the new application version there, then perform a CNAME swap between environments.
D) Use immutable environment updates to meet all the necessary requirements.