Refer to the exhibit. An engineer must troubleshoot an application performance issue using Cisco AppDynamics. Which issue occurred in the application connectivity?

Question

Options

• AThe DNS time was 18 ms on November 14 at 11:41 AM.
• BThe response time was 443 ms on October 14 at 11:56 AM.
• CThe connection time was 9 ms on November 14 at 11:41 AM.
• DThe load time was 28 ms on November 14 at 11: 56 AM.

• A
  11% (5)
• B
  2% (1)
• C
  83% (39)
• D
  4% (2)

Explanation

Option C is correct because connection time is the metric directly tied to application connectivity - it measures the TCP handshake/connection establishment phase between client and server, making it the precise indicator of a connectivity issue. The exhibit shows the connection time spiking to 9 ms on November 14 at 11:41 AM, which is the data point that represents a connectivity anomaly in AppDynamics.

Why the distractors are wrong:

• A (DNS time) - DNS time measures name resolution latency, not the connection itself; it's a pre-connectivity metric.
• B (Response time, October 14) - Response time reflects server-side processing delay, not connectivity; additionally, October 14 is the wrong date per the exhibit.
• D (Load time) - Load time is a holistic end-to-end metric covering the full resource fetch, not specifically connectivity; the timestamp (11:56 AM) also doesn't match the exhibit's anomaly window.

Memory tip: Think "C for Connection = Connectivity." In AppDynamics waterfall metrics, the stages flow DNS → Connection → Response → Load. Connectivity problems live in the Connection phase - if the question uses the word "connectivity," your answer key is the connection time metric.

No community discussion yet for this question.