A global freight company maintains a Java order-tracking service in CodeCommit running on Amazon EC2 Auto Scaling behind an ALB. Leadership requires automated builds with unit tests on every commit, blue/green EC2 deployments with automatic rollback on CloudWatch alarms, and a single orchestrated pipeline view. Which CI/CD orchestration design meets these deployment pipeline requirements?
Select an answer to reveal the explanation.
Short Explanation
You've got all the players, you just need a conductor keeping everyone in time. CodePipeline ties source, build, and deploy together while blue/green swaps traffic safely and rolls back if alarms fire.
Full Explanation
The correct design is right because CodePipeline provides source-driven orchestration on every CodeCommit commit, CodeBuild supplies repeatable compile and unit-test execution, and CodeDeploy implements genuine EC2 blue/green by provisioning replacement instances behind the ALB and shifting traffic only after health validation while retaining automatic rollback tied to CloudWatch alarms, together delivering the single pipeline view leadership requires. The manual-approval variant fails on deployment safety automation because replacing alarm-driven rollback with human approval changes failure detection from continuous metric evaluation to operator intervention and violates the automatic rollback requirement even though build and blue/green mechanics are correct. The ECS Fargate variant fails on compute-platform matching because CodeDeploy deployment models, agents, AppSpec handling, and lifecycle hooks differ fundamentally between EC2 and ECS, so a Fargate service cannot host the existing EC2 Auto Scaling Java fleet behind its ALB target groups. The trigger-chained variant fails on orchestration because separate CodeCommit-triggered CodeBuild and CodeDeploy executions can automate steps but provide no unified execution history, artifact lineage, stage gating, or pipeline visualization. As an exam caveat, do not equate any blue/green traffic shift with the required EC2 blue/green, since Lambda canary, ECS linear, and EC2 blue/green use different CodeDeploy applications and deployment configurations. As a practical check, validate the pipeline source branch, CodeBuild buildspec test phase, CodeDeploy deployment group target group pair, ALB listener rules, and that the specified CloudWatch alarms are attached for automatic rollback before release.