AZ-400 Practice Question: Design and implement build and release pipelines
Your release pipeline uses a multi-stage YAML with environments. You need to ensure that only one deployment runs at a time to a production environment to avoid conflicts. Which feature should you use?
⚠ Common exam trap
Many exam-takers confuse 'parallel deployment' settings (which control concurrency within a single stage) with environment-level locking (which controls concurrency across multiple pipeline runs targeting the same environment).
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
✓
Configure an exclusive lock policy on the production environment.
An exclusive lock policy on an environment ensures that only one deployment can run at a time to that environment. When a deployment starts, it acquires a lock on the environment; subsequent deployments are queued until the lock is released. This prevents conflicts from concurrent deployments to the same production environment.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a condition to check if a previous deployment is in progress.
Why it's wrong here
YAML conditions can check variables and compile-time parameters, but they cannot query the current deployment state of an environment, so you cannot reliably implement mutual exclusion. Additionally, conditions evaluate per-run, not across concurrent runs, so two runs could both pass the condition and proceed simultaneously.
- ✗
Add a pre-deployment approval gate.
Why it's wrong here
Pre-deployment approvals require a designated approver to give consent before the deployment starts, but they do not reserve or lock the environment. Multiple runs can be approved sequentially or in parallel, and once approved they will all execute, possibly overlapping on the same environment.
- ✗
Set the 'parallel' deployment option to 1.
Why it's wrong here
The `parallel` keyword in a YAML pipeline configures the number of job copies or a strategy for agent jobs, such as a matrix or parallel job execution. It does not control environment deployment concurrency; environment concurrency is managed via the environment's lock or exclusive resource settings.
- ✓
Configure an exclusive lock policy on the production environment.
Why this is correct
Configuring an exclusive lock policy on the Production environment ensures that only a single pipeline run can deploy to that environment at any given time. Once a deployment job acquires the lock, any other deployment jobs targeting the same environment will be queued and wait until the lock is released.
Visual reference
Go deeper
Related to this question
Learn chapter
Designing a Build Pipeline
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
Pipeline
A pipeline is an automated series of steps that takes code from development to production, ensuring quality and speed.
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 →
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.