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 conf

Question

Options

• AAdd a new stage to CodePipeline before the production deployment. Add a manual approval
• BDevelop an AWS Step Functions state machine that sends a notification to the product owner and
• CAdd a manual approval action to the existing production deployment stage in CodePipeline.
• DEdit the settings in CodePipeline. Create a new notification rule. Specify manual approval as the

• A
  74% (37)
• B
  16% (8)
• C
  6% (3)
• D
  4% (2)

Explanation

Adding a new stage before the production deployment (Option A) is the correct approach because CodePipeline's manual approval action is designed to pause the pipeline and send an SNS notification to approvers - this is the native, purpose-built mechanism for gating deployments without any custom code.

Why the distractors fail:

• Option B (Step Functions state machine) is unnecessarily complex - it reimplements approval logic that CodePipeline already handles natively, adding operational overhead.
• Option C is tempting but wrong: adding a manual approval action within the existing production deployment stage is not best practice - approvals should gate entry into a stage, not interrupt one already in progress.
• Option D (notification rules via pipeline settings) handles event notifications (e.g., "pipeline succeeded"), not interactive approval gates - it cannot pause execution and wait for a human response.

Memory tip: Think of pipeline stages as gates on a highway. A manual approval action is a tollbooth you add before the production on-ramp, not in the middle of the road. CodePipeline + SNS + manual approval stage = the AWS-native, zero-custom-code solution, which is always the "most operationally efficient" answer on the exam.

No community discussion yet for this question.