A network administrator is investigating high latency from the ThousandEyes Agent to a website. The agent-to-server (HTTP) test results show an increase in network latency at the ThousandEyes…

Question

Options

• AThe agent is overloaded.
• BThe destination website is overloaded.
• CThe agent's default gateway is overloaded.
• DThe network path between the agent's default gateway and the destination is congested.

• A
  8% (2)
• B
  15% (4)
• C
  73% (19)
• D
  4% (1)

Explanation

Option C is correct because ThousandEyes agent-to-server tests measure latency at each hop individually - when the test pinpoints the latency increase specifically at the default gateway, it means that device is where packets are being delayed, which is characteristic of the gateway being overloaded (high CPU, memory pressure, or queue saturation).

Why the distractors are wrong:

• A (agent overloaded): Agent-side overload would manifest as delay before the first hop, not localized to the gateway node itself.
• B (destination overloaded): Destination problems show up as latency at the far end of the path, not at the local gateway near the agent.
• D (path congestion beyond gateway): Mid-path or last-mile congestion would appear as latency increases at hops after the gateway, not at the gateway itself.

Memory tip: Think of ThousandEyes like a speedometer at every intersection - if the slowdown reads on the first intersection (the default gateway), the problem is at that intersection, not the road ahead or the car itself.

No community discussion yet for this question.