A network administrator is evaluating enterprise network telemetry tools and performance metrics. Match each monitoring scenario or metric requirement on the left with the corresponding metric or telemetry mechanism on the right.
- Measuring time variations between packet arrivals that cause choppiness in real-time VoIP callsJitter
- Periodically polling device CPU metrics and interface counters with encrypted payloads and authenticationSNMPv3 authPriv
- Aggregating IP traffic flow statistics, protocol breakdown, and conversation byte counts across router interfacesNetFlow / IPFIX
- Measuring the total elapsed round-trip time required for a packet to travel from source to destination and backLatency
Answer
The correct pairings match packet delay variation to Jitter, authenticated and encrypted metric polling to SNMPv3 authPriv, traffic flow breakdown statistics to NetFlow / IPFIX, and total round-trip travel time to Latency.
Each monitoring scenario directly maps to its corresponding baseline metric or protocol: delay fluctuation in real-time calls is jitter; encrypted/authenticated device polling uses SNMPv3 authPriv; aggregating IP conversation and flow data uses NetFlow/IPFIX; and total transit delay is latency.
Step-by-Step Solution
Key Concept
Network Performance Metrics and Telemetry Mechanisms