4A0-D03 Questions and Answers

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

Layer 3 multi-homing is fundamentally about redundant or load-balanced L3 reachability for external prefixes, not about Layer 2 broadcast-domain flooding toward a host. In single-active L3 multi-homing, DF election determines which attached leaf is active for the Ethernet Segment, and only that leaf advertises or forwards for the attached customer route as required by the redundancy model. In all-active L3 multi-homing, multiple leaf routers can be valid next-hops for the same learned third-party prefix, and remote PEs may load-balance toward them based on the Ethernet Segment association. Learned external prefixes are carried as EVPN route type 5 IP Prefix routes, which is the correct route type for L3 reachability. The Ethernet Segment is associated with the next-hop for those prefixes so that remote PEs understand the multi-homed nature of the path. Option B is false because BUM forwarding is a Layer 2 EVPN concern. In an all-active L3 multi-homing scenario, DF election is not used to identify a BUM-forwarding leaf for host traffic in the same way it is used in Layer 2 multi-homing services. Reference: L3 EVPN multi-homing, RT-5 prefix routes, ES next-hop behavior.

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

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

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

Ethernet Auto-Discovery per EVI information is used in EVPN multi-homing to advertise that a PE has reachability to a particular Ethernet Segment for a specific EVPN instance. Remote PEs use this information for aliasing, allowing them to forward known unicast traffic toward a multi-homed Ethernet Segment through eligible PEs rather than relying only on the PE that advertised a specific MAC route. In VXLAN-based EVPN, the update also carries information needed by remote peers to select the proper data-plane encapsulation and VNI for the service. The multi-homing behavior advertised with the Ethernet Segment enables remote peers to understand whether the attachment is operating in all-active or single-active mode. Option D is the false statement in this context because route-target handling is a general BGP EVPN import/export mechanism associated with VPN route policy and extended communities; it is not the specific operational function that defines AD per EVI behavior. The AD per EVI route's purpose is Ethernet Segment reachability for an EVI, not route-target-based service identification by itself. Reference: EVPN route type 1, AD per EVI, aliasing and multi-homing signaling.

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

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

A BGP route target is an extended community used to control which EVPN routes are imported into which MAC-VRF or IP-VRF. It is carried with EVPN updates and acts as the import/export policy tag for tenant service membership. The statement that it is a BGP extended community is correct. It is also correct that route targets support multi-tenant operation, because they allow different EVPN instances to carry potentially overlapping MAC or IP information while importing only the routes intended for that service. However, option D is false in the wording used here. The route target does not itself identify the EVPN instance in the control plane as a unique route identifier. That role is more closely associated with the route distinguisher and EVPN NLRI construction, while the route target determines import eligibility. A route target tells a receiving PE whether the route belongs in a local service instance, but it is not the unique identity of the EVPN route. This distinction is critical: route distinguishers make routes unique; route targets control route distribution and service membership. Reference: EVPN route targets, BGP extended communities, route import/export policy, RD versus RT function.

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

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

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.

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