4A0-D01 Exam Dumps : Nokia Data Center Fabric Fundamentals Exam

Comprehensive and Detailed Explanation From Exact Extract:

Option A: TRUE – Only one management interface (mgmt0) exists.

"The system supports a single management interface (mgmt0) for out-of-band access."

— SR Linux Interface Guide, "Management Port"

Option B: TRUE – Network interfaces bind to hardware ports.

"Network interfaces (e.g., ethernet-1/1) map directly to physical line card ports."

— SR Linux Interface Guide, "Port Mapping"

Option C: FALSE – Loopback interfaces are virtual, not physical.

"Loopback interfaces (e.g., lo0) are logical entities with no physical hardware association."

— SR Linux Routing Guide, "Loopback Interfaces"

Option D: TRUE – L2 parameters (e.g., MTU) are set at the main interface; L3 (e.g., IP) at subinterfaces.

"Layer 2 attributes (MTU, admin-state) are configured under the main interface. Layer 3 settings (IP, VRF) are applied to subinterfaces."

— SR Linux Interface Guide, "Subinterface Configuration"

Comprehensive and Detailed Explanation From Exact Extract:

Option A: TRUE – "duplicate" status confirms multiple interfaces.

"A 'duplicate' entry indicates the MAC was detected on multiple ports."

— SR Linux Bridge Table Guide, "Duplicate MAC Handling"

Option B: FALSE – No re-learning rate data is present. The output shows a static duplicate entry, not rate violations.

"MAC re-learning rate thresholds generate specific alerts (not shown here). This exhibit only shows a persistent duplicate state."

— SR Linux Monitoring Guide, "MAC Mobility Events"

Option C: TRUE – The MAC is explicitly bound to ethernet-1/10.0.

"The 'Destination' column specifies the interface where the MAC was last observed."

— SR Linux CLI Reference, "show bridge-table"

Option D: TRUE – Duplicate detection is active since duplicates are flagged.

"The presence of 'duplicate' entries confirms MAC duplication detection is enabled."

— SR Linux Security Guide, "MAC Duplication"

Conclusion: Option B is unsupported by the exhibit.

Comprehensive and Detailed Explanation From Exact Extract:

In a leaf-spine Clos network:

Option A is TRUE: Each leaf connects to every spine for full redundancy and non-blocking fabric.

"In a Clos topology, every leaf node connects to every spine node, ensuring any-to-any connectivity."

— Nokia Data Center Fabric Design Guide, "Leaf-Spine Architecture"

Option B is TRUE: East-west traffic flows predictably via spines.

"Leaf-spine provides deterministic paths for east-west traffic, minimizing latency and jitter."

— Nokia SR Linux EVPN Configuration Guide, "Traffic Flow in Clos Networks"

Option C is FALSE: Clos networks do not use STP. They rely on Layer 3 ECMP and routing protocols for loop avoidance.

"Clos fabrics eliminate STP by design. Forwarding loops are avoided through ECMP and routing protocols (e.g., BGP), not Layer 2 STP."

— Nokia Data Center Fabric Best Practices, "Loop Avoidance"

Option D is TRUE: ECMP load-balances traffic across multiple spine paths.

"ECMP is fundamental to leaf-spine, distributing traffic across all available spine links."

— Nokia SR Linux Routing Guide, "ECMP in Clos Fabrics"