Courseiva
Configure processes and communicationshardMultiple ChoiceObjective-mapped

AZ-400 Configure processes and communications Practice Question

Your Azure DevOps pipeline uses a self-hosted agent pool. You notice that builds are queuing for a long time. What is the most effective way to reduce queue times without incurring additional costs?

⚠ Common exam trap

Candidates often confuse improving individual job performance (faster agents or fewer steps) with increasing parallelism. If the pool has idle agents but the parallelism limit is set too low, increasing the limit is a free way to reduce queue times. However, if the pool is actually saturated (all agents busy), increasing the parallelism setting alone will not help; you would need to add agents or optimize the pipeline.

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

Allocate more parallel jobs to the agent pool.

Allocating more parallel jobs to the self-hosted agent pool allows multiple pipelines or jobs to run concurrently, directly reducing queue times. This is achieved by adjusting the parallelism setting in the agent pool's properties, which does not incur additional costs as you are already paying for the self-hosted infrastructure.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Allocate more parallel jobs to the agent pool.

    Why this is correct

    Allocating more parallel jobs to the self-hosted agent pool increases the maximum number of pipeline runs that can execute concurrently on that pool. Each parallel job consumes one agent slot; with additional parallel job capacity, more builds or releases can run at the same time, directly addressing a bottleneck caused by concurrency limits.

  • Reduce the number of steps in the pipeline.

    Why it's wrong here

    Reducing the number of steps in the pipeline shortens the duration of each individual run but does nothing to change how many runs can execute simultaneously. Parallelism is governed by the number of available agents and parallel job limits, not by the number of steps in a single pipeline definition.

  • Increase the agent specification (e.g., from DS2 to DS4).

    Why it's wrong here

    Increasing the agent specification (e.g., from DS2 to DS4) provides a larger VM with more CPU and memory, which can make a single job finish faster. However, it does not increase the number of concurrent jobs allowed; the parallelism limit for the pool remains unchanged, so the queue depth and wait times are unaffected.

  • Switch to Microsoft-hosted agents to get more parallelism.

    Why it's wrong here

    Switching to Microsoft-hosted agents does not guarantee more parallelism because those agents also have parallel job limits (often requiring paid parallel jobs) and are subject to subscription quotas. Furthermore, Microsoft-hosted agents consume parallel jobs from your organization's allocation, so without purchasing additional capacity, you may still face the same concurrency bottleneck.

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 →

How Courseiva writes practice questions · Editorial policy

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.