AZ-400 Configure processes and communications Practice Question
Exhibit
Refer to the exhibit.
```yaml
# azure-pipelines.yml
trigger:
branches:
include:
- main
- releases/*
pr: none
pool:
vmImage: 'ubuntu-latest'
steps:
- script: echo "Building..."
```A developer pushes a commit to a branch named 'releases/v1.0'. What will happen?
⚠ Common exam trap
A common mix-up: candidates assume branch names with dots are invalid or that pipelines only run on the main branch, but Azure Pipelines treats all branches equally by default and dots are perfectly valid in Git branch names.
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
✓
The pipeline runs automatically on the push.
Azure Pipelines, by default, triggers a pipeline run automatically on any push to any branch unless a trigger filter is explicitly configured. The branch name 'releases/v1.0' is valid and does not contain any characters that would prevent a trigger; dots are allowed in branch names. The pipeline will execute the steps defined in the YAML file for that branch.
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 runs but fails because the branch name contains a dot.
Why it's wrong here
Git branch names are allowed to contain dots; Azure Pipelines treats dots as literal characters in branch filter patterns, not as wildcards or invalid syntax. Therefore, a dot in the branch name does not cause the pipeline to fail.
- ✗
The pipeline runs only if a pull request is created.
Why it's wrong here
The pipeline has a continuous integration (CI) trigger configured for branch pushes, while the pull request trigger is explicitly set to none. As a result, the pipeline runs on direct pushes to matching branches, not only when a pull request is created.
- ✓
The pipeline runs automatically on the push.
Why this is correct
This outcome is expected because the repository's Azure Pipelines YAML defines a continuous integration (CI) trigger with a branch include filter such as `releases/*`. Since `releases/v1.0` matches that pattern, the push event automatically queues a new pipeline run, even without a pull request. The filter comparison uses glob-style matching on the full branch ref, and Azure Pipelines evaluates it at the time the push is received, making the run immediate and unattended.
- ✗
The pipeline does not run because the branch is not main.
Why it's wrong here
The pipeline's trigger is not restricted to the main branch; it explicitly includes release branch patterns. Therefore, pushing to a release branch (such as 'releases/v1.0') satisfies the trigger condition and causes the pipeline to execute.
Visual reference
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Pipeline
A pipeline is an automated series of steps that takes code from development to production, ensuring quality and speed.
Key term
Azure Pipelines
Azure Pipelines is a cloud-based CI/CD service from Microsoft that automatically builds, tests, and deploys code to any platform or cloud.
About these practice questions
Courseiva writes every AZ-400 question from scratch — 823 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.