350-601 Exam Dumps - Implementing Cisco Data Center Core Technologies (350-601 DCCOR)

 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

 When storm control is applied to an interface with a zero percent value, it means that the switch will not tolerate any traffic that exceeds the bandwidth of the interfaces during a streaming window. The switch monitors the levels of incoming broadcast, multicast, and unicast traffic over a 1-second interval. When the configured threshold level is reached, further traffic in this category is dropped until the level falls below the threshold.

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.

References: = For further details, you can refer to the official Cisco documentation on EIGRP authentication and configuration for Nexus switches available on the Cisco website.

 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

To implement traffic monitoring for a server vNIC with fabric failover enabled, ensuring that traffic is sent to an analyzer even during a fabric interconnect failure, the correct configuration is to create two traffic monitoring sessions with different names, one per fabric, and connect an analyzer on each FI as the destination for the monitoring session local to the FI. This setup allows continuous monitoring because if one fabric interconnect fails, the other can still send traffic to its connected analyzer2.

References := Cisco Community Discussion on Understanding Fabric Failure and Failover in UCS

The configuration in option C, which includes commands such as switchport port-security, switchport port-security violation restrict, and switchport port-security mac-address sticky, meets the security requirements specified. This configuration secures the end-user ports by limiting the number of MAC addresses allowed on the port, logs security breaches without shutting down the port (restrict mode), and retains the MAC address configuration even if the device restarts (sticky option).

References:

• Cisco Nexus 5000 Series NX-OS Security Configuration Guide
• Cisco Data Center Core Technologies (DCCOR) study materials

The attribute that must be selected to implement microsegmentation of endpoints within the same IP subnet using a network-based attribute that allows IP subnet independence is the Tag attribute. The Tag attribute is a user-defined attribute that can be assigned to endpoints based on any criteria, such as location, function, or security level. The Tag attribute can be used to create microsegmentation policies in ACI, which define the rules for communication between endpoints within the same or different bridge domains. The Tag attribute enables IP subnet independence, which means that the microsegmentation policies are not tied to the IP subnet of the endpoints, and can be applied across different subnets or even different fabrics. The Tag attribute also simplifies the management and scalability of microsegmentation policies, as it does not require the use of IP addresses or MAC addresses to identify endpoints. References :=

• Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 6: Data Center Network Connectivity Design, Lesson 6.2: Cisco ACI Overview and Concepts
• Cisco Application Centric Infrastructure Fundamentals, Chapter: Endpoint Groups and Microsegmentation, Section: Microsegmentation Using Tags