350-601 Questions Bank

 A logical configuration backup is needed to back up user roles and locales from Cisco UCS Manager. This type of backup allows the engineer to replicate settings, including user roles and locales, to a different fabric interconnect. The file can be reviewed before importing it to the target fabric interconnect. References:

• [Cisco UCS Manager Backup and Restore Management Guide, Release 4.0 - Backup and Restore Overview [Cisco UCS Manager]], Backup and Restore Overview, Backup Types
• [Cisco UCS Manager Backup and Restore Management Guide, Release 4.0 - Backup and Restore Overview [Cisco UCS Manager]], Backup and Restore Overview, Logical Configuration Backup

To prevent loops from occurring accidentally on a switch interface designated for host connectivity, the best practice is to enable Spanning Tree Protocol (STP) protections. Option A, which includes the command spanning-tree guard loop, is the correct configuration to apply. This command enables Loop Guard, a feature that prevents alternate or root ports from becoming designated ports due to a failure that leads to a unidirectional link. If a port stops receiving Bridge Protocol Data Units (BPDUs), Loop Guard puts the port into an STP loop-inconsistent state, effectively preventing potential loops.

References := This information is aligned with the best practices for loop prevention as described in Cisco’s Data Center Core Technologies materials. For further details, refer to the study guide or source documents related to STP and its security features within the Cisco Data Center Core Technologies curriculum.

Puppet, an open-source configuration management tool, requires the Open Agent Container (OAC) to run on Cisco NX-OS. The OAC provides a contained environment where third-party agents like Puppet can run without affecting the host NX-OS system.

References: The requirement for OAC when using Puppet in a Cisco NX-OS environment is outlined in the Cisco NX-OS Puppet Configuration Guide, which explains the integration of Puppet with Cisco NX-OS and the necessary components.

 In a Cisco HyperFlex Edge deployment, the witness VM, known as the “Invisible Cloud Witness,” resides within Cisco Intersight. This cloud-based platform eliminates the need for a dedicated witness VM by providing a virtual witness as a service, which simplifies the deployment and ongoing operations of HyperFlex Edge clusters1234.

References:

• Cisco HyperFlex Edge Deployment Guide, Release 5.0(x)1.
• Cisco HyperFlex Systems Installation Guide for VMware ESXi, Release 5.02.
• Cisco Blogs on HyperFlex and Intersight3.
• Cisco’s official page on HyperFlex for Edge Environments