View Full Cisco CCNP Data Center 300-610 Exam Dumps and Practice Test Dumps.

Question 81. What device performs VXLAN encapsulation and decapsulation

1. Route reflector
2. VTEP
3. DHCP relay
4. Fibre Channel director

Correct Answer: 2. VTEP

Explanation:

A VXLAN Tunnel Endpoint performs the encapsulation and decapsulation required to transport Layer 2 traffic across the routed VXLAN underlay. In a typical Cisco Nexus leaf spine fabric, leaf switches operate as VTEPs because endpoints connect to the leaf layer. The ingress VTEP places the original Ethernet frame inside VXLAN, UDP, and IP headers before sending it through the routed fabric. The destination VTEP removes the overlay encapsulation and forwards the original frame toward the endpoint. This allows logical Layer 2 networks to extend across Layer 3 infrastructure.

Question 82. Which logical interface performs VXLAN tunnel functions on a Nexus VTEP

1. SVI
2. Port channel
3. Loopback only
4. NVE interface

Correct Answer: 4. NVE interface

Explanation:

The Network Virtualization Edge interface is the logical interface where VXLAN encapsulation and decapsulation are configured on a Cisco Nexus VTEP. The NVE interface is typically sourced from a loopback interface so the tunnel endpoint remains reachable independently of individual physical link failures. Remote VTEPs send VXLAN traffic toward this NVE source address through the routed underlay. Cisco distinguishes the NVE interface from ordinary switch virtual interfaces, which provide endpoint gateway functions. The NVE interface therefore represents the logical termination point for VXLAN tunnels on the switch.

Question 83. How large is the VXLAN network identifier field

1. 24 bits
2. 12 bits
3. 16 bits
4. 32 bits

Correct Answer: 1. 24 bits

Explanation:

The VXLAN Network Identifier is a 24 bit value carried in the VXLAN header. It identifies the logical VXLAN segment to which an encapsulated frame belongs. The larger identifier space provides substantially greater segmentation scale than the traditional VLAN identifier. Different VNIs maintain isolation between separate overlay networks while sharing the same routed physical underlay. Designers can therefore create very large multitenant environments without being restricted to traditional VLAN scale. The VNI is one of the core values used to map logical Layer 2 or Layer 3 services into a VXLAN fabric.

Question 84. Approximately how many logical segments can VXLAN support

1. Four thousand
2. Sixty five thousand
3. Sixteen million
4. One million

Correct Answer: 3. Sixteen million

Explanation:

Because VXLAN uses a 24 bit VNI field, it can provide approximately sixteen million logical network segments. This represents a substantial scaling improvement over traditional VLAN technology, which provides roughly four thousand usable VLAN identifiers. The expanded segment space is especially valuable in cloud and multitenant data centers where many isolated application environments may be required. VXLAN overlays these logical segments across a common Layer 3 transport network, allowing the physical infrastructure to remain relatively simple while logical segmentation scales independently of the traditional Ethernet VLAN limit.

Question 85. What does a distributed anycast gateway provide in VXLAN EVPN

1. Centralized routing on the spine
2. The same gateway across VTEPs
3. Fibre Channel routing
4. A dedicated DHCP gateway

Correct Answer: 2. The same gateway across VTEPs

Explanation:

A distributed anycast gateway provides the same default gateway IP address and gateway MAC address on participating VTEPs. This allows endpoint traffic to be routed by the local leaf switch rather than being sent to a centralized gateway elsewhere in the fabric. When a workload moves to another VTEP, it can continue using the same gateway information. This approach supports active forwarding close to the endpoint and simplifies workload mobility. Cisco VXLAN EVPN fabrics use distributed anycast gateways for VLANs extended across the overlay, providing a pervasive Layer 3 gateway architecture.

Question 86. Which protocol is unnecessary for the VXLAN EVPN distributed anycast gateway

1. HSRP
2. BGP
3. UDP
4. IP routing

Correct Answer: 1. HSRP

Explanation:

A VXLAN EVPN distributed anycast gateway does not require a traditional first hop redundancy protocol such as HSRP. Participating VTEPs are configured with the same gateway IP address and common anycast gateway MAC address. Each local VTEP can therefore route traffic for directly attached endpoints without waiting for an active router election. Cisco explains that this architecture provides active forwarding across gateway capable VTEPs and removes the need for conventional HSRP or VRRP gateway redundancy for overlay endpoint networks. This improves traffic localization and supports workload mobility throughout the fabric.

Question 87. Which Nexus Dashboard fabric role normally connects directly to workloads

1. Spine
2. Super Spine
3. Core Router
4. Leaf

Correct Answer: 4. Leaf

Explanation:

The leaf role provides the workload attachment layer in a VXLAN EVPN fabric. Servers, storage devices, service appliances, and other endpoints commonly connect directly to leaf switches. Cisco describes leaf switches as VTEPs that provide Layer 2 and Layer 3 connectivity while performing VXLAN encapsulation and decapsulation. Leaf switches can also provide distributed anycast gateway services for attached endpoints. In a typical Clos topology, every leaf connects to the spine layer, allowing traffic to reach any other leaf through equal cost routed paths without requiring leaf switches to connect directly to one another.

Question 88. What does a normal spine role provide in a two tier VXLAN fabric

1. Direct server attachment
2. Fibre Channel zoning
3. Layer 3 underlay and EVPN control functions
4. GPU processing

Correct Answer: 3. Layer 3 underlay and EVPN control functions

Explanation:

In a standard two tier VXLAN EVPN fabric, spine switches provide routed underlay connectivity between leaf switches and commonly participate in the BGP EVPN control plane. Every leaf connects to each spine, which creates multiple equal cost paths across the fabric. Spines form the transport backbone rather than serving as the normal server access layer. Cisco Nexus Dashboard describes the spine role as providing Layer 3 underlay interconnection as well as EVPN control plane functionality. This architecture creates predictable path lengths and supports horizontal scaling as additional leaf or spine capacity is introduced.

Question 89. Where can EVPN control plane functions move in a three tier fabric with super spines

1. Super spine layer
2. Server access layer
3. Storage array
4. Management switch

Correct Answer: 1. Super spine layer

Explanation:

When a VXLAN fabric contains both normal spines and super spines, Cisco supports placing the EVPN control plane functions at the super spine layer. In that design, the normal spine switches primarily provide routed underlay transit, while super spines act as the higher level backbone and EVPN control plane layer. This architecture supports larger fabrics containing multiple spine and leaf groups while preserving Clos connectivity. Super spines are therefore particularly useful when a two tier topology no longer provides the required scale and an additional hierarchical layer is needed.

Question 90. What is the primary role of a VXLAN fabric border switch

1. Host GPU acceleration
2. External network handoff
3. Local server boot
4. SAN zoning

Correct Answer: 2. External network handoff

Explanation:

A border switch provides a handoff between the VXLAN fabric and external IP networks. Cisco describes the border role as a VTEP that connects the internal fabric to outside environments such as WAN networks, enterprise networks, other data center infrastructure, or Internet facing services. Border switches are commonly used for VRF Lite and other north south connectivity models. They can also host endpoints or services where supported, but their distinguishing role is external network connectivity. Designers should provide sufficient border redundancy and capacity because north south traffic may depend heavily on these devices.

Question 91. Which device interconnects separate VXLAN EVPN Multi Site fabrics

1. Access switch
2. Route server only
3. Fibre Channel switch
4. Border Gateway

Correct Answer: 4. Border Gateway

Explanation:

VXLAN EVPN Multi Site uses Border Gateways to interconnect separate EVPN fabric sites over an IP network. Border Gateways communicate with devices inside their local fabric and with Border Gateways belonging to remote sites. They terminate and extend the required Layer 2 and Layer 3 overlay connectivity while creating a clear control and forwarding boundary between sites. Cisco supports Border Gateways in different topological forms depending on platform and release. Multi Site allows individual data center fabrics to preserve local control while providing scalable communication between separate overlay domains.

Question 92. What benefit do Multi Site Border Gateways provide between fabrics

1. Server BIOS management
2. GPU scheduling
3. Failure containment
4. Storage deduplication

Correct Answer: 3. Failure containment

Explanation:

Border Gateways create a control boundary between VXLAN EVPN Multi Site fabrics and provide failure containment between the individual overlay domains. Each site maintains its local EVPN control plane and IP forwarding domain, while the Border Gateways handle the exchange of necessary routes and traffic between sites. This design prevents every local fabric event from automatically becoming a fabric wide event across all locations. Cisco describes traffic enforcement and failure containment as important functions of the Multi Site Border Gateway architecture. This makes Multi Site more scalable than treating geographically separate data centers as one unrestricted overlay domain.

Question 93. Which EVPN route type advertises MAC and host IP information

1. Type 1
2. Type 2
3. Type 3
4. Type 5

Correct Answer: 2. Type 2

Explanation:

EVPN Route Type 2 is the MAC and IP advertisement route. Cisco VXLAN EVPN VTEPs use this route type to distribute endpoint MAC information and optional host IP bindings through the BGP control plane. Remote VTEPs can therefore learn endpoint reachability without relying entirely on data plane flooding and learning. This control plane learning improves scalability and can reduce unnecessary unknown unicast flooding. Type 2 advertisements are fundamental to the way EVPN distributes endpoint reachability across a modern VXLAN fabric and supports efficient host mobility between VTEPs.

Question 94. Which EVPN route type carries VTEP information for ingress replication

1. Type 3
2. Type 1
3. Type 4
4. Type 5

Correct Answer: 1. Type 3

Explanation:

EVPN Route Type 3 is the Inclusive Multicast Ethernet Tag route. Cisco NX OS uses this route type to distribute VTEP information required for ingress replication. In an ingress replication design, a source VTEP creates individual copies of broadcast, unknown unicast, and multicast traffic for the remote VTEPs participating in the VNI. Type 3 routes allow VTEPs to learn which remote tunnel endpoints should receive this replicated traffic. The route type is therefore associated with BUM traffic handling rather than individual endpoint MAC reachability or external IP prefix advertisement.

Question 95. Which EVPN route type advertises IP prefixes without MAC addresses in the route key

1. Type 1
2. Type 2
3. Type 5
4. Type 4

Correct Answer: 3. Type 5

Explanation:

EVPN Route Type 5 advertises IPv4 or IPv6 prefixes independently of MAC advertisement routes. Cisco describes Type 5 as an IP prefix route that can carry subnet reachability through the EVPN control plane without requiring a MAC address in the route key. This is especially useful for Layer 3 VXLAN EVPN services, external route advertisement, and scalable intersubnet routing designs. Type 5 therefore complements Type 2, which is commonly used for individual endpoint MAC and IP host information. Understanding these route types is important when designing EVPN control plane scale and external routing integration.

Question 96. What role does Nexus Dashboard Fabric Controller assign by default in the documented VXLAN workflow

1. Spine
2. Border
3. Super Spine
4. Leaf

Correct Answer: 4. Leaf

Explanation:

Cisco Nexus Dashboard Fabric Controller commonly assigns the Leaf role as the initial default role in the documented VXLAN EVPN fabric workflow. Administrators then change individual switches to roles such as Spine, Border, or Border Gateway according to the intended topology. Setting the role allows NDFC to generate the appropriate configuration intent for the device. The role selection itself does not immediately push all configuration changes. Administrators review the intended state and then use the Recalculate and Deploy process to generate and apply the resulting configuration to the managed switches.

Question 97. Which NDFC operation generates and applies configuration after a role change

1. Recalculate and Deploy
2. Reload and Restore
3. Discover and Delete
4. Export and Reboot

Correct Answer: 1. Recalculate and Deploy

Explanation:

Recalculate and Deploy is the Nexus Dashboard Fabric Controller operation used to generate configuration changes based on the current fabric intent and then deploy them to the switches. For example, after assigning a switch a new supported fabric role, NDFC calculates the configuration required for that role. Administrators can preview the resulting configuration before it is pushed. This intent based workflow allows NDFC to automate large portions of VXLAN EVPN fabric deployment while still providing visibility into the configuration being generated. It is a core operational step in managed fabric provisioning.

Question 98. What does an NDFC fabric represent

1. One physical interface
2. One VLAN only
3. A container of switches sharing fabric attributes
4. One application server

Correct Answer: 3. A container of switches sharing fabric attributes

Explanation:

Cisco Nexus Dashboard Fabric Controller defines a fabric as a container of switches that share common attributes and settings at the fabric level. A data center VXLAN EVPN fabric can therefore contain the leaf, spine, border, and related devices that participate in one managed topology. NDFC can maintain multiple fabrics simultaneously, allowing organizations to operate separate data center environments from the same management platform. Fabric level settings help create consistent deployment behavior while switch roles determine the specific functions each device performs inside that fabric.

Question 99. Which Nexus Dashboard role is commonly used for VRF Lite external connectivity on a non Nexus device

1. Leaf
2. Spine
3. ToR
4. Edge Router

Correct Answer: 4. Edge Router

Explanation:

Cisco Nexus Dashboard documentation identifies the Edge Router role as the appropriate role for supported non Nexus devices participating in VRF Lite external connectivity. The external router connects to a fabric border device and provides Layer 3 communication toward networks outside the VXLAN EVPN fabric. VRF Lite preserves separate routing contexts across the external handoff. This design is useful when the VXLAN fabric must connect to routers or switching platforms that are not themselves functioning as fabric VTEPs. Appropriate interface and VRF configuration must be maintained on both sides of the handoff.

Question 100. What management benefit does NDFC provide for VXLAN EVPN fabrics

1. GPU memory acceleration
2. Centralized fabric configuration and monitoring
3. Fibre Channel disk formatting
4. Server operating system installation

Correct Answer: 2. Centralized fabric configuration and monitoring

Explanation:

Nexus Dashboard Fabric Controller provides centralized deployment, configuration, monitoring, and operational management for supported VXLAN EVPN fabrics. Administrators can discover switches, assign fabric roles, configure vPC relationships, define intent, deploy generated configurations, and monitor topology from a central interface. Cisco also provides change control and rollback capabilities that help administrators manage configuration changes more safely. This reduces the amount of repetitive manual switch configuration required in large fabrics and helps maintain consistency between intended design and deployed state. NDFC therefore addresses both initial fabric provisioning and ongoing operational management.