Which protocol is a sampling-based network traffic monitoring protocol that works across manufacturers?

Which protocol is a sampling-based network traffic monitoring protocol that works across manufacturers?

• A. IPFIX
• B. NetFlow
• C. sFlow
• D. Latency

Answer: (C)

The concept being tested is a protocol that provides visibility into network traffic by sampling packets and exporting that data in a way that works across different manufacturers. sFlow does this directly: it places a lightweight agent on devices to randomly sample packets on interfaces, pairs each sample with metadata, and sends the data to a central collector. This collector can be on gear from many vendors, giving you a unified view of traffic across a mixed network with minimal overhead. That vendor-agnostic, sampling-based approach is what makes sFlow ideal for cross-manufacturer monitoring. NetFlow is a well-established flow-export approach, and IPFIX is its standardized evolution. Both can be used for network visibility, but the key distinction here is the explicit sampling model. sFlow’s design centers on sampling across devices from different vendors, which is why it’s the best fit for cross-manufacturer monitoring. Latency, by contrast, is a metric, not a protocol for exporting traffic data.

The concept being tested is a protocol that provides visibility into network traffic by sampling packets and exporting that data in a way that works across different manufacturers. sFlow does this directly: it places a lightweight agent on devices to randomly sample packets on interfaces, pairs each sample with metadata, and sends the data to a central collector. This collector can be on gear from many vendors, giving you a unified view of traffic across a mixed network with minimal overhead. That vendor-agnostic, sampling-based approach is what makes sFlow ideal for cross-manufacturer monitoring.

NetFlow is a well-established flow-export approach, and IPFIX is its standardized evolution. Both can be used for network visibility, but the key distinction here is the explicit sampling model. sFlow’s design centers on sampling across devices from different vendors, which is why it’s the best fit for cross-manufacturer monitoring. Latency, by contrast, is a metric, not a protocol for exporting traffic data.