Courseiva
Design and implement build and release pipelinesmediumMultiple SelectObjective-mapped

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

Which TWO benefits does using deployment groups provide in Azure Pipelines? (Choose two.)

⚠ Common exam trap

It's easy for candidates to confuse deployment groups with environment-level approvals or think they are exclusive to classic pipelines, but deployment groups are a flexible agent-based targeting mechanism that works across both classic and YAML pipelines.

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

You can deploy to a specific set of target servers (e.g., all web servers in a farm).

Deployment groups in Azure Pipelines allow you to define a logical set of target machines (e.g., all web servers in a farm) and deploy to them collectively. This enables targeted, multi-machine deployments without needing to manage individual agents per environment. Option B is correct because deployment groups support rolling deployments with built-in health validation, where the pipeline can monitor application health after each batch of updates and automatically roll back on failure.

Answer analysis

Option-by-option breakdown

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

  • You can deploy to a specific set of target servers (e.g., all web servers in a farm).

    Why this is correct

    Deployment groups allow you to define a logical set of target machines that share the same deployment role, such as all web servers in a farm. This enables precise, scoped deployments to specific servers within an environment, rather than deploying to an entire pool arbitrarily.

  • They enable rolling deployments with health validation.

    Why this is correct

    Deployment groups support rolling deployment strategies, where the deployment is applied incrementally to subsets of machines in the group. Health validation can be performed after each iteration to detect issues before proceeding to the next set, reducing risk and downtime.

  • You can assign multiple deployment groups to a single agent.

    Why it's wrong here

    An agent is registered to exactly one deployment group at a time; you cannot assign multiple deployment groups to a single agent. If you need to target machines in different groups, register separate agents or use machine-level targeting within a single group.

  • Each target server must have its own agent.

    Why it's wrong here

    While each deployment group target machine typically requires an agent, a single agent can be installed on a machine and target multiple servers if those servers are accessible. However, the statement that each target server must have its own agent is incorrect; an agent can manage multiple servers as long as it has network access and appropriate configurations.

  • Deployment groups can only be used with classic release pipelines.

    Why it's wrong here

    Deployment groups are not limited to classic release pipelines; they can be used in YAML pipelines as well. Azure DevOps supports deployment group jobs in both classic and YAML pipeline definitions, providing flexibility in automation.

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.