AWS DVA-C02 Drill: CodePipeline Manual Approval - Choosing the Most Efficient Integration

Jeff’s Note

#

Unlike generic exam dumps, ADH analyzes this scenario through the lens of a Real-World Lead Developer.

For DVA-C02 candidates, the confusion often lies in understanding how best to integrate manual approval processes into CI/CD pipelines with AWS CodePipeline. In production, this is about knowing exactly how CodePipeline’s native manual approval action works with SNS notifications without redundant workflows or unnecessary orchestration overhead. Let’s drill down.

The Certification Drill (Simulated Question)

#

Scenario

#

ByteMint, a fast-growing SaaS startup, has a development team that requires sign-off from the product manager before deploying new features to their production environment. The developers use an AWS CodePipeline setup to automate deployments. To alert the product manager about pending approvals, they configured an Amazon SNS topic to send notifications. The challenge is to implement the most operationally efficient approval workflow that integrates these elements seamlessly, minimizes custom implementation, and aligns with best practices for CICD pipeline approvals.

The Requirement:

#

Design an approval mechanism within the existing CodePipeline that notifies the product manager using the SNS topic and requires their explicit approval before proceeding to production deployments.

The Options

#

• 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.

• B) 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.

• C) 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.

• D) 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.

Google adsense

#

leave a comment:

Correct Answer

#

A

Quick Insight: The Developer Imperative

#

CodePipeline’s manual approval action is designed to be placed as a distinct pipeline stage before deployment.
Pairing this with a notification rule that triggers the SNS topic ensures automatic alerts without custom orchestration.
This avoids complicating the workflow with extra Step Functions logic (Option B) or misconfiguring events inside an existing stage (Option C).
Simply setting a notification rule without manual approval action (Option D) lacks the gating control.

Content Locked: The Expert Analysis

#

You’ve identified the answer. But do you know the implementation details that separate a Junior from a Senior?

The Expert’s Analysis

#

Correct Answer

#

Option A

The Winning Logic

#

A key best practice for AWS CodePipeline is to use a dedicated stage for manual approval actions, placed before the deployment stage. This ensures clean separation of pipeline logic and clear visibility into approval steps.

• Adding a new stage with a manual approval action acts as a natural gate, pausing the pipeline automatically until the product manager approves via the AWS Management Console or API.
• The pipeline-level notification rule, configured to trigger on manual approval events, connects directly to the SNS topic. This means you leverage AWS fully managed eventing mechanisms without extra infrastructure.
• This setup requires no Lambda functions, Step Functions orchestration, or complex custom workflows — reducing operational overhead and keeping deployments simple and maintainable.
• This approach aligns perfectly with developer-focused responsibilities: use native AWS CI/CD primitives with minimal custom code.

The Trap (Distractor Analysis)

#

• Why not B?
  While integrating Step Functions can solve complex orchestration, it adds unnecessary complexity and operational overhead for a simple approval gate. Remember, less is more in CI/CD pipelines.

• Why not C?
  Manual approval actions cannot be directly wired with SNS topics via the action configuration itself. Notifications happen via pipeline-level notification rules, not within the action definition. This leads to misconfigured notifications and missed alerts.

• Why not D?
  Creating a notification rule without a manual approval action does not enforce the approval gate. The pipeline would continue to deploy regardless, violating the requirement for explicit sign-off.

The Technical Blueprint

#

# Create a manual approval action stage via CLI (sample snippet)
aws codepipeline update-pipeline --pipeline file://pipeline.json

# Example of pipeline.json snippet - new stage before deployment:
{
  "name": "Approval",
  "actions": [
    {
      "name": "ManualApproval",
      "actionTypeId": {
        "category": "Approval",
        "owner": "AWS",
        "provider": "Manual",
        "version": "1"
      },
      "runOrder": 1,
      "configuration": {},
      "outputArtifacts": [],
      "inputArtifacts": []
    }
  ]
}

# Then add notification rule:
aws codestarnotifications create-notification-rule \
  --name "NotifyProductManagerApproval" \
  --resource "arn:aws:codepipeline:region:account:ByteMintPipeline" \
  --event-types "codepipeline-pipeline-manual-approval-needed" \
  --targets "TargetType=SNS,TargetAddress=arn:aws:sns:region:account:ProductManagerSNSTopic"

The Comparative Analysis

#

Real-World Application (Practitioner Insight)

#

Exam Rule

#

“For the exam, always pick a new manual approval stage combined with a CodePipeline notification rule when you see approval gating with notification.”

Real World

#

“In reality, teams sometimes overengineer approvals with Step Functions or Lambda when CodePipeline’s manual approval + notifications cover 90% of approval use cases with less maintenance.”

(CTA) Stop Guessing, Start Mastering

#

Disclaimer

This is a study note based on simulated scenarios for the AWS DVA-C02 exam.