AZ-400 Practice Question: Design and implement build and release pipelines
You are designing a release pipeline in Azure Pipelines that deploys a web app to multiple environments (dev, test, prod). You want to ensure that the same build artifact is deployed to each environment without rebuilding. Which trigger type should you use?
⚠ Common exam trap
Candidates often confuse build completion triggers (which chain builds) with continuous deployment triggers (which chain builds to releases), leading them to select build completion trigger thinking it will automatically deploy to environments, but it only triggers another build pipeline, not a release.
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
✓
Continuous deployment trigger on the release pipeline
A continuous deployment trigger on the release pipeline automatically starts a new release deployment whenever a new build artifact is available, ensuring the same build artifact is deployed to each environment without rebuilding. This is the correct choice because the requirement is to deploy the same artifact across multiple environments, and the continuous deployment trigger is designed to initiate a release pipeline after a build completes, preserving the artifact for downstream stages.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Pull request trigger
Why it's wrong here
PR triggers operate at the build-pipeline level: when a pull request is opened or updated, they queue a validation build of the merged source to catch integration errors before merge. A release pipeline, by contrast, exists to deploy an already-built artifact, and promoting or releasing that artifact is not itself a pull request event. Even when a release pipeline reacts to a PR merge, the artifact is consumed only after a build completes, so a PR trigger alone does not deploy that artifact to stages.
- ✓
Continuous deployment trigger on the release pipeline
Why this is correct
A continuous deployment trigger on the release pipeline is the artifact trigger that watches a connected build artifact for a successful build. When a new version of that artifact is produced, the trigger automatically creates a release and promotes that exact artifact through every stage, so all environments test and receive the same immutable build. This precisely matches the requirement to use the same artifact without rebuilding or recompiling.
- ✗
Schedule trigger
Why it's wrong here
Schedule triggers are time-based cron expressions that initiate releases at specified days or times, independent of whether a new artifact actually exists. A scheduled release consumes whatever artifact version is currently latest from the artifact source at runtime, so the same build is not guaranteed across stages if a newer build arrives mid-release. This does not satisfy the 'same artifact' requirement and can introduce environment drift, unlike an artifact-triggered release.
- ✗
Build completion trigger
Why it's wrong here
Build completion triggers are defined in build pipelines to queue another build when the source build finishes, typically to compile dependent services or run chained CI jobs. They do not create a release or deploy an artifact; they only produce new build outputs. If a release does start afterward, it is because a separate release-pipeline artifact trigger—specifically the continuous deployment trigger—consumes the completed build's artifact, not because build-completion logic promotes the original artifact through release stages.
Visual reference
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Artifact
An artifact is any file or package produced during the software development process that is used to deploy, test, or run an application.
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
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 →
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.