How to Implement Manual Approval in AWS CodePipeline?

DVA-C02 By islever Editorial Last updated Aug 27, 2026

Short answer

A Add a new stage to CodePipeline before the production deployment. Add a manual approval action to the new stage. Add a new notification rule in the pipeline settings. Specify manual approval as the event that initiates the notification. Specify the SNS topic's Amazon Resource Name (ARN) to notify the product owner.

Question

A developer needs approval from a product owner before the developer can deploy code for an application to production. The developer uses AWS CodePipeline to deploy the application. The developer configures an Amazon Simple Notification Service (Amazon SNS) topic to send notifications to the product owner. Which solution is the MOST operationally efficient way for the developer to receive approval from the product owner?

Add a new stage to CodePipeline before the production deployment. Add a manual approval action to the new stage. Add a new notification rule in the pipeline settings. Specify manual approval as the event that initiates the notification. Specify the SNS topic's Amazon Resource Name (ARN) to notify the product owner. Correct Answer
Develop an AWS Step Functions state machine that sends a notification to the product owner and accepts an approval. Add a new stage to CodePipeline before the production deployment. Add the state machine as a Step Functions action to the new stage.
Add a manual approval action to the existing production deployment stage in CodePipeline. Specify the SNS topic's Amazon Resource Name (ARN) while configuring the new manual approval action.
Edit the settings in CodePipeline. Create a new notification rule. Specify manual approval as the event that initiates the notification. Create a new notification target. Specify the SNS topic to notify the product owner. Save the notification rule.

Key Takeaways

Tests native CodePipeline capabilities for human-in-the-loop deployments versus custom orchestration, with the common trap being over-engineering with Step Functions or misconfiguring notification targets.

This question tests implementing secure deployment workflows in AWS CodePipeline using built-in manual approval actions and SNS notifications. The community unanimously agrees that configuring a dedicated stage with a manual approval action linked to an SNS topic is the most operationally efficient approach.

Common mistake: Option C is frequently chosen by candidates who attempt to attach the SNS ARN directly to the existing deployment stage, but CodePipeline requires a separate manual approval action stage to properly halt execution and trigger notifications.

Expert Analysis

Why the Answer Is Correct

Option A correctly adds a dedicated stage before production deployment containing a manual approval action, which natively pauses the pipeline until consent is given. By configuring a notification rule within CodePipeline settings, the system automatically triggers an SNS message to the product owner when the approval event occurs. This leverages AWS-managed features without requiring custom infrastructure, aligning perfectly with the operational efficiency requirement.

Why the Other Options Are Wrong

Option B introduces unnecessary complexity by building a Step Functions state machine, violating the principle of least effort when native pipeline features suffice. Option C incorrectly attempts to bind the SNS ARN directly to a deployment stage rather than using a dedicated approval action, which will not pause execution or trigger the intended workflow. Option D misses the critical step of adding a manual approval action to the pipeline itself, making the notification rule ineffective since no approval event would exist.

Community Comment Notes

Candidates consistently validate Option A as the correct choice, emphasizing its direct integration into the CI/CD workflow. Comment [1] highlights how this setup ensures explicit consent while automating communication through SNS. Comment [2] reinforces that adding a manual approval action to a stage is mandatory for halting the pipeline, confirming the architectural best practice.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

Focus on recognizing when to leverage native AWS service capabilities versus building custom solutions. Always look for options that minimize operational overhead while meeting security and compliance requirements like mandatory pre-production approvals.

Community Votes

100%

100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

SerialiDr 👍 4 Answered A

This solution directly integrates a manual approval process into the CI/CD pipeline. By adding a specific stage for manual approval before the deployment can proceed to production, it ensures that no changes are deployed without explicit consent. The integration of Amazon SNS for notifications automates the communication process, informing the product owner when their input is needed. This setup not only enforces a governance check but also streamlines the approval process, making it both efficient and auditable.
CrescentShared 👍 3 Answered A

Adding a manual approval action to a pipeline stage, which is necessary for halting the pipeline to wait for approval.
monishvster 👍 2 Answered A

should be A
65703c1 👍 1 Answered A

A is the correct answer.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Practice All DVA-C02 Questions

Access 100 questions with complete answers and detailed explanations.

View Full DVA-C02 Practice Test →

← Back to DVA-C02 Study Guide