MS-700 Monitor, Report on, and Troubleshoot Teams Practice Question
Which TWO of the following are common indicators in the Call Analytics 'Advanced' view that a call was impacted by a poor local network connection?
⚠ Common exam trap
MS-700 often tests the distinction between network-layer indicators (RTT, packet loss, jitter) and endpoint or service indicators (CPU, client version) — candidates pick CPU utilization because it 'sounds like' a performance problem, but the question specifically asks about local network connection issues.
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
✓
High round-trip time (RTT)
High round-trip time (RTT) (Option A) is a correct indicator because elevated RTT in the Call Analytics Advanced view reflects latency on the local network path, meaning packets are taking too long to traverse the connection and degrading real-time media quality. High packet loss (Option C) is also correct because lost packets on the local network directly cause audio/video gaps, jitter, and retransmissions that Call Analytics flags as network-related call quality problems. The other options do not belong: CPU utilization over 90% (B) points to endpoint resource exhaustion rather than a network connection issue, low participant count (D) is simply a call size metric and not a quality indicator, and an unsupported client version (E) is a compatibility/software issue unrelated to local network conditions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
High round-trip time (RTT)
Why this is correct
A high RTT indicates significant network latency. When this value exceeds thresholds, it suggests the local network is struggling to handle the traffic or the ISP route is heavily congested, which directly leads to audio delays and choppy video during a Teams session.
- ✗
CPU utilization over 90%
Why it's wrong here
While high CPU can cause stuttering, it is an endpoint performance issue rather than a network connection issue. It does not manifest as network packet loss or high RTT, which are the metrics specifically used to diagnose local network instability in Call Analytics.
- ✓
High packet loss
Why this is correct
Packet loss is a primary indicator that the network cannot maintain a steady media stream. If the loss occurs between the client and the first network hop, it is a definitive sign of local congestion or an unstable wireless connection affecting the stream.
- ✗
Low participant count
Why it's wrong here
The number of participants is a contextual detail rather than a quality metric. A call can be high quality with many participants or low quality with only two, meaning participant count provides no diagnostic value for investigating network connectivity or packet loss issues.
- ✗
Unsupported client version
Why it's wrong here
Using an unsupported client can cause compatibility issues, but it is not a network quality metric. Reporting an unsupported version does not explain high packet loss or latency; those issues are infrastructure-driven and occur regardless of the specific client version being utilized.
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.