How can NPM assist in monitoring WAN links and identifying congestion points?

• A. By tracking hop-level latency, IP SLA results, and NetPath/NetFlow data, NPM reveals congestion, latency variations, and reliability across WANs
• B. Only monitors LAN traffic
• C. Only monitors DNS resolution
• D. Monitors WAN but cannot show latency

Answer: (A)

Gaining visibility into WAN performance requires measuring where delays happen and what traffic is contributing to them. NPM provides hop-by-hop latency, so you can see the delay introduced at each router along the WAN path and quickly spot where congestion starts. IP SLA results give proactive, synthetic performance metrics—such as round-trip time, jitter, and packet loss—for specific destinations or services, with thresholds and alerts to catch degrading links early. NetPath offers a visual map of the actual route and per-hop performance, letting you see exactly where latency or loss spikes along the path, which is essential for locating congestion points. NetFlow adds flow-level visibility, revealing who is using the bandwidth, which applications are consuming it, and how much data is flowing through each link. Together, these capabilities show congestion, latency variations, and reliability across WANs, providing actionable insight to locate and address bottlenecks.

Other options fall short by either focusing only on LAN, or on DNS, or claiming WAN monitoring without latency visibility, which doesn’t give the full picture needed to identify where congestion lies.