Drag a concept onto its matching description — or click a concept then click the description.
SonarQube analysis
Burnup chart
Slack integration on work item update
Terraform task for Azure Pipelines
Match each Azure DevOps extension type to its example.
Drag a concept onto its matching description — or click a concept then click the description.
SonarQube analysis
Burnup chart
Slack integration on work item update
Terraform task for Azure Pipelines
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Build task: NuGet Tool Installer
In this matching exercise, the correct pairs are: Build task → NuGet Tool Installer, Dashboard widget → Sprint Burndown, and Service hook → Notify Slack on build completion. The distractors incorrectly assign Sprint Burndown as a build task and NuGet Tool Installer as a dashboard widget, testing your ability to distinguish between extension types based on their purpose. Build tasks execute during pipeline runs, dashboard widgets display information on dashboards, and service hooks trigger external actions on events.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Build task: NuGet Tool Installer
Why this is correct
NuGet Tool Installer is correctly classified as a build task because it is an executable step that runs inside an Azure Pipelines agent, downloading a specified version of the NuGet client and placing it on the agent's PATH for subsequent tasks like restore or pack. This task is defined in a YAML step or a classic build/release pipeline and participates in the pipeline's execution flow, modifying the agent's tooling state. Unlike read-only dashboard widgets, build tasks are invoked by the pipeline engine and have access to the agent host filesystem, environment variables, and service connections.
Dashboard widget: Sprint Burndown
Why this is correct
Sprint Burndown is a prebuilt Azure DevOps dashboard widget that visualizes remaining work (story points, hours, or count) against the sprint timebox, helping teams track whether they will complete their sprint commitments. It is part of the Analytics or Work widget catalog, not an executable pipeline component, so placing it in a build or release pipeline definition is invalid.
Service hook: Notify Slack on build completion
Why this is correct
Notify Slack on build completion is a service hook because it subscribes to Azure DevOps events—specifically the build.completed event—and sends an HTTP POST to a Slack webhook URL whenever that event fires. Service hooks are event-driven integrations managed at the project or organization level, not steps in a pipeline, so they execute outside the agent within the Azure DevOps service itself. They provide real-time notifications and are ideal for external tool integrations such as Slack, Teams, or Splunk, whereas build tasks run synchronously inside the pipeline as part of an agent job.
Build task: Sprint Burndown
Why it's wrong here
Sprint Burndown is not a build task because build tasks are executable steps that run inside a pipeline (e.g., NuGet Tool Installer, VSBuild, PublishBuildArtifacts) to produce or process artifacts. Sprint Burndown is a dashboard widget that renders a chart from work-tracking data; it cannot be invoked as a step in a YAML or classic build pipeline, so labeling it a build task is incorrect.
Dashboard widget: NuGet Tool Installer
Why it's wrong here
NuGet Tool Installer is not a dashboard widget because widgets are read-only UI components rendered on Azure DevOps team dashboards, not executable tools. NuGet Tool Installer is a build/release task that downloads and installs a specified version of the NuGet client onto the agent host, enabling subsequent build steps to restore packages or push packages with that exact client version.
Go deeper
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Sprint
A Sprint is a time-boxed iteration in Agile project management, typically 2–4 weeks long, during which a development team completes a set of planned work items.
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
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 →
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.