Q: 1
A development team is using AWS CodeCommit to version control application code and AWS
CodePipeline to orchestrate software deployments. The team has decided to use a remote main
branch as the trigger for the pipeline to integrate code changes. A developer has pushed code
changes to the CodeCommit repository, but noticed that the pipeline had no reaction, even after 10
minutes.
Which of the following actions should be taken to troubleshoot this issue?
Options
Discussion
Option A D is a trap since no logs if the event never triggers.
I see the logic, but wouldn't B be possible too? If the pipeline role can't access CodeCommit, it wouldn't run either.
A . If the pipeline isn't triggering at all, it's usually because the EventBridge rule for the branch isn't set up or is misconfigured. D is more for when a failure happens after a trigger. Pretty sure on this but open to other thoughts.
A imo
A or D? But if the pipeline doesn't react at all (not even a failed start), that's almost always a missing or misconfigured EventBridge rule for that branch. CloudWatch logs (D) only help if something triggered. Seen similar in other exam reports.
B
A imo. If CodePipeline isn't reacting at all when code is pushed, usually means the event trigger (EventBridge rule) is missing for that branch. The pipeline role permissions (B) would only matter if it tries to run and then fails, but here nothing starts. Pretty sure it's A, open to other explanations if someone disagrees.
Makes most sense to check A here.
Probably A for this one. No EventBridge rule on the main branch and CodePipeline just stays idle, seen that before.
A makes more sense: The pipeline needs an EventBridge rule (used to be CloudWatch Events) to trigger on changes to the main branch. If it's missing or misconfigured, pushes won't start the pipeline. I've seen similar issues on practice tests. Pretty sure A is the right troubleshooting step here, but happy if anyone thinks otherwise.
Be respectful. No spam.
