Manual Approval Before Production in CodePipeline

Why the Answer Is Correct

Option C adds a manual approval action directly to the existing production deployment stage and specifies the SNS topic ARN inside that action's configuration. CodePipeline manual approval actions support a notification target (NotificationArn) in their action settings, so the approver is notified automatically when the pipeline reaches the approval checkpoint. This is one configuration change, uses the existing stage structure, and requires no auxiliary resources—exactly what "most operationally efficient" asks for. Placing the approval action ahead of the deployment action in the stage guarantees the pipeline halts until the product owner approves.

Why the Other Options Are Wrong

Option A also achieves approval, but it creates a new stage, an approval action, and a separate notification rule—three resources to maintain where one suffices, and every extra resource is added operational surface. Option B introduces AWS Step Functions to build a custom notification-and-approval state machine, which is far more code, cost, and failure modes than the managed approval feature. Option D creates a notification rule but never adds a manual approval action at all, so the pipeline has nothing that actually pauses for the product owner's consent. As one commenter put it, A "builds three things where one is enough."

Community Comment Notes

The comment thread is split between A and C. Supporters of A, including SerialiDr, argue it "directly integrates a manual approval process into the CI/CD pipeline" and ensures nothing deploys without consent. The opposing camp, voiced by cerepx and Kisma86, targets efficiency: "The trap here is A. It works, and that makes it feel safe" but "it builds three things where one is enough," and "Answer A and B are over-complicated." Kisma86 and TEC65 both land on C for exactly that reason, which aligns with the question's emphasis on operational efficiency rather than mere functionality.