AZ-400 Practice Question: Design and implement build and release pipelines
Which TWO features of Azure Pipelines help you manage build artifacts across stages? (Choose two.)
⚠ Common exam trap
Watch out — candidates often confuse pipeline variables (which pass simple values) with artifact tasks (which pass files), or mistakenly think release gates or build tags have a role in artifact management across stages.
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
✓
Download Pipeline Artifact task
The Publish Pipeline Artifact task (option E) makes files available to subsequent stages by uploading them to Azure Pipelines, while the Download Pipeline Artifact task (option D) retrieves those artifacts in later stages. Together, they form the primary mechanism for passing build outputs across stages in a pipeline.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Pipeline variables
Why it's wrong here
Pipeline variables store configuration values and settings that parameterize pipeline runs, but they do not manage build artifacts themselves. They are scoped to pipeline execution and cannot publish, store, or retrieve the binary outputs produced by a build.
- ✗
Release gates
Why it's wrong here
Release gates evaluate health signals—such as incident management, work item queries, or test results—before or after a release deployment, and they are used for release validation rather than build artifact management. They do not handle or store build outputs.
- ✗
Build tags
Why it's wrong here
Build tags are metadata labels that you apply to pipeline runs to filter, organize, and query historical builds, but they do not manage the actual build artifacts. Tags simply classify or annotate a build, not publish or consume its output files.
- ✓
Download Pipeline Artifact task
Why this is correct
The Download Pipeline Artifact task is correct because it downloads pipeline artifacts from a previous build or pipeline run into the current job, enabling the job to consume build outputs that were published earlier. This task is a fundamental part of managing build artifacts across stages and pipelines.
- ✓
Publish Pipeline Artifact task
Why this is correct
The Publish Pipeline Artifact task is correct because it uploads files or directories as pipeline artifacts, making them available for download by subsequent jobs, stages, or releases. This task is the primary method for storing and sharing build outputs within Azure Pipelines.
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Pipeline
A pipeline is an automated series of steps that takes code from development to production, ensuring quality and speed.
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.
About these practice questions
One of 823 original AZ-400 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.