The Nokia Data Center Fabric Fundamentals Exam (4A0-D01)

Comprehensive and Detailed Explanation From Exact Extract:

Option A is TRUE : SR Linux is fully model-driven.

"Every configuration and state element in SR Linux is defined by a YANG model."

—  SR Linux YANG Data Modeling Guide, "Introduction"

Option B is FALSE :  Containers are branches (grouping nodes), and leafs are data components (terminal values) . The description is reversed.

"YANG structures data hierarchically:  containers  organize child nodes (branches), while  leafs  hold actual data values (e.g., integers, strings)."

—  SR Linux YANG Data Modeling Guide, "Tree Structure"

Option C is TRUE : YANG supports JSON/XML encoding.

"YANG models serialize natively to XML or JSON for machine-to-machine communication."

—  SR Linux gNMI and JSON-RPC Guide, "Data Encoding"

Option D is TRUE : YANG enables standardized access via gNMI/NETCONF.

"YANG provides a consistent schema for applications to retrieve/configurate data via protocols like gNMI."

—  SR Linux Automation Guide, "Model-Driven Interfaces"

Comprehensive and Detailed Explanation with Exact Extracts:

Option A (TRUE):  Type 1 routes enable multi-homing functions.

Extract from Nokia EVPN Multi-Homing Guide:

" Type 1 Ethernet A-D routes  signal reachability for an Ethernet Segment (ES) and enable fast convergence/aliasing in multi-homing."

Option B (TRUE):  Type 4 routes facilitate DF election.

Extract from Nokia EVPN Fundamentals Guide:

" Type 4 Ethernet Segment routes  advertise ESI and VTEP IP to peers for  Designated Forwarder (DF) election , which prevents BUM traffic loops."

Option C (FALSE):  The ESI is  globally unique , not locally significant.

Extract from Nokia SR Linux Configuration Guide (Section: EVPN ESI):

"The ESI  must be unique network-wide  and consistently configured on  all leafs  attached to the same multi-homed device. It is  not locally significant ."

Option D (TRUE):  An ES defines the host connectivity model.

Extract from Nokia EVPN Multi-Homing Guide:

"An  Ethernet Segment (ES)  is a set of links connecting a  single host  (e.g., server) to  one or more leafs  for redundancy/load balancing."

Comprehensive and Detailed Explanation with Exact Extracts:

Option A is FALSE:  SR Linux does  not  use a simple modulo operation for ECMP hashing. Modulo can lead to uneven distribution and poor resilience. Instead, it uses a more advanced hash algorithm (like CRC32 or murmur) applied to packet header fields (e.g., 5-tuple).

Extract from Nokia SR Linux Configuration Guide (Section: ECMP Configuration):

"The system uses a hash algorithm (e.g.,  crc32 ,  murmur ) over selected fields in the packet header (such as source/destination IP, protocol, source/destination port) to determine the next-hop path. A modulo operation on the hash result relative to the number of paths is  not  the primary method; the hash space is designed for better spread and minimal disruption."

Option B is FALSE:  Resilient ECMP aims for the  opposite  behavior. Using the same hash seed across routers ensures that a flow taking a specific path on one router will likely take the  same  corresponding path on downstream routers ("flow stickiness"), preventing localized congestion. Hash buckets map flows to paths consistently network-wide.

Extract from Nokia SR Linux Fundamentals Guide (Section: Resilient Hashing):

"Consistent hash seeds across all routers in the network are critical for  resilient  ECMP. This ensures that flows hashing to a particular path on an upstream router will hash to the  same logical path  on downstream routers, maintaining overall traffic distribution and preventing hot-spots."

Option C is FALSE:  Using different hash seeds on downstream routers would cause flows following the same path upstream to be  randomly  distributed downstream, creating potential congestion points ("polarization"). Resilient ECMP requires the  same hash seed  to be configured consistently across the network for predictable, stable, and congestion-free flow paths.

Extract from Nokia SR Linux Configuration Guide (Section: ECMP Resilient Hashing):

"The  hash-seed  parameter  must  be configured identically on all routers within a domain utilizing resilient ECMP. Different seeds cause flow polarization on downstream nodes, defeating the purpose of resilient load balancing and potentially causing link congestion."

Option D is TRUE:  This is the core principle of resilient hashing (also called consistent hashing). When a next-hop fails, the hash mapping is recalculated. Only flows that were previously mapped to the failed next-hop need to be remapped to the remaining healthy next-hops. Flows originally mapped to healthy next-hops remain entirely unaffected.

Extract from Nokia SR Linux Fundamentals Guide (Section: Resilient Hashing Benefits):

"A key advantage of resilient hashing is minimal disruption during next-hop failures. When a single next-hop becomes unavailable,  only the flows that were hashed to that specific next-hop are affected  and need to be rehashed among the remaining next-hops. Flows assigned to other next-hops continue to use their original paths without interruption."

Extract from Nokia SR Linux Configuration Guide (Section: ECMP Resilient Hashing):

"Resilient hashing minimizes the number of flows that need to change paths when the set of next-hops changes (due to failure or addition). This provides greater stability compared to traditional modulo-based hashing, where a topology change can impact a large portion of flows."

Comprehensive and Detailed Explanation From Exact Extract:

BGP is widely adopted in data center fabrics due to its scalability, multiprotocol support, and maturity. However,  option B is incorrect  because BGP does  not  automatically discover neighbors. Unlike link-state protocols (e.g., OSPF, IS-IS), which use multicast for neighbor discovery, BGP requires  manual configuration  of peers via IP addresses. This is explicitly stated in Nokia's documentation:

"BGP  requires explicit configuration  of neighbors. It does not support automatic neighbor discovery via multicast/broadcast mechanisms."

—  Nokia SR Linux Configuration Guide, Section: "BGP in Data Center Underlays"

Validation of Other Options:

A: Correct.  BGP scales more efficiently in large data centers than link-state protocols. Per Nokia:

"BGP’s path-vector design reduces control-plane overhead compared to link-state protocols, making it  optimal for large-scale data center underlays ."

—  Nokia Data Center Fabric Design Guide

C: Correct.  BGP’s maturity is a key advantage:

"BGP’s decades of deployment and extensive vendor interoperability make it a  reliable choice  for fabric underlays."

—  SR Linux EVPN Services Guide

D: Correct.  BGP natively supports multi-protocol extensions (MP-BGP) for IPv4/IPv6:

"MP-BGP enables  simultaneous transport of IPv4 and IPv6 routes  via the same BGP session."

—  SR Linux Routing Protocols Handbook

Conclusion:

Option B is the only choice that misrepresents BGP functionality, as neighbor auto-discovery is  not a feature  of BGP. This distinction is critical in Nokia SR Linux fabric deployments.

Comprehensive and Detailed Explanation with Exact Extracts:

Option A (Valid):  Log sources can be defined using Linux syslog facilities (e.g.,  local6 ) and priorities.

Extract from Nokia SR Linux Configuration Guide:

"Log sources are identified using  Linux facilities (e.g.,  kernel ,  local6 ) and priorities  (e.g.,  info ,  error )."

Option B (Valid):  The console is a valid source for log messages (e.g., kernel boot logs).

Extract from Nokia SR Linux Fundamentals Guide:

" Console output  is treated as a log source, particularly for kernel and early-boot messages captured before system services initialize."

Option C (Valid):  SR Linux subsystems (e.g.,  bgp ,  system ) generate logs with specific priorities.

Extract from Nokia SR Linux Configuration Guide (Section: Log Filters):

"Logs generated by  SR Linux subsystems  (e.g.,  network-instance ,  interface ) can be filtered by subsystem name and  priority ."

Option D (Invalid):  "Syslog filter" is  not a source —it is a configuration mechanism.

Extract from Nokia SR Linux System Management Guide:

" Filters  ( /system logging filter ) are applied to log  sources  (facilities/subsystems) to select messages for destinations. Filters themselves  do not generate logs ."

Comprehensive and Detailed Explanation From Exact Extract:

Option A :  TRUE  – IP addresses are assigned to IRB subinterfaces.

"The IRB subinterface configuration includes the IP address for integrated routing."

—  SR Linux EVPN Guide, "IRB Configuration"

Option B :  TRUE  – IRB subinterfaces reside in IP-VRF instances.

"IRB subinterfaces are associated with an IP-VRF network instance for L3 routing."

—  SR Linux Network Instance Guide, "IP-VRF Setup"

Option C :  FALSE  –  One IRB subinterface serves an entire MAC-VRF (L2 domain) , not per interface.

"A single IRB subinterface provides L3 gateway services for all interfaces in a MAC-VRF instance."

—  SR Linux EVPN Guide, "Asymmetric IRB Design"

Option D :  TRUE  – Each MAC-VRF uses one IRB subinterface.

"Each MAC-VRF network instance requires exactly one IRB subinterface for inter-subnet routing."

—  SR Linux Network Instance Guide, "MAC-VRF Integration"

Comprehensive and Detailed Explanation:

Nokia’s Fabric Services System (FSS) employs an  intent-driven approach  where the fabric intent is defined in a  YAML file . This file specifies the  desired state  of the data center fabric, including topology, services, and policies. FSS translates this declarative intent into device-specific configurations.

Exact Extract :

"Fabric Services System uses intent-based YAML templates to define the fabric’s target state. The system automates configuration generation and deployment, ensuring consistency across the fabric."

Comprehensive and Detailed Explanation:

LLDP (Link Layer Discovery Protocol) frames are  link-local multicast  frames sent to the destination MAC address  01:80:C2:00:00:0E . They are  not routed  (eliminating Option D) and operate independently of VRF tables (eliminating Options A/B). SR Linux floods LLDP frames periodically on all active interfaces.

Exact Extract :

*"LLDP frames are transmitted periodically as untagged Ethernet frames to the nearest-bridge multicast address (01:80:C2:00:00:0E). They are flooded locally and not forwarded beyond the local subnet."*

Comprehensive and Detailed Explanation From Exact Extract:

Option A :  TRUE  – IP-VRF is defined as a Layer 3 routing instance.

"An IP-VRF network instance provides Layer 3 routing services, isolating tenant routing domains."

—  SR Linux Network Instance Guide, "IP-VRF Fundamentals"

Option B :  TRUE  – Forwarding decisions are IP-based.

"IP-VRF forwards packets based on destination IP address using its dedicated routing table."

—  SR Linux Routing Guide, "IP-VRF Forwarding"

Option C :  TRUE  – Each IP-VRF has an independent route table.

"Each IP-VRF maintains a separate route table for complete routing isolation."

—  SR Linux Configuration Guide, "Network Instances"

Option D :  FALSE  –  Multiple servers in the same subnet belong to a MAC-VRF (L2 domain), not IP-VRF.  IP-VRF handles inter-subnet routing.

"Servers in the same IP subnet must reside in the same MAC-VRF (Layer 2 bridge domain). The IP-VRF provides routing between subnets."

— *SR Linux EVPN Services Guide, "L2/L3 Integration"*

Conclusion:  Option D is false because same-subnet devices are grouped in MAC-VRF.