An enterprise network operations team is analyzing complex performance anomalies and telemetry configurations across a hybrid WAN deployment. Match each observed network symptom or monitoring configuration requirement on the left with the correct network performance monitoring metric or protocol mechanism on the right.
- High variation in end-to-end packet delivery delay causing buffer underruns and garbled audio in real-time UDP voice streams despite adequate total bandwidth.Jitter (Packet Delay Variation)
- Exporting statistical packet-header sampling directly from ASIC hardware across high-density 100 GbE core switches without maintaining stateful flow cache tables.sFlow (Sampled Flow Technology)
- Polling infrastructure device metrics with cryptographic user authentication and payload encryption using AES to protect sensitive OID data in transit.SNMPv3 using the USM authPriv Security Level
- Aggregating IP traffic flow statistics based on matching 5-tuple attributes into cached records to identify top bandwidth-consuming applications across Layer 3 interfaces.IPFIX / NetFlow Telemetry
Cevap
The correct pairings are: Packet delay variation affecting VoIP corresponds to Jitter; Stateless hardware packet sampling across 100 GbE interfaces corresponds to sFlow; Authenticated and encrypted OID polling corresponds to SNMPv3 using authPriv; Stateful 5-tuple flow aggregation corresponds to IPFIX / NetFlow Telemetry.
Each observed monitoring requirement correctly maps to its functional metric or protocol: Jitter measures packet arrival time variance; sFlow provides stateless hardware packet sampling for ultra-high-speed links; SNMPv3 authPriv provides authenticated and AES-encrypted management queries; IPFIX/NetFlow aggregates traffic flows based on 5-tuple attributes to identify top talkers.
Adım Adım Çözüm
Anahtar Kavram
Distinguishing Network Performance Metrics, Flow Telemetry, and Secure Device Management Protocols