4A0-D03 Reviews Questions

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

EVPN route type 4 is the Ethernet Segment route. Its core role is to advertise Ethernet Segment membership so that PEs attached to the same multi-homed segment can discover each other. This discovery is essential for multi-homing procedures such as DF election, split-horizon behavior, and redundancy handling. When multiple PEs advertise the same ESI, the EVPN control plane can build the candidate set of PEs that participate in that Ethernet Segment. This enables DF election for BUM forwarding and supports the correct interpretation of the segment's redundancy model. The incorrect statement is option C. The election algorithm itself is not the basic function of the route type 4 advertisement in the way the question frames it. The route type is primarily about Ethernet Segment discovery and participation; the algorithmic decision process is derived from configured DF election behavior and candidate information, not from route type 4 acting as a generic algorithm identifier. Therefore, route type 4 enables DF procedures, but it is not described as the mechanism that identifies the election algorithm type. Reference: EVPN RT-4 Ethernet Segment route, DF election, multi-homing discovery.

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

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

This scenario describes all-active Layer 2 EVPN multi-homing with a host connected through a LAG to Leaf1 and Leaf2. The LAG subinterface is associated with the MAC-VRF on both participating leaves, and the Ethernet Segment ES-1 is configured for all-active multi-homing. In all-active operation, both leaf routers can be active attachment points for host-originated traffic, and remote traffic can use EVPN multi-homing mechanisms to reach the segment. Option D is false because the host does not know or use the EVPN Designated Forwarder state when sending BUM traffic. The host forwards over its LAG based on its local LAG hashing and LACP behavior. DF election is an EVPN PE-side mechanism used mainly to control which PE forwards BUM traffic from the EVPN overlay toward the Ethernet Segment, preventing duplicate delivery to the multihomed access network. The host itself does not selectively forward all BUM traffic toward the DF. That distinction is critical: DF controls overlay-to-segment replication, while the host's LAG controls host-to-leaf link selection. Reference: all-active L2 EVPN multi-homing, host LAG behavior, DF election scope, BUM 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.

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