A county asks whether SNMP polling alone is enough for modern leaf-spine health visibility. Which statement best reflects describe-level monitoring practice?
Select an answer to reveal the explanation.
Short Explanation
SNMP is like checking the mailbox every five minutes—you still learn a lot, but a fire alarm that streams every second catches problems the mailman would miss. Modern leaf-spine ops keep polling in the toolkit and add faster telemetry where coarse intervals hide pain. Neither 'SNMP forever alone' nor 'throw SNMP away' is the grown-up answer.
Full Explanation
Classic SNMP polling remains useful, but many county leaf-spine fabrics also need higher-frequency telemetry for counters and events that five-minute polls miss. SNMP alone does not always replace every other monitoring method in EVPN fabrics. Console-only checks do not scale as the sole monitoring method. Modern fabrics are not required to disable SNMP; counters remain exportable. Exam caveat: Describe-level practice is complementary tooling: polling plus faster telemetry where micro-events matter. Operational check: Compare a microburst drop visible in streaming counters versus the same interval’s SNMP sample on a busy uplink. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure.