mcAfee Secure Website
exam =5
exam =6

Exam Code: JN0-481

Exam Name: Data Center, Specialist (JNCIS-DC)

Certification Provider: Juniper

Juniper JN0-481 Questions & Answers

Reliable & Actual Study Materials for JN0-481 Exam Success

65 Questions & Answers with Testing Engine

"JN0-481: Data Center, Specialist (JNCIS-DC)" Testing Engine covers all the knowledge points of the real Juniper JN0-481 exam.

The latest actual JN0-481 Questions & Answers from Pass4sure. Everything you need to prepare and get best score at JN0-481 exam easily and quickly.

exam =7
Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Juniper Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Was: $137.49
Now: $124.99

Juniper JN0-481 Practice Test 6

Question 50

A fabric engineer successfully logs into Apstra but cannot view the blueprint configuration tools needed for a scheduled change. Which design or operational principle best explains this behavior?

  1. The Apstra server relies on managed device agent connectivity and state collection to maintain an accurate operational model.
  2. Supported device integration requires compatible platform profiles, agents and operating-system capabilities for intended automation.
  3. Centralized intent and change management should distinguish staged edits, reviewed changes and active deployment ownership.
  4. Apstra role-based access control separates read visibility from permissions to change managed fabric objects.

Explanation

Correct Answer

D:

Apstra role-based access control separates read visibility from permissions to change managed fabric objects. Here, a fabric engineer successfully logs into Apstra but cannot view the blueprint configuration tools needed for a scheduled change. A useful discriminating check is to inspect the user's role assignments and denied operation in the Apstra access and audit records.

Incorrect Answers

A:

That choice—“The Apstra server relies on managed device agent connectivity and state collection to maintain an accurate operational model”—addresses this other problem: A control-plane service is healthy yet one switch disappears from the Apstra device inventory after a management-network change. Here the scenario is: A fabric engineer successfully logs into Apstra but cannot view the blueprint configuration tools needed for a scheduled change. Apstra role-based access control separates read visibility from permissions to change managed fabric objects. The controlling principle is “Apstra role-based access control separates read visibility from permissions to change managed fabric objects”.

B:

“Supported device integration requires compatible platform profiles, agents and operating-system capabilities for intended automation” is associated with a distinct issue: A fabric engineer asks whether a managed switch can simply be added to any blueprint without first validating its NOS and device profile. By contrast, the actual problem is: A fabric engineer successfully logs into Apstra but cannot view the blueprint configuration tools needed for a scheduled change. Apstra role-based access control separates read visibility from permissions to change managed fabric objects. The controlling principle is “Apstra role-based access control separates read visibility from permissions to change managed fabric objects”.

C:

The option “Centralized intent and change management should distinguish staged edits, reviewed changes and active deployment ownership” is useful in a different setting: A site adds a second blueprint operator but needs to ensure simultaneous edits do not bypass change ownership. The case being tested is: A fabric engineer successfully logs into Apstra but cannot view the blueprint configuration tools needed for a scheduled change. Apstra role-based access control separates read visibility from permissions to change managed fabric objects. The controlling principle is “Apstra role-based access control separates read visibility from permissions to change managed fabric objects”.

Question 51

A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. Which evidence most directly verifies the intended network outcome?

  1. Confirm no required pending work was silently lost and the correct historical revision became active.
  2. Confirm active blueprint state matches the intended retained revision and critical services recover.
  3. Prove the revised blueprint builds with valid allocations and switches converge on intended active state.
  4. Confirm the pending diff no longer includes the bad edit and the active blueprint is unchanged.

Explanation

Correct Answer

D:

This directly tests the desired result: confirm the pending diff no longer includes the bad edit and the active blueprint is unchanged. The decisive investigation is to determine whether the unwanted modification exists only in Staged or in the Active revision. The governing principle is that reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision.

Incorrect Answers

A:

“Confirm no required pending work was silently lost and the correct historical revision became active” is relevant to a different condition: An operator has valuable staged changes when another administrator proposes jumping to an older blueprint revision. The stated question instead concerns: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision. The direct acceptance evidence is “Confirm the pending diff no longer includes the bad edit and the active blueprint is unchanged”.

B:

That choice—“Confirm active blueprint state matches the intended retained revision and critical services recover”—addresses this other problem: A new fabric commit causes service degradation and the team wants to return to a known earlier revision with minimal manual reconstruction. Here the scenario is: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision. The direct acceptance evidence is “Confirm the pending diff no longer includes the bad edit and the active blueprint is unchanged”.

C:

“Prove the revised blueprint builds with valid allocations and switches converge on intended active state” is associated with a distinct issue: An engineer wants to return to a blueprint commit created before several resource pool and hardware changes. By contrast, the actual problem is: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision. The direct acceptance evidence is “Confirm the pending diff no longer includes the bad edit and the active blueprint is unchanged”.

Question 52

A data center offers centralized DNS across isolated customers while requiring strict east-west access boundaries. Which evidence most directly verifies the intended network outcome?

  1. Verify sanctioned intersite application flows and absence of unauthorized tenant route propagation.
  2. Verify permitted shared-service traffic works and all other inter-tenant paths remain blocked.
  3. Confirm migrated VMs communicate over the intended tenant VN while unauthorized networks remain unreachable.
  4. Confirm the application subnet uses the expected tenant VRF and other tenants remain isolated.

Explanation

Correct Answer

B:

This directly tests the desired result: verify permitted shared-service traffic works and all other inter-tenant paths remain blocked. The decisive investigation is to inspect the proposed external or shared-services routing path, import policy and required security controls. The governing principle is that shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation.

Incorrect Answers

A:

The option “Verify sanctioned intersite application flows and absence of unauthorized tenant route propagation” is useful in a different setting: A multiregion deployment needs to preserve tenant boundaries while propagating specific data center routes across a DCI. The case being tested is: A data center offers centralized DNS across isolated customers while requiring strict east-west access boundaries. Shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation. The direct acceptance evidence is “Verify permitted shared-service traffic works and all other inter-tenant paths remain blocked”.

C:

That choice—“Confirm migrated VMs communicate over the intended tenant VN while unauthorized networks remain unreachable”—addresses this other problem: A VMware workload migration succeeds at compute level but its new host port cannot reach the expected tenant virtual network. Here the scenario is: A data center offers centralized DNS across isolated customers while requiring strict east-west access boundaries. Shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation. The direct acceptance evidence is “Verify permitted shared-service traffic works and all other inter-tenant paths remain blocked”.

D:

“Confirm the application subnet uses the expected tenant VRF and other tenants remain isolated” is associated with a distinct issue: A development VN is accidentally assigned to the wrong routing zone during a project migration. By contrast, the actual problem is: A data center offers centralized DNS across isolated customers while requiring strict east-west access boundaries. Shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation. The direct acceptance evidence is “Verify permitted shared-service traffic works and all other inter-tenant paths remain blocked”.

Question 53

A failed managed switch is swapped physically yet Apstra refuses deployment to the replacement inventory device. Which evidence most directly verifies the intended network outcome?

  1. Confirm each device has one accurate unique inventory record and intended blueprint role.
  2. Confirm the device appears healthy, available and uniquely identified for blueprint assignment.
  3. Confirm the active revision and target device running configuration reflect the approved change.
  4. Verify logical port mappings, rendered configuration and fabric services recover on the new physical device.

Explanation

Correct Answer

D:

This directly tests the desired result: verify logical port mappings, rendered configuration and fabric services recover on the new physical device. The decisive investigation is to review device replacement workflow, old/new system identifiers and required port/profile compatibility. The governing principle is that device replacement requires reconciling the blueprint's intended logical device with the actual managed system identity.

Incorrect Answers

A:

“Confirm each device has one accurate unique inventory record and intended blueprint role” is associated with a distinct issue: A deployment team duplicates a device-system ID when registering two new leaf switches. By contrast, the actual problem is: A failed managed switch is swapped physically yet Apstra refuses deployment to the replacement inventory device. Device replacement requires reconciling the blueprint's intended logical device with the actual managed system identity. The direct acceptance evidence is “Verify logical port mappings, rendered configuration and fabric services recover on the new physical device”.

B:

The option “Confirm the device appears healthy, available and uniquely identified for blueprint assignment” is useful in a different setting: A switch is reachable over SSH but Apstra cannot assign it to a blueprint because the device agent is not installed correctly. The case being tested is: A failed managed switch is swapped physically yet Apstra refuses deployment to the replacement inventory device. Device replacement requires reconciling the blueprint's intended logical device with the actual managed system identity. The direct acceptance evidence is “Verify logical port mappings, rendered configuration and fabric services recover on the new physical device”.

C:

“Confirm the active revision and target device running configuration reflect the approved change” is relevant to a different condition: A design is staged and rendered correctly, but a production switch still uses the previous running configuration. The stated question instead concerns: A failed managed switch is swapped physically yet Apstra refuses deployment to the replacement inventory device. Device replacement requires reconciling the blueprint's intended logical device with the actual managed system identity. The direct acceptance evidence is “Verify logical port mappings, rendered configuration and fabric services recover on the new physical device”.

Question 54

An IBA probe reports intermittent latency spikes but application errors are not visible in basic device health summaries. Which evidence most directly verifies the intended network outcome?

  1. Verify objective service and interface measurements improve and a valid probe no longer detects an anomaly.
  2. Confirm latency measurements and anomaly state return within accepted bounds under representative traffic.
  3. Confirm the root metric stabilizes and correlated anomalies across dependent probes clear.
  4. Generate a controlled test condition and confirm the probe reports the expected anomaly with accurate context.

Explanation

Correct Answer

B:

This directly tests the desired result: confirm latency measurements and anomaly state return within accepted bounds under representative traffic. The decisive investigation is to inspect affected probe stages, timestamps and source telemetry along the application path. The governing principle is that analytics anomalies can indicate measured performance deviations that do not coincide with configuration intent mismatches.

Incorrect Answers

A:

That choice—“Verify objective service and interface measurements improve and a valid probe no longer detects an anomaly”—addresses this other problem: A data center dashboard becomes green immediately after an engineer increases alert thresholds without addressing failing application traffic. Here the scenario is: An IBA probe reports intermittent latency spikes but application errors are not visible in basic device health summaries. Analytics anomalies can indicate measured performance deviations that do not coincide with configuration intent mismatches. The direct acceptance evidence is “Confirm latency measurements and anomaly state return within accepted bounds under representative traffic”.

C:

The option “Confirm the root metric stabilizes and correlated anomalies across dependent probes clear” is useful in a different setting: An operations team receives repeated probe-stage alerts after an optic begins incrementing errors. The case being tested is: An IBA probe reports intermittent latency spikes but application errors are not visible in basic device health summaries. Analytics anomalies can indicate measured performance deviations that do not coincide with configuration intent mismatches. The direct acceptance evidence is “Confirm latency measurements and anomaly state return within accepted bounds under representative traffic”.

D:

“Generate a controlled test condition and confirm the probe reports the expected anomaly with accurate context” is relevant to a different condition: An operator wants an early-warning signal when fabric interface errors exceed a defined threshold. The stated question instead concerns: An IBA probe reports intermittent latency spikes but application errors are not visible in basic device health summaries. Analytics anomalies can indicate measured performance deviations that do not coincide with configuration intent mismatches. The direct acceptance evidence is “Confirm latency measurements and anomaly state return within accepted bounds under representative traffic”.

Question 55

A dashboard reports that all switches are reachable while a recent staged policy change has not been deployed. Which evidence most directly verifies the intended network outcome?

  1. Observe the updated active blueprint and running device configuration reflect the approved new virtual network.
  2. Confirm the resulting active revision contains only approved changes and has a traceable description.
  3. Confirm device health and active configuration separately, then document any pending staged work.
  4. Confirm no required pending work was silently lost and the correct historical revision became active.

Explanation

Correct Answer

C:

This directly tests the desired result: confirm device health and active configuration separately, then document any pending staged work. The decisive investigation is to compare dashboard health with active revision and pending staged configuration diffs. The governing principle is that device health, intended active blueprint state and pending staged edits describe different dimensions of operations.

Incorrect Answers

A:

“Observe the updated active blueprint and running device configuration reflect the approved new virtual network” is relevant to a different condition: A service owner tests a new VRF assignment while the proposed change appears only in the Staged view. The stated question instead concerns: A dashboard reports that all switches are reachable while a recent staged policy change has not been deployed. Device health, intended active blueprint state and pending staged edits describe different dimensions of operations. The direct acceptance evidence is “Confirm device health and active configuration separately, then document any pending staged work”.

B:

That choice—“Confirm the resulting active revision contains only approved changes and has a traceable description”—addresses this other problem: A blueprint has accumulated unrelated uncommitted routing and rack modifications from different change windows. Here the scenario is: A dashboard reports that all switches are reachable while a recent staged policy change has not been deployed. Device health, intended active blueprint state and pending staged edits describe different dimensions of operations. The direct acceptance evidence is “Confirm device health and active configuration separately, then document any pending staged work”.

D:

The option “Confirm no required pending work was silently lost and the correct historical revision became active” is useful in a different setting: An operator has valuable staged changes when another administrator proposes jumping to an older blueprint revision. The case being tested is: A dashboard reports that all switches are reachable while a recent staged policy change has not been deployed. Device health, intended active blueprint state and pending staged edits describe different dimensions of operations. The direct acceptance evidence is “Confirm device health and active configuration separately, then document any pending staged work”.

Question 56

A data center needs to add another rack to a production fabric without replacing the existing blueprint. Which initial check would most directly distinguish the likely cause?

  1. Check current spine port availability, resource pools and the proposed rack type against the active blueprint.
  2. Compare pristine baseline, incremental changes and final rendered config against the active blueprint.
  3. Inspect the intended leaf attachment ports, generic-system definition and relevant cable map.
  4. Compare staged differences with active configuration and deployment status before testing production traffic.

Explanation

Correct Answer

A:

This checks the relevant evidence first: check current spine port availability, resource pools and the proposed rack type against the active blueprint. The underlying concept is that Apstra supports controlled blueprint day-two rack additions using supported rack types, resources and spine capacity. After confirming the finding, a controlled remediation is to stage the new rack, assign valid devices and resources, validate, then commit through change control.

Incorrect Answers

B:

“Compare pristine baseline, incremental changes and final rendered config against the active blueprint” is relevant to a different condition: A network engineer sees differences among the pristine, incremental and rendered configurations for a managed leaf. The stated question instead concerns: A data center needs to add another rack to a production fabric without replacing the existing blueprint. The relevant inspection is: Check current spine port availability, resource pools and the proposed rack type against the active blueprint. The most discriminating first check is “Check current spine port availability, resource pools and the proposed rack type against the active blueprint”.

C:

That choice—“Inspect the intended leaf attachment ports, generic-system definition and relevant cable map”—addresses this other problem: A new dual-homed application server is physically connected but its logical attachment is absent from the active blueprint. Here the scenario is: A data center needs to add another rack to a production fabric without replacing the existing blueprint. The relevant inspection is: Check current spine port availability, resource pools and the proposed rack type against the active blueprint. The most discriminating first check is “Check current spine port availability, resource pools and the proposed rack type against the active blueprint”.

D:

“Compare staged differences with active configuration and deployment status before testing production traffic” is associated with a distinct issue: A service owner tests a new VRF assignment while the proposed change appears only in the Staged view. By contrast, the actual problem is: A data center needs to add another rack to a production fabric without replacing the existing blueprint. The relevant inspection is: Check current spine port availability, resource pools and the proposed rack type against the active blueprint. The most discriminating first check is “Check current spine port availability, resource pools and the proposed rack type against the active blueprint”.

Question 57

Two racks advertise the same distributed gateway virtual address but clients see intermittent first-hop behavior after a deployment. Which controlled change best addresses the described requirement?

  1. Align the authorized distributed gateway configuration across participating VTEPs.
  2. Implement an authorized distributed gateway design and ensure the overlay advertises the required endpoint or prefix routes.
  3. Advertise and import the required host or prefix routes according to the approved ERB routing design.
  4. Align approved Ethernet segment and multihoming configuration on the participating leaf devices.

Explanation

Correct Answer

A:

This action addresses the stated defect: align the authorized distributed gateway configuration across participating VTEPs. The underlying constraint is that a distributed anycast gateway needs consistent gateway identity and virtual network association across participating leaf devices. Verify rather than assume success: confirm local first-hop forwarding and cross-rack routing continue consistently through each attached leaf.

Incorrect Answers

B:

The option “Implement an authorized distributed gateway design and ensure the overlay advertises the required endpoint or prefix routes” is useful in a different setting: An architect wants gateway functions distributed across tenant leafs in an EVPN-VXLAN fabric. The case being tested is: Two racks advertise the same distributed gateway virtual address but clients see intermittent first-hop behavior after a deployment. Align the authorized distributed gateway configuration across participating VTEPs. The most relevant correction is “Align the authorized distributed gateway configuration across participating VTEPs”.

C:

“Advertise and import the required host or prefix routes according to the approved ERB routing design” is relevant to a different condition: An engineer wants both endpoint reachability and aggregated routed prefixes but is uncertain which EVPN routes serve each purpose. The stated question instead concerns: Two racks advertise the same distributed gateway virtual address but clients see intermittent first-hop behavior after a deployment. Align the authorized distributed gateway configuration across participating VTEPs. The most relevant correction is “Align the authorized distributed gateway configuration across participating VTEPs”.

D:

That choice—“Align approved Ethernet segment and multihoming configuration on the participating leaf devices”—addresses this other problem: An EVPN multihomed endpoint exhibits unstable forwarding after both attachment leafs advertise the same segment independently. Here the scenario is: Two racks advertise the same distributed gateway virtual address but clients see intermittent first-hop behavior after a deployment. Align the authorized distributed gateway configuration across participating VTEPs. The most relevant correction is “Align the authorized distributed gateway configuration across participating VTEPs”.

Question 58

A custom telemetry probe flags a latency anomaly but the blueprint shows no service configuration errors. Which controlled change best addresses the described requirement?

  1. Route the issue to the correct service, telemetry or device workflow based on the observed anomaly evidence.
  2. Correct the mismatched service intent or deployed configuration while preserving authorized tenant isolation.
  3. Investigate the measured condition and adjust the approved monitored system or justified probe threshold.
  4. Investigate unexpected changes using the appropriate generated-config view and approved override workflow.

Explanation

Correct Answer

C:

This action addresses the stated defect: investigate the measured condition and adjust the approved monitored system or justified probe threshold. The underlying constraint is that probe anomalies can reflect telemetry thresholds or conditions independently of blueprint service configuration anomalies. Verify rather than assume success: confirm live telemetry returns inside accepted bounds and the probe alert clears with supporting samples.

Incorrect Answers

A:

That choice—“Route the issue to the correct service, telemetry or device workflow based on the observed anomaly evidence”—addresses this other problem: A support engineer assumes every anomaly is a device-down alarm even when the affected rule is a tenant connectivity expectation. Here the scenario is: A custom telemetry probe flags a latency anomaly but the blueprint shows no service configuration errors. Investigate the measured condition and adjust the approved monitored system or justified probe threshold. The most relevant correction is “Investigate the measured condition and adjust the approved monitored system or justified probe threshold”.

B:

“Correct the mismatched service intent or deployed configuration while preserving authorized tenant isolation” is associated with a distinct issue: A blueprint raises a service anomaly for a virtual network even though all interfaces in its rack are administratively up. By contrast, the actual problem is: A custom telemetry probe flags a latency anomaly but the blueprint shows no service configuration errors. Investigate the measured condition and adjust the approved monitored system or justified probe threshold. The most relevant correction is “Investigate the measured condition and adjust the approved monitored system or justified probe threshold”.

D:

“Investigate unexpected changes using the appropriate generated-config view and approved override workflow” is relevant to a different condition: An audit asks why some device commands come from the baseline while others appear from intended virtual-network configuration. The stated question instead concerns: A custom telemetry probe flags a latency anomaly but the blueprint shows no service configuration errors. Investigate the measured condition and adjust the approved monitored system or justified probe threshold. The most relevant correction is “Investigate the measured condition and adjust the approved monitored system or justified probe threshold”.

Question 59

A site sees hundreds of anomaly events from one failing uplink and wants to distinguish one root cause from many symptoms. Which initial check would most directly distinguish the likely cause?

  1. Group probe anomalies by affected node and stage, then inspect linked telemetry and topology edges.
  2. Inspect affected probe stages, timestamps and source telemetry along the application path.
  3. Compare live raw telemetry, probe thresholds and application SLOs before and after the change.
  4. Inspect the graph query's node types, filters and returned relationship paths for the intended rack.

Explanation

Correct Answer

A:

This checks the relevant evidence first: group probe anomalies by affected node and stage, then inspect linked telemetry and topology edges. The underlying concept is that graph and probe context can correlate multiple anomalies to a shared physical or logical source. After confirming the finding, a controlled remediation is to repair the verified common uplink fault and retain alert history for root-cause analysis.

Incorrect Answers

B:

That choice—“Inspect affected probe stages, timestamps and source telemetry along the application path”—addresses this other problem: An Apstra dashboard shows probe anomalies while fabric service topology and device reachability stay normal. Here the scenario is: A site sees hundreds of anomaly events from one failing uplink and wants to distinguish one root cause from many symptoms. Group probe anomalies by affected node and stage, then inspect linked telemetry and topology edges. The most discriminating first check is “Group probe anomalies by affected node and stage, then inspect linked telemetry and topology edges”.

C:

“Compare live raw telemetry, probe thresholds and application SLOs before and after the change” is associated with a distinct issue: A data center dashboard becomes green immediately after an engineer increases alert thresholds without addressing failing application traffic. By contrast, the actual problem is: A site sees hundreds of anomaly events from one failing uplink and wants to distinguish one root cause from many symptoms. Group probe anomalies by affected node and stage, then inspect linked telemetry and topology edges. The most discriminating first check is “Group probe anomalies by affected node and stage, then inspect linked telemetry and topology edges”.

D:

The option “Inspect the graph query's node types, filters and returned relationship paths for the intended rack” is useful in a different setting: A large fabric includes many repeated physical device names and an operator needs the exact topology relationship for one rack. The case being tested is: A site sees hundreds of anomaly events from one failing uplink and wants to distinguish one root cause from many symptoms. Group probe anomalies by affected node and stage, then inspect linked telemetry and topology edges. The most discriminating first check is “Group probe anomalies by affected node and stage, then inspect linked telemetry and topology edges”.

Question 60

A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. Which controlled change best addresses the described requirement?

  1. Advertise the approved VTEP loopbacks through the fabric underlay and check next-hop reachability.
  2. Use validated spine-leaf cabling and routing relationships rather than ad hoc lateral transit links.
  3. Repair the routed underlay addressing or protocol configuration and then validate overlay sessions.
  4. Correct underlay failure detection and routing convergence within the approved topology and timer policy.

Explanation

Correct Answer

C:

This action addresses the stated defect: repair the routed underlay addressing or protocol configuration and then validate overlay sessions. The underlying constraint is that an IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly. Verify rather than assume success: observe established underlay peers and reachability of every intended VTEP loopback before testing virtual networks.

Incorrect Answers

A:

The option “Advertise the approved VTEP loopbacks through the fabric underlay and check next-hop reachability” is useful in a different setting: An engineer brings up BGP peers to the spines but omits export of the overlay endpoint loopbacks. The case being tested is: A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. Repair the routed underlay addressing or protocol configuration and then validate overlay sessions. The most relevant correction is “Repair the routed underlay addressing or protocol configuration and then validate overlay sessions”.

B:

“Use validated spine-leaf cabling and routing relationships rather than ad hoc lateral transit links” is relevant to a different condition: A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. The stated question instead concerns: A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. Repair the routed underlay addressing or protocol configuration and then validate overlay sessions. The most relevant correction is “Repair the routed underlay addressing or protocol configuration and then validate overlay sessions”.

D:

“Correct underlay failure detection and routing convergence within the approved topology and timer policy” is associated with a distinct issue: A two-spine fabric can tolerate one path failure but the application sees blackholing for several minutes after a spine uplink drops. By contrast, the actual problem is: A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. Repair the routed underlay addressing or protocol configuration and then validate overlay sessions. The most relevant correction is “Repair the routed underlay addressing or protocol configuration and then validate overlay sessions”.

Data Center, Specialist (JNCIS-DC) (JN0-481) Practice Tests