The deployment must have the following:• Separate environment pipelines for testing and production• Automatic deployment that occurs for test environments onlyWhich steps should be taken to meet these requirements?
Configure a new AWS CodePipeline service. Create a CodeCommit repository for each environment. Set up CodePipeline to retrieve the source code from the appropriate repository. Set up the deployment step to deploy the Lambda functions with AWS CloudFormation.
Create two AWS CodePipeline configurations for test and production environments. Configure the production pipeline to have a manual approval step. Create a CodeCommit repository for each environment. Set up each CodePipeline to retrieve the source code from the appropriate repository. Set up the deployment step to deploy the Lambda functions with AWS CloudFormation.
Create two AWS CodePipeline configurations for test and production environments. Configure the production pipeline to have a manual approval step. Create one CodeCommit repository with a branch for each environment. Set up each CodePipeline to retrieve the source code from the appropriate branch in the repository. Set up the deployment step to deploy the Lambda functions with AWS CloudFormation.
Create an AWS CodeBuild configuration for test and production environments. Configure the production pipeline to have a manual approval step. Create one CodeCommit repository with a branch for each environment. Push the Lambda function code to an Amazon S3 bucket. Set up the deployment step to deploy the Lambda functions from the S3 bucket.
Explanations:
This option suggests creating separate repositories for each environment, which is unnecessary when using environment-specific branches in a single CodeCommit repository. Additionally, using CloudFormation for Lambda deployment isn’t the most efficient solution in this case.
This option introduces separate repositories, which complicates management. Also, it incorrectly sets up manual approval for the test environment, which is not needed.
This option correctly utilizes a single CodeCommit repository with separate branches for each environment, aligning with the requirement for automatic deployments to test environments. It also includes the necessary manual approval for the production pipeline.
This option suggests pushing Lambda code to an S3 bucket, which isn’t necessary when using CodePipeline with CodeCommit. Also, it involves CodeBuild, which is not required for the described use case.