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

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

In asymmetric L3 EVPN routing, the ingress PE performs the routing decision and then sends traffic across the overlay in the context of the destination MAC-VRF. The egress PE performs Layer 2 MAC forwarding only toward the destination host. This is why options A and B correctly describe asymmetric data-plane behavior. Asymmetric routing relies heavily on EVPN route type 2 MAC/IP Advertisement routes because the ingress PE must know the destination host's MAC/IP binding and the destination bridge domain information. EVPN route type 5, which advertises IP prefixes, is a symmetric L3 EVPN mechanism and is not mandatory for asymmetric routing. Therefore, option C is false. Option D is treated as correct in this asymmetric-routing model because each PE participating in inter-subnet forwarding needs the destination MAC-VRF context to encapsulate traffic toward the correct L2 VNI. This requirement is one reason asymmetric routing scales less efficiently than symmetric routing: MAC-VRF presence and host reachability information must be broadly available. Symmetric routing improves scale by using an IP-VRF routed VXLAN interface and RT-5 prefix routes instead. Reference: asymmetric L3 EVPN routing, ingress IP/MAC forwarding, egress MAC forwarding, RT-2 versus RT-5 usage.

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

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

In EVPN PE-CE routing, the PE exchanges ordinary IPv4 or IPv6 unicast routing information with the CE. When the PE learns CE prefixes, it imports them into the tenant IP-VRF and advertises them to other EVPN PEs as EVPN route type 5 IP Prefix routes. Conversely, when the PE receives EVPN routes from remote PEs, it can advertise corresponding IPv4/IPv6 BGP updates toward the CE, subject to policy. Import and export policies are essential because they control which customer routes are accepted, which EVPN-learned routes are advertised, and how attributes are modified. Option C is false because iBGP is not the preferred PE-CE model in this context. eBGP is typically preferred between PE and CE because it creates a clean administrative routing boundary between the provider/data-center edge and the customer or external router. Using eBGP also simplifies route policy, loop prevention, and operational separation. The CE does not need to participate in the EVPN overlay; it speaks standard BGP unicast with the PE, while the PE performs the EVPN RT-5 advertisement into the fabric. Reference: EVPN PE-CE BGP routing, eBGP preference, RT-5 prefix advertisement, import/export policy.

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

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

In all-active Layer 2 EVPN multi-homing, the host is typically dual-homed to two or more leaf routers using a LAG. The participating leaf routers must configure the LAG and associate it with the Ethernet Segment so EVPN can advertise the common ESI and apply aliasing, split-horizon, and DF procedures. If VLAN tagging is used for service separation, tagging must be configured on the LAG interface so that the correct subinterfaces can bind into the MAC-VRF and Ethernet Segment. Option C is false because it states that the LACP system-id-mac must uniquely identify each leaf router. In an all-active EVPN multihomed LAG, the opposite principle applies: from the host's LACP perspective, the multihomed leaf pair must appear as a single logical LACP system. That generally requires a shared LACP system ID or coordinated system MAC behavior across the participating PEs. If each leaf presented a unique LACP system identity, the host would treat them as separate LAG partners and the all-active bundle would not form correctly. Reference: all-active L2 EVPN multi-homing, LAG attachment, LACP system ID behavior, Ethernet Segment association.

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

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

Designated Forwarder election determines which PE forwards BUM traffic from the EVPN overlay toward a multi-homed Ethernet Segment for a given service. In this scenario, all leaf routers share the same DF candidate list for mac-vrf103, but the election configuration is not identical. Leaf1 and Leaf2 use the default algorithm, while Leaf3 and Leaf4 use the preference-based algorithm. Under preference-based DF election, the candidate with the highest configured preference is selected over lower-preference candidates, assuming the candidate list is valid and consistent. The question states that Leaf3 has the higher preference value compared with Leaf4. Therefore, Leaf3 becomes the DF for mac-vrf103. This is the correct outcome because the preference-based election explicitly overrides simple default behavior by assigning operator-defined priority to a PE. In production designs, this is useful when the operator wants deterministic forwarding placement, maintenance control, or service-specific primary-path selection rather than relying only on the default modulo-based DF selection process. Reference: EVPN DF election, preference-based algorithm, MAC-VRF service forwarding.

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

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

Layer 3 multi-homing is fundamentally about redundant or load-balanced L3 reachability for external prefixes, not about Layer 2 broadcast-domain flooding toward a host. In single-active L3 multi-homing, DF election determines which attached leaf is active for the Ethernet Segment, and only that leaf advertises or forwards for the attached customer route as required by the redundancy model. In all-active L3 multi-homing, multiple leaf routers can be valid next-hops for the same learned third-party prefix, and remote PEs may load-balance toward them based on the Ethernet Segment association. Learned external prefixes are carried as EVPN route type 5 IP Prefix routes, which is the correct route type for L3 reachability. The Ethernet Segment is associated with the next-hop for those prefixes so that remote PEs understand the multi-homed nature of the path. Option B is false because BUM forwarding is a Layer 2 EVPN concern. In an all-active L3 multi-homing scenario, DF election is not used to identify a BUM-forwarding leaf for host traffic in the same way it is used in Layer 2 multi-homing services. Reference: L3 EVPN multi-homing, RT-5 prefix routes, ES next-hop behavior.

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

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

EVPN route type 2 carries MAC/IP advertisement information. It is central to host-based routing and to designs where the fabric must distribute host MAC-to-IP bindings for integrated routing and bridging. In host routing, RT-2 is required because individual host reachability is signaled through MAC/IP advertisements. In interface-less prefix routing, RT-2 is still needed because the system relies on host or gateway MAC/IP information associated with the IRB and distributed gateway behavior. Interface-ful unnumbered designs may also require RT-2-style information to resolve next-hop or adjacency behavior because the routed interface does not use a conventional numbered next-hop model. Prefix routing with interface-ful numbered operation is different. In that model, the routed interface has explicit IP addressing and prefix reachability can be carried with L3 prefix routes without requiring EVPN RT-2 host MAC/IP advertisement as a dependency. Therefore, the symmetric routing option that does not require EVPN route type 2 is prefix routing interface-ful numbered. Reference: symmetric L3 EVPN routing models, RT-2 MAC/IP advertisements, prefix routing behavior.

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

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

Designated Forwarder election determines which PE forwards BUM traffic from the EVPN overlay toward a multi-homed Ethernet Segment for a given service. In this scenario, all leaf routers share the same DF candidate list for mac-vrf103, but the election configuration is not identical. Leaf1 and Leaf2 use the default algorithm, while Leaf3 and Leaf4 use the preference-based algorithm. Under preference-based DF election, the candidate with the highest configured preference is selected over lower-preference candidates, assuming the candidate list is valid and consistent. The question states that Leaf3 has the higher preference value compared with Leaf4. Therefore, Leaf3 becomes the DF for mac-vrf103. This is the correct outcome because the preference-based election explicitly overrides simple default behavior by assigning operator-defined priority to a PE. In production designs, this is useful when the operator wants deterministic forwarding placement, maintenance control, or service-specific primary-path selection rather than relying only on the default modulo-based DF selection process. Reference: EVPN DF election, preference-based algorithm, MAC-VRF service forwarding.

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

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

When a new Layer 2 EVPN MAC-VRF instance is enabled, the PE advertises an Inclusive Multicast Ethernet Tag route, commonly called an IMET route or EVPN route type 3. The IMET route is used to auto-discover remote PEs that participate in the same EVPN service and to build the BUM flooding list for that MAC-VRF. In this topology, all leaf routers peer with the route reflector on Spine-1. Leaf-1 therefore advertises its IMET route to the route reflector, not directly to Leaf-2 and Leaf-3. The route reflector then reflects the EVPN update to the other client leaves. Leaf-2 and Leaf-3 import the route based on matching route-target policy and add Leaf-1 to the replication list for broadcast, unknown unicast, and multicast traffic. Option B is the step that is not taken because it incorrectly describes direct leaf-to-leaf EVPN advertisement. In a route-reflector design, the RR centralizes EVPN route distribution and avoids the need for a full mesh of MP-BGP EVPN sessions between leaves. Reference: EVPN RT-3 IMET route, route-reflector operation, BUM flooding-list auto-discovery.

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

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

In interface-less symmetric routing, the EVPN fabric exchanges host forwarding information using EVPN route type 2 MAC/IP advertisements. RT-2 carries the host MAC address and, when present, the associated host IP address, allowing remote PEs to build the forwarding state needed for distributed gateway operation. Unlike asymmetric routing, interface-less symmetric routing does not require every MAC-VRF to be instantiated on every PE. The design scales better because each leaf only needs the locally attached MAC-VRFs plus the shared IP-VRF/routed VXLAN construct for inter-subnet forwarding. Option B describes an asymmetric forwarding pattern more than a symmetric one; in symmetric routing, both ingress and egress PEs perform routed forwarding functions through the IP-VRF. Option C is also incorrect because anycast gateway is fundamental when multiple leaves provide the same default-gateway service for a subnet. Therefore, the true statement is that forwarding information is exchanged using EVPN route type 2 updates. Reference: interface-less symmetric routing, EVPN RT-2 host MAC/IP signaling, distributed IRB operation.

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

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

In a single-active EVPN multi-homing design, the connected PE routers perform Designated Forwarder election to determine which PE is active for the relevant service or Ethernet Segment. The DF is responsible for forwarding toward the attached segment and, in a Layer 3 multi-homing case, only the active/DF PE advertises the customer IP prefix route toward the EVPN control plane. Single-active redundancy is communicated using Ethernet Segment-related EVPN procedures, including Ethernet A-D information, so remote PEs can identify the redundancy behavior and avoid forwarding traffic to an inactive attachment. The false statement is that the elected DF uses an AD per EVI update to identify itself as primary. AD per EVI is primarily used to advertise per-service Ethernet Segment reachability and support aliasing/load-balancing behavior in multi-homed services. DF election itself is driven by Ethernet Segment route procedures, not by the DF declaring itself primary through AD per EVI. Therefore, option B misstates the role of AD per EVI in the single-active L3 multi-homing control plane. Reference: EVPN DF election, single-active multi-homing, Ethernet A-D routes.

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