Correct answer - "blue/green" : As AWS Elastic Beanstalk performs an in-place update when you
update your application versions, 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 of the two environments
to redirect traffic to the new version at what ever point you want the traffic to be completely
redirected to the new environment. See here:
Incorrect:
"rolling" - Some instances serve requests with the old version of the application, while
instances in completed batches serve other requests with the new version
"immutable" - Launches a full set of new instances running the new version of the application in
a separate Auto Scaling group, alongside the instances running the old version
"all at once" - All instances in your environment are out of service for a short time while the
deployment occurs
"rolling with additional batches" - Deploy the new version in batches, but first launch a new
batch of instances to ensure full capacity during the deployment process
For more information visit