AZ-400 Practice Question: Design and implement build and release pipelines
Network Topology
Refer to the exhibit. A developer commits code to the 'develop' branch. The pipeline does not trigger. What is the most likely reason?
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 trigger is configured to only run on the 'main' branch.
The trigger is set to 'main' branch only. Commits to 'develop' will not trigger the pipeline.
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 trigger is configured to only run on the 'main' branch.
Why this is correct
The YAML pipeline defines a CI trigger using `trigger: - main`, which instructs Azure Pipelines to start a run only for pushes that land on the `main` branch. A commit pushed to `devel` does not match that branch filter, so no pipeline run is created. Therefore the reason for the missing run is scope, not a bad agent pool or manual mode.
- ✗
The pipeline requires a manual trigger.
Why it's wrong here
This is incorrect because the pipeline includes an explicit `trigger:` block, meaning a CI trigger is active and pushes automatically initiate evaluation against branch filters. A manual trigger would instead require the pipeline definition to specify `trigger: none` or require a user to click Run when no CI trigger exists. Since the trigger is present, the pipeline does not rely on a manual kick-off.
- ✗
The pipeline has a CI trigger disabled.
Why it's wrong here
The CI trigger is not disabled; it is configured, but only for the `main` branch. With `trigger: none` or no trigger block at all, Azure DevOps would disable automatic CI, but here the YAML contains a branch-scoped trigger. Thus the pipeline is not globally disabled, just filtered by branch.
- ✗
The pool 'ubuntu-latest' is not available.
Why it's wrong here
The `ubuntu-latest` pool is a Microsoft-hosted agent that is widely available in Azure DevOps, so it would not be the cause of a trigger failure. More fundamentally, agent pool selection only affects where a job executes after the pipeline is triggered; it has no role in determining whether a push to `devel` starts the pipeline. The absence of a run must be explained by the branch filter, not the pool.
Go deeper
Related to this question
Learn chapter
Designing a Build Pipeline
Key term
Branch
A branch is a pointer to a specific commit in a version control system that allows you to work on features or fixes in isolation from the main codebase.
Key term
Pipeline
A pipeline is an automated series of steps that takes code from development to production, ensuring quality and speed.
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.