AZ-400 Design and implement source control Practice Question
Exhibit
Azure DevOps Pipeline resource trigger configuration:
resources:
repositories:
- repository: shared
type: git
name: MyProject/SharedRepo
trigger:
branches:
include:
- main
- release/*Refer to the exhibit. A pipeline in repository 'MyProject/AppRepo' is configured to trigger when changes are pushed to 'SharedRepo'. A developer pushes a commit to the 'release/v1' branch of 'SharedRepo'. What will happen?
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 will trigger because 'release/v1' matches the 'release/*' include pattern.
The trigger includes branches matching 'main' and 'release/*'. 'release/v1' matches the wildcard 'release/*', so the pipeline in AppRepo will be triggered.
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 will trigger only if the commit also includes changes to 'main'.
Why it's wrong here
The trigger is branch-based and does not require any changes to 'main'. When a commit is pushed to 'release/v1', Azure Pipelines evaluates the branch trigger against the branch for that push, so the pipeline triggers on 'release/v1' itself, not because of concurrent changes to 'main'.
- ✗
The pipeline will fail because the trigger configuration is invalid.
Why it's wrong here
The trigger configuration is syntactically valid and correctly structured; Azure Pipelines accepts the YAML trigger block with 'branches.include: release/*'. The wildcard pattern is supported, so the pipeline will not fail due to an invalid configuration.
- ✓
The pipeline will trigger because 'release/v1' matches the 'release/*' include pattern.
Why this is correct
The 'release/*' include pattern is a wildcard that matches any branch name beginning with 'release/' and containing any characters after the slash. Because 'release/v1' starts with 'release/', it matches the pattern, satisfying the branch trigger and causing the pipeline to trigger on that branch.
- ✗
The pipeline will not trigger because 'release/v1' is not explicitly listed.
Why it's wrong here
The pipeline does not require an exact, explicit branch name like 'release/v1' to be listed in the trigger configuration. The wildcard 'release/*' already covers 'release/v1' as a matching branch, so the absence of an explicit entry does not prevent the pipeline from triggering.
Visual reference
Go deeper
Related to this question
Learn chapter
Designing a Build Pipeline
Key term
Repository
A repository is a central storage location where software packages, code, or configuration files are kept, managed, and distributed for use by IT systems.
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
This AZ-400 question is part of Courseiva's 823-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.