A logistics company wants image compliance and configuration for dozens of Nexus switches from one place, rather than a console session on each switch. Which platform service matches?
Select an answer to reveal the explanation.
Short Explanation
Nexus Dashboard is a balcony that looks over the whole yard. You use its fabric controller service when the logistics company wants one place to handle images and configuration for dozens of switches. An applet on each box is still a per-switch tool, and it will not give you that single balcony.
Full Explanation
Nexus Dashboard hosts the fabric controller service that manages an NX-OS fabric: image compliance, configuration, and inventory across many switches, without a console session on each one. That is the platform service that matches a logistics estate of dozens of switches. An EEM applet reacts to an event on the switch where it is configured. Deploying applets one by one is still per-switch automation, and a syslog trigger is not a fabric-wide compliance service. POAP provisions a switch at first boot when startup configuration is missing. It does not continuously enforce image compliance on a live fabric. SPAN copies frames to an analyzer. Those frames are not the running configuration, and a SPAN destination does not push images or policy. Caveat: the dashboard service programs the switches, and the switches still forward on their own if the dashboard is later unreachable. Operational check: open the fabric controller inventory, confirm the logistics switches are managed there, and confirm an image-compliance result covers the group rather than a single CLI session.