4A0-D03 Nokia SR Linux EVPN and Data Center Interconnect Questions and Answers

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

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

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

A Gratuitous ARP is an ARP message a host sends to announce or refresh its own IP-to-MAC binding without waiting for another host to request it. In a traditional Ethernet subnet, the GARP is sent as a broadcast so that other hosts can update their ARP caches with the sender's current MAC address. This is useful after a host boots, changes NICs, moves to another attachment point, or takes over an IP address in a redundancy scenario. In EVPN environments, GARPs are also important because a leaf can snoop the ARP information and update local proxy ARP and EVPN MAC/IP state. Option D is false because recipients do not acknowledge a gratuitous ARP with a reply. GARP is an announcement mechanism, not a request/response transaction. If every receiving host acknowledged a broadcast GARP, the result would be unnecessary ARP traffic amplification. The correct behavior is passive update of ARP state by receiving systems and, in EVPN, potential control-plane propagation of the learned binding by the local PE. Reference: GARP behavior, proxy ARP learning, Layer 2 EVPN endpoint update procedures.

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

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

When Leaf-1 receives an ARP request from Host-1, it learns the source MAC address in the local MAC table and learns the source IP/MAC binding in the proxy ARP table. For EVPN distribution, the relevant control-plane advertisement is an EVPN route type 2 MAC/IP advertisement containing Host-1's MAC and the actual host IP address, 192.168.100.1. This allows remote PEs to populate their EVPN-derived forwarding and proxy ARP state with the correct endpoint binding. Option A is false because advertising the host MAC with the IP address set to 0.0.0.0 does not represent the learned MAC/IP binding required for proxy ARP synchronization. A MAC-only RT-2 advertisement may exist in EVPN contexts, but the question specifically states that Leaf-1 has learned the MAC/IP binding through ARP and is distributing that information. Therefore, the valid advertisement must include the real host IP address. Remote PEs use the MAC/IP route to learn the endpoint, not an all-zero IP placeholder for this proxy ARP learning event. Reference: EVPN RT-2 MAC/IP advertisement, proxy ARP table population, endpoint synchronization.

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

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

A gateway-less DCI design extends the data center EVPN/VXLAN model across the WAN without a distinct gateway function separating the data center fabric from the WAN VPN edge. Because the leaf routers or route reflectors must establish the necessary EVPN control-plane and VXLAN data-plane reachability across data centers, the WAN must provide reachability for those fabric endpoints. This design can simplify service continuity and preserve the EVPN overlay model end-to-end, but it does not provide the clean security and QoS demarcation that exists in a decoupled gateway model. A clear demarcation between a border leaf and a separate gateway/WAN PE is specifically a property of decoupled gateway-based DCI, not gateway-less DCI. The gateway-less model also requires reachability between route reflectors or EVPN control-plane endpoints across sites. Therefore, option A is false because it incorrectly assigns the demarcation benefit to the gateway-less design. Reference: gateway-less DCI, stretched EVPN overlay, route-reflector and leaf reachability requirements.

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

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 an integrated gateway-based data center interconnect design, the gateway must interwork between the data center EVPN/VXLAN domain and the WAN VPN transport domain. For Layer 3 VPN connectivity on a Nokia 7750 SR integrated gateway, the base BGP instance must support the relevant VPN address families, such as VPN-IPv4 and EVPN, because the gateway participates in control-plane exchange between the data center and WAN sides. The VPRN must also be associated with the WAN transport, normally through MPLS tunnel binding, and the VRF target must match the corresponding VPRN on the remote gateway so that VPN routes are imported and exported correctly. A routed VXLAN interface, however, is an SR Linux IP-VRF/VXLAN construct used for symmetric L3 EVPN forwarding inside a VXLAN-based data center fabric. In this question, dcgw10 is acting as the integrated WAN gateway for L3VPN connectivity, so a routed VXLAN interface is not the required configuration item on the VPRN instance. Reference: integrated gateway DCI, VPRN over MPLS, EVPN-to-VPN interworking.

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

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

In active-standby, or single-active, Layer 2 EVPN multi-homing, only one PE is active for the Ethernet Segment and MAC-VRF at a time. Leaf1 and Leaf2 participate in DF election, and the elected DF becomes the active forwarding PE for that service attachment. Because this is not all-active multi-homing, the non-DF must not forward traffic to the host for the protected service. This prevents duplicate frames, incorrect MAC learning, and loops on the access side. The DF accepts traffic from the host and forwards BUM traffic received from remote PEs toward the host-facing segment. Option D is false because it claims that the non-DF can forward unicast traffic from remote PEs to the host. In single-active operation, remote peers must direct traffic to the active PE, and the standby PE remains ready to take over only after DF state changes. This is the operational distinction from all-active multi-homing, where more than one PE may be used for forwarding depending on the traffic type and aliasing behavior. Reference: single-active L2 EVPN multi-homing, DF role, non-DF forwarding suppression.

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

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

In SR Linux BGP configuration, parameters defined at a more specific hierarchy level can override broader protocol-level settings. Therefore, if a `local-as` value is configured within the BGP group used for EVPN MP-BGP route-reflector sessions, that value overrides the AS number configured directly under the BGP protocol for that group's sessions. Option A is correct. Option B is false because the cluster ID is configured on the route reflector, not on every participating client. The cluster ID identifies the RR cluster and helps prevent route-reflection loops. Option C is false because redundant route reflectors normally operate in parallel rather than as strict primary/backup devices; clients can peer with both for resilience. Option D is misleading because EVPN route reflectors are used to avoid a full mesh of overlay MP-BGP EVPN sessions between leaves, not to replace ordinary underlay eBGP leaf-spine routing sessions. In a clean fabric design, the underlay provides IP reachability, while the EVPN overlay uses MP-BGP sessions, often via route reflectors, to distribute tenant reachability. Reference: SR Linux BGP hierarchy, EVPN route reflector sessions, local-AS override, cluster ID behavior.

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

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

In a distributed Layer 2 EVPN service, the local leaf learns host reachability from frames received on access interfaces. When a host replies to an ARP request, the local leaf can learn the source MAC address from the Ethernet frame and install it in the MAC forwarding table. If the ARP payload contains an IP/MAC binding, the PE can also use that information for proxy ARP and EVPN MAC/IP advertisement. The local PE then advertises the learned endpoint reachability using EVPN route type 2 to its BGP EVPN peers or route reflector. The false statement is B. The ARP reply is not replicated to every leaf in the flooding list as a normal operation. EVPN's purpose is to reduce unnecessary flooding by distributing endpoint reachability through the control plane. BUM replication is used for broadcast, unknown unicast, and multicast traffic when needed, but a learned ARP reply does not require blind replication to all remote leaves. Instead, the leaf advertises the learned MAC/IP state through MP-BGP EVPN, allowing remote PEs to install accurate forwarding and proxy ARP state. Reference: distributed L2 EVPN operation, ARP learning, EVPN RT-2 advertisement.

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

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

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.

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