MS-700 Monitor, Report on, and Troubleshoot Teams Practice Question
You are a Teams administrator. A user reports that during a Teams meeting, their audio was choppy and they experienced delays. You need to determine whether the issue was caused by network latency or by the user's device. Which Call Analytics metric should you review first to assess network latency?
⚠ Common exam trap
It's easy for candidates to confuse jitter with latency; jitter is variation in delay, while RTT is the actual delay.
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
✓
Round-trip time (RTT)
Round-trip time (RTT) is the metric that directly measures network latency. In Call Analytics, RTT is shown for each participant and indicates the time for data to travel to the service and back. High RTT values correlate with delays and choppy audio. While jitter and packet loss can also cause audio issues, they are not measures of latency. Therefore, RTT is the correct metric to review first to assess network latency.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Jitter
Why it's wrong here
Jitter measures the variation in packet arrival times, which can cause choppy audio. However, it is not a direct measure of latency. While jitter can contribute to audio issues, the question specifically asks about network latency, which is measured by round-trip time. Jitter is a separate metric that indicates network stability.
- ✓
Round-trip time (RTT)
Why this is correct
Round-trip time (RTT) measures the time it takes for a signal to go from the source to the destination and back. It is the primary metric for network latency. High RTT indicates delays in audio transmission, which matches the user's experience of choppy audio and delays. In Call Analytics, RTT is displayed for each participant and can help identify network latency issues.
- ✗
Packet loss
Why it's wrong here
Packet loss measures the percentage of packets that did not reach their destination. It can cause choppy audio and delays, but it is not a measure of latency. High packet loss would show as missing audio, not necessarily delays. The question asks for a metric to assess network latency, so packet loss is not the primary metric.
- ✗
Audio codec
Why it's wrong here
Audio codec indicates the compression algorithm used for audio. It affects audio quality and bandwidth usage, but it is not a measure of network latency. A codec change might be a mitigation for poor network conditions, but it does not directly indicate latency. The question asks for a metric to assess network latency, so codec is not appropriate.
About these practice questions
One of 211 original MS-700 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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
This MS-700 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 MS-700 exam.