Courseiva
Implement an instrumentation strategyeasyMultiple ChoiceObjective-mapped

AZ-400 Implement an instrumentation strategy Practice Question

You need to monitor the health of your Azure Pipeline agents. Which Azure DevOps Analytics view should you use to identify agents that have not reported in the last hour?

⚠ Common exam trap

Candidates may confuse 'Release Analytics' or 'Pipeline Run Analytics' with agent health monitoring, because they assume any analytics view related to pipelines would include agent status, but Azure DevOps separates agent infrastructure health (monitored via the Agent Health dashboard) from pipeline execution analytics.

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

Agent Health dashboard

The Agent Health dashboard in Azure DevOps provides real-time status of pipeline agents, including their last communication timestamp. By filtering for agents that have not reported in the last hour, you can identify unhealthy or disconnected agents. This dashboard directly surfaces agent connectivity and health metrics. Note that this is a dashboard, not an Analytics view like Release Analytics, Test Analytics, or Pipeline Run Analytics.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Agent Health dashboard

    Why this is correct

    The Agent Health dashboard in Azure DevOps provides a real-time view of pipeline agents, including their status (online/offline), enabled state, and the last time the agent contacted the service. It is the appropriate tool for monitoring agent health, as it directly surfaces connectivity and availability issues for both Microsoft-hosted and self-hosted agents.

  • Release Analytics

    Why it's wrong here

    Release Analytics focuses on release pipeline performance and outcomes, such as deployment frequency, success rates, and duration of releases. It does not report on the underlying infrastructure agents that execute those deployments, so it is not suitable for monitoring agent health.

  • Test Analytics

    Why it's wrong here

    Test Analytics is designed to analyze test results, including pass rates, failure trends, and test duration across runs. It contains no information about the health, status, or connectivity of the agents that run the tests, making it irrelevant for agent health monitoring.

  • Pipeline Run Analytics

    Why it's wrong here

    Pipeline Run Analytics provides metrics about pipeline runs, such as queue time, duration, and success/failure patterns. While it may indirectly reflect issues with agents, it is not a designated tool for checking agent status or last contact time; the Agent Health dashboard is the direct source for that information.

Visual reference

Client DHCP Server 1 Discover (broadcast) 2 Offer (IP: 192.168.1.10) 3 Request (I accept) 4 Acknowledge (lease confirmed) DORA — the four-step DHCP lease process

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 →

How Courseiva writes practice questions · Editorial policy

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.