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 36

Question 350

At Skyline Municipal Networks, while planning a link-failure test, the data center fabric team observes: Link failure takes down tenant services even though another physical underlay path is up. Which evidence directly validates the intended repair?

  1. Representative addresses within the target subnet follow the expected route
  2. A controlled single-link failure leaves remote VTEP loopbacks reachable
  3. The appropriate Layer 3 adjacency forms and exchanges required routes
  4. Both peers reach Established using the approved AS assignment

Explanation

Correct Answer

B:

At Skyline Municipal Networks, while planning a link-failure test, for Skyline Municipal Networks, accept the repair only after this observation: A controlled single-link failure leaves remote VTEP loopbacks reachable. The test distinguishes real recovery from a superficial status change.

Incorrect Answers

A:

At Skyline Municipal Networks, while planning a link-failure test, this option proposes: Representative addresses within the target subnet follow the expected route. The alternative focuses on The destination prefix length does not cover the intended address range, not on the stated defect. For this scenario the expected acceptance result would be: A controlled single-link failure leaves remote VTEP loopbacks reachable.

C:

At Skyline Municipal Networks, while planning a link-failure test, this option proposes: The appropriate Layer 3 adjacency forms and exchanges required routes. It tests a different symptom: Underlay BGP sessions appear stable but a wrong VLAN tag prevents one adjacency from exchanging routes. For the observed case, the relevant distinction is The remaining path was omitted from routing adjacencies or next-hop eligibility, with verification: A controlled single-link failure leaves remote VTEP loopbacks reachable.

D:

At Skyline Municipal Networks, while planning a link-failure test, this option proposes: Both peers reach Established using the approved AS assignment. The option describes a different failure mode: A BGP neighbor remains stuck due to a mismatched local or peer autonomous system. It would address The two sides disagree on the expected remote AS number, but here the case reports Link failure takes down tenant services even though another physical underlay path is up. The current required evidence is: A controlled single-link failure leaves remote VTEP loopbacks reachable.

Question 351

At Skyline Municipal Networks, while planning a link-failure test, the data center fabric team observes: Link failure takes down tenant services even though another physical underlay path is up. Which underlying mechanism best accounts for this symptom?

  1. The peer address is unreachable or TCP 179 is blocked by the underlay policy
  2. The destination prefix length does not cover the intended address range
  3. The control-plane frames do not reach the intended tagged subinterface
  4. The remaining path was omitted from routing adjacencies or next-hop eligibility

Explanation

Correct Answer

D:

At Skyline Municipal Networks, while planning a link-failure test, the remaining path was omitted from routing adjacencies or next-hop eligibility. That is the cause of the described failure, and a corrective check should demonstrate: A controlled single-link failure leaves remote VTEP loopbacks reachable.

Incorrect Answers

A:

At Skyline Municipal Networks, while planning a link-failure test, this option proposes: The peer address is unreachable or TCP 179 is blocked by the underlay policy. This option assumes the other problem (Two fabric peers have BGP configured but the session stays Idle with no TCP connection) is present. The case instead describes Link failure takes down tenant services even though another physical underlay path is up, for which the causal issue is The remaining path was omitted from routing adjacencies or next-hop eligibility.

B:

At Skyline Municipal Networks, while planning a link-failure test, this option proposes: The destination prefix length does not cover the intended address range. It tests a different symptom: An engineer configures a static route destination as a host when an entire subnet is needed. For the observed case, the relevant distinction is The remaining path was omitted from routing adjacencies or next-hop eligibility, with verification: A controlled single-link failure leaves remote VTEP loopbacks reachable.

C:

At Skyline Municipal Networks, while planning a link-failure test, this option proposes: The control-plane frames do not reach the intended tagged subinterface. The option describes a different failure mode: Underlay BGP sessions appear stable but a wrong VLAN tag prevents one adjacency from exchanging routes. It would address The control-plane frames do not reach the intended tagged subinterface, but here the case reports Link failure takes down tenant services even though another physical underlay path is up. The current required evidence is: A controlled single-link failure leaves remote VTEP loopbacks reachable.

Question 352

At Skyline Municipal Networks, while planning a link-failure test, the data center fabric team observes: Link failure takes down tenant services even though another physical underlay path is up. Which review gate should be added to prevent the same error?

  1. Review BGP source-interface assumptions for multihop peering
  2. Validate AFI/SAFI and IPv6 routes independently from IPv4
  3. Perform one-link-at-a-time underlay failover testing
  4. Include post-reboot persistence in routing change acceptance

Explanation

Correct Answer

C:

At Skyline Municipal Networks, while planning a link-failure test, for Skyline Municipal Networks, include the safeguard: Perform one-link-at-a-time underlay failover testing. It reduces repeat risk from the original mechanism and complements a validation of: A controlled single-link failure leaves remote VTEP loopbacks reachable.

Incorrect Answers

A:

At Skyline Municipal Networks, while planning a link-failure test, this option proposes: Review BGP source-interface assumptions for multihop peering. It tests a different symptom: An eBGP leaf peering configuration uses an incorrect update source for loopback peering. For the observed case, the relevant distinction is The remaining path was omitted from routing adjacencies or next-hop eligibility, with verification: A controlled single-link failure leaves remote VTEP loopbacks reachable.

B:

At Skyline Municipal Networks, while planning a link-failure test, this option proposes: Validate AFI/SAFI and IPv6 routes independently from IPv4. The option describes a different failure mode: An underlay peer advertises only IPv4 while an expected IPv6 reachability test fails. It would address IPv6 family activation or transport address configuration is missing on that adjacency, but here the case reports Link failure takes down tenant services even though another physical underlay path is up. The current required evidence is: A controlled single-link failure leaves remote VTEP loopbacks reachable.

D:

At Skyline Municipal Networks, while planning a link-failure test, this option proposes: Include post-reboot persistence in routing change acceptance. This is a valid category of fabric maintenance for another scenario (An underlay route vanishes after a leaf is reloaded but returns after a manual CLI edit), not the targeted action for Skyline Municipal Networks. The distinction is the actual cause: The remaining path was omitted from routing adjacencies or next-hop eligibility.

Question 353

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, the data center fabric team observes: Traffic follows an unexpected spine after a route-policy update. What configuration or operational change should the engineer prioritize?

  1. Compare effective policy and route attributes and restore intended path selection
  2. Correct the approved fabric edge route exchange and return-path policy
  3. Apply the correct IP prefix and next-hop-group to the static route
  4. Verify peer addressing, routing and permitted control-plane connectivity

Explanation

Correct Answer

A:

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, compare effective policy and route attributes and restore intended path selection. This addresses the specific failure mechanism (The path preference or BGP route attributes changed without validating selected forwarding paths) rather than treating only the visible alarm. The required acceptance evidence is: The forwarding table matches the approved spine preference and still has required backup paths.

Incorrect Answers

B:

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, this option proposes: Correct the approved fabric edge route exchange and return-path policy. This is a valid category of fabric maintenance for another scenario (A new server subnet cannot reach external routed services although its gateway replies), not the targeted action for Brightwater Rail Logistics. The distinction is the actual cause: The path preference or BGP route attributes changed without validating selected forwarding paths.

C:

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, this option proposes: Apply the correct IP prefix and next-hop-group to the static route. Although related to Underlay routing, BGP, BFD and ECMP, the proposed change fits another mechanism: The destination prefix length does not cover the intended address range. The evidence in the current case requires a different result: The forwarding table matches the approved spine preference and still has required backup paths.

D:

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, this option proposes: Verify peer addressing, routing and permitted control-plane connectivity. Using that approach would investigate Two fabric peers have BGP configured but the session stays Idle with no TCP connection instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The path preference or BGP route attributes changed without validating selected forwarding paths.

Question 354

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, the data center fabric team observes: Traffic follows an unexpected spine after a route-policy update. What test result proves the affected fabric function now works?

  1. The forwarding table matches the approved spine preference and still has required backup paths
  2. An end-to-end test succeeds with routes present in both forward and return directions
  3. The remote peer sees the expected source and the session reaches Established
  4. The default route resolves to an active next hop and controlled traffic reaches the gateway

Explanation

Correct Answer

A:

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, this result is the relevant closure evidence: The forwarding table matches the approved spine preference and still has required backup paths. It checks the effect of: Compare effective policy and route attributes and restore intended path selection. The underlying issue was: The path preference or BGP route attributes changed without validating selected forwarding paths.

Incorrect Answers

B:

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, this option proposes: An end-to-end test succeeds with routes present in both forward and return directions. Although related to Underlay routing, BGP, BFD and ECMP, the proposed change fits another mechanism: The fabric edge lacks a route toward the external destination or the return subnet. The evidence in the current case requires a different result: The forwarding table matches the approved spine preference and still has required backup paths.

C:

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, this option proposes: The remote peer sees the expected source and the session reaches Established. Using that approach would investigate An eBGP leaf peering configuration uses an incorrect update source for loopback peering instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The path preference or BGP route attributes changed without validating selected forwarding paths.

D:

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, this option proposes: The default route resolves to an active next hop and controlled traffic reaches the gateway. The alternative focuses on The referenced next-hop group has no reachable selected member, not on the stated defect. For this scenario the expected acceptance result would be: The forwarding table matches the approved spine preference and still has required backup paths.

Question 355

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, the data center fabric team observes: Traffic follows an unexpected spine after a route-policy update. What specific misconfiguration or design error is most likely?

  1. The path preference or BGP route attributes changed without validating selected forwarding paths
  2. The route export policy fails to distinguish infrastructure and tenant prefixes
  3. BFD connectivity or session parameters are incompatible across the peer pair
  4. IPv6 family activation or transport address configuration is missing on that adjacency

Explanation

Correct Answer

A:

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, for Brightwater Rail Logistics, investigate this cause first: The path preference or BGP route attributes changed without validating selected forwarding paths. It is directly linked to the observed symptom rather than another service issue.

Incorrect Answers

B:

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, this option proposes: The route export policy fails to distinguish infrastructure and tenant prefixes. Using that approach would investigate A leaf exports its connected management subnet into tenant-visible fabric routing instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The path preference or BGP route attributes changed without validating selected forwarding paths.

C:

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, this option proposes: BFD connectivity or session parameters are incompatible across the peer pair. The alternative focuses on BFD connectivity or session parameters are incompatible across the peer pair, not on the stated defect. For this scenario the expected acceptance result would be: The forwarding table matches the approved spine preference and still has required backup paths.

D:

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, this option proposes: IPv6 family activation or transport address configuration is missing on that adjacency. This option assumes the other problem (An underlay peer advertises only IPv4 while an expected IPv6 reachability test fails) is present. The case instead describes Traffic follows an unexpected spine after a route-policy update, for which the causal issue is The path preference or BGP route attributes changed without validating selected forwarding paths.

Question 356

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, the data center fabric team observes: Traffic follows an unexpected spine after a route-policy update. What repeatable acceptance check would reduce recurrence?

  1. Validate ASN topology and peer definitions when adding leaves
  2. Capture selected next hops before and after routing policy deployment
  3. Include post-reboot persistence in routing change acceptance
  4. Test announced routes and applied policy alongside session state

Explanation

Correct Answer

B:

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, capture selected next hops before and after routing policy deployment. This ongoing review specifically addresses: The path preference or BGP route attributes changed without validating selected forwarding paths. It should remain part of change acceptance, not only incident closure.

Incorrect Answers

A:

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, this option proposes: Validate ASN topology and peer definitions when adding leaves. Using that approach would investigate A BGP neighbor remains stuck due to a mismatched local or peer autonomous system instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The path preference or BGP route attributes changed without validating selected forwarding paths.

C:

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, this option proposes: Include post-reboot persistence in routing change acceptance. This option assumes the other problem (An underlay route vanishes after a leaf is reloaded but returns after a manual CLI edit) is present. The case instead describes Traffic follows an unexpected spine after a route-policy update, for which the causal issue is The path preference or BGP route attributes changed without validating selected forwarding paths.

D:

At Brightwater Rail Logistics, while restoring an underlay BGP adjacency, this option proposes: Test announced routes and applied policy alongside session state. It tests a different symptom: A BGP session is Established but the expected underlay prefix is not learned. For the observed case, the relevant distinction is The path preference or BGP route attributes changed without validating selected forwarding paths, with verification: The forwarding table matches the approved spine preference and still has required backup paths.

Question 357

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, the data center fabric team observes: A new server subnet cannot reach external routed services although its gateway replies. Which action resolves the identified fabric-management issue?

  1. Correct the tagged subinterface binding and validate neighbor-layer connectivity before BGP changes
  2. Remove the unintended discard action and install the approved reachable next-hop group
  3. Review BGP path attributes and ECMP configuration to permit only equivalent eligible paths
  4. Correct the approved fabric edge route exchange and return-path policy

Explanation

Correct Answer

D:

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, the targeted correction is: Correct the approved fabric edge route exchange and return-path policy. The reported symptom is explained by: The fabric edge lacks a route toward the external destination or the return subnet. Confirm the change by testing this outcome: An end-to-end test succeeds with routes present in both forward and return directions.

Incorrect Answers

A:

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, this option proposes: Correct the tagged subinterface binding and validate neighbor-layer connectivity before BGP changes. This option assumes the other problem (Underlay BGP sessions appear stable but a wrong VLAN tag prevents one adjacency from exchanging routes) is present. The case instead describes A new server subnet cannot reach external routed services although its gateway replies, for which the causal issue is The fabric edge lacks a route toward the external destination or the return subnet.

B:

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, this option proposes: Remove the unintended discard action and install the approved reachable next-hop group. It tests a different symptom: A static route sends production traffic into a blackhole after an emergency change. For the observed case, the relevant distinction is The fabric edge lacks a route toward the external destination or the return subnet, with verification: An end-to-end test succeeds with routes present in both forward and return directions.

C:

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, this option proposes: Review BGP path attributes and ECMP configuration to permit only equivalent eligible paths. The option describes a different failure mode: All spine-to-leaf BGP sessions exist but one leaf uses a single path instead of ECMP. It would address The learned routes differ in preference or multipath eligibility, but here the case reports A new server subnet cannot reach external routed services although its gateway replies. The current required evidence is: An end-to-end test succeeds with routes present in both forward and return directions.

Question 358

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, the data center fabric team observes: A new server subnet cannot reach external routed services although its gateway replies. Which result would establish that the original defect has been corrected?

  1. BFD establishes and a controlled path failure triggers the intended rapid adjacency reaction
  2. An end-to-end test succeeds with routes present in both forward and return directions
  3. The route and BGP state return automatically after restart under approved config
  4. The default route resolves to an active next hop and controlled traffic reaches the gateway

Explanation

Correct Answer

B:

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, for Pinebrook Digital Commerce, accept the repair only after this observation: An end-to-end test succeeds with routes present in both forward and return directions. The test distinguishes real recovery from a superficial status change.

Incorrect Answers

A:

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, this option proposes: BFD establishes and a controlled path failure triggers the intended rapid adjacency reaction. It tests a different symptom: A BFD session shows Down while the BGP peer continues waiting for its normal hold timer. For the observed case, the relevant distinction is The fabric edge lacks a route toward the external destination or the return subnet, with verification: An end-to-end test succeeds with routes present in both forward and return directions.

C:

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, this option proposes: The route and BGP state return automatically after restart under approved config. That choice would be more relevant when this different symptom occurs: An underlay route vanishes after a leaf is reloaded but returns after a manual CLI edit. The present scenario instead points to: The fabric edge lacks a route toward the external destination or the return subnet. The correct resolution has its own verification outcome: An end-to-end test succeeds with routes present in both forward and return directions.

D:

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, this option proposes: The default route resolves to an active next hop and controlled traffic reaches the gateway. This is a valid category of fabric maintenance for another scenario (A static default route appears in configuration but never forwards traffic), not the targeted action for Pinebrook Digital Commerce. The distinction is the actual cause: The fabric edge lacks a route toward the external destination or the return subnet.

Question 359

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, the data center fabric team observes: A new server subnet cannot reach external routed services although its gateway replies. Which root cause fits the reported state?

  1. The fabric edge lacks a route toward the external destination or the return subnet
  2. The session's source address does not match the remote peer definition and route reachability
  3. A prefix match was broader than the approved route-exchange scope
  4. The peer address is unreachable or TCP 179 is blocked by the underlay policy

Explanation

Correct Answer

A:

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, for Pinebrook Digital Commerce, investigate this cause first: The fabric edge lacks a route toward the external destination or the return subnet. It is directly linked to the observed symptom rather than another service issue.

Incorrect Answers

B:

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, this option proposes: The session's source address does not match the remote peer definition and route reachability. That choice would be more relevant when this different symptom occurs: An eBGP leaf peering configuration uses an incorrect update source for loopback peering. The present scenario instead points to: The fabric edge lacks a route toward the external destination or the return subnet. The correct resolution has its own verification outcome: An end-to-end test succeeds with routes present in both forward and return directions.

C:

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, this option proposes: A prefix match was broader than the approved route-exchange scope. This is a valid category of fabric maintenance for another scenario (A route policy intended to permit fabric loopbacks inadvertently permits all tenant prefixes), not the targeted action for Pinebrook Digital Commerce. The distinction is the actual cause: The fabric edge lacks a route toward the external destination or the return subnet.

D:

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, this option proposes: The peer address is unreachable or TCP 179 is blocked by the underlay policy. Although related to Underlay routing, BGP, BFD and ECMP, the proposed change fits another mechanism: The peer address is unreachable or TCP 179 is blocked by the underlay policy. The evidence in the current case requires a different result: An end-to-end test succeeds with routes present in both forward and return directions.

Question 360

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, the data center fabric team observes: A new server subnet cannot reach external routed services although its gateway replies. Which recurring validation best prevents this failure mode?

  1. Measure equal-cost route installation after underlay changes
  2. Use positive and negative prefix fixtures when revising route policy
  3. Validate symmetric reachability across fabric-to-external boundaries
  4. Capture selected next hops before and after routing policy deployment

Explanation

Correct Answer

C:

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, for Pinebrook Digital Commerce, include the safeguard: Validate symmetric reachability across fabric-to-external boundaries. It reduces repeat risk from the original mechanism and complements a validation of: An end-to-end test succeeds with routes present in both forward and return directions.

Incorrect Answers

A:

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, this option proposes: Measure equal-cost route installation after underlay changes. That choice would be more relevant when this different symptom occurs: All spine-to-leaf BGP sessions exist but one leaf uses a single path instead of ECMP. The present scenario instead points to: The fabric edge lacks a route toward the external destination or the return subnet. The correct resolution has its own verification outcome: An end-to-end test succeeds with routes present in both forward and return directions.

B:

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, this option proposes: Use positive and negative prefix fixtures when revising route policy. This is a valid category of fabric maintenance for another scenario (A route policy intended to permit fabric loopbacks inadvertently permits all tenant prefixes), not the targeted action for Pinebrook Digital Commerce. The distinction is the actual cause: The fabric edge lacks a route toward the external destination or the return subnet.

D:

At Pinebrook Digital Commerce, while restoring an underlay BGP adjacency, this option proposes: Capture selected next hops before and after routing policy deployment. Using that approach would investigate Traffic follows an unexpected spine after a route-policy update instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The fabric edge lacks a route toward the external destination or the return subnet.

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