Which WAN analysis component helps identify where congestion occurs along the path?

Which WAN analysis component helps identify where congestion occurs along the path?

• A. End-user device on-site
• B. NetPath provides path topology and latency information to identify where in the path congestion occurs
• C. Only routers provide congestion data
• D. DNS servers are used to measure WAN performance

Answer: (B)

Understanding end-to-end visibility is key for pinpointing where congestion sits on a WAN path. NetPath gives you the path topology and latency information across the entire route from source to destination, showing each hop and its performance. By seeing how latency or packet loss changes at specific points along the path, you can identify exactly where congestion occurs. Other options don’t provide this end-to-end, hop-by-hop view. an on-site end-user device reflects only the local connection, not the whole WAN path. DNS servers measure name-resolution timing, not WAN link congestion. Relying on routers alone doesn’t give a complete picture of performance across the entire path. NetPath’s path-focused visibility is what lets you locate bottlenecks along the route.

Understanding end-to-end visibility is key for pinpointing where congestion sits on a WAN path. NetPath gives you the path topology and latency information across the entire route from source to destination, showing each hop and its performance. By seeing how latency or packet loss changes at specific points along the path, you can identify exactly where congestion occurs.

Other options don’t provide this end-to-end, hop-by-hop view. an on-site end-user device reflects only the local connection, not the whole WAN path. DNS servers measure name-resolution timing, not WAN link congestion. Relying on routers alone doesn’t give a complete picture of performance across the entire path. NetPath’s path-focused visibility is what lets you locate bottlenecks along the route.