AZ-400 Practice Question: Design and implement build and release pipelines
You are designing a release pipeline for a .NET application. The pipeline must deploy to multiple environments (Dev, Test, Prod) with manual approval at each stage. Which release trigger should you configure for the production stage?
⚠ Common exam trap
Many candidates confuse build triggers (like PR or continuous integration) with release triggers, mistakenly applying build automation concepts to production deployment stages where manual approval is required.
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
✓
Manual trigger with pre-deployment approvals.
The requirement specifies manual approval at each stage, and for the production stage, a manual trigger with pre-deployment approvals ensures that deployments only occur after explicit human authorization. This aligns with the need for controlled, gated releases to production, preventing automatic or scheduled deployments that bypass approval.
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 from the main branch.
Why it's wrong here
Pull request triggers are a feature of build pipelines, not release pipelines; release pipelines rely on artifacts from builds or external sources. Even if a PR merged, it would not initiate a release deployment, so it cannot satisfy the requirement for controlled, human-initiated releases.
- ✗
Continuous deployment trigger after a successful build.
Why it's wrong here
Continuous deployment triggers automatically start a release every time a build succeeds, which bypasses any manual approval gate. While convenient for automated delivery, it contradicts the scenario's need for explicit user initiation and pre-deployment approval, so it is not the appropriate trigger type.
- ✓
Manual trigger with pre-deployment approvals.
Why this is correct
A manual trigger requires a user to explicitly initiate the release, and adding pre-deployment approvals ensures that a designated approver must authorize the deployment before it proceeds. This combination gives full human control over when the release starts and enforces a review step, which directly supports the design requirement.
- ✗
Scheduled trigger set to run nightly.
Why it's wrong here
A scheduled trigger runs the release automatically at predefined times, such as nightly, without any manual initiation or approval step. This automation means the deployment would happen unattended, so it cannot enforce the manual approval required in this scenario, making it an incorrect choice.
Visual reference
Go deeper
Related to this question
Learn chapter
Designing a Build Pipeline
Key term
Pipeline
A pipeline is an automated series of steps that takes code from development to production, ensuring quality and speed.
Key term
Release pipeline
A Release pipeline is an automated sequence of steps that takes software from code commit to production deployment, ensuring quality and consistency.
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.