- A
Call the Azure DevOps REST API from a custom script in the pipeline to capture telemetry.
Why wrong: Possible but not the recommended approach; Analytics is built for this.
- B
Run the Azure DevOps CLI command 'az devops telemetry publish' in a build task.
Why wrong: No such CLI command exists.
- C
Use the built-in 'Pipeline Telemetry' dashboard in Azure DevOps.
Why wrong: Built-in charts are pre-defined and cannot be customized.
- D
Use the Azure DevOps Analytics OData endpoint to query pipeline telemetry and send to Application Insights via a release task.
OData provides structured telemetry data that can be streamed.
AZ-400 Implement an instrumentation strategy Practice Question
This AZ-400 practice question tests your understanding of implement an instrumentation strategy. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Your team uses Azure DevOps for CI/CD. You need to ensure that every build publishes telemetry to Application Insights, including build duration, test pass rate, and deployment frequency. Which approach should you use?
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
Use the Azure DevOps Analytics OData endpoint to query pipeline telemetry and send to Application Insights via a release task.
Option D is correct because the Azure DevOps Analytics OData endpoint provides a standardized, queryable interface to pipeline telemetry data (build duration, test pass rate, deployment frequency). By using a release task to query this endpoint and forward the data to Application Insights, you can instrument your CI/CD pipeline to send custom telemetry without relying on manual scripting or unsupported commands. This approach aligns with the 'Implement an instrumentation strategy' domain by leveraging Azure DevOps Analytics and Application Insights integration.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Call the Azure DevOps REST API from a custom script in the pipeline to capture telemetry.
Why it's wrong here
Possible but not the recommended approach; Analytics is built for this.
- ✗
Run the Azure DevOps CLI command 'az devops telemetry publish' in a build task.
Why it's wrong here
No such CLI command exists.
- ✗
Use the built-in 'Pipeline Telemetry' dashboard in Azure DevOps.
Why it's wrong here
Built-in charts are pre-defined and cannot be customized.
- ✓
Use the Azure DevOps Analytics OData endpoint to query pipeline telemetry and send to Application Insights via a release task.
Why this is correct
OData provides structured telemetry data that can be streamed.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may assume Azure DevOps has a built-in 'telemetry publish' command or dashboard that directly sends data to Application Insights, but in reality, you must use the Analytics OData endpoint as an intermediary to extract and forward pipeline telemetry.
Trap categories for this question
Command / output trap
No such CLI command exists.
Detailed technical explanation
How to think about this question
The Azure DevOps Analytics OData endpoint exposes pipeline run data in a structured format (e.g., tables like PipelineRun, TestResult) that can be queried using OData syntax. A release task can use an HTTP request to fetch this data, then transform and send it to Application Insights via its REST API (e.g., using the TrackEvent or TrackMetric endpoints). This approach ensures that telemetry is captured consistently across builds and can be correlated with application performance data in Application Insights, enabling unified dashboards and alerts.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Implement an instrumentation strategy — study guide chapter
Learn the concepts, then practise the questions
- →
Implement an instrumentation strategy practice questions
Targeted practice on this topic area only
- →
All AZ-400 questions
913 questions across all exam domains
- →
Microsoft Azure DevOps Engineer Expert AZ-400 study guide
Full concept coverage aligned to exam objectives
- →
AZ-400 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related AZ-400 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Configure processes and communications practice questions
Practise AZ-400 questions linked to Configure processes and communications.
Design and implement source control practice questions
Practise AZ-400 questions linked to Design and implement source control.
Design and implement build and release pipelines practice questions
Practise AZ-400 questions linked to Design and implement build and release pipelines.
Develop a security and compliance plan practice questions
Practise AZ-400 questions linked to Develop a security and compliance plan.
Implement an instrumentation strategy practice questions
Practise AZ-400 questions linked to Implement an instrumentation strategy.
Design and implement a DevOps infrastructure practice questions
Practise AZ-400 questions linked to Design and implement a DevOps infrastructure.
Design and implement a source control strategy practice questions
Practise AZ-400 questions linked to Design and implement a source control strategy.
AZ-400 fundamentals practice questions
Practise AZ-400 questions linked to AZ-400 fundamentals.
AZ-400 scenario practice questions
Practise AZ-400 questions linked to AZ-400 scenario.
AZ-400 troubleshooting practice questions
Practise AZ-400 questions linked to AZ-400 troubleshooting.
Practice this exam
Start a free AZ-400 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this AZ-400 question test?
Implement an instrumentation strategy — This question tests Implement an instrumentation strategy — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use the Azure DevOps Analytics OData endpoint to query pipeline telemetry and send to Application Insights via a release task. — Option D is correct because the Azure DevOps Analytics OData endpoint provides a standardized, queryable interface to pipeline telemetry data (build duration, test pass rate, deployment frequency). By using a release task to query this endpoint and forward the data to Application Insights, you can instrument your CI/CD pipeline to send custom telemetry without relying on manual scripting or unsupported commands. This approach aligns with the 'Implement an instrumentation strategy' domain by leveraging Azure DevOps Analytics and Application Insights integration.
What should I do if I get this AZ-400 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.