Nokia 4A0-D03 Exam Questions

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

Asymmetric routing relies heavily on host MAC/IP information because the ingress PE performs routing into the destination subnet and then sends the frame across the overlay using the destination MAC-VRF/VNI. This means PEs require enough ARP and MAC/IP binding information to forward traffic toward remote hosts correctly. If a host has multiple IP addresses on the same interface, separate EVPN route type 2 advertisements may be needed to communicate each IP-to-MAC binding. The ingress and egress PEs participate in MAC and IP forwarding across the end-to-end service path, but the forwarding responsibilities differ by direction and stage. The false statement is option C. The statement says all MAC-VRFs connected to the L3 EVPN network must exist on each PE, but that is not the correct requirement in this question's verified answer set. In practical EVPN designs, the exact MAC-VRF placement depends on whether the service is implemented as asymmetric, symmetric, interface-less, or interface-ful routing. Here, the course answer marks the universal MAC-VRF requirement as false. Reference: asymmetric L3 EVPN routing, RT-2 MAC/IP advertisements, ARP and MAC forwarding behavior.

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

MAC mobility is the EVPN mechanism used when a host MAC moves from one PE to another. The control plane uses a MAC Mobility extended community and sequence number behavior to determine the most recent valid location for the MAC. When a PE locally learns a MAC that was previously learned through EVPN, it advertises the MAC with an incremented sequence number, allowing remote PEs to prefer the newer location. Therefore, option B is wrong because the sequence number is not decremented. Option A is also wrong because the original PE does not advertise the locally learned MAC with a maximum sequence value as a normal mobility procedure. Option D is inaccurate because PEs do not need direct MAC table synchronization; they rely on EVPN control-plane advertisements and withdrawals. The true statement is option C: the originating PE generates a withdraw message after the same locally learned MAC ages out. This withdrawal removes stale reachability from remote PEs and prevents continued forwarding toward a PE that no longer has the host locally attached. Reference: EVPN MAC mobility, sequence-number handling, MAC route withdrawal after aging.

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

When Host-1 sends its first Ethernet frame into MAC VRF-1, Leaf-1 performs normal local data-plane MAC learning on the access interface and installs Host-1's MAC address into the MAC forwarding table. In an L2 EVPN MAC-VRF, host MAC reachability is then advertised into the EVPN control plane using EVPN route type 2, the MAC/IP Advertisement route. Route type 5 is not used for host MAC advertisement; RT-5 is used for IP prefix advertisement in Layer 3 EVPN services. Therefore, option B is false because it incorrectly states that Leaf-1 generates an EVPN RT-5 update with the host MAC address. In this topology, Leaf-1 sends the correct EVPN update to the route reflector, Spine-1. The route reflector then reflects the update to Leaf-2 and Leaf-3, and those remote leaves import the route if the route target matches their MAC VRF-1 import policy. The route target controls service membership, ensuring that only PEs participating in the same EVPN instance import the MAC route. Reference: L2 EVPN MAC learning, RT-2 MAC/IP advertisement, route-reflector distribution, route-target import.

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.