A national retailer wants interface counters delivered every minute to a collector. The collector must not poll, and a quiet interface must still report. Which subscription matches?
Select an answer to reveal the explanation.
Short Explanation
A cadence subscription is a postcard that goes out on the clock, even when the room is quiet. You have the switch push interface counters every minute, and the collector does not have to knock. An event-driven feed stays silent until something changes, which misses the quiet interfaces this store still wants reported.
Full Explanation
Streaming telemetry pushes data to a collector on a subscription. A periodic cadence sends a sample on a timer, so a quiet interface still reports every minute and the collector does not poll the switch. That is the retailer's requirement. Event-driven telemetry sends an update when the subscribed value changes. A quiet interface that does not change can produce no sample, so it fails the rule that quiet ports must still report. SNMP is a pull model: the collector asks the switch on each interval. Even a one-minute poll is still a poll, which the retailer ruled out. SPAN copies frames to an analyzer. The collector would be reconstructing counters from packets instead of receiving the interface statistics the switch already keeps. Caveat: the cadence you configure is the reporting interval, and a very aggressive interval on many sensors can load the collector even though the model is right. Operational check: confirm the collector receives a sample from an idle test interface at each interval without issuing an SNMP request.