A sanitation department’s WAN Edges churn counters and path quality quickly, and frequent SNMP polls are loading the devices and still lagging. What is the strongest reason to move those Edges to streaming telemetry?
Select an answer to reveal the explanation.
Short Explanation
Constant SNMP polls are like calling every truck every minute to ask where it is—radio stays busy and you still miss turns. Streaming telemetry lets the Edge push updates when things change. You get fresher numbers without hammering the box.
Full Explanation
Sanitation WAN Edges with rapidly churning counters and path quality suffer under frequent SNMP polls that load devices yet still lag. Moving those Edges to streaming telemetry is strongest because push-based subscriptions reduce poll overhead and deliver fresher high-churn metrics than periodic GET/GETBULK cycles. That rationale is the EI justification for telemetry adoption on busy WAN Edges.
Claiming streaming telemetry eliminates the need for any YANG models is false—subscriptions target modeled paths. Saying SNMP cannot measure WAN path quality under any circumstances overstates SNMP’s limits and misses the overhead/freshness argument. Claiming telemetry only works for campus switches and cannot attach to WAN Edges is incorrect for SD-WAN/IOS XE telemetry deployments.
Exam caveat: dial-out vs dial-in, encoding (GPB/JSON), and collector capacity must be planned or you trade SNMP load for collector overload. Operational check: enable a bounded subscription for path-quality sensors on a pilot Edge, compare freshness and CPU versus SNMP polling, then migrate remaining sanitation sites. Keep SNMP as fallback only where telemetry paths are unavailable. Record the chosen control and rejected alternatives in the municipal change record so future on-call engineers understand the failure modes avoided for city services.