4A0-D03 Exam Dumps - Nokia SR Linux EVPN and Data Center Interconnect

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

A distributed Layer 2 EVPN in SR Linux is implemented using MAC-VRF network instances, EVPN control-plane signaling, and VXLAN data-plane encapsulation. A common mistake is assuming that every PE must use the same EVI value for the same L2 service. In SR Linux, the important operational requirement is that the correct EVPN routes are imported and exported using matching route-target policy, not necessarily that every PE has the same locally configured EVI. Therefore, option A is false. The route distinguisher can be automatically generated using local values such as the autonomous system number and EVI, giving each PE's EVPN routes uniqueness in MP-BGP. A MAC-VRF is associated with VXLAN encapsulation for its data-plane service mapping, and route targets may need to be manually configured when leaf routers are in different autonomous systems because automatic derivation may not produce matching import/export policy across AS boundaries. The key separation is this: the RD gives uniqueness, the route target controls service membership, and the EVI is a local service identifier rather than a universal mandatory match in all designs. Reference: SR Linux distributed L2 EVPN configuration, EVI, RD auto-generation, route-target policy.

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

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

This setup represents single-active Layer 2 EVPN multi-homing. In single-active mode, the Ethernet Segment is configured so that only one PE acts as the active forwarding node for a given service, while the other remains standby. The ports connecting to the host are associated with ES-1 so the EVPN control plane can perform Ethernet Segment discovery, DF election, and standby behavior. If Leaf1 is the active/DF node for the service, all traffic to and from the host flows through Leaf1 until a failure or DF transition occurs. Option D is false because a host LAG is not required for this single-active topology. A LAG is typically required for all-active L2 multi-homing, where the host must treat multiple physical links toward different leaf routers as one logical bundle. In single-active operation, the host can be connected through separate physical links or active/standby access behavior without requiring LACP bundling. The EVPN PEs enforce the active path selection through DF and ES state rather than relying on host-side LAG hashing. Reference: single-active EVPN multi-homing, Ethernet Segment port association, DF-controlled active forwarding.

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

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

Symmetric L3 EVPN routing uses an IP-VRF-based overlay model in which both ingress and egress PEs participate in routed forwarding. The ingress PE receives the frame from the local MAC-VRF, routes it into the IP-VRF, and sends it across the VXLAN routed interface. The egress PE receives the routed overlay packet, performs the corresponding IP-VRF lookup, and then forwards it into the locally attached destination MAC-VRF. Because the routed overlay is built per IP-VRF, a routed-VXLAN interface is required for that IP-VRF. EVPN route type 5 support is also required because RT-5 carries IP prefix reachability across the EVPN control plane. The false statement is option D. Symmetric routing specifically removes the requirement for every MAC-VRF to exist on every PE. A PE only needs the MAC-VRFs for locally attached subnets, plus the shared IP-VRF and routed overlay state. This is the major scaling advantage of symmetric routing compared with designs that require broad MAC-VRF instantiation across the fabric. Reference: symmetric L3 EVPN routing, routed VXLAN interface, RT-5 prefix reachability, MAC-VRF scaling.

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

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

In a decoupled gateway-based DCI design, the data center border leaf and the WAN PE are separate devices. Traffic between them can be identified using VLAN tags, allowing different data center EVPN services to be mapped to corresponding WAN VPN services. This architecture provides a clean operational boundary: the border leaf remains aligned with the data center EVPN/VXLAN fabric, while the WAN PE handles WAN VPN transport, QoS, security policy, and service interconnection. The separation gives a strong demarcation point for troubleshooting and administrative control. Option D is false because the WAN PE does not maintain an MP-BGP EVPN peering session with the data center route reflector. In the decoupled model, the route reflector remains part of the data center EVPN control plane, while the WAN PE exchanges routing or service information with the border leaf through the local handoff model. Direct WAN PE-to-data-center-RR peering would blur the separation that defines the decoupled design and would make the WAN PE part of the data center EVPN overlay control plane, which is not the intended architecture. Reference: decoupled gateway DCI, VLAN handoff, WAN VPN mapping, security/QoS demarcation, route-reflector separation.

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

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 asymmetric L3 EVPN routing, each participating PE must have the MAC-VRFs needed to forward traffic in the destination bridge domain. However, the specific exhibit describes two MAC-VRFs interconnected through IP-VRF3, with Leaf-1 hosting MAC-VRF1 and Leaf-2 hosting MAC-VRF2. The false statement is that Leaf-1 and Leaf-2 must both have instances of MAC-VRF1 and MAC-VRF2. That requirement is not true for this described deployment. Each local MAC-VRF connects to IP-VRF3 using an IRB interface, and host MAC/IP information is advertised using EVPN route type 2 so remote PEs can learn endpoint reachability. The question's answer also implies that IP prefix advertisement using route type 5 is part of the control-plane exchange between the leaves for the routed service context. What matters is that the fabric can resolve host and prefix reachability through EVPN without forcing every PE to instantiate every MAC-VRF in this topology. Option B overstates the MAC-VRF placement requirement and is therefore false. Reference: asymmetric L3 EVPN routing, RT-2 host advertisements, RT-5 IP prefix routes, IRB attachment.

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

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]:

Aliasing is an EVPN multi-homing mechanism that allows remote PEs to send traffic to any eligible PE attached to the same Ethernet Segment, even if a specific MAC address was learned and advertised by only one of those PEs. This avoids a traffic bottleneck and enables load-sharing in all-active multi-homing designs. The route type used to implement this behavior is the Ethernet Auto-Discovery per EVI route, commonly referred to as AD per EVI. This route tells remote PEs that a given PE has reachability to a specific Ethernet Segment for a specific EVPN instance. When remote PEs receive these advertisements from multiple PEs for the same ESI and EVI, they can treat those PEs as valid next-hops for traffic toward that Ethernet Segment. Ethernet Segment routes support ES discovery and DF election, while IP/MAC routes advertise host MAC and optionally IP binding information. AD per ES routes are used for broader Ethernet Segment-level procedures, but aliasing at the service level relies on AD per EVI reachability. Reference: EVPN route type 1, AD per EVI, aliasing in all-active multi-homing.

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