Configure processes and communications →easyMultiple ChoiceObjective-mapped

AZ-400 Configure processes and communications Practice Question

Exhibit

Refer to the exhibit.

```json
{
  "resources": {
    "repositories": {
      "self": {
        "ref": "refs/heads/feature/*"
      }
    }
  },
  "trigger": {
    "batch": true,
    "branches": {
      "include": ["main", "release/*"]
    }
  },
  "pr": {
    "branches": {
      "include": ["main"]
    }
  }
}
```

You see the above YAML pipeline trigger configuration in an Azure Pipeline. The repository uses Git Flow with branches: feature/new-feature, develop, release/v1.0, and main. A developer pushes a commit to the branch feature/new-feature. Which action will trigger the pipeline?

⚠ Common exam trap

Azure Pipelines triggers on all branches by default when no trigger block is specified. However, when a trigger block is present, only the listed branches trigger. Do not assume that a branch name containing 'feature' automatically triggers CI or PR. In this question, the branch filter excludes feature/*, so no trigger starts.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

No trigger will start.

The YAML trigger configuration (shown) explicitly lists the branches that trigger CI. Since feature/new-feature is not included in the branch filter, a push to that branch does not start a CI run. PR triggers are separate and require an actual PR to be created, not a push.

Answer analysis

Option-by-option breakdown

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

✗
A CI trigger will start because the branch name starts with 'feature/'.
Why it's wrong here
A CI trigger only starts for branches explicitly listed in the trigger's include section. Since 'feature/*' is not in the include list, a push to 'feature/new-feature' does not match any include pattern, so the pipeline will not run.
✓
No trigger will start.
Why this is correct
The push to feature/new-feature does not match any branch in the trigger include list, and the PR trigger only applies to PRs.
✗
A PR trigger will start because the branch name contains 'feature'.
Why it's wrong here
PR triggers are separate from CI triggers and only execute when a pull request is created or updated, not on a simple push to a branch. A branch name containing 'feature' does not by itself create a PR, so no PR trigger will fire.
✗
A CI trigger will start for all branches because batch is set to true.
Why it's wrong here
The batch property only controls whether multiple commits are batched into a single run when a qualifying branch is pushed; it does not broaden which branches trigger the pipeline. Branch inclusion is still strictly governed by the trigger's include/exclude list, which does not contain 'feature/*'.

Visual reference

Go deeper

AZ-400 Configure processes and communications Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question