This AZ-400 practice question tests your understanding of design and implement build and release pipelines. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You need to run a set of tasks only when the build pipeline runs for the main branch. Which condition should you add to the job or step?
condition: eq(variables['Build.SourceBranch'], 'main')
Why wrong: Missing 'refs/heads/' prefix, so it won't match.
condition: and(succeeded(), eq(variables['System.PullRequest.TargetBranch'], 'main'))
Why wrong: This checks PR target branch, not the source branch.
condition: ne(variables['Build.Reason'], 'PullRequest')
Why wrong: This excludes PRs but does not limit to main branch.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
condition: eq(variables['Build.SourceBranch'], 'refs/heads/main')
Option A is correct because the `Build.SourceBranch` variable in Azure Pipelines contains the full Git ref (e.g., `refs/heads/main`). Using `eq(variables['Build.SourceBranch'], 'refs/heads/main')` ensures the condition evaluates to true only when the pipeline runs on the main branch. This is the standard way to filter by branch in YAML pipeline conditions.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
condition: eq(variables['Build.SourceBranch'], 'main')
Why it's wrong here
Missing 'refs/heads/' prefix, so it won't match.
condition: and(succeeded(), eq(variables['System.PullRequest.TargetBranch'], 'main'))
Why it's wrong here
This checks PR target branch, not the source branch.
condition: ne(variables['Build.Reason'], 'PullRequest')
Why it's wrong here
This excludes PRs but does not limit to main branch.
Option-by-option analysis
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-400 exam frequently reuses these exact scenarios with slightly different constraints.
Why this is wrong here
Missing 'refs/heads/' prefix, so it won't match.
Why this is wrong here
This checks PR target branch, not the source branch.
Why this is wrong here
This excludes PRs but does not limit to main branch.
Analysis generated from the official AZ-400blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Common exam traps
The trap here is that candidates often assume `Build.SourceBranch` contains only the short branch name (like `main`) rather than the full Git ref path (`refs/heads/main`), leading them to choose Option B.
Detailed technical explanation
Azure Pipelines uses the `Build.SourceBranch` variable to expose the full Git reference (e.g., `refs/heads/feature/x`). For branch filters in conditions, you must match the full ref string. The `eq()` function performs a case-sensitive string comparison. In real-world scenarios, using `startsWith(variables['Build.SourceBranch'], 'refs/heads/main')` can also work if you need to include potential sub-branch patterns, but the exact match is safest for the main branch.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Design and implement build and release pipelines — study guide chapter
Learn the concepts, then practise the questions
Design and implement build and release pipelines practice questions
Targeted practice on this topic area only
All AZ-400 questions
913 questions across all exam domains
Microsoft Azure DevOps Engineer Expert AZ-400 study guide
Full concept coverage aligned to exam objectives
AZ-400 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise AZ-400 questions linked to Configure processes and communications.
Practise AZ-400 questions linked to Design and implement source control.
Practise AZ-400 questions linked to Design and implement build and release pipelines.
Practise AZ-400 questions linked to Develop a security and compliance plan.
Practise AZ-400 questions linked to Implement an instrumentation strategy.
Practise AZ-400 questions linked to Design and implement a DevOps infrastructure.
Practise AZ-400 questions linked to Design and implement a source control strategy.
Practise AZ-400 questions linked to AZ-400 fundamentals.
Practise AZ-400 questions linked to AZ-400 scenario.
Practise AZ-400 questions linked to AZ-400 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Design and implement build and release pipelines — This question tests Design and implement build and release pipelines — Read the scenario before looking for a memorised answer..
The correct answer is: condition: eq(variables['Build.SourceBranch'], 'refs/heads/main') — Option A is correct because the `Build.SourceBranch` variable in Azure Pipelines contains the full Git ref (e.g., `refs/heads/main`). Using `eq(variables['Build.SourceBranch'], 'refs/heads/main')` ensures the condition evaluates to true only when the pipeline runs on the main branch. This is the standard way to filter by branch in YAML pipeline conditions.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.