Ultimate access to all questions.
As an AWS Certified Developer Associate, you are tasked with creating an AWS Elastic Beanstalk environment to manage the deployment of a high-traffic, high-availability application. Your goal is to deploy a new version of the application using Elastic Beanstalk while ensuring that both performance and availability remain unaffected. Additionally, you need to maintain cost-effectiveness throughout the process.
What is the MOST optimal way to achieve this deployment while keeping costs in check?
Explanation:
Correct option:
AWS Elastic Beanstalk offers several deployment policies and settings. Choosing the right deployment policy for your application is a tradeoff based on a few considerations and depends on your business needs.
Deploy using 'Rolling with additional batch' deployment policy - With this method, Elastic Beanstalk launches an extra batch of instances, then performs a rolling deployment. Launching the extra batch takes time, and ensures that the same bandwidth is retained throughout the deployment. This policy also avoids any reduced availability, although at a cost of an even longer deployment time compared to the Rolling method. Finally, this option is suitable if you must maintain the same bandwidth throughout the deployment.