A media company must rebuild service profiles, pools, and policies on a replacement fabric interconnect pair and wants an importable XML file. Which backup contains that logical configuration?
Select an answer to reveal the explanation.
Short Explanation
A logical export is the typed inventory of profiles, pools, and policies. You import that XML onto the replacement pair to rebuild those objects. A full-state backup is a binary snapshot of system state, not the editable document this rebuild is asking for.
Full Explanation
Cisco UCS logical configuration is an XML export of the logical objects: service profiles, pools, policies, and the related templates and VLAN or VSAN definitions those objects use. That file is what the media company can import to rebuild those objects on a replacement pair. A full-state backup is a binary snapshot of the system, taken for restoring that domain's state. It is not an editable XML document of the profiles and pools, so it does not meet a request for an importable XML file. Traffic monitoring on a fabric interconnect copies frames. A mirror session does not serialize service profiles into a backup file. The chassis discovery policy is one infrastructure setting that controls how many links are required before a chassis is discovered. Exporting that idea, or editing the policy, does not produce the identity pools or the service profiles. Caveat: a logical export omits system settings such as users and authentication, which live in a broader all-configuration XML, so a rebuild of only the logical file still needs those system settings created again. Operational check: import the logical XML on the replacement pair and confirm the profiles, pools, and policies appear before you associate any blade.