Courseiva
Design and implement build and release pipelineshardMultiple ChoiceObjective-mapped

AZ-400 Practice Question: Design and implement build and release pipelines

Your organization uses Azure Pipelines to build a large monolithic application. The build takes over 60 minutes. Management wants to reduce the build time to under 30 minutes. The application has multiple independent modules that could be built in parallel. What is the most effective strategy to reduce build time?

⚠ Common exam trap

Watch out — candidates often choose 'upgrade the build agent' (Option B) because they assume more CPU/RAM will linearly speed up compilation, but for a build with many independent modules, the real bottleneck is sequential execution; adding parallelism yields the greatest reduction. Hardware upgrades may help somewhat but do not remove the sequential dependency.

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

Refactor the build pipeline to use multiple parallel jobs, each building a separate module.

The build time is dominated by sequential compilation of independent modules. By refactoring the pipeline to use multiple parallel jobs, each building a separate module, Azure Pipelines can leverage its built-in parallelism to reduce wall-clock time significantly. This directly addresses the root cause—lack of concurrency—without sacrificing code quality or infrastructure cost.

Answer analysis

Option-by-option breakdown

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

  • Reduce the number of unit tests run during the build.

    Why it's wrong here

    Cutting unit tests weakens regression detection and does not address the main bottleneck, which is typically compilation and packaging of a large monorepo; tests can be parallelized or run at separate stages instead, but removing them sacrifices quality without guaranteeing a meaningful time reduction.

  • Upgrade the build agent to a larger VM size with more CPU and memory.

    Why it's wrong here

    A larger build agent adds CPU and memory, which can speed up individual tasks, but a single-agent pipeline still executes steps sequentially; to cut wall-clock time substantially, you must parallelize the work across multiple agents, not just give one agent more cores.

  • Move the build to a self-hosted agent in the same network as the source code repository.

    Why it's wrong here

    Self-hosted agents on the same network reduce source-fetch latency, but for a large monorepo the dominant costs are compile, test, and package steps, which are unaffected by network proximity; this change rarely halves total build time.

  • Refactor the build pipeline to use multiple parallel jobs, each building a separate module.

    Why this is correct

    A monorepo with independent modules can be split into multiple parallel jobs, each building a separate module on its own agent; this leverages true concurrency to reduce overall wall-clock time, provided you correctly manage inter-module dependencies and publish artifacts for downstream consumption.

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 →

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.