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

 To configure a Fibre Channel device alias named TEST for a device attached to port fc1/9 on a Cisco Nexus Series Switch, the correct command set is found in Option A. The commands should be entered in configuration mode, starting with accessing the device-alias database, creating the device-alias named TEST with the specified pwwn, and committing the changes to the database123.

References := The process for configuring a Fibre Channel device alias on a Cisco Nexus Series Switch is detailed in the Cisco Nexus 9000 Series NX-OS SAN Switching Configuration Guide and other Cisco documentation related to SAN switching and device aliases

The Cisco UCS firmware Auto Sync Server policy includes several configuration settings that determine how and when firmware on servers is synchronized. The two available settings from the options provided are ‘User Acknowledge’ and ‘No Action’. ‘User Acknowledge’ requires an administrator to manually acknowledge firmware upgrades in the Pending Activities dialog box before they are applied. ‘No Action’ means no firmware upgrade is initiated on the server. These settings allow administrators to control the firmware synchronization process according to their operational policies and procedures.

References := Using Firmware Automatic Synchronization Server Policy - Cisco, Cisco UCS B-Series CLI Firmware Management Guide, Release 2.2

 EPLDs (Electronic Programmable Logic Devices) can be upgraded to enhance hardware functionality or resolve known issues without the need for hardware replacement. The upgrade process is disruptive as it requires the module to power down briefly during the upgrade. However, the system performs EPLD upgrades on one module at a time, minimizing the disruption to traffic through only one module at any given time.

References: Cisco Community discussion on Upgrading EPLD on N9k3 and Cisco Nexus 9000 Series FPGA/EPLD Upgrade Release Notes

 Terraform is an infrastructure as code (IaC) tool that allows users to define both cloud and on-premises resources in human-readable configuration files that can be versioned, reused, and shared. In the context of Cisco Data Center Core Technologies, Terraform can be used to enforce the desired state of the network by automatically managing, updating, and reverting configurations as needed to maintain consistency. It supports a wide range of Cisco products and can be extended to manage server infrastructure in the future.

References: The Implementing and Operating Cisco Data Center Core Technologies (DCCOR) course provides insights into the essentials of automation and security in data centers, including the use of IaC tools like Terraform for enforcing desired state configuration1. Additionally, the Implementing Automation for Cisco Data Center Solutions (DCAUI) course further explores the implementation of automation solutions, including Terraform, in Cisco data centers2

Text Description automatically generated

 Option A is the correct configuration set to create an EEM script that saves a copy of the running configuration on bootflash and writes a message to syslog when a user saves the configuration to a Cisco Nexus switch. The EEM script uses the event manager applet command to define the applet name and the event that triggers the script. In this case, the event is the CLI pattern “copy running-config startup-config” which matches the command that a user would use to save the configuration. The action commands specify the commands that the script will execute when the event occurs. In this case, the script will copy the running configuration to bootflash, write a message to syslog, and exit. The other options have incorrect commands or syntax errors. For example, option B uses the wrong event keyword, option C uses the wrong action keyword, and option D uses the wrong file name. References:

• Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 9.3(x) - Configuring Embedded Event Manager [Cisco Nexus 9000 Series Switches], Configuring Embedded Event Manager, Configuring EEM Policies Using the CLI
• Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 9.3(x) - Configuring Embedded Event Manager [Cisco Nexus 9000 Series Switches], Configuring Embedded Event Manager, Configuring EEM Event Statements
• Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 9.3(x) - Configuring Embedded Event Manager [Cisco Nexus 9000 Series Switches], Configuring Embedded Event Manager, Configuring EEM Action Statements

When configuring the connection between a Cisco MDS 9700 Series Multilayer Director and a Cisco Nexus 5672UP switch, it’s important to consider the following:

• Ensure compatibility: Verify that both devices are running compatible NX-OS versions to ensure they can communicate properly.
• Configure interfaces: Set up the interfaces on both devices with the appropriate type (E, F, or TE), speed, and other relevant settings.
• Establish connectivity: Use the show interface command to confirm that the interfaces are up and the show flogi database command to verify that the Fibre Channel login has been successful.
• Zoning configuration: Configure zoning on the MDS 9700 to control access between devices connected to the fabric.
• VSAN setup: Ensure that the Virtual Storage Area Network (VSAN) is correctly configured and that both switches are part of the same VSAN if required for the topology.

References:

• Cisco MDS 9700 Series Multilayer Directors documentation1.
• Cisco Nexus 5672UP switch documentation

 Option C is the correct configuration to apply a power redundancy policy on a Cisco UCS C-Series Rack Server that supports two power sources. The power redundancy policy determines how the server uses the available power supplies to optimize power usage. The grid option means that the server uses power from both power supplies simultaneously. If one power supply fails, the server continues to operate with the remaining power supply. The other options are not suitable for this requirement. The n+1 option means that the server uses one fewer power supply than the number of power supplies that are installed. If a power supply fails, the server uses the extra power supply. The non-redundant option means that the server uses only one power supply, regardless of the number of power supplies that are installed. If the power supply fails, the server shuts down. The ps-redundant option means that the server uses power from the most efficient power supply. If the power supply fails, the server switches to another power supply. References:

• Cisco UCS C-Series Servers Integrated Management Controller GUI Configuration Guide, Release 4.0 - Configuring Server Power [Cisco Integrated Management Controller], Configuring Server Power, Configuring the Power Policy
• Cisco UCS C-Series Servers Integrated Management Controller GUI Configuration Guide, Release 4.0 - Configuring Server Power [Cisco Integrated Management Controller], Configuring Server Power, Power Redundancy Modes

To configure multiple EPGs on a single access port in a large Cisco ACI fabric without using VMM integration, the EPGs must be linked to the correct physical domain (Option B) and configured as static ports (Option E). The physical domain is associated with VLAN namespaces and determines the VLAN encapsulation at the interface level. The static ports are used to manually assign the EPGs to the access port. The other options are not required for this configuration. A contract is used to define the communication policy between EPGs, but it is not necessary to create one for this scenario. The EPGs do not link directly to the AAEP, but rather to the interface policy group that is associated with the AAEP. The bridge domains do not need to be configured in legacy mode, which is a mode that allows communication with non-ACI networks. References:

• Cisco Application Centric Infrastructure Fundamentals, Release 4.x - Endpoint Groups (EPGs) [Cisco Application Centric Infrastructure], Endpoint Groups (EPGs), Physical Domain
• Cisco Application Centric Infrastructure Fundamentals, Release 4.x - Endpoint Groups (EPGs) [Cisco Application Centric Infrastructure], Endpoint Groups (EPGs), Static Ports
• Cisco Application Centric Infrastructure Fundamentals, Release 4.x - Endpoint Groups (EPGs) [Cisco Application Centric Infrastructure], Endpoint Groups (EPGs), Contracts
• Cisco Application Centric Infrastructure Fundamentals, Release 4.x - Endpoint Groups (EPGs) [Cisco Application Centric Infrastructure], Endpoint Groups (EPGs), Attachable Access Entity Profile
• Cisco Application Centric Infrastructure Fundamentals, Release 4.x - Bridge Domains [Cisco Application Centric Infrastructure], Bridge Domains, Legacy Mode

 To automate the provisioning of Cisco ACI objects using Terraform while ensuring that APIC counts the authentication login requests against the threshold to avoid a DOS attack, signature-based authentication should be used. This method involves obtaining an authentication token from Cisco APIC, which will use the token to authenticate. However, APIC counts these authentication requests and applies a threshold to prevent DOS attacks. After too many attempts, the user ID and password authentication method may fail as the threshold is exceeded. To circumvent this issue, signature-based authentication is recommended, where a signature is calculated using a private key and passed with the request. This signature is then used to authenticate the user without being counted against the threshold, thus avoiding the risk of exceeding it and failing authentication.

References: The information is based on the Terraform documentation provided by CiscoDevNet