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

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 DCI design, the same physical or logical router performs both the data center gateway role and the WAN PE role. This is why option D is correct. The device terminates or participates in the data center-side EVPN service and also handles the WAN-side VPN transport, including route translation or re-advertisement where needed. This approach avoids exposing every data center leaf router to the WAN and avoids requiring route reflector reachability between data centers. It also avoids building VXLAN tunnels directly between all leaf routers in separate data centers. Those characteristics belong to gateway-less DCI, where the EVPN overlay stretches more directly across the WAN and the WAN must carry the underlay or overlay reachability required by the data center leaves. Integrated gateway design is more controlled: the gateway is the interworking point, which makes it suitable when the provider or operator wants a strong service boundary and centralized DCI policy enforcement. Reference: integrated gateway-based DCI, single-router gateway/WAN PE function, EVPN/VPN interworking.

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

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

In SR Linux, a Layer 2 EVPN service is implemented using a MAC-VRF network instance. The MAC-VRF represents the tenant bridge domain and is associated with access subinterfaces and a VXLAN data-plane mapping. Local hosts are learned through the data plane when Ethernet frames arrive on local interfaces. Remote hosts, however, are not learned by flooding or by configuring static per-peer VXLAN interfaces. They are learned through MP-BGP EVPN updates, especially EVPN route type 2 MAC/IP Advertisement routes. Option B is false because SR Linux does not require a separate manually configured VXLAN interface toward each remote VTEP for the MAC-VRF. Instead, the MAC-VRF is bound to VXLAN encapsulation and a VNI, while remote VTEPs and their MAC reachability are discovered dynamically through the EVPN control plane. This is one of the central advantages of EVPN compared with static VXLAN flood-and-learn models: the overlay endpoints and endpoint reachability are signaled through BGP, reducing manual configuration and improving scale. Reference: SR Linux L2 EVPN MAC-VRF configuration, MP-BGP EVPN learning, VXLAN data-plane mapping.

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

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 DCI solution, the data center gateway and WAN PE functions reside on the same router. This device acts as the interworking point between the data center EVPN/VXLAN environment and the WAN transport service. It may need to translate or interwork between VXLAN encapsulation in the data center and MPLS or another WAN tunneling protocol in the WAN. For Layer 3 services, the integrated gateway may also re-advertise EVPN routes learned from the data center fabric into VPN-IPv4 or VPN-IPv6 routes for transport across the WAN. Option B does not describe the integrated gateway model. A border leaf using eBGP or static routes to interconnect with a gateway is a decoupled gateway-based design, where the data center border leaf and WAN PE/gateway are separate devices with a routing handoff between them. In the integrated model, that border-leaf-to-separate-gateway handoff is not the defining architecture because the gateway and WAN PE roles are combined on one router. Reference: integrated gateway DCI, VXLAN-to-WAN interworking, EVPN to VPN-IPv4/VPN-IPv6 re-advertisement, decoupled gateway distinction.

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

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

A route distinguisher is used in MP-BGP VPN and EVPN address families to make otherwise overlapping tenant routes unique in the BGP control plane. In EVPN, different tenants or EVPN instances may legitimately use the same MAC or IP values. The route distinguisher makes the NLRI globally unique by prepending a unique value to the tenant route. It is typically unique per PE and per EVI, and it is carried in EVPN route advertisements. However, the route distinguisher does not control route import, export, or service membership. That role belongs to the route target, which is a BGP extended community used by receiving PEs to decide which EVPN instance should import the route. Therefore, option D is not part of the correct description of a route distinguisher. Saying that the RD identifies the EVPN instance in the control plane confuses RD uniqueness with route-target membership. The RD makes routes unique; the route target associates those routes with the appropriate MAC-VRF or IP-VRF import policy. Reference: EVPN route distinguisher, overlapping tenant addresses, route target separation.

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