A user reports slow access to a cloud application. The switch shows normal CPU utilization. What should be checked next?

Question

Options

• AEnd-to-end latency
• BSTP configuration
• CQoS policies
• DVLAN assignments

• A
  73% (16)
• B
  5% (1)
• C
  14% (3)
• D
  9% (2)

Explanation

End-to-end latency (A) is the right next step because slow cloud application access is a performance problem that spans multiple network hops - measuring latency across the full path (client → network → cloud) pinpoints exactly where the delay is occurring, whether in the WAN, ISP, or cloud provider side.

Why the distractors are wrong:

• B (STP): Spanning Tree Protocol affects Layer 2 loop prevention and convergence. Since the switch CPU is normal, STP isn't thrashing - and STP issues typically cause outages or instability, not just slowness.
• C (QoS): QoS is worth investigating eventually, but it's a specific configuration fix. You wouldn't jump to tuning QoS before first confirming where the latency exists.
• D (VLAN assignments): Misconfigured VLANs would likely cause connectivity failures or incorrect segmentation, not subtle slowness to a cloud app.

Memory tip: Think of troubleshooting like a doctor - before prescribing a fix (QoS, VLANs, STP), you need a diagnosis. "Slow cloud access" = measure the path first with end-to-end latency, then narrow down the sick segment.

No community discussion yet for this question.