350-601 Exam Dumps - Cisco CCNP Data Center Questions and Answers

The statement that applies to a Cisco Nexus 5600 Series switch when performing a rollback is that errors are skipped when an atomic rollback type is triggered. An atomic rollback is a type of rollback that implements the checkpoint configuration only if no errors occur during the process. If any errors are encountered, the rollback is aborted and the running configuration is restored to its previous state. This ensures that the switch does not end up in a partially configured or inconsistent state. The other statements are not true because:

• A user who is assigned to the network-operator user role cannot perform a rollback. The network-operator user role has read-only access to the switch and cannot modify the configuration. To perform a rollback, the user must have the network-admin or vdc-admin user role.
• The configuration rollback functionality is not disabled when FCoE is enabled. The rollback feature is supported on all Cisco Nexus 5600 Series switches regardless of the FCoE configuration. However, some FCoE-related commands may not be rolled back due to dependencies or conflicts with other features.
• A system checkpoint is not generated automatically when the running configuration is saved to NVRAM. A system checkpoint is a predefined checkpoint that contains the last saved configuration of the switch. A system checkpoint is created or updated only when the user explicitly saves the running configuration to the startup configuration using the copy running-config startup-config command or its alias, copy run start. References: For more details on how to configure and use the rollback feature on a Cisco Nexus 5600 Series switch, please refer to the following resources:
• Configuring Rollback
• Cisco Nexus 5600 Series NX-OS System Management Configuration Guide, Release 7.x
• Cisco Nexus 5600 Series NX-OS System Management Command Reference

 The command aaa authentication login default group ISE local configures the Cisco Nexus Series Switch to use TACACS+ for authentication by default and specifies a fallback to local authentication if the TACACS+ server becomes unavailable. This ensures that users are authenticated against the TACACS+ server when it is available, but allows them to use local switch credentials if the server cannot be reached, meeting the requirement for failover to local account1.

References :=

• Cisco documentation on configuring TACACS+ for Cisco Nexus Series Switches provides detailed steps and explanations for setting up authentication and ensuring failover to local accounts

Table Description automatically generated with low confidence

SPAN (Switched Port Analyzer) is a feature that allows network traffic from one or more source ports to be mirrored to a destination port for analysis. When configuring SPAN on a Cisco Nexus 5000 Series switch, two characteristics must be considered:

• A SPAN source port can be monitored in multiple SPAN sessions. This means that the same port can send traffic to different destination ports for different purposes or applications.
• A SPAN source port cannot be a destination SPAN port. This means that a port cannot receive traffic from another port that it is already monitoring. This prevents loops and conflicts in the SPAN configuration.

References := Configuring SPAN

https://www.cisco.com/en/US/docs/switches/datacen ter/nexus5000/sw/configuration/guide/cli_rel_4_1/Cisco_Nexus_5000_Series_Switch_CLI_Software_Configuration_Guide_chapter50.html

 NFS 4 reduces file locks by using leasing, which is an improvement over the locking mechanisms used in previous versions of NFS like NFS 3 or CIFS/SMB. Leasing allows clients to cache file data locally, reducing the need for frequent and potentially costly network operations. References:

• Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide, Release 9.3(x) - Configuring NFS [Cisco Nexus 9000 Series Switches], Configuring NFS, NFS Overview
• Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide, Release 9.3(x) - Configuring NFS [Cisco Nexus 9000 Series Switches], Configuring NFS, Configuring NFSv4 Leasing

To configure HSRP on a Nexus 7000 series switch for VLAN 100 and ensure the router is the active master, you would typically use the hsrp command within the VLAN configuration mode, set the priority higher than the default to make it the preferred active router, and use the preempt command to allow the router to take over as the active router if it has a higher priority.

 EPLD upgrades on Cisco MDS 9000 series switches can be done without powering down the module during the upgrade (Option B), which allows for continuous operation and no downtime. Additionally, EPLDs can be upgraded without replacing the hardware (Option D), making the process more cost-effective and less resource-intensive. References := Cisco Data Center Core Technologies

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/7_3/upgrade/upgrade.html

EPLD updates on Cisco MDS 9000 Series Switches are characterized by updating hardware functionality on a device (Option B). This means that the updates can enhance device capabilities or address issues without the need for physical hardware changes. References := Cisco Data Center Core Technologies

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/6_2/release/notes/epld/epld_rn.html

 When configuring an Intersight virtual application and claiming targets, the information required in the comma-separated value (CSV) file for provisioning includes the target type, hostname or IP address, user name, and password. This set of information is necessary to uniquely identify and authenticate each target for the claim process.

References := The requirements for the CSV file format for claiming targets in Cisco Intersight can be found in the official Cisco documentation on the Intersight Virtual Appliance and Intersight Assist Getting Started Guide

Before upgrading the Cisco NX-OS software on a Cisco MDS switch, it is important to perform some preparatory steps to ensure a smooth and successful upgrade process. Two of these steps are:

• Check the impact of the upgrade using the show install all impact command. This command displays the compatibility and impact matrix for the upgrade, which shows the current and target versions of the software, the modules that will be upgraded, the modules that will be reloaded, and the modules that will be powered down. This information helps to plan the upgrade and minimize the disruption to the network.
• Back up the configuration of the switch using the copy running-config startup-config command. This command saves the current running configuration to the startup configuration file, which is stored in the bootflash memory of the switch. This ensures that the configuration is preserved and can be restored in case of any issues during or after the upgrade.

References := The information is supported by the Cisco MDS 9000 NX-OS Software Upgrade and Downgrade Guide, which provides detailed instructions and guidelines for upgrading the software on a Cisco MDS switch