Nokia 4A0-D03 - 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]:

In interface-less symmetric L3 EVPN routing, hosts in a subnet may be attached to different leaf routers, while inter-subnet forwarding is performed through the IP-VRF using VXLAN routed interfaces. The ingress and egress PEs both participate in L3 forwarding, and the routed VXLAN interface provides the per-IP-VRF overlay data-plane construct needed for symmetric routing. The IRB interfaces on the local MAC-VRFs must advertise learned local host routes so that remote PEs have the necessary host reachability information. The MAC-VRFs also need the appropriate EVPN control-plane configuration so host MAC/IP information can be exchanged, while the IP-VRF participates in L3 VPN-style route exchange for routed reachability. Option A is false because anycast gateway is not optional in this design for Leaf1 and Leaf2. Anycast gateway allows the same default-gateway IP and virtual MAC behavior to exist consistently on multiple leaves serving the same subnet. Without it, host default-gateway behavior would be inconsistent and traffic mobility across the fabric would break expected distributed gateway operation. Reference: interface-less symmetric routing, IRB, anycast gateway, routed VXLAN interface.

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

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

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

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

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

The route target is the extended community consistently associated with EVPN updates to control route import and export between EVPN instances. In SR Linux EVPN services, route targets determine which MAC-VRF or IP-VRF should import a received EVPN route. This is essential for tenant separation because multiple tenants may use overlapping MAC or IP address spaces while sharing the same physical fabric and BGP control plane. The AFI/SAFI is not an extended community; it identifies the BGP address family and subsequent address family used to carry EVPN NLRI. The EVPN route type is also not an extended community; it is part of the EVPN NLRI structure and identifies whether the route is RT-1, RT-2, RT-3, RT-4, RT-5, and so on. The VXLAN network ID may be carried or inferred through service and encapsulation-specific attributes, but it is not universally present as the required extended community in every EVPN update. The route target is the mandatory policy element that enables receiving PEs to place EVPN routes into the correct service context. Reference: EVPN extended communities, route-target import/export policy, tenant service identification.

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

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

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.

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