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

The correct answer is option C. The fabric binding configuration in option C matches the output required for the Cisco MDS 9000 Series Switch. Fabric binding enhances the security of the SAN fabric by allowing only authorized switches to join the fabric. The configuration includes specifying the switch world wide name (swwn), domain ID, and member world wide node name (nwwn) to ensure that only the specified devices can participate in the fabric.

The Bash script is designed to loop through the available namespaces and output all registered interfaces within the Cisco NX-OS Guest Shell. The correct code snippet to complete the script is option C,ifconfig '$ns'. This command will display the network configuration for each namespace, allowing the engineer to view all registered interfaces.

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.

The correct code snippet to ensure that the Cisco NX-OS scheduler runs every day at 3:00 a.m. is ''time daily 3:00''. This command configures the scheduler to execute the specified job daily at the given time, without the need for a 'start' keyword, which is not required in the syntax for daily repetitive tasks.

The PowerShell command in option D is the correct choice for automating the removal of switches from VLANs using the Cisco UCS Manager PowerShell module. This command uses environment variables to specify the VLAN name and switch identifiers, ensuring that the VLAN persists even when it is no longer associated with the switch port. The command structure allows for the removal of the VLAN association from the switch port without deleting the VLAN itself, thus maintaining the VLAN configuration for potential future use.

To meet the requirements for configuring Cisco NX-OS REST API on a Cisco 9000 Series Switch, the correct configuration set is option B. This set of commands enables the NX-API feature, sets the NX-API to listen for HTTP traffic on TCP port 83, uploads the HTTPS certificate, and then enables the certificate. The inclusion of thenxapi certificate enablecommand is crucial as it activates the uploaded certificate, which is necessary for establishing secure HTTPS connections.

The correct configuration to capture traffic only from the server with the IP address of 198.19.1.19/24 is option C. This configuration uses an IP access list to match packets from the specific IP address with a subnet mask of 255.255.255.255, which indicates a single host. Themonitor sessioncommand is then used to apply this access list to a SPAN session, ensuring that only traffic from the specified server is captured.

EIGRP authentication is used to prevent unauthorized devices from forming neighbor relationships. The correct CLI commands to establish EIGRP neighborship with authentication on Cisco Nexus switches involve configuring the interface with EIGRP, setting the EIGRP autonomous system number, and specifying the authentication key and key-chain. The commands in Option A are consistent with these requirements, hence it is the verified answer.

To meet the requirements of configuring a QoS policy on Cisco UCS that includes a no-drop class and enables jumbo frames without fragmentation, a QoS system class must be created with an MTU value of 9216 bytes. This MTU size is large enough to support jumbo frames, which can carry more data than standard frames, reducing the number of frames sent and improving network efficiency. The no-drop class ensures that frames are not dropped, which is crucial for certain types of traffic that require reliable delivery, such as storage traffic.