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

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/6-x/unicast/configuration/guide/l3_cli_nxos/l3_hsrp.html

The command that completes the EEM script configuration for saving a copy of the running configuration to bootflash on a Cisco Nexus 9000 Series Switch isrunning-config. This command is used in the EEM applet to specify the source of the configuration file that needs to be copied. The complete command in the EEM applet would beaction 1.0 cli command 'copy running-config bootflash:/current-config.txt'. This command will save the running configuration to a file namedcurrent-config.txtin the bootflash when the specified event occurs, which is when a user saves the configuration.

When moving traffic between switches configured with NPV and NPIV features, it's crucial to ensure that the NPV traffic management settings are correctly configured to handle the new interface allocation. This typically involves updating the NPV traffic-map and ensuring that the upstream NPIV core switch recognizes the new paths for the traffic.Additionally, the engineer may need to verify the zoning and VSAN configurations to ensure that the new interface is part of the correct VSAN and that the zoning allows for the FLOGI to be processed correctly on the new interface123.

Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x1.

Cisco documentation on Configuring N Port Virtualization2.

Cisco guide on N-Port Identifier Virtualization (NPIV) and N-Port Virtualization (NPV)

In the context of Bash scripting for system automation, thekillproccommand is often used to stop a process. The correct option to complete the script for a Chef Client reload would involve sending a HUP (hang-up) signal to the Chef Client process, which is typically done to cause the process to reload its configuration without stopping the service. The commandkillproc -p $pidfile $exec --HUPwould send the HUP signal to the process identified by the pidfile, which is the expected behavior for a Chef Client reload on a system reset.

SSH (Secure Shell) is the protocol that allows secure remote login from one computer to another. It provides strong authentication and secure communications over unsecured channels. This protocol is preferred for automated onboarding of devices like Cisco Nexus 9000 Series Switches because it supports strong encryption and credential-based authentication, which aligns with the requirement for minimal connection methods and security. SSH is commonly used in network automation for secure command execution and file transfers.

The Device Connector Access Mode should be configured as 'Allow Control' within the Cisco UCS Manager to enable full configuration capabilities. Claiming the device on Intersight as 'UCSM Managed Mode' ensures that the device can be managed through both the Cisco UCS Manager and the Intersight platform.This configuration aligns with the best practices for setting up Cisco UCS domains for integration with Intersight, allowing for seamless monitoring and management while maintaining security and control12.

The configuration in Cisco UCS Manager needs to specify the source of the traffic for the SPAN session. Since the requirement is to monitor the traffic from VSAN 11, selecting VSAN 11 as the source will direct the traffic to the monitoring session. This is consistent with the SPAN session's purpose, which is to create a copy of the traffic for analysis or monitoring.

Applying a control plane service policy with a rate-limiting feature allows the engineer to match all ICMP traffic and set a threshold for it. Traffic that exceeds this threshold can be dropped, thus mitigating the risk of ICMP-based DoS attacks while allowing legitimate ICMP traffic to pass through.This method ensures that the current ICMP traffic is not affected as long as it does not exceed the configured rate limit12.

In a VXLAN implementation with anycast gateway, PIM Source-Specific Multicast (SSM) is used for efficient host reachability. The IP address 10.10.0.1/32 should be applied to interface loopback1 to facilitate this setup. This address is used in conjunction with theip pim anycast-rpcommand to configure the rendezvous point (RP) for multicast traffic in a PIM SSM environment. The loopback interface is typically used for this purpose because it is always up and reachable as long as the device is operational.