DOP-C02 Blue/Green Deployment Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  CodeDeployDefault.ECSAllAtOnce

  Why it's wrong here

  CodeDeployDefault.ECSAllAtOnce is the deployment configuration that shifts 100% of traffic from the blue task set to the green task set immediately when the deployment reaches the traffic-shifting step. It provides no canary staging and no 5-minute observation window, so any latent issue in the new task set would immediately impact the entire production workload instead of just a 10% subset. This directly contradicts the requirement for a staged 10%-then-90% traffic shift.

• ✗

  CodeDeployDefault.ECSLinear10PercentEvery1Minutes

  Why it's wrong here

  CodeDeployDefault.ECSLinear10PercentEvery1Minutes shifts traffic in successive 10% increments every minute, with no holding period at 10%. Specifically, after 1 minute 10% of traffic is on green, after 2 minutes 20%, and by the 5th minute 50% would already be shifted. This fails the requirement because it does not wait 5 minutes at the 10% level; instead, it moves continuously toward 100% over a 10-minute period.

• ✓

  CodeDeployDefault.ECSCanary10Percent5Minutes

  Why this is correct

  The built-in deployment configuration CodeDeployDefault.ECSCanary10Percent5Minutes instructs CodeDeploy to initially route 10% of the load balancer's traffic to the new ECS task set (the green environment) while the remaining 90% continues to go to the blue task set. After a 5-minute waiting period, during which health checks and metrics can be evaluated, CodeDeploy automatically shifts the remaining 90% of traffic to green, completing the deployment. This two-step canary pattern exactly satisfies the requirement for a 10% initial shift with a 5-minute soak before the final 90% cutover.

• ✗

  Custom configuration with 10% initial traffic and 100% after 5-minute interval

  Why it's wrong here

  Although a custom traffic-shifting configuration with a 10% initial traffic and 100% after a 5-minute interval could be built in CodeDeploy's deployment configuration editor, it is unnecessary because CodeDeployDefault.ECSCanary10Percent5Minutes already provides this exact managed behavior. Using a custom configuration adds operational overhead: you must manually create and maintain the configuration, and doing so provides no functional advantage over the built-in canary policy. The requirement does not demand any customized behavior, so the predefined configuration is the correct and simplest choice.

Go deeper

Related to this question