AWS Certified Solutions Architect Professional SAP-C02 Practice Question

AWS CodeDeploy's blue/green deployment type for Amazon ECS provides predefined canary configurations (such as CodeDeployDefault.ECSCanary10Percent5Minutes) that shift 10 percent of traffic to a replacement task set for 5 minutes and then route the remainder if no alarms fire. A CloudWatch alarm for the ALB's HTTP 5xx metric can be attached to the deployment group, and automatic rollback can be enabled so that CodeDeploy restores the last known-good task set when the alarm enters the ALARM state. The Deploy action in AWS CodePipeline natively supports invoking CodeDeploy, so no custom orchestration or third-party tooling is required.

ECS rolling updates with the deployment circuit breaker can roll back unhealthy deployments, but they control task replacement, not percentage-based traffic shifting, so the 10 percent canary requirement is not guaranteed. Elastic Beanstalk immutable updates deploy an entirely new environment and only route traffic after health checks pass; they do not provide a 10 percent traffic canary. A Step Functions-based DNS weight-shifting solution could meet the functional goals, but it introduces additional services and custom logic, violating the requirement to avoid extra orchestration.