Jeff’s Note #
Unlike generic exam dumps, ADH analyzes this scenario through the lens of a Real-World Lead Developer.
For DVA-C02 candidates, the confusion often lies in choosing the right CodeDeploy traffic shifting configuration for containerized ECS deployments. In production, this is about knowing exactly how predefined deployment configurations control traffic routing and the timing nuances to enable safe releases with minimal user impact. Let’s drill down.
The Certification Drill (Simulated Question) #
Scenario #
A software development startup named CloudStream Solutions is preparing to deploy a new version of their microservices application running on Amazon Elastic Container Service (ECS). To minimize risk and ensure stability, the DevOps team wants to gradually shift live user traffic. Initially, only 10% of the live traffic should be routed to the new application version. After a 15-minute observation period with no issues, the deployment should complete by routing 100% of the live traffic to the new version.
The Requirement: #
Identify which AWS CodeDeploy predefined deployment configuration meets these gradual traffic shifting and timing criteria for ECS applications.
The Options #
- A) CodeDeployDefault.ECSCanary10Percent15Minutes
- B) CodeDeployDefault.LambdaCanary10Percent5Minutes
- C) CodeDeployDefault.LambdaCanary10Percent15Minutes
- D) CodeDeployDefault.ECSLinear10PercentEvery1Minutes
Google adsense #
leave a comment:
Correct Answer #
A) CodeDeployDefault.ECSCanary10Percent15Minutes
Quick Insight: The Developer Imperative #
When deploying containerized applications on ECS using CodeDeploy, the predefined ECSCanary configurations provide both logical correctness and minimum downtime.
LambdaCanary options, although similarly named, apply only to Lambda deployments and are incompatible with ECS services.
Linear deployments proceed in small increments over a fixed interval, but do not offer an initial 10% canary followed by a wait period.
Content Locked: The Expert Analysis #
You’ve identified the answer. But do you know the implementation details that separate a Junior from a Senior?
The Expert’s Analysis #
Correct Answer #
Option A: CodeDeployDefault.ECSCanary10Percent15Minutes
The Winning Logic #
This predefined CodeDeploy configuration is explicitly designed for Amazon ECS blue/green deployments. It shifts 10% of live traffic immediately to the new container version as a canary, waits for 15 minutes to verify health and performance, and then shifts the remaining 90% traffic to complete the deployment. This meets the exact timing and traffic exposure requirements in the scenario.
- For ECS deployments using CodeDeploy, canary deployments provide controlled gradual rollouts with built-in validation windows.
- The “10Percent15Minutes” suffix defines the percentage and the wait duration between traffic increments.
- This configuration optimizes risk mitigation by allowing a quick rollback if errors appear during the canary period.
The Trap (Distractor Analysis): #
- Option B & C (LambdaCanary configurations): These are only for AWS Lambda functions. Lambda and ECS use different deployment mechanisms under CodeDeploy, so these would not work with an ECS service.
- Option D (ECSLinear10PercentEvery1Minutes): This splits traffic evenly in increments every 1 minute, e.g., 10% every minute until fully shifted. It doesn’t wait 15 minutes after the initial 10%, which violates the timing requirement.
The Technical Blueprint #
# Example AWS CLI snippet to start a deployment using the correct config:
aws deploy create-deployment \
--application-name my-ecs-app \
--deployment-config-name CodeDeployDefault.ECSCanary10Percent15Minutes \
--deployment-group-name my-ecs-deployment-group \
--github-location repository=repo-name,commitId=commit-sha
The Comparative Analysis #
| Option | API/Config Target | Deployment Type | Traffic Shift Pattern | Wait Time | Use Case |
|---|---|---|---|---|---|
| A | ECS | Canary | 10% initially, then 100% at 15m | 15 minutes | ECS gradual deployment + pause |
| B | Lambda | Canary | 10% initially, then 100% at 5m | 5 minutes | Lambda function deployments |
| C | Lambda | Canary | 10% initially, then 100% at 15m | 15 minutes | Lambda function deployments |
| D | ECS | Linear | 10% traffic every 1 minute | No pause | ECS incremental rollout |
Real-World Application (Practitioner Insight) #
Exam Rule #
For the exam, always pick ECSCanary configurations when you see ECS applications requiring traffic shifting with specified wait times.
Real World #
In production, teams sometimes use linear deployments for smoother, more continuous traffic shifts instead of canary—especially when the tolerance for risk is lower or automated monitoring systems detect anomalies more rapidly.
(CTA) Stop Guessing, Start Mastering #
Disclaimer
This is a study note based on simulated scenarios for the AWS DVA-C02 exam.