AZ-400 Implement an instrumentation strategy Practice Question
You are building a comprehensive instrumentation strategy for a large-scale Azure DevOps environment. You need to ensure that all pipeline events (build, release, test) are automatically tracked and correlated with application performance data. Which THREE components should you include?
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
✓
A shared Correlation ID that flows from pipeline to application.
Options A, C, and E are correct. A shared Correlation ID (A) flows from pipeline to application, enabling end-to-end trace correlation. Custom pipeline tasks (C) send telemetry (e.g., build/release events) to Application Insights. The OpenTelemetry SDK (E) emits trace context from the application, which can include the correlation ID. Option B is wrong because Azure Monitor Workbooks are visualization tools, not data collection components. Option D is wrong because Azure Boards is for work item tracking, not pipeline event capture.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
A shared Correlation ID that flows from pipeline to application.
Why this is correct
A shared Correlation ID that flows from pipeline to application is correct because it enables end-to-end traceability, linking build/release pipeline events to application telemetry. This ID is propagated via environment variables or HTTP headers, allowing every log, metric, and trace to be correlated across the CI/CD boundary, which is essential for diagnosing failures that span pipeline and runtime.
- ✗
Azure Monitor Workbooks to visualize pipeline data.
Why it's wrong here
Azure Monitor Workbooks are incorrect because they are an interactive visualization and reporting tool, not a data collection mechanism. While they can display pipeline data if it is already stored in Log Analytics or Application Insights, they do not capture or emit telemetry from the pipeline itself, so they cannot serve as the instrumentation strategy's collection layer.
- ✓
Custom pipeline tasks that send telemetry to Application Insights.
Why this is correct
Custom pipeline tasks that send telemetry to Application Insights are correct because they directly emit pipeline-level events (e.g., task durations, success/failure, resource usage) as custom telemetry. These tasks can be added to Azure Pipelines to capture build and release metrics, enabling monitoring and alerting on pipeline health and performance, which is a core part of a comprehensive instrumentation strategy.
- ✗
Azure Boards to track pipeline run metadata.
Why it's wrong here
Azure Boards is incorrect because it is a work management and agile tracking tool, not a telemetry or diagnostics system. Tracking pipeline run metadata in Azure Boards (e.g., linking work items to builds) is useful for traceability, but it does not collect operational metrics or provide the real-time, event-driven data needed for pipeline instrumentation and monitoring.
- ✓
OpenTelemetry SDK in the application to emit trace context.
Why this is correct
OpenTelemetry SDK in the application to emit trace context is correct because it provides standardized, vendor-neutral application telemetry (traces, metrics, logs) and supports context propagation. When the correlation ID is injected into the trace context, OpenTelemetry ensures that all spans and logs within the application carry that ID, enabling seamless correlation with pipeline events and making the end-to-end visibility possible.
Visual reference
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
DevOps
DevOps is a set of practices that combines software development (Dev) and IT operations (Ops) to shorten the development lifecycle and deliver high-quality software continuously.
Key term
Application Insights
Application Insights is an Azure monitoring service that helps developers detect, diagnose, and understand issues in live web applications by collecting telemetry data like requests, exceptions, and performance counters.
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.