Nokia Updated 4A0-D03 Exam Questions and Answers by kenza

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

A Gratuitous ARP is an ARP message a host sends to announce or refresh its own IP-to-MAC binding without waiting for another host to request it. In a traditional Ethernet subnet, the GARP is sent as a broadcast so that other hosts can update their ARP caches with the sender's current MAC address. This is useful after a host boots, changes NICs, moves to another attachment point, or takes over an IP address in a redundancy scenario. In EVPN environments, GARPs are also important because a leaf can snoop the ARP information and update local proxy ARP and EVPN MAC/IP state. Option D is false because recipients do not acknowledge a gratuitous ARP with a reply. GARP is an announcement mechanism, not a request/response transaction. If every receiving host acknowledged a broadcast GARP, the result would be unnecessary ARP traffic amplification. The correct behavior is passive update of ARP state by receiving systems and, in EVPN, potential control-plane propagation of the learned binding by the local PE. Reference: GARP behavior, proxy ARP learning, Layer 2 EVPN endpoint update procedures.

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

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.

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