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.)
Select an option, then click Submit answer.
Reference / correct answer:
One of the earlier stages in the pipeline failed and the pipeline has terminated.
Most accepted answer: B. One of the earlier stages in the pipeline failed and the pipeline has terminated.
Community votes: A=4, B=6, C=1, D=1
Selected Answer: AB A. The change was not made in the main branch of the AWS CodeCommit repository: In this pipeline setup, if the change was made in a branch other than the main branch, it would not trigger the pipeline, and therefore, AWS CodeDeploy wouldn't deploy the updated application. B. One of the earlier stages in the pipeline failed and the pipeline has terminated: If one of the preceding stages in the pipeline failed, it would prevent the subsequent stages, including AWS CodeDeploy, from being executed. upvoted 10 times
Selected Answer: AB AB is the correct answer. upvoted 1 times
Selected Answer: AB A. The change was not made in the main branch of the AWS CodeCommit repository. If the change to the application's source code was not made in the main branch (or the branch that triggers the pipeline), AWS CodePipeline would not detect the change and therefore would not initiate the deployment process. It's crucial that changes are made in the correct branch that is configured to trigger the pipeline. B. One of the earlier stages in the pipeline failed and the pipeline has terminated. If any stage in AWS CodePipeline fails (such as a failure in the test or build stages in AWS CodeBuild), the pipeline stops and does not proceed to the deployment stage. It is common for pipelines to be configured to halt on failure to prevent the deployment of potentially faulty code. upvoted 3 times
Selected Answer: AB AB is correct - there have been no changes, so someone either merged code into the wrong branch (not triggering the pipeline) or it failed at an earlier stage. Other options dont make sence given the scenario upvoted 2 times
Selected Answer: BC The delivery pipeline is triggered by changes to the main branch - so new code change should have triggered this but this cause errors for some reasons and option C upvoted 1 times