DOP-C02 Configuration Management and IaC Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  The pipeline uses a different branch name.

  Why it's wrong here

  A branch name mismatch would indeed prevent the pipeline from processing pushes to the intended branch, but the branch is explicitly defined in the source action's configuration. If the branch were incorrect, the webhook would still receive the push event, but the pipeline's execution would not start because the event filtering (based on the branch name) would exclude it. This is a configuration error visible in the pipeline settings, not a failure of the webhook mechanism itself, so it cannot be the reason for a properly configured pipeline failing to trigger automatically.

• ✗

  The GitHub repository is not in the same AWS region as the pipeline.

  Why it's wrong here

  GitHub is a third-party SaaS service completely outside the AWS global infrastructure, so it has no regional concept or residency. AWS CodePipeline accesses it over the public internet using HTTPS and either OAuth tokens or a CodeStar Connections/GitHub App, neither of which is tied to an AWS region. Even if the pipeline and the GitHub repository are in the same region, that is purely coincidental; the source action would behave identically regardless of the repository's logical location, so this has no bearing on webhook triggering behavior.

• ✓

  The webhook in GitHub is not properly configured or has been removed.

  Why this is correct

  Automatic triggering in CodePipeline with a GitHub source action depends on an active webhook that GitHub uses to notify the CodePipeline API whenever commits are pushed to the repository. If that webhook has been deleted, or if its payload URL or secret token no longer matches what CodePipeline expects, GitHub's push events will never reach CodePipeline and no new pipeline execution will be started. This is the classic cause of 'commits pushed but pipeline doesn't run,' and it is precisely why this is the correct answer.

• ✗

  The pipeline does not have permission to access the GitHub repository.

  Why it's wrong here

  The pipeline's IAM role or connection token is only used when the source action runs to clone or download the repository contents during execution. A missing or invalid permission would not prevent GitHub from sending a webhook event to CodePipeline; instead, the webhook would fire, the pipeline would transition to the Source stage, and then fail with an authentication or authorization error when attempting to access the GitHub repository. Therefore, the symptom of the pipeline not triggering at all points away from permissions and toward the webhook itself.

Go deeper

Related to this question