You have a development team that is continuously spending a lot of time rolling back updates for an application. If the software change fails, they spend more than 5-6h in rolling back the update. Which of the below options is the best to reduce the time for rolling back application versions?

Answer options:

A.Use Elastic Beanstalk and re-deploy using Application Versions.
B.Use S3 to store each version and then re-deploy with Elastic Beanstalk.
C.Use CloudFormation and update the stack with the previous template.
D.Configure an AutoScalingRollingUpdate policy for the Auto Scaling group in OpsWorks.

Answer – A
Option B is incorrect because Elastic Beanstalk already has the facility to manage various versions. You don’t need to use S3 separately for this.
Option C is incorrect because in Cloudformation you will need to maintain the versions. Elastic Beanstalk can do that automatically for you.
Option D is incorrect because the AutoScalingRollingUpdate policy is used in the CloudFormation template to specify the rolling updates for an ASG. The policy is not for OpsWorks.
AWS Beanstalk is the perfect solution for developers to maintain application versions.
With AWS Elastic Beanstalk, you can quickly deploy and manage applications in the AWS Cloud without worrying about the infrastructure that runs those applications. AWS Elastic Beanstalk reduces management complexity without restricting choice or control. You upload your application, and AWS Elastic Beanstalk automatically handles the details of capacity provisioning, load balancing, scaling, and application health monitoring.
For more information on AWS Beanstalk, please refer to the below link:
https://aws.amazon.com/documentation/elastic-beanstalk/