AWS Certified Developer – Associate (DVA-C02)DeploymentEasy
A development team is deploying a new version of their web application to Amazon EC2 instances. They want to ensure that the new application version is rolled out gradually to a small subset of instances first, and if no issues are detected, it is then deployed to the remaining instances. Which AWS CodeDeploy deployment type should they choose to achieve this strategy?
- ALinear
- BCanary
- CAll-at-once
- DBlue/Green
Show answer & explanationAnswer & explanation
Correct answer: A. Linear
The Linear deployment type in AWS CodeDeploy allows you to roll out new application versions in increments, such as 10% every 5 minutes, which fits the requirement of a gradual rollout to a small subset first and then to the rest if no issues are detected.
Why the other options are wrong
- B. Canary deployment routes a small percentage of traffic to the new version before shifting all traffic, primarily for serverless or ECS, not directly for EC2 instance-based gradual rollout.
- C. All-at-once deploys to all instances simultaneously, which does not meet the gradual rollout requirement.
- D. Blue/Green deployment creates a completely new environment and swaps traffic, which is different from a gradual rollout to existing instances.
CodeDeploy Linear Deployment
A CodeDeploy deployment type that rolls out new application versions in equal increments (e.g., 10% every 5 minutes) to EC2 instances, allowing for a controlled, gradual release.
- Deploys to EC2/on-premises instances.
- Rolls out in equal increments over a specified time.
- Allows for monitoring between increments.
Memory trick: CODE-PLOY: Choose Only Deployments, Look Over Your Progress.