Operations wants continuous interface counters from IOS XE civic edge routers without walking MIBs on a timer. Which statement correctly describes model-driven telemetry versus classic polling?
Select an answer to reveal the explanation.
Short Explanation
Polling is asking “how’s the river?” every few minutes; telemetry is the river sending you readings you subscribed to. MDT streams YANG-modeled data—it is not SNMP GET in a new hat.
Full Explanation
Model-driven telemetry (MDT) streams subscribed YANG-modeled data from devices to collectors; classic SNMP GET polling is the operational contrast. For continuous interface counters from IOS XE civic edge routers without walking MIBs on a timer, MDT subscriptions push or stream the modeled fields on cadence or on-change, while SNMP polling would repeatedly pull MIB objects from an NMS schedule. That distinction is the consumption starting point for DEVCOR telemetry items.
Claiming MDT is identical to periodic SNMP GET of MIB objects fails: different models, encodings, and session paradigms. Saying MDT only works if SNMP community strings are embedded in each YANG leaf mixes unrelated access mechanisms into YANG paths. Asserting SNMP polling publishes YANG subscriptions dial-out to collectors reverses the relationship—SNMP poll is pull; dial-out telemetry is device-initiated streaming of configured subscriptions.
Exam caveat: MDT can use dial-out or dial-in transports; the scored contrast remains streaming subscribed YANG versus SNMP polling. NETCONF or RESTCONF may configure subscriptions, but that is not the same as an SNMP walk loop.
Operational check: enable a simple interface-counter subscription to a lab collector and confirm streaming updates arrive without an NMS timer issuing SNMP GETs for those same counters.