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

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

An anycast-gateway IRB allows multiple PEs to present the same default-gateway IP address to hosts in the same subnet. This is the mechanism that enables distributed gateway behavior in EVPN fabrics. The same anycast gateway IP may be configured on equivalent IRB subinterfaces across remote PEs participating in the same IP-VRF, allowing hosts to use the nearest leaf as their default gateway without changing their gateway address. SR Linux also associates gateway MAC information with the IRB, including virtual gateway MAC behavior used inside the MAC-VRF forwarding table. Option C is false because the anycast gateway IP is not treated as a normal unique host route that appears in the IP-VRF route table alongside the subnet prefix. The subnet route is installed for the connected network, but the shared anycast gateway address is a gateway function, not a separately advertised host endpoint that should appear as ordinary routed host reachability. Treating the anycast IP as a regular host route would undermine the distributed gateway model and create ambiguous ownership across PEs. Reference: IRB anycast gateway, MAC-VRF/IP-VRF interconnection, distributed default-gateway operation.

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

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

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

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.

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

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

PE-CE routing is the mechanism used to exchange customer prefix reachability between a provider edge or data center leaf and the attached customer edge router. It can be implemented statically or dynamically. Static routing is operationally simple but does not scale well when many prefixes or frequent changes are involved. BGP is preferred for larger deployments because it supports policy, route filtering, attributes, and automated advertisement of changing reachability. In most EVPN PE-CE designs, eBGP is preferred because it creates a clean routing boundary between the PE and CE, with each device operating in a different autonomous system. Option D is false because the CE does not advertise BGP EVPN route type 5 updates to the PE. The CE advertises ordinary IPv4 or IPv6 unicast prefixes over the PE-CE routing session. The PE then imports those customer prefixes into the IP-VRF and advertises them into the EVPN overlay as route type 5 IP Prefix routes toward other PEs. This distinction matters: EVPN signaling is a PE-to-PE overlay function, not a CE-originated EVPN control-plane role. Reference: PE-CE routing, eBGP, EVPN RT-5 prefix advertisement.

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

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

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

The scenario describes Layer 3 EVPN multi-homing with an IP-VRF service and an external CE VNF advertising the 40.40.40.0/24 prefix through BGP. A DF election can occur among the leaf routers participating in the Ethernet Segment, and the active/primary forwarding node is used for the relevant service behavior. The AD per EVI route can participate in identifying service-level reachability for the Ethernet Segment, and the prefix traffic follows the valid advertised path toward the CE VNF. Because Leaf3 has the BGP connection to the CE VNF, traffic for 40.40.40.0/24 is forwarded through Leaf3. Option B is false because it incorrectly states that all connected leaf routers will use single-active redundancy. The exhibit and answer context indicate a more specific forwarding/primary selection for the service, not a blanket statement that every connected leaf operates using single-active redundancy. In L3 multi-homing, redundancy behavior depends on the ES mode, prefix advertisement, next-hop association, and CE connectivity. The forwarding decision for the customer prefix is tied to the active/valid route advertisement, not to every leaf uniformly acting as single-active. Reference: L3 EVPN multi-homing, DF election, AD per EVI role, PE-CE BGP prefix forwarding.

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

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

An IRB interface is the logical connection point between a Layer 2 MAC-VRF and a Layer 3 IP-VRF. It provides the routed gateway function for hosts in the bridge domain while allowing traffic to move into the routed VRF for inter-subnet forwarding. The correct statement is that when an IRB sub-interface has multiple IP addresses, one can be designated as the primary. This is important because the primary address is used for normal gateway or subnet behavior when more than one address is present on the same routed interface context. Option A is inaccurate because the question is about an IRB sub-interface, not a generic subinterface selection between bridge or routed access modes. Option B is not the defining multi-homing model; EVPN multi-homing is implemented through Ethernet Segment association and MAC-VRF attachment behavior, not by adding multiple IRB subinterfaces for multi-homing. Option D is also wrong because the IRB is the shared logical link between the MAC-VRF and IP-VRF; the design does not require separate IRB subinterfaces on each side as independent constructs. Reference: SR Linux IRB configuration, MAC-VRF to IP-VRF interconnection, primary IP addressing.

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

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

Proxy ARP in a Layer 2 EVPN service allows the leaf to answer ARP requests locally using learned IP/MAC bindings, reducing broadcast flooding across the overlay. SR Linux can also monitor IP duplication and MAC/IP inconsistencies in the proxy ARP table. A pending state indicates that the system has detected suspicious or conflicting information and is monitoring the binding before declaring it duplicate. If the entry becomes duplicate, SR Linux can use a blackhole behavior to prevent forwarding traffic toward a conflicted endpoint, and a special discard MAC such as 00:00:00:00:DE:AD can be associated with the duplicate entry. Option D is false because it incorrectly states that all traffic destined to 192.168.100.1 will be discarded for exactly 9 minutes. The exhibit references monitoring and hold-down behavior, but the answer key rejects the fixed “9 minutes” traffic-discard statement. The key concept is that duplicate handling protects the EVPN service from unstable or conflicting IP/MAC bindings, but the specific discard duration in option D is not correct. Reference: proxy ARP, IP duplication monitoring, duplicate-state blackhole behavior.

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

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

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.

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