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 28

Question 270

At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, the data center fabric team observes: All spine-to-leaf BGP sessions exist but one leaf uses a single path instead of ECMP. Which evidence directly validates the intended repair?

  1. The remote peer sees the expected source and the session reaches Established
  2. BFD establishes and a controlled path failure triggers the intended rapid adjacency reaction
  3. The selected route exposes multiple valid next hops and a link-loss test preserves access
  4. An end-to-end test succeeds with routes present in both forward and return directions

Explanation

Correct Answer

C:

At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, the decisive validation is: The selected route exposes multiple valid next hops and a link-loss test preserves access. It verifies that the change (Review BGP path attributes and ECMP configuration to permit only equivalent eligible paths) resolved the mechanism: The learned routes differ in preference or multipath eligibility.

Incorrect Answers

A:

An eBGP leaf peering configuration uses an incorrect update source for loopback peering. Here, the learned routes differ in preference or multipath eligibility.

B:

At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, this option proposes: BFD establishes and a controlled path failure triggers the intended rapid adjacency reaction. This is a valid category of fabric maintenance for another scenario (A BFD session shows Down while the BGP peer continues waiting for its normal hold timer), not the targeted action for Highcrest Municipal Networks. The distinction is the actual cause: The learned routes differ in preference or multipath eligibility.

D:

At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, this option proposes: An end-to-end test succeeds with routes present in both forward and return directions. Using that approach would investigate A new server subnet cannot reach external routed services although its gateway replies instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The learned routes differ in preference or multipath eligibility.

Question 271

At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, the data center fabric team observes: All spine-to-leaf BGP sessions exist but one leaf uses a single path instead of ECMP. Which underlying mechanism best accounts for this symptom?

  1. The referenced next-hop group has no reachable selected member
  2. The static next hop is not being withdrawn or tracked through a supported reachability mechanism
  3. BFD connectivity or session parameters are incompatible across the peer pair
  4. The learned routes differ in preference or multipath eligibility

Explanation

Correct Answer

D:

At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, the learned routes differ in preference or multipath eligibility. That is the cause of the described failure, and a corrective check should demonstrate: The selected route exposes multiple valid next hops and a link-loss test preserves access.

Incorrect Answers

A:

At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, this option proposes: The referenced next-hop group has no reachable selected member. 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 Highcrest Municipal Networks. The distinction is the actual cause: The learned routes differ in preference or multipath eligibility.

B:

At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, this option proposes: The static next hop is not being withdrawn or tracked through a supported reachability mechanism. Although related to Underlay routing, BGP, BFD and ECMP, the proposed change fits another mechanism: The static next hop is not being withdrawn or tracked through a supported reachability mechanism. The evidence in the current case requires a different result: The selected route exposes multiple valid next hops and a link-loss test preserves access.

C:

At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, this option proposes: BFD connectivity or session parameters are incompatible across the peer pair. Using that approach would investigate A BFD session shows Down while the BGP peer continues waiting for its normal hold timer instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The learned routes differ in preference or multipath eligibility.

Question 272

At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, the data center fabric team observes: All spine-to-leaf BGP sessions exist but one leaf uses a single path instead of ECMP. Which review gate should be added to prevent the same error?

  1. Measure equal-cost route installation after underlay changes
  2. Validate symmetric reachability across fabric-to-external boundaries
  3. Validate representative prefix membership before installing static entries
  4. Maintain explicit management-prefix exclusion tests

Explanation

Correct Answer

A:

At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, the preventive control is: Measure equal-cost route installation after underlay changes. It catches the same mechanism (The learned routes differ in preference or multipath eligibility) before the symptom recurs. An appropriate regression observation is: The selected route exposes multiple valid next hops and a link-loss test preserves access.

Incorrect Answers

B:

At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, this option proposes: Validate symmetric reachability across fabric-to-external boundaries. Using that approach would investigate A new server subnet cannot reach external routed services although its gateway replies instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The learned routes differ in preference or multipath eligibility.

C:

At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, this option proposes: Validate representative prefix membership before installing static entries. 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: The selected route exposes multiple valid next hops and a link-loss test preserves access.

D:

At Highcrest Municipal Networks, while restoring an underlay BGP adjacency, this option proposes: Maintain explicit management-prefix exclusion tests. This option assumes the other problem (A leaf exports its connected management subnet into tenant-visible fabric routing) is present. The case instead describes All spine-to-leaf BGP sessions exist but one leaf uses a single path instead of ECMP, for which the causal issue is The learned routes differ in preference or multipath eligibility.

Question 273

At Lakeshore Health Systems, while investigating next-hop reachability, the data center fabric team observes: Link failure takes down tenant services even though another physical underlay path is up. What configuration or operational change should the engineer prioritize?

  1. Restore the redundant underlay peer and route selection according to design
  2. Correct the local and peer AS values to match the fabric plan
  3. Move the route or BGP neighbor context to the intended IP-VRF network instance
  4. Tune approved BFD timing based on measured path stability and redundancy needs

Explanation

Correct Answer

A:

At Lakeshore Health Systems, while investigating next-hop reachability, restore the redundant underlay peer and route selection according to design. This addresses the specific failure mechanism (The remaining path was omitted from routing adjacencies or next-hop eligibility) rather than treating only the visible alarm. The required acceptance evidence is: A controlled single-link failure leaves remote VTEP loopbacks reachable.

Incorrect Answers

B:

At Lakeshore Health Systems, while investigating next-hop reachability, this option proposes: Correct the local and peer AS values to match the fabric plan. This option assumes the other problem (A BGP neighbor remains stuck due to a mismatched local or peer autonomous system) 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.

C:

At Lakeshore Health Systems, while investigating next-hop reachability, this option proposes: Move the route or BGP neighbor context to the intended IP-VRF network instance. It tests a different symptom: A routed subinterface can ping its neighbor but the wrong routing table is being populated. 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 Lakeshore Health Systems, while investigating next-hop reachability, this option proposes: Tune approved BFD timing based on measured path stability and redundancy needs. The option describes a different failure mode: A leaf's BGP session resets repeatedly after a minor interface disturbance. It would address BFD detection values are too aggressive for the observed link characteristics, 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 274

At Lakeshore Health Systems, while investigating next-hop reachability, the data center fabric team observes: Link failure takes down tenant services even though another physical underlay path is up. What test result proves the affected fabric function now works?

  1. Representative addresses within the target subnet follow the expected route
  2. The session stays stable during acceptable variations and detects actual link failure within objective
  3. A controlled single-link failure leaves remote VTEP loopbacks reachable
  4. Both peers reach Established using the approved AS assignment

Explanation

Correct Answer

C:

At Lakeshore Health Systems, while investigating next-hop reachability, the decisive validation is: A controlled single-link failure leaves remote VTEP loopbacks reachable. It verifies that the change (Restore the redundant underlay peer and route selection according to design) resolved the mechanism: The remaining path was omitted from routing adjacencies or next-hop eligibility.

Incorrect Answers

A:

At Lakeshore Health Systems, while investigating next-hop reachability, this option proposes: Representative addresses within the target subnet follow the expected route. This option assumes the other problem (An engineer configures a static route destination as a host when an entire subnet is needed) 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 Lakeshore Health Systems, while investigating next-hop reachability, this option proposes: The session stays stable during acceptable variations and detects actual link failure within objective. It tests a different symptom: A leaf's BGP session resets repeatedly after a minor interface disturbance. 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:

A BGP neighbor remains stuck due to a mismatched local or peer autonomous system. Here, the remaining path was omitted from routing adjacencies or next-hop eligibility.

Question 275

At Lakeshore Health Systems, while investigating next-hop reachability, the data center fabric team observes: Link failure takes down tenant services even though another physical underlay path is up. What specific misconfiguration or design error is most likely?

  1. IPv6 family activation or transport address configuration is missing on that adjacency
  2. The two sides disagree on the expected remote AS number
  3. The remaining path was omitted from routing adjacencies or next-hop eligibility
  4. The BGP or static route belongs to an incorrect network instance

Explanation

Correct Answer

C:

At Lakeshore Health Systems, while investigating next-hop reachability, the evidence points to: The remaining path was omitted from routing adjacencies or next-hop eligibility. The follow-up test (A controlled single-link failure leaves remote VTEP loopbacks reachable) distinguishes this mechanism from a separate fabric fault.

Incorrect Answers

A:

At Lakeshore Health Systems, while investigating next-hop reachability, this option proposes: IPv6 family activation or transport address configuration is missing on that adjacency. It tests a different symptom: An underlay peer advertises only IPv4 while an expected IPv6 reachability test fails. 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 Lakeshore Health Systems, while investigating next-hop reachability, this option proposes: The two sides disagree on the expected remote AS number. 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.

D:

At Lakeshore Health Systems, while investigating next-hop reachability, this option proposes: The BGP or static route belongs to an incorrect network instance. This is a valid category of fabric maintenance for another scenario (A routed subinterface can ping its neighbor but the wrong routing table is being populated), not the targeted action for Lakeshore Health Systems. The distinction is the actual cause: The remaining path was omitted from routing adjacencies or next-hop eligibility.

Question 276

At Lakeshore Health Systems, while investigating next-hop reachability, the data center fabric team observes: Link failure takes down tenant services even though another physical underlay path is up. What repeatable acceptance check would reduce recurrence?

  1. Maintain explicit management-prefix exclusion tests
  2. Perform one-link-at-a-time underlay failover testing
  3. Verify loopback reachability before activating overlay peers
  4. Validate symmetric reachability across fabric-to-external boundaries

Explanation

Correct Answer

B:

At Lakeshore Health Systems, while investigating next-hop reachability, perform one-link-at-a-time underlay failover testing. This ongoing review specifically addresses: The remaining path was omitted from routing adjacencies or next-hop eligibility. It should remain part of change acceptance, not only incident closure.

Incorrect Answers

A:

At Lakeshore Health Systems, while investigating next-hop reachability, this option proposes: Maintain explicit management-prefix exclusion tests. The option describes a different failure mode: A leaf exports its connected management subnet into tenant-visible fabric routing. It would address The route export policy fails to distinguish infrastructure and tenant prefixes, 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.

C:

At Lakeshore Health Systems, while investigating next-hop reachability, this option proposes: Verify loopback reachability before activating overlay peers. This is a valid category of fabric maintenance for another scenario (A leaf can reach its directly connected spine but not the loopback used for BGP sessions), not the targeted action for Lakeshore Health Systems. The distinction is the actual cause: The remaining path was omitted from routing adjacencies or next-hop eligibility.

D:

At Lakeshore Health Systems, while investigating next-hop reachability, this option proposes: Validate symmetric reachability across fabric-to-external boundaries. 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: A controlled single-link failure leaves remote VTEP loopbacks reachable.

Question 277

At Pinebrook Health Systems, while commissioning a routed spine uplink, the data center fabric team observes: Two fabric peers have BGP configured but the session stays Idle with no TCP connection. Which action resolves the identified fabric-management issue?

  1. Verify peer addressing, routing and permitted control-plane connectivity
  2. Correct the next-hop-group membership and adjacency reachability
  3. Restore the redundant underlay peer and route selection according to design
  4. Restore physical interface health and then review peer and route state

Explanation

Correct Answer

A:

At Pinebrook Health Systems, while commissioning a routed spine uplink, verify peer addressing, routing and permitted control-plane connectivity. This addresses the specific failure mechanism (The peer address is unreachable or TCP 179 is blocked by the underlay policy) rather than treating only the visible alarm. The required acceptance evidence is: The BGP TCP session establishes and the peer reaches the expected state.

Incorrect Answers

B:

At Pinebrook Health Systems, while commissioning a routed spine uplink, this option proposes: Correct the next-hop-group membership and adjacency reachability. Although related to Underlay routing, BGP, BFD and ECMP, the proposed change fits another mechanism: The referenced next-hop group has no reachable selected member. The evidence in the current case requires a different result: The BGP TCP session establishes and the peer reaches the expected state.

C:

At Pinebrook Health Systems, while commissioning a routed spine uplink, this option proposes: Restore the redundant underlay peer and route selection according to design. Using that approach would investigate Link failure takes down tenant services even though another physical underlay path is up instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The peer address is unreachable or TCP 179 is blocked by the underlay policy.

D:

At Pinebrook Health Systems, while commissioning a routed spine uplink, this option proposes: Restore physical interface health and then review peer and route state. The alternative focuses on Troubleshooting began at the protocol layer without validating lower-layer status, not on the stated defect. For this scenario the expected acceptance result would be: The BGP TCP session establishes and the peer reaches the expected state.

Question 278

At Pinebrook Health Systems, while commissioning a routed spine uplink, the data center fabric team observes: Two fabric peers have BGP configured but the session stays Idle with no TCP connection. Which result would establish that the original defect has been corrected?

  1. The BGP TCP session establishes and the peer reaches the expected state
  2. The selected route exposes multiple valid next hops and a link-loss test preserves access
  3. The forwarding table matches the approved spine preference and still has required backup paths
  4. A controlled single-link failure leaves remote VTEP loopbacks reachable

Explanation

Correct Answer

A:

At Pinebrook Health Systems, while commissioning a routed spine uplink, this result is the relevant closure evidence: The BGP TCP session establishes and the peer reaches the expected state. It checks the effect of: Verify peer addressing, routing and permitted control-plane connectivity. The underlying issue was: The peer address is unreachable or TCP 179 is blocked by the underlay policy.

Incorrect Answers

B:

At Pinebrook Health Systems, while commissioning a routed spine uplink, this option proposes: The selected route exposes multiple valid next hops and a link-loss test preserves access. Using that approach would investigate All spine-to-leaf BGP sessions exist but one leaf uses a single path instead of ECMP instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The peer address is unreachable or TCP 179 is blocked by the underlay policy.

C:

At Pinebrook Health Systems, while commissioning a routed spine uplink, this option proposes: The forwarding table matches the approved spine preference and still has required backup paths. The alternative focuses on The path preference or BGP route attributes changed without validating selected forwarding paths, not on the stated defect. For this scenario the expected acceptance result would be: The BGP TCP session establishes and the peer reaches the expected state.

D:

At Pinebrook Health Systems, while commissioning a routed spine uplink, this option proposes: A controlled single-link failure leaves remote VTEP loopbacks reachable. This option assumes the other problem (Link failure takes down tenant services even though another physical underlay path is up) is present. The case instead describes Two fabric peers have BGP configured but the session stays Idle with no TCP connection, for which the causal issue is The peer address is unreachable or TCP 179 is blocked by the underlay policy.

Question 279

At Pinebrook Health Systems, while commissioning a routed spine uplink, the data center fabric team observes: Two fabric peers have BGP configured but the session stays Idle with no TCP connection. Which root cause fits the reported state?

  1. Troubleshooting began at the protocol layer without validating lower-layer status
  2. The peer address is unreachable or TCP 179 is blocked by the underlay policy
  3. The destination prefix length does not cover the intended address range
  4. The referenced next-hop group has no reachable selected member

Explanation

Correct Answer

B:

At Pinebrook Health Systems, while commissioning a routed spine uplink, the specific mechanism is: The peer address is unreachable or TCP 179 is blocked by the underlay policy. It explains the reported state: Two fabric peers have BGP configured but the session stays Idle with no TCP connection. The targeted corrective action is: Verify peer addressing, routing and permitted control-plane connectivity.

Incorrect Answers

A:

At Pinebrook Health Systems, while commissioning a routed spine uplink, this option proposes: Troubleshooting began at the protocol layer without validating lower-layer status. Using that approach would investigate A routing incident is blamed on BGP even though an interface has no operational carrier instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The peer address is unreachable or TCP 179 is blocked by the underlay policy.

C:

At Pinebrook Health Systems, while commissioning a routed spine uplink, this option proposes: The destination prefix length does not cover the intended address range. This option assumes the other problem (An engineer configures a static route destination as a host when an entire subnet is needed) is present. The case instead describes Two fabric peers have BGP configured but the session stays Idle with no TCP connection, for which the causal issue is The peer address is unreachable or TCP 179 is blocked by the underlay policy.

D:

At Pinebrook Health Systems, while commissioning a routed spine uplink, this option proposes: The referenced next-hop group has no reachable selected member. It tests a different symptom: A static default route appears in configuration but never forwards traffic. For the observed case, the relevant distinction is The peer address is unreachable or TCP 179 is blocked by the underlay policy, with verification: The BGP TCP session establishes and the peer reaches the expected state.

Question 280

At Pinebrook Health Systems, while commissioning a routed spine uplink, the data center fabric team observes: Two fabric peers have BGP configured but the session stays Idle with no TCP connection. Which recurring validation best prevents this failure mode?

  1. Monitor unresolved next hops separately from BGP state
  2. Maintain explicit management-prefix exclusion tests
  3. Include peer transport checks before tuning route policies
  4. Use positive and negative prefix fixtures when revising route policy

Explanation

Correct Answer

C:

At Pinebrook Health Systems, while commissioning a routed spine uplink, for Pinebrook Health Systems, include the safeguard: Include peer transport checks before tuning route policies. It reduces repeat risk from the original mechanism and complements a validation of: The BGP TCP session establishes and the peer reaches the expected state.

Incorrect Answers

A:

At Pinebrook Health Systems, while commissioning a routed spine uplink, this option proposes: Monitor unresolved next hops separately from BGP state. The alternative focuses on The received route's next hop cannot be resolved in the relevant routing instance, not on the stated defect. For this scenario the expected acceptance result would be: The BGP TCP session establishes and the peer reaches the expected state.

B:

At Pinebrook Health Systems, while commissioning a routed spine uplink, this option proposes: Maintain explicit management-prefix exclusion tests. This option assumes the other problem (A leaf exports its connected management subnet into tenant-visible fabric routing) is present. The case instead describes Two fabric peers have BGP configured but the session stays Idle with no TCP connection, for which the causal issue is The peer address is unreachable or TCP 179 is blocked by the underlay policy.

D:

At Pinebrook Health Systems, while commissioning a routed spine uplink, this option proposes: Use positive and negative prefix fixtures when revising route policy. The option describes a different failure mode: A route policy intended to permit fabric loopbacks inadvertently permits all tenant prefixes. It would address A prefix match was broader than the approved route-exchange scope, but here the case reports Two fabric peers have BGP configured but the session stays Idle with no TCP connection. The current required evidence is: The BGP TCP session establishes and the peer reaches the expected state.

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