Pass the Nokia Nokia Certified Data Center Fabric Professional 4A0-D03 Questions and answers with CertsForce

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

In many SR Linux data center fabrics, eBGP is used in the underlay because it gives simple hop-by-hop routing, fast convergence, and clean autonomous-system separation between leaf and spine nodes. The EVPN overlay, however, is a separate MP-BGP control plane used to distribute EVPN NLRI. The overlay route-reflector session does not have to reuse the leaf's underlay autonomous system number. In practice, an overlay BGP group may use a distinct local AS or configuration model separate from the underlay AS design. Therefore, option B is false. The route reflector's cluster ID is configured on the route reflector itself to prevent reflection loops and identify the RR cluster. Redundant route reflectors can be deployed for resiliency, and clients may receive duplicate paths or duplicate updates from multiple RRs; the BGP decision process and route reflection rules handle this. The key design distinction is that underlay eBGP provides IP reachability between loopbacks, while overlay MP-BGP EVPN carries tenant service reachability. Mixing these roles leads to incorrect AS planning. Reference: SR Linux EVPN MP-BGP route reflectors, eBGP underlay, overlay BGP sessions.

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

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

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

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

VXLAN provides a Layer 2 overlay over a Layer 3 underlay by encapsulating Ethernet frames in UDP/IP. This allows tenant bridge domains to span a routed IP fabric without requiring the underlay itself to behave like one large Layer 2 network. VXLAN uses a 24-bit VXLAN Network Identifier, which supports approximately 16 million logical overlays, far exceeding the scale of traditional 12-bit VLAN IDs. Because the VXLAN underlay is IP-routed, traffic can benefit from ECMP across equal-cost paths, improving fabric utilization and resiliency. The false statement is B. VXLAN was not originally developed specifically to support EVPN. VXLAN began as a data-plane overlay encapsulation technology, while EVPN later became the preferred control plane for distributing MAC, MAC/IP, multicast, and prefix reachability in VXLAN-based fabrics. In modern data center design, EVPN and VXLAN are commonly paired: VXLAN supplies the encapsulation and VNI-based segmentation, while EVPN supplies scalable control-plane learning and signaling. Reference: VXLAN data plane, EVPN control plane, ECMP underlay, VNI-based tenant isolation.

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

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.

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