A company uses a pipeline in AWS CodePipeline to upload AWS CloudFormation templates to an...

The requirement is simply: review changes before production deployment, with the least operational overhead.

B is the lightest change: adding a Manual approval (review) action in CodePipeline creates a controlled gate before the deploy stage. It requires no new repositories, no new services, and no custom code—just pipeline configuration.

Why not the others:

A introduces additional moving parts (Git repo integration, PR workflow management, and CloudFormation Git sync). That’s useful, but it’s more operational overhead than necessary to satisfy “review before deploy.”

C requires custom Lambda logic to inspect templates and decide whether to proceed—more code to write, run, secure, and maintain.

D adds both Git integration and a manual approval step—again more overhead than just adding the approval gate.

So B best meets the requirement with the least operational effort: a simple manual approval stage in the pipeline before production deployment.