AWS Certified Developer – Associate (DVA-C02)DeploymentEasy
A development team uses AWS CodePipeline to automate deployments. They have multiple stages, including Build, Test, and Production Deployment. They need to ensure that an approval step is required before deploying to the Production stage. How can this be configured in AWS CodePipeline?
- ASet up an Amazon SNS topic for approval notifications in the Test stage.
- BConfigure an AWS Lambda function to trigger approval in the Build stage.
- CInsert a manual approval action as the first action in the Production Deployment stage.
- DAdd a manual approval action in the source stage.
Show answer & explanationAnswer & explanation
Correct answer: C. Insert a manual approval action as the first action in the Production Deployment stage.
AWS CodePipeline allows you to add a manual approval action to any stage. To gate deployments to production, the manual approval action should be placed as the first action within the Production Deployment stage, ensuring human review before any production resources are modified.
Why the other options are wrong
- A. An SNS topic can be used for notifications, but it's not the mechanism for enforcing a mandatory approval step itself. The manual approval action uses SNS for notifications.
- B. While Lambda can be used for custom approvals, CodePipeline has a built-in manual approval action for this exact purpose, making it simpler and more direct.
- D. Approval in the source stage would halt the entire pipeline too early, before any builds or tests run.
CodePipeline Manual Approval
A CodePipeline action type that pauses the pipeline execution at a specific stage until a user manually approves or rejects the action.
- Pauses pipeline execution.
- Can be configured with SNS for notifications.
- Requires a user to approve or reject for the pipeline to proceed.
Memory trick: Approval action, at the stage, before deployment's rage.