A developer is configuring an applications deployment environment in AWS CodePipeine. The application code is stored in a GitHub repository. The developer wants to ensure that the repository package’s unit tests run in the new deployment environment. The deployment has already set the pipeline’s source provider to GitHub and has specified the repository and branch to use in the deployment.

A developer is configuring an applications deployment environment in AWS CodePipeine. The application code is stored in a GitHub repository. The developer wants to ensure that the repository package’s unit tests run in the new deployment environment. The deployment has already set the pipeline’s source provider to GitHub and has specified the repository and branch to use in the deployment.

When combination of steps should the developer take next to meet these requirements with the least the LEAST overhead’ (Select TWO).
A . Create an AWS CodeCommt project. Add the repository package’s build and test commands to the protects buildspec
B . Create an AWS CodeBuid project. Add the repository package’s build and test commands to the projects buildspec
C . Create an AWS CodeDeploy protect. Add the repository package’s build and test commands to the project’s buildspec
D . Add an action to the source stage. Specify the newly created project as the action provider. Specify the build attract as the actions input artifact.
E . Add a new stage to the pipeline alter the source stage. Add an action to the new stage. Speedy the newly created protect as the action provider. Specify the source artifact as the action’s input artifact.

View Answer

Answer: B, E

Explanation:

This solution will ensure that the repository package’s unit tests run in the new deployment environment with the least overhead because it uses AWS CodeBuild to build and test the code in a fully managed service, and AWS CodePipeline to orchestrate the deployment stages and actions. Option A is not optimal because it will use AWS CodeCommit instead of AWS CodeBuild, which is a source control service, not a build and test service. Option C is not optimal because it will use AWS CodeDeploy instead of AWS CodeBuild, which is a deployment service, not a build and test service. Option D is not optimal because it will add an action to the source stage instead of creating a new stage, which will not follow the best practice of separating different deployment phases.

Reference: AWS CodeBuild, AWS CodePipeline