The operations desk sees a warehouse switch stop answering polls. The dashboard marks it down. Nobody compared its configuration, and utilization is blank because it cannot be reached. Which monitoring reported that?
Select an answer to reveal the explanation.
Short Explanation
The dashboard is not telling you the recipe changed or which conversations were busy. It is telling you the switch stopped answering, the way a store light tells you the shop is closed, and that up-or-down check is availability monitoring. You cannot read utilization from a device you cannot reach.
Full Explanation
Availability monitoring tests whether a device or path is up, commonly by polling it, and raises a down state when the device stops answering. The warehouse switch stopped answering, the dashboard marks it down, and utilization is blank because the device cannot be reached. That is an availability signal. Configuration monitoring compares a configuration with a baseline. The stem says nobody did that comparison, and a config diff is not how a poll failure is detected. A cable certification test measures a run at install time. It does not mark a live switch down on an operations dashboard. Flow export describes conversations and volume. It is useful for performance and for seeing who talked to whom. A device can be declared down from a failed poll with no flow records at all. Exam caveat: a single missed poll can be a false alarm, so most systems wait for several failures or a second path before paging. Operational check: confirm the poll fails from the monitoring station, then check the switch's power, uplink, and management address before you treat it as a configuration drift.