McAfee-Secured Website

Exam Code: 4A0-D01

Exam Name: Nokia Data Center Fabric Fundamentals

Certification Provider: Nokia

100% Nokia 4A0-D01 Guaranteed Success With Testking Training Materials

Get Real 4A0-D01 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

61 Questions & Answers with Testing Engine

"Nokia Data Center Fabric Fundamentals Exam", also known as 4A0-D01 exam, is a Nokia certification exam.

Pass your tests with the always up-to-date 4A0-D01 Exam Engine. Your 4A0-D01 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Nokia 4A0-D01 Practice Test 60

Question 590

At Riverbend Municipal Networks, while moving a workload between leaves, the data center fabric team observes: A multi-leaf EVPN service intermittently fails after a spine path changes. Which evidence directly validates the intended repair?

  1. The intended remote VTEPs are present and test traffic traverses the service
  2. Tenant traffic remains successful during a controlled single-underlay-path failover
  3. An approved workload reaches its default gateway and a remote destination through that VRF
  4. A controlled routed flow succeeds using the service model chosen for the fabric

Explanation

Correct Answer

B:

At Riverbend Municipal Networks, while moving a workload between leaves, for Riverbend Municipal Networks, accept the repair only after this observation: Tenant traffic remains successful during a controlled single-underlay-path failover. The test distinguishes real recovery from a superficial status change.

Incorrect Answers

A:

At Riverbend Municipal Networks, while moving a workload between leaves, this option proposes: The intended remote VTEPs are present and test traffic traverses the service. That choice would be more relevant when this different symptom occurs: An EVPN service is configured but no tunnels are shown to its intended peer leaves. The present scenario instead points to: The overlay's remote VTEP reachability depends on an unhealthy or missing underlay ECMP path. The correct resolution has its own verification outcome: Tenant traffic remains successful during a controlled single-underlay-path failover.

C:

At Riverbend Municipal Networks, while moving a workload between leaves, this option proposes: An approved workload reaches its default gateway and a remote destination through that VRF. Although related to EVPN, VXLAN, MAC-VRF and IP-VRF overlays, the proposed change fits another mechanism: The tenant gateway interface is not associated with the correct IP-VRF and subnet. The evidence in the current case requires a different result: Tenant traffic remains successful during a controlled single-underlay-path failover.

D:

At Riverbend Municipal Networks, while moving a workload between leaves, this option proposes: A controlled routed flow succeeds using the service model chosen for the fabric. Using that approach would investigate An asymmetric routed overlay cannot send traffic when the destination subnet is absent locally instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The overlay's remote VTEP reachability depends on an unhealthy or missing underlay ECMP path.

Question 591

At Riverbend Municipal Networks, while moving a workload between leaves, the data center fabric team observes: A multi-leaf EVPN service intermittently fails after a spine path changes. Which underlying mechanism best accounts for this symptom?

  1. The old EVPN MAC/IP advertisement has not been updated or withdrawn after the move
  2. The new MAC-VRF lacks correct endpoint learning or EVPN service advertisement
  3. The overlay's remote VTEP reachability depends on an unhealthy or missing underlay ECMP path
  4. The EVPN route-target import policy is too broad for the isolated IP-VRF

Explanation

Correct Answer

C:

At Riverbend Municipal Networks, while moving a workload between leaves, the evidence points to: The overlay's remote VTEP reachability depends on an unhealthy or missing underlay ECMP path. The follow-up test (Tenant traffic remains successful during a controlled single-underlay-path failover) distinguishes this mechanism from a separate fabric fault.

Incorrect Answers

A:

At Riverbend Municipal Networks, while moving a workload between leaves, this option proposes: The old EVPN MAC/IP advertisement has not been updated or withdrawn after the move. This is a valid category of fabric maintenance for another scenario (A relocated virtual machine is reachable from one leaf but stale on another), not the targeted action for Riverbend Municipal Networks. The distinction is the actual cause: The overlay's remote VTEP reachability depends on an unhealthy or missing underlay ECMP path.

B:

At Riverbend Municipal Networks, while moving a workload between leaves, this option proposes: The new MAC-VRF lacks correct endpoint learning or EVPN service advertisement. Although related to EVPN, VXLAN, MAC-VRF and IP-VRF overlays, the proposed change fits another mechanism: The new MAC-VRF lacks correct endpoint learning or EVPN service advertisement. The evidence in the current case requires a different result: Tenant traffic remains successful during a controlled single-underlay-path failover.

D:

At Riverbend Municipal Networks, while moving a workload between leaves, this option proposes: The EVPN route-target import policy is too broad for the isolated IP-VRF. The alternative focuses on The EVPN route-target import policy is too broad for the isolated IP-VRF, not on the stated defect. For this scenario the expected acceptance result would be: Tenant traffic remains successful during a controlled single-underlay-path failover.

Question 592

At Riverbend Municipal Networks, while moving a workload between leaves, the data center fabric team observes: A multi-leaf EVPN service intermittently fails after a spine path changes. Which review gate should be added to prevent the same error?

  1. Validate L2 and L3 EVPN functions independently
  2. Pair overlay service tests with routed underlay resilience drills
  3. Test unknown-unicast handling when onboarding a new EVPN segment
  4. Monitor unusual tenant MAC growth and audit service attachments

Explanation

Correct Answer

B:

At Riverbend Municipal Networks, while moving a workload between leaves, pair overlay service tests with routed underlay resilience drills. This ongoing review specifically addresses: The overlay's remote VTEP reachability depends on an unhealthy or missing underlay ECMP path. It should remain part of change acceptance, not only incident closure.

Incorrect Answers

A:

At Riverbend Municipal Networks, while moving a workload between leaves, this option proposes: Validate L2 and L3 EVPN functions independently. Although related to EVPN, VXLAN, MAC-VRF and IP-VRF overlays, the proposed change fits another mechanism: The design implements only MAC-VRF bridging without the necessary IP-VRF routing and gateway service. The evidence in the current case requires a different result: Tenant traffic remains successful during a controlled single-underlay-path failover.

C:

At Riverbend Municipal Networks, while moving a workload between leaves, this option proposes: Test unknown-unicast handling when onboarding a new EVPN segment. The alternative focuses on Unknown unicast handling or endpoint learning is not aligned with intended overlay behavior, not on the stated defect. For this scenario the expected acceptance result would be: Tenant traffic remains successful during a controlled single-underlay-path failover.

D:

At Riverbend Municipal Networks, while moving a workload between leaves, this option proposes: Monitor unusual tenant MAC growth and audit service attachments. This option assumes the other problem (A tenant's bridge MAC table grows with unexpected external endpoint addresses) is present. The case instead describes A multi-leaf EVPN service intermittently fails after a spine path changes, for which the causal issue is The overlay's remote VTEP reachability depends on an unhealthy or missing underlay ECMP path.

Question 593

At Farsight Municipal Networks, while checking a remote VTEP path, the data center fabric team observes: A leaf learns a remote host's MAC but not its expected IP information. What configuration or operational change should the engineer prioritize?

  1. Configure the intended L3 EVPN tenant routing context and gateway associations
  2. Review local address discovery and EVPN MAC/IP route attributes for the learned host
  3. Correct the tenant gateway address and routing-instance binding for the new subnet
  4. Adjust and validate supported end-to-end transport MTU for the encapsulated service

Explanation

Correct Answer

B:

At Farsight Municipal Networks, while checking a remote VTEP path, for Farsight Municipal Networks, the applicable change is: Review local address discovery and EVPN MAC/IP route attributes for the learned host. The causal issue is: MAC and IP binding dissemination is incomplete for the endpoint advertisement. A successful validation would show: A remote leaf displays the correct MAC-to-IP association and forwards permitted traffic.

Incorrect Answers

A:

At Farsight Municipal Networks, while checking a remote VTEP path, this option proposes: Configure the intended L3 EVPN tenant routing context and gateway associations. The alternative focuses on The design implements only MAC-VRF bridging without the necessary IP-VRF routing and gateway service, not on the stated defect. For this scenario the expected acceptance result would be: A remote leaf displays the correct MAC-to-IP association and forwards permitted traffic.

C:

At Farsight Municipal Networks, while checking a remote VTEP path, this option proposes: Correct the tenant gateway address and routing-instance binding for the new subnet. It tests a different symptom: A tenant interface uses the wrong virtual-router gateway address after a new subnet is created. For the observed case, the relevant distinction is MAC and IP binding dissemination is incomplete for the endpoint advertisement, with verification: A remote leaf displays the correct MAC-to-IP association and forwards permitted traffic.

D:

The routed underlay MTU does not accommodate the additional VXLAN encapsulation overhead, but here the case reports A leaf learns a remote host's MAC but not its expected IP information. Here, mAC and IP binding dissemination is incomplete for the endpoint advertisement.

Question 594

At Farsight Municipal Networks, while checking a remote VTEP path, the data center fabric team observes: A leaf learns a remote host's MAC but not its expected IP information. What test result proves the affected fabric function now works?

  1. The MAC-VRF contains only legitimate tenant MACs after the correction
  2. Remote peers no longer import the deleted service routes while remaining tenants stay healthy
  3. A remote leaf displays the correct MAC-to-IP association and forwards permitted traffic
  4. Traffic between tenant subnets crosses the fabric and uses the approved L3 VNI context

Explanation

Correct Answer

C:

At Farsight Municipal Networks, while checking a remote VTEP path, the decisive validation is: A remote leaf displays the correct MAC-to-IP association and forwards permitted traffic. It verifies that the change (Review local address discovery and EVPN MAC/IP route attributes for the learned host) resolved the mechanism: MAC and IP binding dissemination is incomplete for the endpoint advertisement.

Incorrect Answers

A:

At Farsight Municipal Networks, while checking a remote VTEP path, this option proposes: The MAC-VRF contains only legitimate tenant MACs after the correction. This option assumes the other problem (A tenant's bridge MAC table grows with unexpected external endpoint addresses) is present. The case instead describes A leaf learns a remote host's MAC but not its expected IP information, for which the causal issue is MAC and IP binding dissemination is incomplete for the endpoint advertisement.

B:

At Farsight Municipal Networks, while checking a remote VTEP path, this option proposes: Remote peers no longer import the deleted service routes while remaining tenants stay healthy. It tests a different symptom: EVPN paths continue to advertise a deleted tenant service after offboarding. For the observed case, the relevant distinction is MAC and IP binding dissemination is incomplete for the endpoint advertisement, with verification: A remote leaf displays the correct MAC-to-IP association and forwards permitted traffic.

D:

The design expects symmetric L3 EVPN routing but only configures local MAC-VRF gateways. Here, mAC and IP binding dissemination is incomplete for the endpoint advertisement.

Question 595

At Farsight Municipal Networks, while checking a remote VTEP path, the data center fabric team observes: A leaf learns a remote host's MAC but not its expected IP information. What specific misconfiguration or design error is most likely?

  1. Required tenant L3 overlay forwarding and inter-subnet transport context are missing
  2. The tenant gateway interface is not associated with the correct IP-VRF and subnet
  3. MAC and IP binding dissemination is incomplete for the endpoint advertisement
  4. Service decommissioning did not remove all associated EVPN route advertisements

Explanation

Correct Answer

C:

At Farsight Municipal Networks, while checking a remote VTEP path, the evidence points to: MAC and IP binding dissemination is incomplete for the endpoint advertisement. The follow-up test (A remote leaf displays the correct MAC-to-IP association and forwards permitted traffic) distinguishes this mechanism from a separate fabric fault.

Incorrect Answers

A:

At Farsight Municipal Networks, while checking a remote VTEP path, this option proposes: Required tenant L3 overlay forwarding and inter-subnet transport context are missing. It tests a different symptom: The design expects symmetric L3 EVPN routing but only configures local MAC-VRF gateways. For the observed case, the relevant distinction is MAC and IP binding dissemination is incomplete for the endpoint advertisement, with verification: A remote leaf displays the correct MAC-to-IP association and forwards permitted traffic.

B:

At Farsight Municipal Networks, while checking a remote VTEP path, this option proposes: The tenant gateway interface is not associated with the correct IP-VRF and subnet. The option describes a different failure mode: A routed tenant interface has no effective gateway for workloads. It would address The tenant gateway interface is not associated with the correct IP-VRF and subnet, but here the case reports A leaf learns a remote host's MAC but not its expected IP information. The current required evidence is: A remote leaf displays the correct MAC-to-IP association and forwards permitted traffic.

D:

At Farsight Municipal Networks, while checking a remote VTEP path, this option proposes: Service decommissioning did not remove all associated EVPN route advertisements. This is a valid category of fabric maintenance for another scenario (EVPN paths continue to advertise a deleted tenant service after offboarding), not the targeted action for Farsight Municipal Networks. The distinction is the actual cause: MAC and IP binding dissemination is incomplete for the endpoint advertisement.

Question 596

At Farsight Municipal Networks, while checking a remote VTEP path, the data center fabric team observes: A leaf learns a remote host's MAC but not its expected IP information. What repeatable acceptance check would reduce recurrence?

  1. Document L3 overlay forwarding model before provisioning tenant VNIs
  2. Validate L2 and L3 EVPN functions independently
  3. Compare learned MAC and IP bindings after endpoint mobility events
  4. Compare per-tenant VNI mappings across fabric nodes during deployment

Explanation

Correct Answer

C:

At Farsight Municipal Networks, while checking a remote VTEP path, for Farsight Municipal Networks, include the safeguard: Compare learned MAC and IP bindings after endpoint mobility events. It reduces repeat risk from the original mechanism and complements a validation of: A remote leaf displays the correct MAC-to-IP association and forwards permitted traffic.

Incorrect Answers

A:

At Farsight Municipal Networks, while checking a remote VTEP path, this option proposes: Document L3 overlay forwarding model before provisioning tenant VNIs. The option describes a different failure mode: An asymmetric routed overlay cannot send traffic when the destination subnet is absent locally. It would address The model expects direct destination bridge reachability that is not provisioned for that routing approach, but here the case reports A leaf learns a remote host's MAC but not its expected IP information. The current required evidence is: A remote leaf displays the correct MAC-to-IP association and forwards permitted traffic.

B:

At Farsight Municipal Networks, while checking a remote VTEP path, this option proposes: Validate L2 and L3 EVPN functions independently. That choice would be more relevant when this different symptom occurs: Inter-subnet tenant traffic fails even though same-subnet EVPN traffic works. The present scenario instead points to: MAC and IP binding dissemination is incomplete for the endpoint advertisement. The correct resolution has its own verification outcome: A remote leaf displays the correct MAC-to-IP association and forwards permitted traffic.

D:

At Farsight Municipal Networks, while checking a remote VTEP path, this option proposes: Compare per-tenant VNI mappings across fabric nodes during deployment. Although related to EVPN, VXLAN, MAC-VRF and IP-VRF overlays, the proposed change fits another mechanism: The L2 EVPN service-to-VNI mapping is inconsistent across participants. The evidence in the current case requires a different result: A remote leaf displays the correct MAC-to-IP association and forwards permitted traffic.

Question 597

At Lakeshore Rail Logistics, while checking a remote VTEP path, the data center fabric team observes: An EVPN service is configured but no tunnels are shown to its intended peer leaves. Which action resolves the identified fabric-management issue?

  1. Adjust and validate supported end-to-end transport MTU for the encapsulated service
  2. Align the gateway subinterface and tenant IP-VRF service configuration
  3. Confirm service activation, VNI membership and approved EVPN peer connectivity
  4. Separate the tenants' bridge services, VNIs and interface memberships

Explanation

Correct Answer

C:

At Lakeshore Rail Logistics, while checking a remote VTEP path, choose this remediation because it targets the mechanism: The service was not associated with an active EVPN signaling or VTEP endpoint context. The supported corrective action is: Confirm service activation, VNI membership and approved EVPN peer connectivity. Verification requires: The intended remote VTEPs are present and test traffic traverses the service.

Incorrect Answers

A:

At Lakeshore Rail Logistics, while checking a remote VTEP path, this option proposes: Adjust and validate supported end-to-end transport MTU for the encapsulated service. This is a valid category of fabric maintenance for another scenario (An overlay forwarding issue affects only jumbo-sized packets), not the targeted action for Lakeshore Rail Logistics. The distinction is the actual cause: The service was not associated with an active EVPN signaling or VTEP endpoint context.

B:

At Lakeshore Rail Logistics, while checking a remote VTEP path, this option proposes: Align the gateway subinterface and tenant IP-VRF service configuration. Although related to EVPN, VXLAN, MAC-VRF and IP-VRF overlays, the proposed change fits another mechanism: The tenant gateway interface is not associated with the correct IP-VRF and subnet. The evidence in the current case requires a different result: The intended remote VTEPs are present and test traffic traverses the service.

D:

At Lakeshore Rail Logistics, while checking a remote VTEP path, this option proposes: Separate the tenants' bridge services, VNIs and interface memberships. The alternative focuses on Two MAC-VRFs share an unintended service attachment or VNI mapping, not on the stated defect. For this scenario the expected acceptance result would be: The intended remote VTEPs are present and test traffic traverses the service.

Question 598

At Lakeshore Rail Logistics, while checking a remote VTEP path, the data center fabric team observes: An EVPN service is configured but no tunnels are shown to its intended peer leaves. Which result would establish that the original defect has been corrected?

  1. Remote peers no longer import the deleted service routes while remaining tenants stay healthy
  2. The intended remote VTEPs are present and test traffic traverses the service
  3. A remote tenant IP-VRF imports the required prefix with the correct overlay next hop
  4. Tenant traffic remains successful during a controlled single-underlay-path failover

Explanation

Correct Answer

B:

At Lakeshore Rail Logistics, while checking a remote VTEP path, for Lakeshore Rail Logistics, accept the repair only after this observation: The intended remote VTEPs are present and test traffic traverses the service. The test distinguishes real recovery from a superficial status change.

Incorrect Answers

A:

At Lakeshore Rail Logistics, while checking a remote VTEP path, this option proposes: Remote peers no longer import the deleted service routes while remaining tenants stay healthy. Although related to EVPN, VXLAN, MAC-VRF and IP-VRF overlays, the proposed change fits another mechanism: Service decommissioning did not remove all associated EVPN route advertisements. The evidence in the current case requires a different result: The intended remote VTEPs are present and test traffic traverses the service.

C:

At Lakeshore Rail Logistics, while checking a remote VTEP path, this option proposes: A remote tenant IP-VRF imports the required prefix with the correct overlay next hop. The alternative focuses on The intended IP prefix route is not originated or imported for the L3 service, not on the stated defect. For this scenario the expected acceptance result would be: The intended remote VTEPs are present and test traffic traverses the service.

D:

At Lakeshore Rail Logistics, while checking a remote VTEP path, this option proposes: Tenant traffic remains successful during a controlled single-underlay-path failover. This option assumes the other problem (A multi-leaf EVPN service intermittently fails after a spine path changes) is present. The case instead describes An EVPN service is configured but no tunnels are shown to its intended peer leaves, for which the causal issue is The service was not associated with an active EVPN signaling or VTEP endpoint context.

Question 599

At Lakeshore Rail Logistics, while checking a remote VTEP path, the data center fabric team observes: An EVPN service is configured but no tunnels are shown to its intended peer leaves. Which root cause fits the reported state?

  1. An unintended physical attachment or route-target import is feeding a MAC-VRF
  2. The service was not associated with an active EVPN signaling or VTEP endpoint context
  3. An unintended overlay attachment or duplicated MAC advertisement exists in the fabric
  4. Two MAC-VRFs share an unintended service attachment or VNI mapping

Explanation

Correct Answer

B:

At Lakeshore Rail Logistics, while checking a remote VTEP path, the specific mechanism is: The service was not associated with an active EVPN signaling or VTEP endpoint context. It explains the reported state: An EVPN service is configured but no tunnels are shown to its intended peer leaves. The targeted corrective action is: Confirm service activation, VNI membership and approved EVPN peer connectivity.

Incorrect Answers

A:

At Lakeshore Rail Logistics, while checking a remote VTEP path, this option proposes: An unintended physical attachment or route-target import is feeding a MAC-VRF. Using that approach would investigate A tenant's bridge MAC table grows with unexpected external endpoint addresses instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The service was not associated with an active EVPN signaling or VTEP endpoint context.

C:

At Lakeshore Rail Logistics, while checking a remote VTEP path, this option proposes: An unintended overlay attachment or duplicated MAC advertisement exists in the fabric. This option assumes the other problem (A remote server's MAC is learned through two unexpected VTEPs) is present. The case instead describes An EVPN service is configured but no tunnels are shown to its intended peer leaves, for which the causal issue is The service was not associated with an active EVPN signaling or VTEP endpoint context.

D:

At Lakeshore Rail Logistics, while checking a remote VTEP path, this option proposes: Two MAC-VRFs share an unintended service attachment or VNI mapping. It tests a different symptom: An EVPN change accidentally exposes one tenant's broadcast traffic to another. For the observed case, the relevant distinction is The service was not associated with an active EVPN signaling or VTEP endpoint context, with verification: The intended remote VTEPs are present and test traffic traverses the service.

Question 600

At Lakeshore Rail Logistics, while checking a remote VTEP path, the data center fabric team observes: An EVPN service is configured but no tunnels are shown to its intended peer leaves. Which recurring validation best prevents this failure mode?

  1. Validate service instantiation and remote tunnel discovery together
  2. Document L3 overlay forwarding model before provisioning tenant VNIs
  3. Test ARP resolution and subsequent unicast after overlay configuration changes
  4. Review tenant service boundaries before accepting EVPN provisioning changes

Explanation

Correct Answer

A:

At Lakeshore Rail Logistics, while checking a remote VTEP path, the preventive control is: Validate service instantiation and remote tunnel discovery together. It catches the same mechanism (The service was not associated with an active EVPN signaling or VTEP endpoint context) before the symptom recurs. An appropriate regression observation is: The intended remote VTEPs are present and test traffic traverses the service.

Incorrect Answers

B:

At Lakeshore Rail Logistics, while checking a remote VTEP path, this option proposes: Document L3 overlay forwarding model before provisioning tenant VNIs. This option assumes the other problem (An asymmetric routed overlay cannot send traffic when the destination subnet is absent locally) is present. The case instead describes An EVPN service is configured but no tunnels are shown to its intended peer leaves, for which the causal issue is The service was not associated with an active EVPN signaling or VTEP endpoint context.

C:

At Lakeshore Rail Logistics, while checking a remote VTEP path, this option proposes: Test ARP resolution and subsequent unicast after overlay configuration changes. It tests a different symptom: Two virtual machines share a subnet across leaves but ARP requests fail to discover their peers. For the observed case, the relevant distinction is The service was not associated with an active EVPN signaling or VTEP endpoint context, with verification: The intended remote VTEPs are present and test traffic traverses the service.

D:

At Lakeshore Rail Logistics, while checking a remote VTEP path, this option proposes: Review tenant service boundaries before accepting EVPN provisioning changes. The option describes a different failure mode: An EVPN change accidentally exposes one tenant's broadcast traffic to another. It would address Two MAC-VRFs share an unintended service attachment or VNI mapping, but here the case reports An EVPN service is configured but no tunnels are shown to its intended peer leaves. The current required evidence is: The intended remote VTEPs are present and test traffic traverses the service.

Nokia Data Center Fabric Fundamentals (4A0-D01) Practice Tests