You are asked for TX and RX traffic statistics for each interface to which an application server is attached. The statistics need to be reported…

The Junos Telemetry Interface (JTI) provides multiple ways to stream data. For high-frequency (every five seconds) reporting of interface traffic statistics, native sensors are the most appropriate and efficient method. Native sensors are compiled into the Junos kernel and push data directly from the line card's forwarding ASIC, minimizing CPU impact on the Routing Engine. This push-based model is ideal for collecting granular, time-sensitive data like per-interface counters, as requested in the scenario. Using native sensors via UDP is the default and most performant method for this use case.

A. gNMI

gNMI is a transport protocol for telemetry, not the data source itself. It can be used to stream data from native sensors or OpenConfig models, but "Native Sensors" is the more specific answer.

B. SNMP

SNMP is a poll-based protocol. Polling every five seconds for numerous interfaces would create significant CPU load on the device and is less scalable and efficient than JTI's push model.

D. OpenConfig

OpenConfig provides standardized data models for telemetry. While it can be used to model interface statistics, "Native Sensors" refers to the high-performance, Junos-specific data source itself.

1. Juniper Networks Documentation, Junos Telemetry Interface User Guide, "Sensor Support". "Junos Telemetry Interface supports two sources for data: Native (Junos-specific) sensors... Native sensors export data for Junos-specific parameters, such as RPD statistics and forwarding engine statistics."

2. Juniper Networks Documentation, Junos Telemetry Interface User Guide, "Understanding the Junos Telemetry Interface". "For native sensors, data is streamed directly from the system software or hardware, such as the line card forwarding ASIC, to the collection server. This method results in more efficient delivery of telemetry data."