Answer-first summary for fast verification
Answer: Elastic Beanstalk will replace the failed instances with instances running the application version from the most recent successful deployment
When processing a batch, Elastic Beanstalk detaches all instances in the batch from the load balancer, deploys the new application version, and then reattaches the instances. If you enable connection draining, Elastic Beanstalk drains existing connections from the Amazon EC2 instances in each batch before beginning the deployment. If a deployment fails after one or more batches completed successfully, the completed batches run the new version of your application while any pending batches continue to run the old version. You can identify the version running on the instances in your environment on the health page in the console. This page displays the deployment ID of the most recent deployment that was executed on each instance in your environment. If you terminate instances from the failed deployment, Elastic Beanstalk replaces them with instances running the application version from the most recent successful deployment. Incorrect options: Elastic Beanstalk will not replace the failed instances Elastic Beanstalk will replace the failed instances with instances running the application version from the oldest successful deployment Elastic Beanstalk will replace the failed instances after the application version to be installed is manually chosen from AWS Console These three options contradict the explanation provided above, so these options are incorrect.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
In an AWS Elastic Beanstalk environment, your development team is performing a Rolling deployment. During this process, the updated version was successfully deployed in only two batches, but the remaining batches failed to deploy. After the failed deployment, the development team decided to terminate the instances that were part of the failed batches.
What will be the status of these instances after they are terminated?
A
Elastic Beanstalk will not replace the failed instances
B
Elastic Beanstalk will replace the failed instances with instances running the application version from the most recent successful deployment
C
Elastic Beanstalk will replace the failed instances after the application version to be installed is manually chosen from AWS Console
D
Elastic Beanstalk will replace the failed instances with instances running the application version from the oldest successful deployment