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

The virtual MAC address that is the default for HSRP version 2 group 10 is 0000.0C9F.F00A. HSRP (Hot Standby Router Protocol) is a protocol that provides redundancy and load balancing for IP networks by allowing multiple routers to share a virtual IP address and MAC address. HSRP version 2 supports up to 4096 groups, and uses a different MAC address format than HSRP version 1. The MAC address format for HSRP version 2 is 0000.0C9F.FXXX, where XXX is the hexadecimal value of the group number. For group 10, the hexadecimal value is 0A, so the MAC address is 0000.0C9F.F00A.Reference:=

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 3: Data Center LAN Network Connectivity, Lesson 3.6: Cisco Nexus 5000 Series Switches

Cisco Nexus 5000 Series NX-OS Unicast Routing Configuration Guide, Release 5.2(1)N1(1), Chapter: Configuring HSRP, Section: HSRP Version 2 edge browser The user has the page open in a Microsoft Edge browser window whose metadata is:

In the ERSPAN configuration provided, Host B is connected to Switch A and is configured as the source of the ERSPAN spanned traffic. This is indicated by the configuration on Switch A, which includes the commandmonitor session 48 type erspan-source, specifying that it is sending ERSPAN traffic to a destination. The destination IP address for this traffic is set to 10.11.11.2, which corresponds to Host A's interface VLAN12 IP address. Therefore, Host A, connected to Switch B, is the traffic analyzer, receiving the spanned traffic from Host B.

In the context of Cisco ACI (Application Centric Infrastructure), TEP (Tunnel Endpoint) addresses are used for encapsulating and forwarding traffic within the fabric. The next hop addresses mentioned in options A and D are indicative of TEP addresses, which are typically assigned to border leaf switches within the ACI fabric. These border leaf switches are responsible for routing traffic between the ACI fabric and external networks.

Option Ais correct because the next hop 10.0.1.14 for the route 172.16.99.0/24 is consistent with the TEP address format used in ACI, suggesting it is the TEP address of a border leaf.

Option Dis also correct as the next hop 10.1.168.95 for the route 172.16.100.0/24 follows the TEP address pattern, indicating it is the TEP address of another border leaf in ACI.

Bidirectional PIM is designed for scenarios where there are many sources and receivers that need to communicate with each other, such as in videoconferencing. Unlike traditional PIM sparse mode, which creates both (,G) and (S,G) entries, Bidirectional PIM only allows the (*,G) entry for the shared tree and does not build an (S,G) entry. This approach reduces the number of mroute state entries, conserving resources. Traffic can flow up and down the shared tree in Bidirectional PIM, and there is no RPF check; instead, a Designated Forwarder (DF) is used to prevent loops.Reference:=Multicast Bidirectional PIM - NetworkLessons.com

https://community.cisco.com/t5/networking-documents/peer-gateway-feature-on-the-nexus-7000/ta-p/3113290

The HA NOT READY status on a Cisco Fabric Interconnect typically indicates that the system is not in a state to provide High Availability due to certain connectivity issues. In this case, the status message ''No device connected to this Fabric Interconnect'' suggests that there is no connectivity through the management ports. Establishing a connection through these ports is essential for the Fabric Interconnect to communicate with other devices in the network and form a High Availability cluster. Once the management ports are connected and properly configured, the HA NOT READY status should be resolved.

In an OSPF Not-So-Stubby Area (NSSA), external routes can be introduced into the area by an NSSA Autonomous System Boundary Router (ASBR) as type 7 LSAs. These LSAs are unique to NSSA areas and allow for the injection of external routes in a limited fashion. An NSSA Area Border Router (ABR) then translates these type 7 LSAs into type 5 LSAs, which are propagated throughout the OSPF domain.Reference:=Configure the OSPF Not-So-Stubby Area (NSSA) - Cisco

In a vPC configuration, both Nexus switches (N7K-1 and N7K-2) are designed to work together to present themselves as a single logical entity to downstream devices. This design allows for a loop-free topology without the need for Spanning Tree Protocol (STP) to block any of the ports to prevent loops. As a result, both N7K-1 and N7K-2 share the same STP priority, making them appear as a single STP root to the rest of the network. This approach enhances the use of available bandwidth and provides redundancy without relying on STP to resolve loops.

The commands shown in the exhibit configure Unicast Reverse Path Forwarding (uRPF) in loose mode on the interface Ethernet 2/2. Theip verify unicast source reachable-via rxcommand enables uRPF to check that the source address of a received packet has a route in the routing table and that the packet has been received from a valid interface that aligns with the routing table. This helps prevent IP spoofing by ensuring that packets are received from the expected interface.