Pass the Nokia Nokia Certified Data Center Fabric Professional 4A0-D03 Questions and answers with CertsForce

Comprehensive and Detailed 150 to 250 words of Explanation From [SR Linux EVPN and Data Center Interconnect/Course Guide/topics]:

In a gateway-less DCI design, there is no dedicated gateway device performing EVPN-to-WAN service interworking. Instead, the data center EVPN overlay is extended across the WAN more directly. Because leaf routers must establish overlay reachability across sites, the IP addresses of the leaf VTEPs need to be reachable through the WAN, commonly by redistributing or otherwise carrying the necessary loopback reachability. The WAN transparently carries the EVPN/VXLAN overlay, and leaf routers can establish VXLAN tunnels across the WAN to remote leaves. Option D is false because it introduces “data center gateway routers” maintaining MP-BGP EVPN peering with the data center route reflector. That is not the gateway-less model; it describes a gateway-based role that does not exist as a separate function in this architecture. In gateway-less DCI, the EVPN control-plane and VXLAN data-plane extension are handled by the fabric endpoints themselves, so the design trades demarcation and interworking control for a more direct overlay extension model. Reference: gateway-less DCI, WAN reachability for leaf VTEPs, transparent EVPN overlay carriage, VXLAN tunnel extension.

================

Comprehensive and Detailed 150 to 250 words of Explanation From [SR Linux EVPN and Data Center Interconnect/Course Guide/topics]:

For Layer 2 all-active EVPN multi-homing on SR Linux, the Ethernet Segment configuration is the control-plane anchor that binds the redundant access attachment to EVPN. The relevant LAG subinterfaces must be associated with the Ethernet Segment so that the PE can advertise the segment correctly and apply split-horizon and aliasing behavior. The Ethernet Segment must also be administratively enabled; otherwise, the PE will not participate properly in ES discovery and DF procedures. The multi-homing mode must be set to all-active to permit forwarding through multiple attached leaf routers and support host-side LAG operation. The false statement is option B. The Ethernet Segment Identifier has a defined structure, and the blanket statement that the 2nd through 7th octets “must not be all zeros” is not a valid requirement as stated. What matters operationally is that the ESI uniquely identifies the same multi-homed Ethernet Segment across participating PEs and is consistently configured where required. The ESI must be non-zero as a meaningful segment identifier, but the specific octet restriction in the option is not the SR Linux all-active configuration rule. Reference: SR Linux L2 EVPN all-active multi-homing, Ethernet Segment configuration, LAG association.

================

Comprehensive and Detailed 150 to 250 words of Explanation From [SR Linux EVPN and Data Center Interconnect/Course Guide/topics]:

The EVPN route type used for aliasing and fast convergence in multi-homing is RT-1, the Ethernet Auto-Discovery route. RT-1 has two important forms: Ethernet A-D per Ethernet Segment and Ethernet A-D per EVI. These routes advertise reachability to a multi-homed Ethernet Segment and to a specific EVPN instance on that segment. Remote PEs use this information for aliasing, meaning they can forward traffic toward any eligible PE attached to the same Ethernet Segment, even when a specific MAC was advertised by only one PE. RT-1 also supports fast convergence because withdrawal of Ethernet A-D routes quickly informs remote PEs that an attachment path or PE is no longer valid, avoiding slow MAC aging as the primary failure-detection mechanism. RT-4 Ethernet Segment routes are related to multi-homing, but their main function is Ethernet Segment discovery and Designated Forwarder election. RT-2 advertises host MAC/IP reachability, and RT-3 builds multicast/BUM replication lists. Therefore, RT-1 is the precise answer for aliasing and fast convergence. Reference: EVPN multi-homing route types, Ethernet Auto-Discovery, aliasing and convergence behavior.

================

Comprehensive and Detailed 150 to 250 words of Explanation From [SR Linux EVPN and Data Center Interconnect/Course Guide/topics]:

EVPN route type 4 is the Ethernet Segment route. Its core role is to advertise Ethernet Segment membership so that PEs attached to the same multi-homed segment can discover each other. This discovery is essential for multi-homing procedures such as DF election, split-horizon behavior, and redundancy handling. When multiple PEs advertise the same ESI, the EVPN control plane can build the candidate set of PEs that participate in that Ethernet Segment. This enables DF election for BUM forwarding and supports the correct interpretation of the segment's redundancy model. The incorrect statement is option C. The election algorithm itself is not the basic function of the route type 4 advertisement in the way the question frames it. The route type is primarily about Ethernet Segment discovery and participation; the algorithmic decision process is derived from configured DF election behavior and candidate information, not from route type 4 acting as a generic algorithm identifier. Therefore, route type 4 enables DF procedures, but it is not described as the mechanism that identifies the election algorithm type. Reference: EVPN RT-4 Ethernet Segment route, DF election, multi-homing discovery.

================

Comprehensive and Detailed 150 to 250 words of Explanation From [SR Linux EVPN and Data Center Interconnect/Course Guide/topics]:

In an all-active Layer 2 EVPN multi-homing design, the host is normally dual-attached through a LAG to multiple leaf routers that share the same Ethernet Segment Identifier. Leaf1 and Leaf2 both participate in the Ethernet Segment and may receive traffic from the host. For BUM traffic sourced by the host, the host-side hashing can send frames toward either attached leaf. For BUM traffic sent from the EVPN overlay toward the multi-homed segment, DF election controls which PE forwards that replicated traffic toward the local Ethernet Segment to prevent duplicate delivery. The false statement is option B. A remote leaf such as Leaf3 does not simply enable ECMP on the MAC-VRF to load-balance traffic between Leaf1 and Leaf2. EVPN all-active forwarding uses Ethernet Segment discovery, Ethernet A-D routes, aliasing, and split-horizon procedures to determine valid next-hops and prevent loops. ECMP alone is an underlay or routing-table behavior; it is not the MAC-VRF mechanism that authorizes multi-homed L2 forwarding across an Ethernet Segment. Reference: all-active L2 EVPN multi-homing, Ethernet Segment association, DF election, aliasing.

================

Comprehensive and Detailed 150 to 250 words of Explanation From [SR Linux EVPN and Data Center Interconnect/Course Guide/topics]:

In asymmetric EVPN IRB, the ingress PE performs routing from the source subnet into the destination subnet, then forwards the packet across the VXLAN overlay using the destination MAC-VRF/VNI. The egress PE does not perform another IP-VRF lookup for that packet; it performs Layer 2 forwarding in the destination MAC-VRF. In this scenario, Host-2 sends traffic toward Host-1. After the ingress routing decision, the traffic arrives at Leaf-2 in the context of the destination MAC-VRF, mac-vrf-1. Leaf-2 then performs a MAC lookup in mac-vrf-1 and forwards the frame to Host-1. Option D is therefore correct. Option A reverses the forwarding direction and misidentifies the leaf action. Option B incorrectly sends mac-vrf-2 traffic toward the IP-VRF on Leaf-2, even though Leaf-2 is acting as the egress PE for Host-1. Option C is also incorrect because the egress forwarding action is based on the MAC table in the destination MAC-VRF, not an IP-VRF ARP lookup at that stage. Reference: asymmetric L3 EVPN IRB data-plane operation, ingress routing and egress MAC forwarding.

================