Nokia Certification 4A0-D01 Exam Questions and Answers PDF

Comprehensive and Detailed Explanation with Exact Extracts:

Options A, B, and C are Day 2+ operations:

A: Telemetry enables real-time monitoring.

B: Health analysis supports proactive maintenance.

C: Sandbox validates changes pre-deployment.

Extract from Nokia FSS Day 2 Operations Guide:

"Day 2+ includes telemetry-based monitoring, health analytics, and sandbox testing for upgrades/changes."

Option D is a Day 0 activity:

Fabric intents define initial design templates (Day 0), not ongoing operations.

Extract from Nokia FSS Lifecycle Management Guide:

"Fabric intents are used during Day 0 design to build templates. Day 2+ focuses on operational tasks like monitoring (A), health checks (B), and sandbox validation (C)."

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"