AZ-400 Practice Question: Design and implement build and release pipelines
Which THREE are benefits of using 'Environment' resources in YAML pipelines compared to classic release pipelines? (Choose three.)
⚠ Common exam trap
Candidates often confuse the classic release pipeline's gate mechanism (Option D) with the YAML pipeline's check system, or incorrectly assume Environments are only for classic pipelines (Option B), when in fact Environments are a cross-pipeline resource that enhances YAML pipelines with deployment tracking and approval workflows.
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
✓
Environments provide a dashboard showing the deployment history and resource health.
Option A is correct because Azure DevOps Environments provide a dedicated dashboard that surfaces deployment history and the health/status of the associated resources (VMs, Kubernetes, etc.), giving visibility that classic release pipelines lack in a unified view. Option C is correct because Environments support configurable checks such as approvals, business hours, and manual intervention, which gate pipeline stages before deployment proceeds. Option E is correct because an Environment can be backed by a Kubernetes resource, where the target can be a namespace, and the environment tracks the deployed versions/artifacts to that namespace. Option B is incorrect because Environments are designed for YAML pipelines, not classic release pipelines. Option D is incorrect because pre-deployment and post-deployment gates are a classic release pipeline feature, not a benefit of Environments in YAML pipelines.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Environments provide a dashboard showing the deployment history and resource health.
Why this is correct
In Azure DevOps, an environment provides a centralized dashboard that consolidates the deployment history from every pipeline that targets that environment, displaying each run's status, artifact version, and timestamp. It also shows resource health, such as whether a VM agent is online or the current state of a Kubernetes namespace, giving teams immediate visibility into both past deployments and the live readiness of infrastructure. This combined view is essential for quickly diagnosing failed deployments, identifying drift, and ensuring auditability across multi-pipeline release processes.
- ✗
Environments can only be used in classic release pipelines.
Why it's wrong here
This statement is incorrect because Environments are fully supported in both YAML pipelines and classic release pipelines. In YAML pipelines, they are used with deployment jobs to enable checks and approvals, making them a core concept in modern CI/CD workflows.
- ✓
Environments support checks like approval gates and manual intervention.
Why this is correct
Environments support checks such as manual approval gates and required template reviews, which are evaluated before a deployment job runs. These checks give teams fine-grained control over deployment stages, including pausing for human sign-off or verifying that specific conditions are met.
- ✗
Environments allow you to define pre-deployment and post-deployment gates using the classic release pipeline interface.
Why it's wrong here
This is misleading because pre-deployment and post-deployment gates are a feature of classic release pipelines, configured on stages rather than on the environment resource itself. In contrast, YAML pipelines use environment-specific checks to provide similar governance, but the classic release interface gates are not a direct environment feature.
- ✓
Environments can represent Kubernetes namespaces and track deployed versions.
Why this is correct
Environments can include Kubernetes resources that map to specific namespaces in a cluster. When using a Kubernetes resource in a deployment job, the environment tracks deployed manifests and versions, giving visibility into what is running and enabling rollback and auditability.
Visual reference
Go deeper
Related to this question
Learn chapter
Implementing Deployment Patterns and Strategies
Key term
Environment
An environment is a dedicated set of computing resources, configurations, and services used to develop, test, or host software applications in a controlled and repeatable way.
Key term
Anthos
Anthos is a Google Cloud platform that lets you run applications consistently across different computing environments, like on-premises data centers and multiple public clouds.
About these practice questions
This AZ-400 question is part of Courseiva's 696-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.