Refer to the exhibit. Cisco ThousandEyes sent an alert that an application is unreachable from the Ljubljana office. What is the root cause of the issue?

Question

Options

• AErrors are occurring in the application server.
• BThere is end-to-end network loss.
• CThe Cisco ThousandEyes agent is sending an incorrect payload to the destination.
• DThe network is congested.

• A
  84% (37)
• B
  5% (2)
• C
  9% (4)
• D
  2% (1)

Explanation

Option A is correct because Cisco ThousandEyes performs layered testing - it separately measures network health (latency, packet loss, routing) and application health (HTTP response codes, server errors). When the network path shows no issues but the application layer reports failures (such as 5xx server errors or connection errors at the destination), the root cause is isolated to the application server itself, not the network.

Why the distractors are wrong:

• B (end-to-end network loss): ThousandEyes path visualization would explicitly show packet loss at specific network hops; the exhibit indicates the network is healthy, ruling this out.
• C (incorrect payload): ThousandEyes agents use validated, consistent test configurations - malformed payloads are not a realistic failure mode and would not be indicated in a typical alert exhibit.
• D (network congestion): Congestion appears as elevated latency and jitter across multiple hops in the path view; the exhibit shows no such degradation in the network layer.

Memory tip: Think of ThousandEyes as peeling an onion - it tests from the outside in (network → transport → application). If the outer layers are clean but the core (application server) fails, the problem lives in the application. "Healthy path, broken app = server error."

No community discussion yet for this question.