AZ-400 Practice Question: Design and implement build and release pipelines
Your team uses Microsoft-hosted agents for builds. Recently, builds are taking longer to start. What is the best way to reduce queue times?
⚠ Common exam trap
Many candidates confuse 'parallel jobs' (concurrency limit) with 'agent availability' (queue wait time), assuming that buying more parallelism will speed up agent assignment when it only affects how many builds can run at once.
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
✓
Provision self-hosted agents.
Microsoft-hosted agents share a global pool with other Azure DevOps organizations, so queue times increase during peak usage. Provisioning self-hosted agents gives you dedicated compute resources that are always available, eliminating dependency on the shared pool and reducing queue wait times.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the number of parallel jobs in the organization.
Why it's wrong here
In Azure DevOps, parallel jobs represent concurrent pipeline runs that can execute simultaneously, but they are constrained by the number of available hosted agents. Simply increasing the parallel job limit does not add more physical agents; if the current agent pool is saturated, additional jobs will still wait in the queue until an agent becomes free, so queue times persist.
- ✗
Use more pipeline triggers.
Why it's wrong here
Adding more triggers (e.g., CI on pushes, PR triggers, scheduled triggers) creates more pipeline runs and increases the frequency of job submissions. This intensifies contention for the same finite pool of hosted agents, leading to longer queue wait times rather than resolving the congestion.
- ✓
Provision self-hosted agents.
Why this is correct
Self-hosted agents are owned and managed by your team, providing dedicated compute capacity that operates independently of Microsoft's hosted agent pool. By registering self-hosted agents in an agent pool that your pipelines target, you can scale out processing capacity and reduce or eliminate queue waiting times, especially for high-frequency builds.
- ✗
Reduce the number of parallel jobs.
Why it's wrong here
Reducing the parallel job limit decreases the number of pipeline runs that can execute concurrently, which forces more jobs to wait in the queue. This directly increases queue wait times and slows down overall build throughput, making it counterproductive when trying to address long queue durations.
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
DevOps
DevOps is a set of practices that combines software development (Dev) and IT operations (Ops) to shorten the development lifecycle and deliver high-quality software continuously.
Key term
Azure DevOps
Azure DevOps is a Microsoft service that provides development tools for planning, building, testing, and deploying software applications using automated pipelines and collaboration features.
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.