A logistics rack server is claimed in Intersight. A server profile that contains the new BIOS policy is assigned to that server and has not been deployed. The server still runs the previous BIOS. What has not happened?
Select an answer to reveal the explanation.
Short Explanation
You’ve put the work order on the clipboard, but it hasn’t reached the floor. Claiming the server puts it in the account, and assigning a profile names the target; the BIOS policy reaches the server when you deploy that profile, which has not happened.
Full Explanation
An Intersight server profile is a collection of policies, including a BIOS policy. Assignment selects the claimed server, while deployment is the action that pushes those policies onto it. Until deployment succeeds, the server keeps its existing BIOS, which explains why this logistics host still runs the previous version. The server has already been claimed and the profile assigned, so the missing step is not claiming; claiming is what makes assignment possible. NX-API on a leaf programs a Nexus switch, not an Intersight BIOS policy on a rack server. POAP configures a switch that booted without a startup configuration; it does not copy a server BIOS policy into the switch startup configuration. Exam caveat: deploying a profile can reboot the server when the BIOS change requires it, so check the maintenance behavior before deploying during a shift. Practical check: deploy the profile and confirm that the server reports the new BIOS policy rather than the previous one. Watch the deployment result: a profile that remains failed is not the same as a profile that was never deployed, and the BIOS will not change in either case.