Free Practice Questions for Nokia 4A0-D03 Exam

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

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

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

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

A decoupled gateway-based DCI model separates the data center border-leaf function from the WAN PE function. This separation is the key design point. The border leaf remains part of the data center EVPN/VXLAN environment, while the WAN PE participates in WAN VPN transport and policy enforcement. Because the roles are split across two devices, the handoff between the border leaf and WAN PE provides a clean administrative and operational boundary. That boundary is useful for security policy, QoS marking, traffic classification, and troubleshooting ownership. The WAN does not need direct reachability to every leaf and route reflector as in a gateway-less model. The WAN PE also does not peer directly with the data center route reflector in a decoupled model; route exchange occurs through the border-leaf/WAN-PE handoff. VXLAN tunnels between leaf routers across different data centers are characteristic of gateway-less extension, not decoupled gateway operation. Therefore, the statement about clear demarcation between the data center border leaf and WAN PE is the accurate description. Reference: decoupled gateway-based DCI, security/QoS demarcation, WAN PE separation.

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

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

EVPN route type 2 carries MAC/IP advertisement information. It is central to host-based routing and to designs where the fabric must distribute host MAC-to-IP bindings for integrated routing and bridging. In host routing, RT-2 is required because individual host reachability is signaled through MAC/IP advertisements. In interface-less prefix routing, RT-2 is still needed because the system relies on host or gateway MAC/IP information associated with the IRB and distributed gateway behavior. Interface-ful unnumbered designs may also require RT-2-style information to resolve next-hop or adjacency behavior because the routed interface does not use a conventional numbered next-hop model. Prefix routing with interface-ful numbered operation is different. In that model, the routed interface has explicit IP addressing and prefix reachability can be carried with L3 prefix routes without requiring EVPN RT-2 host MAC/IP advertisement as a dependency. Therefore, the symmetric routing option that does not require EVPN route type 2 is prefix routing interface-ful numbered. Reference: symmetric L3 EVPN routing models, RT-2 MAC/IP advertisements, prefix routing behavior.

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