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

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

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.