DOP-C02 SDLC Automation 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.

• ✓

  Use AWS CodeDeploy with an ECS compute platform, configure a CloudWatch alarm for health checks, and enable automatic rollback.

  Why this is correct

  CodeDeploy with the ECS compute platform natively orchestrates blue/green deployments by shifting traffic between the original and replacement ECS task sets using a load balancer target group. You can associate CloudWatch alarms with the deployment and enable automatic rollback so that if health checks or custom metrics fail, CodeDeploy reverts traffic to the original task set without manual intervention. This is the only option that combines native ECS support, health monitoring, and automated rollback.

• ✗

  Use AWS CloudFormation with a custom resource to perform blue/green deployment.

  Why it's wrong here

  A CloudFormation custom resource would require you to author and maintain a Lambda function to orchestrate ECS service updates, target group registration, and traffic shifting, all of which CodeDeploy already provides. Moreover, CloudFormation rollback is triggered only by stack creation/update failures, not by post-deployment health checks, so you would need to build and manage your own rollback logic inside the custom resource. This adds significant complexity and operational risk compared to a managed deployment service.

• ✗

  Use AWS Elastic Beanstalk with blue/green environment swapping.

  Why it's wrong here

  Elastic Beanstalk is a platform-as-a-service offering for running web applications, not a control plane for ECS services; it does not deploy Docker containers to an Amazon ECS cluster as a first-class target. While Elastic Beanstalk supports blue/green environment swap, that swap swaps DNS CNAME records between Beanstalk environments and does not provide deployment-level health check rollback for ECS microservices. Therefore it is architecturally incompatible with the stated ECS pipeline requirement.

• ✗

  Use AWS CodePipeline with ECS deployment action and manual approval for rollback.

  Why it's wrong here

  The CodePipeline ECS deployment action can update your ECS service with a new task definition, but adding a manual approval step does not create any automatic rollback behavior; it simply pauses the pipeline for human approval before proceeding. If the deployment fails health checks, the pipeline has no built-in mechanism to revert traffic to the previous task set unless you manually re-run a prior pipeline stage or build separate rollback logic. Automatic rollback requires CodeDeploy's deployment groups and CloudWatch alarm integration, not a manual approval gate.

Go deeper

Related to this question