Cisco 350-601 Practice Test - Questions Answers, Page 12

DCNM (Data Center Network Manager) is a UI-based infrastructure management system that meets the requirements of the question. DCNM can monitor and deploy standardized VXLAN BGP EVPN deployments across multiple Cisco Nexus switches, using predefined templates and workflows. DCNM can also manage Cisco MDS 9000 series switches, providing visibility and control over the storage network. DCNM supports various features and functions for both LAN and SAN environments, such as configuration, provisioning, monitoring, troubleshooting, automation, and security. DCNM is a comprehensive and scalable solution for data center network management.

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 8: Data Center Automation and Orchestration, Lesson 8.1: Cisco Data Center Network Manager

[Cisco Data Center Network Manager 11.x Data Sheet], which provides an overview of DCNM features and benefits.

The preserve identities feature is not included in the logical configuration backup operation type. This type of backup includes the configuration settings that are logically grouped, such as service profiles, policies, and pools, but does not include the unique identifiers or configurations that are specific to a particular system or setup, which are preserved in a full state or system configuration backup.

To ensure that the Cisco Nexus 7000 series switches are the primary devices for LACP, the configuration must use thelacp system-prioritycommand to assign a lower priority value to the switches. This command determines which device is the active partner in an LACP negotiation. The lower the priority value, the higher the preference. In option A, the switches have a priority value of 1, which is the lowest possible value and the highest preference. Therefore, option A is the correct configuration to make the switches the primary devices for LACP.

To enable port security on all Cisco MDS series switches in the fabric and avoid the extensive manual configuration of the switch ports, the network engineer must activate the CFS (Cisco Fabric Services) distribution and enable the auto-learning port security feature on a per-VSAN basis. CFS is a protocol that allows the switches to distribute and synchronize configuration information across the fabric. By activating the CFS distribution for port security, the network engineer can propagate the port security configuration to all the switches in the fabric automatically, without having to configure each switch individually. The auto-learning port security feature allows the switches to learn and store the port security information of the devices that are already logged in and authorized on the ports, and prevent any unauthorized devices from logging in. The auto-learning port security feature can be enabled on a per-VSAN basis, which means that the port security information is specific to each VSAN and does not affect other VSANs. This provides more flexibility and granularity for the port security configuration.Reference:=

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 7: Data Center Storage Connectivity, Lesson 7.3: Fibre Channel Protocol

Cisco MDS 9000 Family NX-OS Security Configuration Guide, Chapter: Configuring Port Security

A Cisco All-Flash HyperFlex solution requires two solid state drives (SSDs) for the local storage configuration of the operating system and persistent logging. The SSDs are used to store the hypervisor, the HyperFlex controller VM, and the system logs. The SSDs also provide high performance and reliability for the system operations. The SSDs are configured in a RAID 1 mirror mode, which provides redundancy and fault tolerance. The SSDs are separate from the data storage drives, which are also SSDs in an All-Flash HyperFlex solution.Reference:=

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 4: Cisco HyperFlex, Lesson 4.1: Cisco HyperFlex Overview

Cisco HyperFlex Systems Installation Guide for Cisco Intersight, Chapter: Cisco HyperFlex System Requirements

To meet the requirements of using the secondary interface and then falling back to the primary interface when it becomes available again, the engineer should enable the Uplink failover option in the vNIC properties of the Cisco UCS Cisco Integrated Management Controller (CIMC) network adapter for a standalone Cisco C-Series server. The Uplink failover option allows the vNIC to switch to the secondary interface in case of a failure in the primary interface, and then switch back to the primary interface when it recovers. The Uplink failover option also allows the engineer to configure the Fallback Timeout value, which determines how long the vNIC waits before switching back to the primary interface. In this case, the Fallback Timeout value is set to 600 seconds, which means the vNIC will wait for 10 minutes before falling back to the primary interface.Reference:=

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 5: Cisco Unified Computing System, Lesson 5.3: Cisco UCS C-Series Servers

Cisco UCS C-Series Servers Integrated Management Controller GUI Configuration Guide, Release 4.0, Chapter: Configuring Network-Related Settings and Features, Section: Configuring vNICs

To prevent data corruption due to cross fabric communication in an FCoE environment, the network engineer must apply the configuration Switch(config)#fcoe fcmap 0e,fc,2a to the Cisco Nexus Unified Switches. This configuration sets the FCoE MAC address prefix (fcmap) to a custom value of 0e,fc,2a, which is different from the default value of 0e,fc,00. The fcmap is used to identify the FCoE traffic and map it to the corresponding Fibre Channel ID (FCID). By using a custom fcmap, the network engineer can avoid the possibility of FCID conflicts or overlaps between different FCoE fabrics, which can cause data corruption or loss. The custom fcmap must be configured on all the switches in the same FCoE fabric, and must be unique across different FCoE fabrics.Reference:=

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 7: Data Center Storage Connectivity, Lesson 7.4: FCoE Protocol

Cisco Nexus 9000 Series NX-OS FCoE Configuration Guide, Release 9.3(x), Chapter: Configuring FCoE, Section: Configuring the FCoE MAC Address Prefix

The Cisco Integrated Management Controller (IMC) is a system management component built into Cisco UCS C-Series servers. When the IMC is upgraded, it disrupts the Keyboard, Video, Mouse (KVM) sessions that are used for remote server management. This is because the IMC upgrade process requires a reboot of the controller, which temporarily disconnects any active KVM sessions. However, it does not affect Cisco UCS Manager, SAN traffic, or data traffic, as these components operate independently of the IMC.

Ansible is an open-source IT automation tool that is easy to set up and does not require an agent to be installed on target devices. It uses a declarative language and can be extended with custom modules written in Python, which aligns well with the IT team's experience. Ansible's agentless architecture and support for Python make it an ideal choice for the company's requirements.