A logistics company wants to claim new rack servers and stamp them from one set of policies through an external API, rather than configuring each server's local controller by hand. Which product is that automation plane?
Select an answer to reveal the explanation.
Short Explanation
You can manage new rack servers from one front office and give them the same packet of rules as their neighbors. Intersight lets you claim each server and apply policies through a server profile. NX-API configures a Nexus switch, but creating a VLAN there does not claim a rack server.
Full Explanation
Intersight is the cloud operations plane for UCS compute. You claim a new rack server, define firmware, boot, and network intent in policies, and use a server profile to apply that intent to the hardware. These objects are exposed through the Intersight API, providing the external automation path the logistics company needs. NX-API is a programmatic interface to a Nexus switch; creating a VLAN does not discover or claim a server, and NX-API has no server-profile object. The onboard scheduler runs CLI on a switch at a set time; it does not own a server inventory or push a server profile to a rack server. An MDS device-alias database maps friendly names to Fibre Channel port WWNs; it does not store a compute claim, boot policy, or server profile. One caveat: a claimed server still needs its device connector to be reachable, and a profile that references a missing policy will not finish deployment just because the API call was accepted. For a practical check, claim one new serial number, assign a server profile built from the shared policies, and confirm that the server shows the profile as deployed rather than merely showing a local controller login.