Home › AWS Developer Associate › cloudcomputing › awsdevdeployment › Which Elastic Beanstalk deployment policy shifts…
Which Elastic Beanstalk deployment policy shifts traffic to new instances WHILE keeping the original environment running, so rollback is a DNS swap?
ARolling deployment in place
BBlue/green (or 'Swap Environment URLs') deployment
CDisabled deployment policy
DAll-at-once
Answer & Solution
Correct answer: B. Blue/green (or 'Swap Environment URLs') deployment
Blue/green creates a parallel environment, swaps the CNAME on success, and rolls back by un-swapping. Rolling deploys in place; all-at-once has no rollback safety net.
Related questions
Which strategy lets a serverless API safely deploy a new Lambda alias while keeping old clWhich AWS service lets developers store and version build artefacts and intermediate filesA Lambda function is deployed as a container image stored in ECR. Which change triggers LaWhich CloudFormation feature lets a developer reference an existing resource (e.g. an exisA team wants to deploy a Lambda update with the option to roll back automatically if a CloWhich AWS service automates Docker image builds and publishes them to a private container Which combination provides end-to-end CI/CD for an application stored in CodeCommit, builtWhich CodeDeploy deployment strategy for a Lambda alias shifts traffic from version V1 to