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

The exhibit describes a Layer 3 multi-homing scenario where the Ethernet Segment is associated with an IP-VRF and the configuration references an EVI value of 1000. The segment is configured with all-active multi-homing, allowing multiple attached leaf routers to advertise reachability for the same external L3 next-hop or third-party prefix attachment. In this model, the Ethernet Segment represents the shared L3 attachment and is used by EVPN to associate remote prefix reachability with the multi-homed segment. The incorrect statement is that a LAG must be configured on the connected leaf routers and the host. That requirement is specific to many Layer 2 all-active host attachment designs, where the host commonly uses LACP toward multiple leaf routers and the leaf LAG subinterfaces are associated with the Ethernet Segment. In Layer 3 multi-homing, the attached device can be a router or VNF, and the EVPN ES association can be used for L3 prefix reachability without mandating that the host side be configured as a LAG. Reference: L3 EVPN multi-homing, EVI association, all-active Ethernet Segment 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 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]:

Aliasing is an EVPN multi-homing mechanism that allows remote PEs to send traffic to any eligible PE attached to the same Ethernet Segment, even if a specific MAC address was learned and advertised by only one of those PEs. This avoids a traffic bottleneck and enables load-sharing in all-active multi-homing designs. The route type used to implement this behavior is the Ethernet Auto-Discovery per EVI route, commonly referred to as AD per EVI. This route tells remote PEs that a given PE has reachability to a specific Ethernet Segment for a specific EVPN instance. When remote PEs receive these advertisements from multiple PEs for the same ESI and EVI, they can treat those PEs as valid next-hops for traffic toward that Ethernet Segment. Ethernet Segment routes support ES discovery and DF election, while IP/MAC routes advertise host MAC and optionally IP binding information. AD per ES routes are used for broader Ethernet Segment-level procedures, but aliasing at the service level relies on AD per EVI reachability. Reference: EVPN route type 1, AD per EVI, aliasing in all-active multi-homing.

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

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

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

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

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

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 provides the logical L3 gateway function between a Layer 2 MAC-VRF and a Layer 3 IP-VRF on the same PE. It allows locally bridged hosts to route into the tenant IP-VRF while preserving EVPN control-plane signaling for MAC/IP reachability. The IRB subinterface must have at least one IP address because it acts as the routed gateway for the subnet, and it may also be configured with ACLs to apply traffic policy at the L3 boundary. Option B is false because it incorrectly generalizes the IRB relationship. In SR Linux EVPN service modeling, an IRB subinterface connects a MAC-VRF to an IP-VRF in a controlled one-to-one service attachment context; the design is not that both IP-VRFs and MAC-VRFs arbitrarily contain multiple IRB interfaces for the same relationship. A MAC-VRF has its IRB gateway association into the IP-VRF, and the IP-VRF may connect to multiple MAC-VRFs through distinct IRB contexts, but the statement as written is not the correct rule for IRB interface behavior. Reference: SR Linux IRB interface operation, MAC-VRF/IP-VRF interconnection, gateway IP and ACL support.

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

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

Layer 3 EVPN multi-homing with a centralized router uses an Ethernet Segment to associate multiple leaf routers with a common external L3 attachment. The centralized router is part of that attached segment from the forwarding perspective, and the connected leaf routers advertise third-party or customer prefixes into EVPN so that remote leaves can reach those prefixes through the multi-homed attachment. For L3 EVPN, learned customer prefixes are normally advertised using EVPN route type 5, which carries IP prefix reachability. In an all-active design, remote leaf routers may load balance traffic to the customer prefix through multiple attached leaf routers because the ES next-hop allows the remote PE to understand that the prefix is reachable through a multi-homed Ethernet Segment. The false statement is that every router participating in the Ethernet Segment must be configured with all-active mode. Multi-homing mode is a design and configuration property of the EVPN PEs participating in the ES, and designs may use single-active or all-active behavior depending on redundancy and forwarding requirements. Reference: L3 EVPN multi-homing, centralized router attachment, EVPN RT-5 prefix advertisement.

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