Nokia Updated 4A0-D01 Exam Questions and Answers by jannat

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.

Comprehensive and Detailed Explanation with Exact Extracts:

Options A, B, and C describe standard leaf-spine eBGP operation:

Leaf routers peer with spines (eBGP), advertising local prefixes (Option C).

Spines learn prefixes from leaves (Option B) and re-advertise them to other leaves (Option A).

Extract from Nokia Data Center Fabric Guide (Section: eBGP Leaf-Spine):

"Leaf routers establish eBGP sessions with spine routers, advertising prefixes of locally attached endpoints. Spine routers propagate these prefixes to all other leaf routers, providing full connectivity."

Option D is FALSE: Leaf routers do not peer directly with each other in standard designs. They communicate via spines.

Extract from Nokia Data Center Fabric Guide (Section: Routing Design):

"Leaf routers never establish direct eBGP sessions with other leaf routers. All inter-leaf communication occurs via spine routers, which act as route reflectors or forwarding hubs."

Comprehensive and Detailed Explanation with Exact Extracts:

Option A (TRUE): SR Linux uses local6 as the default syslog facility.

Extract from Nokia SR Linux System Management Guide:

"System logs are emitted with the syslog facility local6 by default, allowing integration with standard Linux syslog utilities."

Option B (TRUE): SR Linux supports local encrypted log storage.

Extract from Nokia SR Linux Security Guide:

"Log files stored locally can be encrypted using AES-256 to ensure confidentiality and integrity of audit trails."

Option C (TRUE): Log filters are fully supported for message selection.

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

"Filters can be applied to log messages based on severity, subsystem, or content, enabling granular control over log destinations."

Option D (FALSE): SR Linux uses systemd-journald, not rsyslog, for log management.

*Extract from Nokia SR Linux Release Notes (v21.11+):*

"SR Linux logging configurations are not translated to /etc/rsyslog.conf. The system relies on systemd-journald for log collection and storage, with configurations managed via SR Linux CLI and stored in /etc/journald.conf."