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

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 commandspanning-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.

To test connectivity from the guest shell of the NX-OS, the command that should be used isping vrf management [IP address]. This command sends ICMP Echo requests to the specified IP address within the management VRF, which is useful for verifying network connectivity from the guest shell environment.

To monitor traffic between leaf switches in a Cisco ACI network and support filtering traffic from a Bridge Domain or VRF, the configuration must allow for specifying the traffic of interest based on tenant, application, and EPG. Option C,filter tenant t1 application app1 epg epg1, meets these requirements by defining a filter that targets traffic from a specific EPG within an application profile in the tenant 't1'. This filter can be applied to the monitoring session to capture the relevant traffic.

To achieve the goal of creating a new user in the local user database on Cisco UCS Fabric Interconnect that can change the vNIC and vHBA profiles and the fan speed and power redundancy profile of UCS Manager, the engineer needs to assign two roles to the user: server-compute and server-profile. The server-compute role allows the user to configure and manage the compute resources, such as servers, service profiles, pools, and policies. The server-profile role allows the user to configure and manage the network resources, such as vNICs, vHBAs, VLANs, VSANs, and LAN and SAN connectivity policies. These two roles provide the user with the necessary permissions to change the configuration inside UCS Manager version 3.1, as required by the goal.Reference:=

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 5: Cisco Unified Computing System, Lesson 5.3: Cisco UCS Fabric Interconnect and Unified Port Feature

Cisco UCS Manager GUI Configuration Guide, Release 3.1, Chapter: Managing User Accounts, Roles, and Passwords, Section: Creating User Accounts

https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-manager/GUI-User-Guides/Admin-Management/3-1/b_Cisco_UCS_Admin_Mgmt_Guide_3_1/b_UCSM_Admin_Mgmt_Guide_chapter_01.html

Cisco Fabric Services (CFS) utilizes IPv4 multicast addresses to disseminate configuration information across network devices. This ensures that all devices within the network have consistent and synchronized configuration data, which is crucial for maintaining the integrity and stability of the network.

Upgrading the EPLD on a Cisco Nexus switch is a disruptive process that requires the switch to reboot multiple times. Each EPLD device on the switch must be upgraded individually, and the switch must reboot to initialize the new EPLD version for each device. This process ensures that all hardware components are properly updated and can operate with the new firmware, but it does cause temporary disruptions to network traffic as each module reboots.

To meet the requirements of performing a backup and restore of the Cisco Nexus 5000 Series Switch configuration using UDP as the only protocol, the network engineer must follow these steps:

Perform a startup-config backup to a TFTP server. The startup-config file contains the configuration that is applied when the switch boots up. To backup this file to a TFTP server, the engineer can use the copy startup-config tftp: command, and specify the IP address or hostname of the TFTP server and the destination filename. For example:

switch# copy startup-config tftp: Enter hostname for the tftp server: 10.10.10.10 Enter destination filename: backup-config

Copy backup-config from the backup server to the running-config file. The running-config file contains the configuration that is currently active on the switch. To restore this file from the backup-config file on the TFTP server, the engineer can use the copy tftp: running-config command, and specify the IP address or hostname of the TFTP server and the source filename. For example:

switch# copy tftp: running-config Enter hostname for the tftp server: 10.10.10.10 Enter source filename: backup-config

These steps will allow the engineer to backup and restore the switch configuration using UDP as the only protocol, as TFTP is a UDP-based protocol. The backup-config file can be used when the current working configuration of the switch gets corrupted, as required by the goal.Reference:=

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 3: Data Center LAN Network Connectivity, Lesson 3.6: Cisco Nexus 5000 Series Switches

Cisco Nexus 5000 Series NX-OS Fundamentals Configuration Guide, Release 5.2(1)N1(1), Chapter: Configuring System Files, Section: Copying a Configuration File to a Remote Server Using TFTP, FTP, SFTP, or SCP

In a vPC (Virtual Port-Channel) configuration, multicast traffic is handled based on the vPC design and operational rules. When a host sends traffic to a multicast group, the vPC switches determine the forwarding path based on the source and the vPC domain configuration. If multicast traffic is received on a vPC member port, such as Po10 on Switch1, the traffic is typically forwarded out on all ports that are part of the same VLAN and have receivers interested in the multicast group, which includes Po1 and Po20 in this case. This ensures that the multicast traffic reaches all intended recipients across the vPC domain.

To ensure that the Cisco Nexus 7000 series switches are the primary devices for LACP, the system priority needs to be configured with lower values indicating higher priority. In this case, setting N7K_A with a system priority of 100 and N7K_B with a system priority of 200 ensures that N7K_A has a higher priority and becomes the primary device for LACP. The system priority is used in the LACP system ID which determines the LACP priority; the lower the value, the higher the priority.