Q12 — AWS DOP-C02 Ch.2

Question 12 of 100 | ← Chapter 2

A development team uses AWS CodeCommit for application code version control and AWS CodePipeline to orchestrate software deployments. The team decided to use the remote main branch as the pipeline trigger for infrastructure-as-code changes. Developers pushed code changes to the CodeCommit repository but observed no pipeline response—even after 10 minutes. Which action should be taken to resolve this issue?

• A. Verify whether an Amazon CloudWatch Events rule has been created for the main branch to trigger the pipeline. ✓
• B. Verify whether the CodePipeline service role has permissions to access the CodeCommit repository.
• C. Verify whether the developers’ IAM roles have permissions to push to the CodeCommit repository.
• D. Check whether the pipeline failed to start due to CodeCommit errors logged in Amazon CloudWatch Logs.

Correct Answer: A. Verify whether an Amazon CloudWatch Events rule has been created for the main branch to trigger the pipeline.

Explanation

The best choice is A. Reason: Trigger configuration: Verify whether the Amazon CloudWatch Events rule is correctly configured to capture code push events on the main branch and trigger the pipeline. Event capture: Without proper configuration, the pipeline will not respond to code changes. B: If the CodePipeline service role lacks permissions, the pipeline may fail later in execution—but would not prevent triggering itself, so it is unlikely the root cause. C: Insufficient IAM permissions for developers would prevent successful pushes—if pushes succeeded, this is not the issue. D: If the pipeline never started, there would be no CodeCommit-related errors logged in CloudWatch Logs, making this an ineffective diagnostic path.