A fintech team stores microservice code in CodeCommit and must build Docker images, run security scans, and deploy progressively to ECS with manual approval for production. Build artifacts must be traceable across stages. Which CI/CD orchestration design automates build and deployment pipelines with governance?
Select an answer to reveal the explanation.
Short Explanation
You want traceable guardrails, not hero deploys, so CodePipeline ties it together. It chains builds, scans, approvals, and canary rollouts in one visible flow.
Full Explanation
CodePipeline orchestrates source, build, and deploy stages with artifacts passed between actions, CodeBuild compiles images and runs tests and scans, CodeDeploy performs ECS blue-green or canary deployments with automatic rollback, and manual approval actions enforce production governance. Manual CodeBuild runs lack orchestration, approvals, artifact traceability, and progressive deployment control, missing automation and governance needs. CodeDeploy is a deployment service and cannot natively build, test, or approve source from CodeCommit without a pipeline, and lifecycle hooks do not replace build stages. Lambda plus EventBridge can automate tasks but requires custom code for artifacts, approvals, and deployment strategies, losing managed pipeline visibility and safety. For the exam, remember Pipeline orchestrates, Build builds and tests, Deploy deploys progressively. In practice version artifacts in ECR and S3, require approvals, and add automated rollback alarms.