AWS Certified Developer – Associate — Question 250

A company is using AWS CodePipeline to deliver one of its applications. The delivery pipeline is triggered by changes to the main branch of an AWS CodeCommit repository and uses AWS CodeBuild to implement the test and build stages of the process and AWS CodeDeploy to deploy the application.

The pipeline has been operating successfully for several months and there have been no modifications. Following a recent change to the application's source code, AWS CodeDeploy has not deployed the updated application as expected.

What are the possible causes? (Choose two.)

Answer options

• A. The change was not made in the main branch of the AWS CodeCommit repository.
• B. One of the earlier stages in the pipeline failed and the pipeline has terminated.
• C. One of the Amazon EC2 instances in the company's AWS CodePipeline cluster is inactive.
• D. The AWS CodePipeline is incorrectly configured and is not invoking AWS CodeDeploy.
• E. AWS CodePipeline does not have permissions to access AWS CodeCommit.

Correct answer: A, B

Explanation

Option A is valid because if the change was not made to the main branch, the pipeline would not trigger. Option B is also correct since if an earlier stage failed, the entire pipeline would halt, preventing deployment. Options C, D, and E are less likely causes as they do not directly relate to the deployment trigger failure in this scenario.