Exam AWS Certified Developer Associate topic 1 question 96 discussion

CE "Today's release adds a new policy—Traffic splitting. Traffic-splitting deployments let you perform canary testing as part of your application deployment. " beanstalk has canary https://docs.aws.amazon.com/elasticbeanstalk/latest/relnotes/release-2020-05-18-ts-deploy.html

I would go for BC. https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.rollingupdates.html

Canary - primarily to code changes and not infrastructure-level configuration updates like instance type changes.

CE is actually the correct ans. w/o any doubt!

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environments-updating.html. Clearly mentioned in we are doing environment changes like instance type.

For configuration changes, Rolling updates and Immutable updates are recommended to "prevent downtime during the update process". https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environments-updating.html

B+C E is incorrect, it uses for application deployment Change of instance type requires "Configuration changes" cannot simultaneously deploy an application and modify an instance Any configuration change is applied using Disabled, Rolling Based on Health, Rolling Based on Time or Immutable

CE because Elastic Beanstalk offers Traffic Splitting

Tricky one! I was for C and E but, looking at the documentation, the canary release doesn't exists for the Elastic Beanstalk. So the correct answer, in my opinion, is B (Rolling based on Health) and C (Immutable). (https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.deploy-existing-version.html) (https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.rollingupdates.html)

The deployment options that will meet these requirements are Rolling based on Health and Immutable. B and C

C is obvious. E because by Canary they mean traffic splitting

I go with C, E no matter what you do in Rolling, there is always a chance of partial outage. https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.rolling-version-deploy.html All at once – Deploy the new version to all instances simultaneously. All instances in your environment are out of service for a short time while the deployment occurs. Rolling – Deploy the new version in batches. Each batch is taken out of service during the deployment phase, reducing your environment's capacity by the number of instances in a batch. Rolling with additional batch – Deploy the new version in batches, but first launch a new batch of instances to ensure full capacity during the deployment process. Immutable – Deploy the new version to a fresh group of instances by performing an immutable update. Traffic splitting – Deploy the new version to a fresh group of instances and temporarily split incoming client traffic between the existing application version and the new one. - this means canary

Immutable + Canary testing (traffic splitting)

It shall be C and E

1st Canary and traffic splitting are not the same. EB offers traffic splitting. 2nd "minimize downtime" so using rolling updates is next best choice

Traffic Splitting is not Canary Canary by name is only offered in Lambda and API Gateway. This comes up often in TutorialDojo's practice exams.

BC https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.rolling-version-deploy.html#environments-cfg-rollingdeployments-method