DVA-C02 · Question #786
A company uses AWS CodePipeline to create a fully automated continuous integration and continuous delivery (CI/CD) workflow. Any code changes that the company commits to production will be automatical
The correct answer is D. Add a manual approval action to the workflow in CodePipeline before code is deployed. Manually. A manual approval action is a built-in CodePipeline feature designed specifically to pause a pipeline at a defined point and require a human to approve before continuing. Placing this action before the production deploy stage satisfies the requirement for leadership validation wi
Question
A company uses AWS CodePipeline to create a fully automated continuous integration and continuous delivery (CI/CD) workflow. Any code changes that the company commits to production will be automatically deployed to the company's Amazon EC2 instances. The company's leadership team must manually validate any changes before the company releases changes to production. Which solution will meet these requirements in the MOST operationally efficient way?
Options
- ASet up an Amazon SNS topic. Configure the SNS topic to stop the workflow at a specific stage by
- BCreate a CodePipeline custom action for the workflow. Create a job worker to invoke an AWS
- CStop the workflow on a stage execution state change by using an Amazon EventBridge rule and
- DAdd a manual approval action to the workflow in CodePipeline before code is deployed. Manually
How the community answered
(24 responses)- B4% (1)
- C8% (2)
- D88% (21)
Explanation
A manual approval action is a built-in CodePipeline feature designed specifically to pause a pipeline at a defined point and require a human to approve before continuing. Placing this action before the production deploy stage satisfies the requirement for leadership validation with minimal additional configuration and operational overhead.
Community Discussion
No community discussion yet for this question.