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

Comprehensive and Detailed Explanation with Exact Extracts:

Options A, B, and C ARE configured in static-routes:

Blackhole: Configured under static-routes for a prefix to drop traffic.

IPv4 destination prefix: Defined directly in the static-routes container.

Preference value: Set per static route entry within static-routes.

Extract from Nokia SR Linux Configuration Guide (Section: Static Routes):

"Static routes are configured under /routing-policy/static-routes. Each entry requires a prefix (e.g., 0.0.0.0/0). The blackhole parameter and preference value are configured directly within this container for a specific prefix."

Option D (Next-hop group) CANNOT be configured in static-routes:

Next-hop groups are separate objects defined under /routing-policy/next-hop-groups.

The static-routes container references a next-hop group by name but does not define its properties.

Extract from Nokia SR Linux Configuration Guide (Section: Next-Hop Groups):

"Next-hop groups are configured under /routing-policy/next-hop-groups. Each group is given a name and defines properties like next-hop IPs, blackhole behavior, or indirect settings. Static routes reference a next-hop group via the next-hop-group parameter under /routing-policy/static-routes but do not configure the group itself here."

Comprehensive and Detailed Explanation with Exact Extracts:

Options A, B, and C are part of ZTP autoboot:

A: DHCP assigns IP/gateway.

B/C: Scripts download images/RPMs from servers (HTTP/FTP).

Extract from Nokia SR Linux ZTP Guide:

"Autoboot triggers DHCP discovery for IP/gateway. The device then fetches a provisioning script (via DHCP/DNS) that downloads RPMs/images from HTTP/FTP servers."

Option D is NOT part of ZTP autoboot:

Fabric Services System (FSS) and its digital sandbox are separate tools for lifecycle management. ZTP does not auto-deploy them.

Extract from Nokia FSS Deployment Guide:

"FSS deployment requires manual setup or orchestration tools. The digital sandbox is not automatically deployed via ZTP autoboot."

The "baseline diff" command is used to compare the candidate configuration against the baseline datastore to see changes or conflicts, especially when multiple users are involved or to verify differences. It does not indicate that the user is unable to commit changes.