DevNet Associate (DEVASC) v1.0Infrastructure and AutomationHard
A senior network architect is evaluating different approaches for network telemetry. The requirement is for high-frequency, push-based streaming of operational data from thousands of network devices to a central collector, minimizing latency and bandwidth consumption. Which approach is best suited for this scenario?
- ARESTCONF GET operations
- BSNMP Polling
- CCLI Scraping
- DStreaming Telemetry with gRPC
Show answer & explanationAnswer & explanation
Correct answer: D. Streaming Telemetry with gRPC
Streaming Telemetry, particularly using gRPC with Protocol Buffers, is designed for high-frequency, push-based data streaming. It offers significant advantages in terms of efficiency (binary encoding, HTTP/2 multiplexing) and scalability over traditional pull-based methods like SNMP polling or RESTCONF GET, making it ideal for large-scale, low-latency data collection.
Why the other options are wrong
- A. RESTCONF GET is pull-based and uses text-based (JSON/XML) data, which is less efficient for high-volume streaming than gRPC and protobuf.
- B. SNMP Polling is pull-based, less efficient, and can't achieve high frequency or low latency for thousands of devices.
- C. CLI Scraping is highly inefficient, error-prone, and not suitable for programmatic, high-frequency data collection.
Streaming Telemetry
Streaming Telemetry is a modern approach for collecting operational data from network devices, where devices actively push data to collectors at high frequency, often using efficient protocols like gRPC.
- Push-based data model.
- High frequency and granularity.
- Efficient data encoding (e.g., Protocol Buffers).
- Uses protocols like gRPC or NETCONF/RESTCONF subscriptions.
Memory trick: Telemetry methods vary by push/pull, frequency, and efficiency.