A city NOC needs to know when a leaf-spine link flaps before citizen portal SLAs burn. Which monitoring focus best matches that operational need?
Select an answer to reveal the explanation.
Short Explanation
Citizen portals die when the fabric link flaps—not when next year's license spreadsheet updates. Watch the leaf-spine link state like a bridge sensor that beeps the second a cable goes dark. If you only stare at DNS from a laptop, you miss the actual road that just collapsed.
Full Explanation
Data-center fabric health for leaf-spine designs depends heavily on timely visibility into interface operational state and link flaps on critical uplinks. Catching those events early lets operators restore or fail over before application SLAs for municipal services are breached. License calendars, annual capacity sheets, and client DNS checks do not substitute for fabric link-state monitoring.