A media company wants an XML export of service profiles, pools, and policies that an engineer can read. A binary snapshot of the whole fabric interconnect domain is not required. Which backup matches that request?
Select an answer to reveal the explanation.
Short Explanation
A logical backup is the readable blueprint, and a full-state backup is a photograph of the whole building. You export the logical configuration when you want XML of the profiles, pools, and policies. The full-state file is a binary snapshot, not that XML.
Full Explanation
UCS logical configuration backup is an XML export of the service profiles, pools, policies, and related logical objects. That is the file the media company can open and read when they do not need a binary image of the entire domain. Full-state backup is a binary snapshot of the fabric interconnect state. It is the right tool for restoring a domain image, and it is not a readable XML document of just the profiles, pools, and policies. An NX-OS checkpoint stores the configuration of the Nexus it was taken on. It does not contain UCS service profiles. Traffic monitoring on a fabric interconnect copies frames for analysis. It does not export policy objects. Caveat: a logical backup does not capture everything a full-state snapshot holds, so it is the wrong file if the goal is to rebuild a failed fabric interconnect exactly as it was. Operational check: export the logical configuration, open the XML, and confirm the service profiles, pools, and policies are present before you archive it with the change record.