4A0-D01 Sample Questions Answers

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 From Exact Extract:

Option A: TRUE – Fabric intent is declaratively defined in YAML.

"FSS uses YAML-based declarative intent to define and manage fabric configurations."

— Nokia Fabric Services System User Guide, "Intent-Based Fabric"

Option B: FALSE – The Digital Sandbox is for pre-deployment validation, not performance monitoring.

"The Digital Sandbox simulates configurations for validation before deployment. Performance monitoring is handled by telemetry analytics, not the sandbox."

— Nokia FSS Deployment Guide, "Digital Sandbox"

Option C: TRUE – Telemetry is contextualized with intent.

"Telemetry data is correlated with fabric intent, providing context-aware insights."

— Nokia FSS Operations Guide, "Telemetry and Analytics"

Option D: TRUE – FSS is cloud-native for flexible integration.

"FSS’s cloud-native microservices architecture simplifies integration with customer ecosystems."

— Nokia FSS Architecture White Paper, "Cloud-Native Design"

Conclusion: Option B misrepresents the Digital Sandbox’s purpose.

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 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."

Comprehensive and Detailed Explanation From Exact Extract:

The SR Linux Application Manager (app_mgr):

Option A is TRUE: Monitors application health and restarts failed processes.

"The Application Manager monitors the status of all running applications and triggers recovery actions if failures occur."

— SR Linux System Management Guide, "Application Manager"

Option B is TRUE: Manages both Nokia-provided and user-added containerized applications.

"app_mgr manages the lifecycle of all applications, whether preinstalled by Nokia or custom-developed by users."

— SR Linux DevOps Guide, "Custom Application Deployment"

Option C is TRUE: Parses application manifests and launches applications.

"The Application Manager reads manifest files (including configuration) and starts applications accordingly."

— SR Linux Configuration Fundamentals, "Application Initialization"

Option D is FALSE: Translation of YANG to protobuf is handled by the Management Server (mgmt_server), not app_mgr.

"The Management Server (mgmt_server) compiles YANG models into protobuf schemas for the Interface Database (IDB). The Application Manager does not handle model translation."

— SR Linux Architecture White Paper, "Data Modeling Components"

Comprehensive and Detailed Explanation with Exact Extracts:

Option A (TRUE): VTEPs (VXLAN Tunnel Endpoints) are deployed flexibly.

Extract from Nokia VXLAN Configuration Guide:

"VTEPs can reside on hypervisors (virtual switches), leaf routers (network-based overlays), or data center gateways (for inter-fabric connectivity)."

Option B (TRUE): EVPN is the control plane for VXLAN.

Extract from Nokia EVPN-VXLAN Integration Guide:

"EVPN route types (e.g., Type 2 MAC/IP, Type 3 Inclusive Multicast) are exchanged between VTEPs to establish forwarding semantics for the VXLAN overlay."

Option C (FALSE): The VNI (VXLAN Network Identifier) is not automatically assigned per VTEP.

Extract from Nokia SR Linux Fundamentals Guide (Section: VXLAN):

"The VNI is a manually configured 24-bit segment ID per Layer 2 domain (or VRF for L3VNI). A single VTEP handles multiple VNIs simultaneously. VTEPs are identified by IP addresses, not VNIs."

Option D (TRUE): VXLAN enables L2 extension over IP underlays.

Extract from Nokia Data Center Design Guide:

"VXLAN encapsulation provides Layer 2 connectivity between workloads (e.g., VMs, containers) across a routed underlay network."

Comprehensive and Detailed Explanation with Exact Extracts:

Option B (CPM-filter ACL) is CORRECT:

The CPM-filter ACL is explicitly designed to match control-plane traffic and copy it to the CPM (Control/Management Plane). It is instantiated in hardware on all line cards.

Extract from Nokia SR Linux Security Guide (Section: Control Plane Protection):

"The cpm-filter ACL is instantiated on every line card to identify packets destined for the CPM (e.g., routing protocols, ICMP). Matched packets are copied to the CPM while data-plane traffic is forwarded normally."

Other Options are INCORRECT:

A: Capture-filter ACL is for packet mirroring (e.g., SPAN), not CPM copying.

C/D: Ingress/Egress ACLs filter user traffic and are not specific to CPM-bound packets.

Extract from Nokia SR Linux ACL Configuration Guide:

"Only cpm-filter ACLs are globally applied across line cards for CPM protection. Interface ACLs (ingress/egress) operate locally and do not copy packets to the CPM."