QuestionQ15

SDLC Automation

A company uses an AWS CodePipeline pipeline to upload AWS CloudFormation templates to an Amazon S3 bucket. The pipeline uses those templates to deploy CloudFormation stacks whose names match the template names.

The company has encountered problems when attempting to revert templates to an earlier version. To avoid these problems, the company must be able to review template changes before the changes are deployed to production.

Which solution meets these requirements with the LEAST operational overhead?

  • A Configure a connection in AWS CodeConnections to a Git repository. Store the templates in the Git repository. Configure a pull request workflow to review template modifications. Configure AWS CloudFormation Git sync for the stacks.
  • B Add a manual review action in the pipeline to review modifications to the template code before the stack deployments.
  • C Update the pipeline to invoke an AWS Lambda function to check the template modifications before the stack deployments.
  • D Configure a connection in AWS CodeConnections to a Git repository. Store the templates in the Git repository. Configure the pipeline to include a source action that uses the connection. Add a manual review action to the pipeline to review template modifications before the stack deployments.
Explanation

AWS CloudFormation Git sync uses a Git repository connected through AWS CodeConnections to manage CloudFormation templates and stack deployment files. Pull requests provide version history and a review gate; after a pull request is approved and merged into the monitored branch, CloudFormation synchronizes and deploys the stack. This managed integration avoids maintaining a separate manual-approval pipeline stage or custom Lambda validation logic.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!