Drag a concept onto its matching description — or click a concept then click the description.
Compute resource to run jobs
Logical boundary for pipeline phases
Sequence of steps on a single agent
Atomic build or deployment action
Match each Azure Pipeline concept to its definition.
Drag a concept onto its matching description — or click a concept then click the description.
Compute resource to run jobs
Logical boundary for pipeline phases
Sequence of steps on a single agent
Atomic build or deployment action
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Pipeline: A collection of stages that defines the CI/CD process.
The correct matches are: A: Pipeline → 'A collection of stages that defines the CI/CD process' (correct); B: Stage → 'A logical boundary in the pipeline used to group jobs' (correct); C: Job → 'A unit of work that runs on an agent' (correct); D: Task → 'A single operation to perform in a job' (correct). E is incorrect because Pipeline is not a logical boundary; that definition belongs to Stage. F is incorrect because Stage is not a collection of stages; that definition belongs to Pipeline. The most common confusion is swapping the definitions of Pipeline and Stage.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Pipeline: A collection of stages that defines the CI/CD process.
Why this is correct
A pipeline is the highest-level resource in Azure Pipelines, defined in YAML or classic UI, that encapsulates the entire CI/CD workflow. It contains stages that group jobs and tasks, and it controls triggers, variables, and artifact publishing. The pipeline as a whole moves code from commit through build, test, and deployment.
Stage: A logical boundary in the pipeline used to group jobs.
Why this is correct
A stage is a logical boundary inside a pipeline that groups related jobs into a named phase, such as Build, Test, or Deploy to Production. Stages can have conditional execution, approval checks, and deployment strategies, and they run sequentially unless a dependency is defined. This grouping lets teams add security checkpoints between environments.
Job: A unit of work that runs on an agent.
Why this is correct
A job is a unit of work that runs on a single agent (or within an agent pool) and contains an ordered sequence of tasks executing sequentially in the same workspace. Jobs can also be parallelized using a strategy or matrix, but each job remains a discrete execution unit assigned to one agent.
Task: A single operation to perform in a job.
Why this is correct
A task is the smallest unit of work in a pipeline, executed as a single step within a job's ordered sequence. Each task is a packaged script or built-in action with defined inputs, and it either succeeds or fails, immediately affecting the job's outcome. Examples include 'Command line', 'Copy Files', and 'Publish Pipeline Artifact' tasks.
Pipeline: A logical boundary in the pipeline used to group jobs.
Why it's wrong here
This reverses the hierarchy. The definition of a logical boundary used to group jobs actually describes a stage, not a pipeline. A pipeline is the top-level container made up of stages, not the boundary that groups jobs.
Stage: A collection of stages that defines the CI/CD process.
Why it's wrong here
This also reverses the hierarchy. A stage is a logical grouping of jobs (e.g., Build, Test, Deploy), while a pipeline is the top-level collection of stages that defines the entire CI/CD process. The description 'a collection of stages' defines a pipeline, not a stage.
Go deeper
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Task
A Task in Azure DevOps is a predefined, reusable step that performs a specific action during a build or release pipeline, like compiling code or running tests.
Key term
Stage
A stage is a discrete phase in a software development or deployment pipeline where code is built, tested, integrated, or released in a controlled environment.
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 →
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.