Which data sources are used by NPM to assess path performance and detect issues in network routing?

Which data sources are used by NPM to assess path performance and detect issues in network routing?

• A. SNMP traps
• B. NetPath results and IP SLA
• C. Disk usage only
• D. CPU usage only

Answer: (B)

The data sources used by NPM to assess path performance and detect routing issues are NetPath results and IP SLA measurements. NetPath provides visibility into the actual route packets take between the monitoring point and the destination, showing per‑hop latency, jitter, and loss. This helps pinpoint where a routing problem or slowdown is occurring along the path. IP SLA adds active, synthetic tests between the monitor and the target, measuring metrics such as round‑trip time, packet loss, and jitter over time, which can reveal deteriorations or changes in path performance that static monitoring might miss. Together, they give end‑to‑end visibility of how data travels through the network and where issues arise. SNMP traps are alerts from devices but don’t continuously quantify path performance. Disk usage and CPU usage reflect device health rather than network path characteristics, so they don’t directly provide the path‑level insights needed for routing problems.

The data sources used by NPM to assess path performance and detect routing issues are NetPath results and IP SLA measurements. NetPath provides visibility into the actual route packets take between the monitoring point and the destination, showing per‑hop latency, jitter, and loss. This helps pinpoint where a routing problem or slowdown is occurring along the path. IP SLA adds active, synthetic tests between the monitor and the target, measuring metrics such as round‑trip time, packet loss, and jitter over time, which can reveal deteriorations or changes in path performance that static monitoring might miss. Together, they give end‑to‑end visibility of how data travels through the network and where issues arise.

SNMP traps are alerts from devices but don’t continuously quantify path performance. Disk usage and CPU usage reflect device health rather than network path characteristics, so they don’t directly provide the path‑level insights needed for routing problems.