Refer to the exhibit. An employee working from home reports that his application performance is poor occasionally. A NOC operator opens Cisco ThousandEyes and investigates the employee's Endpoint…

Question

Options

• Alow Wi-Fi signal strength
• BISP network problem
• Cexcessive bandwidth usage on the user's router
• Dpoor application server performance

• A
  8% (3)
• B
  73% (29)
• C
  5% (2)
• D
  15% (6)

Explanation

In a ThousandEyes Endpoint Agent investigation, the path visualization and network metrics would reveal latency spikes or packet loss specifically at ISP hops - the segment between the user's home router and the destination - pointing clearly to an ISP network problem as the root cause of intermittent poor performance.

Why the distractors are wrong:

• A (low Wi-Fi signal): ThousandEyes reports local wireless metrics separately; if Wi-Fi signal were the culprit, you'd see poor RSSI/SNR values in the local network section, not degradation in the network path hops.
• C (excessive bandwidth usage): Router congestion would appear as high local network utilization or increased round-trip time at the first hop, which the exhibit does not indicate.
• D (poor application server performance): Server-side issues would degrade performance for all users simultaneously, not just one remote employee, and would show up as high server response times rather than mid-path packet loss.

Memory tip: Think of ThousandEyes as a "blame the layer" tool - it isolates problems into three buckets: local (Wi-Fi/device), network path (ISP/middle mile), and server (application). When the exhibit shows clean local metrics and clean server metrics but trouble in the hops in between, the ISP is the culprit.

No community discussion yet for this question.