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 15

Question 140

An endpoint's remote leaf cannot deliver traffic even though the local access VLAN is assigned correctly because the tunnel endpoint is unreachable. Which initial check would most directly distinguish the likely cause?

  1. Inspect the VLAN-to-VNI bindings on both local and remote VTEPs and compare the blueprint virtual-network intent.
  2. Inspect EVPN route exchange and the selected VTEP's learned endpoint state instead of inferring learning from floods.
  3. Inspect VTEP loopback next-hop resolution, VXLAN encapsulation and underlay reachability.
  4. Trace effective underlay MTU and path fragmentation or drop counters between the participating VTEPs.

Explanation

Correct Answer

C:

This checks the relevant evidence first: inspect VTEP loopback next-hop resolution, VXLAN encapsulation and underlay reachability. The underlying concept is that a VTEP provides VXLAN encapsulation and decapsulation and its IP reachability must exist independently of bridge membership. After confirming the finding, a controlled remediation is to restore routed reachability to the advertised VTEP and the correct tunnel forwarding state.

Incorrect Answers

A:

The option “Inspect the VLAN-to-VNI bindings on both local and remote VTEPs and compare the blueprint virtual-network intent” is useful in a different setting: A rack migration assigns the correct switch access VLAN but places the VTEP into another tenant's virtual network identifier. The case being tested is: An endpoint's remote leaf cannot deliver traffic even though the local access VLAN is assigned correctly because the tunnel endpoint is unreachable. The relevant inspection is: Inspect VTEP loopback next-hop resolution, VXLAN encapsulation and underlay reachability. The most discriminating first check is “Inspect VTEP loopback next-hop resolution, VXLAN encapsulation and underlay reachability”.

B:

“Inspect EVPN route exchange and the selected VTEP's learned endpoint state instead of inferring learning from floods” is relevant to a different condition: An architect compares an EVPN control plane with reliance on data-plane flood-and-learn for VXLAN workloads. The stated question instead concerns: An endpoint's remote leaf cannot deliver traffic even though the local access VLAN is assigned correctly because the tunnel endpoint is unreachable. The relevant inspection is: Inspect VTEP loopback next-hop resolution, VXLAN encapsulation and underlay reachability. The most discriminating first check is “Inspect VTEP loopback next-hop resolution, VXLAN encapsulation and underlay reachability”.

D:

“Trace effective underlay MTU and path fragmentation or drop counters between the participating VTEPs” is associated with a distinct issue: A VXLAN packet encapsulation crosses a routed fabric but is discarded along the path due to frame size. By contrast, the actual problem is: An endpoint's remote leaf cannot deliver traffic even though the local access VLAN is assigned correctly because the tunnel endpoint is unreachable. The relevant inspection is: Inspect VTEP loopback next-hop resolution, VXLAN encapsulation and underlay reachability. The most discriminating first check is “Inspect VTEP loopback next-hop resolution, VXLAN encapsulation and underlay reachability”.

Question 141

A template identifies uplink ports by logical role but a new hardware SKU has different port naming. Which evidence most directly verifies the intended network outcome?

  1. Validate that physical port assignments and supported speeds match the rack design without resource conflicts.
  2. Confirm the design validator has no duplicate port assignments and each link role maps to the intended connector.
  3. Validate logical port counts and generated rack connections before building the blueprint.
  4. Confirm rendered port assignments match the physical cable map and supported switch interfaces.

Explanation

Correct Answer

D:

This directly tests the desired result: confirm rendered port assignments match the physical cable map and supported switch interfaces. The decisive investigation is to review logical-to-physical interface mappings and device profile nomenclature for the new platform. The governing principle is that logical device interfaces must be mapped to actual supported physical device ports through the correct interface map.

Incorrect Answers

A:

“Validate that physical port assignments and supported speeds match the rack design without resource conflicts” is associated with a distinct issue: An Apstra design refuses a proposed uplink because its interface map does not match hardware port mode. By contrast, the actual problem is: A template identifies uplink ports by logical role but a new hardware SKU has different port naming. Logical device interfaces must be mapped to actual supported physical device ports through the correct interface map. The direct acceptance evidence is “Confirm rendered port assignments match the physical cable map and supported switch interfaces”.

B:

The option “Confirm the design validator has no duplicate port assignments and each link role maps to the intended connector” is useful in a different setting: A fabric build fails because one interface was assigned to both an uplink and a server-facing logical port. The case being tested is: A template identifies uplink ports by logical role but a new hardware SKU has different port naming. Logical device interfaces must be mapped to actual supported physical device ports through the correct interface map. The direct acceptance evidence is “Confirm rendered port assignments match the physical cable map and supported switch interfaces”.

C:

“Validate logical port counts and generated rack connections before building the blueprint” is relevant to a different condition: A rack template chooses a logical device with insufficient server ports for its planned generic systems. The stated question instead concerns: A template identifies uplink ports by logical role but a new hardware SKU has different port naming. Logical device interfaces must be mapped to actual supported physical device ports through the correct interface map. The direct acceptance evidence is “Confirm rendered port assignments match the physical cable map and supported switch interfaces”.

Question 142

An Apstra designer tries to deploy a rack without allocating required underlay interface and IP pools. Which shortcut would be most likely to undermine this objective?

  1. Assume every active fabric instantly adopts an edited global template without a staged change.
  2. Depend on later untracked switch CLI changes to supply all missing external links.
  3. Force generated configuration onto an unsupported NOS and disable syntax checking.
  4. Ignore design validation failures and push partial configurations directly to switches.

Explanation

Correct Answer

D:

This is the unsafe shortcut to avoid: ignore design validation failures and push partial configurations directly to switches. It violates the principle that design-phase resource and topology validation must succeed before a controlled deployment can be trusted. An appropriate alternative is to resolve the specific design and resource conflicts and regenerate intended configuration.

Incorrect Answers

A:

That choice—“Assume every active fabric instantly adopts an edited global template without a staged change”—addresses this other problem: A design template was edited after the first rack was built and an engineer assumes existing active blueprints are retroactively rewritten. Here the scenario is: An Apstra designer tries to deploy a rack without allocating required underlay interface and IP pools. Design-phase resource and topology validation must succeed before a controlled deployment can be trusted. The directly relevant unsafe shortcut is “Ignore design validation failures and push partial configurations directly to switches”.

B:

“Depend on later untracked switch CLI changes to supply all missing external links” is associated with a distinct issue: A proposed rack blueprint includes all needed devices but its graph does not represent an external border connection required by applications. By contrast, the actual problem is: An Apstra designer tries to deploy a rack without allocating required underlay interface and IP pools. Design-phase resource and topology validation must succeed before a controlled deployment can be trusted. The directly relevant unsafe shortcut is “Ignore design validation failures and push partial configurations directly to switches”.

C:

The option “Force generated configuration onto an unsupported NOS and disable syntax checking” is useful in a different setting: A team assigns a device image and platform combination not supported by the chosen Apstra reference design. The case being tested is: An Apstra designer tries to deploy a rack without allocating required underlay interface and IP pools. Design-phase resource and topology validation must succeed before a controlled deployment can be trusted. The directly relevant unsafe shortcut is “Ignore design validation failures and push partial configurations directly to switches”.

Question 143

An Apstra graph search reveals a workload object disconnected from its expected virtual-network relation. Which shortcut would be most likely to undermine this objective?

  1. Assume a single tag-text search always represents every intended server-to-leaf relationship.
  2. Match every interface whose label includes the rack number without checking topology relationships.
  3. Raise the anomaly threshold to infinity because the probe currently selects unrelated devices.
  4. Delete any graph node that appears isolated without checking whether it represents a real device.

Explanation

Correct Answer

D:

This is the unsafe shortcut to avoid: delete any graph node that appears isolated without checking whether it represents a real device. It violates the principle that graph query results reflect the modeled topology and may reveal missing or misassigned relationships that need validation. An appropriate alternative is to repair the validated missing logical relation or correct the query filter if it is misleading.

Incorrect Answers

A:

“Assume a single tag-text search always represents every intended server-to-leaf relationship” is relevant to a different condition: An operations dashboard must report which workload attachments inherit a specific project label. The stated question instead concerns: An Apstra graph search reveals a workload object disconnected from its expected virtual-network relation. Graph query results reflect the modeled topology and may reveal missing or misassigned relationships that need validation. The directly relevant unsafe shortcut is “Delete any graph node that appears isolated without checking whether it represents a real device”.

B:

That choice—“Match every interface whose label includes the rack number without checking topology relationships”—addresses this other problem: A large fabric includes many repeated physical device names and an operator needs the exact topology relationship for one rack. Here the scenario is: An Apstra graph search reveals a workload object disconnected from its expected virtual-network relation. Graph query results reflect the modeled topology and may reveal missing or misassigned relationships that need validation. The directly relevant unsafe shortcut is “Delete any graph node that appears isolated without checking whether it represents a real device”.

C:

“Raise the anomaly threshold to infinity because the probe currently selects unrelated devices” is associated with a distinct issue: A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. By contrast, the actual problem is: An Apstra graph search reveals a workload object disconnected from its expected virtual-network relation. Graph query results reflect the modeled topology and may reveal missing or misassigned relationships that need validation. The directly relevant unsafe shortcut is “Delete any graph node that appears isolated without checking whether it represents a real device”.

Question 144

A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. Which initial check would most directly distinguish the likely cause?

  1. Compare the proposed topology with supported reference-design dimensions and template requirements.
  2. Calculate required leaf uplinks and available spine ports for projected growth under the topology template.
  3. Review intended external service connectivity and supported blueprint reference-design capabilities.
  4. Review single-versus-dual leaf rack settings and server connectivity requirements.

Explanation

Correct Answer

C:

This checks the relevant evidence first: review intended external service connectivity and supported blueprint reference-design capabilities. The underlying concept is that reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements. After confirming the finding, a controlled remediation is to choose the reference design and blueprint template that satisfy gateway connectivity and scaling constraints.

Incorrect Answers

A:

The option “Compare the proposed topology with supported reference-design dimensions and template requirements” is useful in a different setting: An architect wants consistent rack scale-out using a reference design rather than independently inventing each fabric topology. The case being tested is: A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. The relevant inspection is: Review intended external service connectivity and supported blueprint reference-design capabilities. The most discriminating first check is “Review intended external service connectivity and supported blueprint reference-design capabilities”.

B:

“Calculate required leaf uplinks and available spine ports for projected growth under the topology template” is relevant to a different condition: A planned Apstra fabric includes future rack growth but the initial design leaves no capacity for additional spine downlinks. The stated question instead concerns: A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. The relevant inspection is: Review intended external service connectivity and supported blueprint reference-design capabilities. The most discriminating first check is “Review intended external service connectivity and supported blueprint reference-design capabilities”.

D:

“Review single-versus-dual leaf rack settings and server connectivity requirements” is associated with a distinct issue: A rack designer wants a redundant host attachment pattern for critical appliances. By contrast, the actual problem is: A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. The relevant inspection is: Review intended external service connectivity and supported blueprint reference-design capabilities. The most discriminating first check is “Review intended external service connectivity and supported blueprint reference-design capabilities”.

Question 145

A site models 48 server attachments using a logical device profile that exposes only 32 suitable host interfaces. Which initial check would most directly distinguish the likely cause?

  1. Inspect pool size, consumed allocations and required identifiers for all logical devices.
  2. Compare the selected logical device's interface count, speeds and connection roles with rack requirements.
  3. Inspect object tags and query results before selecting the intended device set.
  4. Check the VNI resource pool, existing reservations and intended tenant-to-VN mappings.

Explanation

Correct Answer

B:

This checks the relevant evidence first: compare the selected logical device's interface count, speeds and connection roles with rack requirements. The underlying concept is that logical device definitions represent required interface roles and capacities, independent of hardware SKU details. After confirming the finding, a controlled remediation is to use a compatible logical device and device profile combination with sufficient supported host ports.

Incorrect Answers

A:

“Inspect pool size, consumed allocations and required identifiers for all logical devices” is associated with a distinct issue: A new blueprint assigns every VTEP from a resource pool that is too small for the proposed rack count. By contrast, the actual problem is: A site models 48 server attachments using a logical device profile that exposes only 32 suitable host interfaces. The relevant inspection is: Compare the selected logical device's interface count, speeds and connection roles with rack requirements. The most discriminating first check is “Compare the selected logical device's interface count, speeds and connection roles with rack requirements”.

C:

“Inspect object tags and query results before selecting the intended device set” is relevant to a different condition: A team needs to group rack devices for maintenance based on operational ownership without renaming every node. The stated question instead concerns: A site models 48 server attachments using a logical device profile that exposes only 32 suitable host interfaces. The relevant inspection is: Compare the selected logical device's interface count, speeds and connection roles with rack requirements. The most discriminating first check is “Compare the selected logical device's interface count, speeds and connection roles with rack requirements”.

D:

That choice—“Check the VNI resource pool, existing reservations and intended tenant-to-VN mappings”—addresses this other problem: An expansion accidentally reuses a virtual network identifier assigned to another isolated overlay segment. Here the scenario is: A site models 48 server attachments using a logical device profile that exposes only 32 suitable host interfaces. The relevant inspection is: Compare the selected logical device's interface count, speeds and connection roles with rack requirements. The most discriminating first check is “Compare the selected logical device's interface count, speeds and connection roles with rack requirements”.

Question 146

An IBA probe reports intermittent latency spikes but application errors are not visible in basic device health summaries. 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. Compare live raw telemetry, probe thresholds and application SLOs before and after the change.
  3. Inspect affected probe stages, timestamps and source telemetry along the application path.
  4. Inspect probe data sources, monitored stages, thresholds and the exact interfaces being selected.

Explanation

Correct Answer

C:

This checks the relevant evidence first: inspect affected probe stages, timestamps and source telemetry along the application path. The underlying concept is that analytics anomalies can indicate measured performance deviations that do not coincide with configuration intent mismatches. After confirming the finding, a controlled remediation is to correlate the observed metrics with topology and tune or remediate the validated underlying condition.

Incorrect Answers

A:

That choice—“Group probe anomalies by affected node and stage, then inspect linked telemetry and topology edges”—addresses this other problem: An operations team receives repeated probe-stage alerts after an optic begins incrementing errors. Here the scenario is: An IBA probe reports intermittent latency spikes but application errors are not visible in basic device health summaries. The relevant inspection is: Inspect affected probe stages, timestamps and source telemetry along the application path. The most discriminating first check is “Inspect affected probe stages, timestamps and source telemetry along the application path”.

B:

“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: An IBA probe reports intermittent latency spikes but application errors are not visible in basic device health summaries. The relevant inspection is: Inspect affected probe stages, timestamps and source telemetry along the application path. The most discriminating first check is “Inspect affected probe stages, timestamps and source telemetry along the application path”.

D:

“Inspect probe data sources, monitored stages, thresholds and the exact interfaces being selected” 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. The relevant inspection is: Inspect affected probe stages, timestamps and source telemetry along the application path. The most discriminating first check is “Inspect affected probe stages, timestamps and source telemetry along the application path”.

Question 147

A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Which evidence most directly verifies the intended network outcome?

  1. Verify the intended external session and imported/exported prefixes appear only in the proper tenant routing context.
  2. Confirm only approved routes are exchanged and unauthorized prefixes no longer leave the fabric.
  3. Confirm the host receives exactly the intended VLANs and no unrelated tenant traffic.
  4. Verify permitted shared-service traffic works and all other inter-tenant paths remain blocked.

Explanation

Correct Answer

A:

This directly tests the desired result: verify the intended external session and imported/exported prefixes appear only in the proper tenant routing context. The decisive investigation is to inspect border-leaf interfaces, attached connectivity template and tenant-specific routing policy. The governing principle is that connectivity templates can describe supported external routing sessions and attach them to the intended routing zone.

Incorrect Answers

B:

That choice—“Confirm only approved routes are exchanged and unauthorized prefixes no longer leave the fabric”—addresses this other problem: An external peer receives a tenant's internal subnets that were supposed to stay private. Here the scenario is: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. The direct acceptance evidence is “Verify the intended external session and imported/exported prefixes appear only in the proper tenant routing context”.

C:

“Confirm the host receives exactly the intended VLANs and no unrelated tenant traffic” is associated with a distinct issue: A generic system connects to a leaf with one untagged network and a small approved list of tagged VNs. By contrast, the actual problem is: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. The direct acceptance evidence is “Verify the intended external session and imported/exported prefixes appear only in the proper tenant routing context”.

D:

The option “Verify permitted shared-service traffic works and all other inter-tenant paths remain blocked” is useful in a different setting: Two tenants require a controlled shared service, and a proposal suggests importing every route into each tenant VRF. The case being tested is: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. The direct acceptance evidence is “Verify the intended external session and imported/exported prefixes appear only in the proper tenant routing context”.

Question 148

A new rack is partially configured and the change ticket lacks a clear record of who initiated its commit. Which initial check would most directly distinguish the likely cause?

  1. Correlate blueprint revision history, actor identity and event logs around the failure timestamp.
  2. Check collector or agent timestamps, sample rates and ingestion connectivity before trusting status.
  3. Review the event timeline, blueprint commit notes, deployment status and actor records.
  4. Inspect supported syslog configuration, transport reachability and receiving collector parsing.

Explanation

Correct Answer

C:

This checks the relevant evidence first: review the event timeline, blueprint commit notes, deployment status and actor records. The underlying concept is that controller event logs and deployment records should be correlated with intent revisions and change approvals. After confirming the finding, a controlled remediation is to document the causal change and correct the failed deployment through an auditable workflow.

Incorrect Answers

A:

The option “Correlate blueprint revision history, actor identity and event logs around the failure timestamp” is useful in a different setting: An operator needs to explain who committed a change after a rack lost connectivity overnight. The case being tested is: A new rack is partially configured and the change ticket lacks a clear record of who initiated its commit. The relevant inspection is: Review the event timeline, blueprint commit notes, deployment status and actor records. The most discriminating first check is “Review the event timeline, blueprint commit notes, deployment status and actor records”.

B:

“Check collector or agent timestamps, sample rates and ingestion connectivity before trusting status” is relevant to a different condition: An Apstra operator sees no current alerts after a telemetry collector became unreachable. The stated question instead concerns: A new rack is partially configured and the change ticket lacks a clear record of who initiated its commit. The relevant inspection is: Review the event timeline, blueprint commit notes, deployment status and actor records. The most discriminating first check is “Review the event timeline, blueprint commit notes, deployment status and actor records”.

D:

“Inspect supported syslog configuration, transport reachability and receiving collector parsing” is associated with a distinct issue: A data center runs a centralized SOC and requests appliance event forwarding without sharing administrator credentials. By contrast, the actual problem is: A new rack is partially configured and the change ticket lacks a clear record of who initiated its commit. The relevant inspection is: Review the event timeline, blueprint commit notes, deployment status and actor records. The most discriminating first check is “Review the event timeline, blueprint commit notes, deployment status and actor records”.

Question 149

A rack type requests a 100G leaf uplink but the selected switch's physical port profile only exposes that interface as four 25G breakout channels. Which shortcut would be most likely to undermine this objective?

  1. Disable interface conflict checks rather than correcting the physical resource plan.
  2. Force a 100G logical port onto unsupported breakout lanes and rely on autonegotiation to fix the design.
  3. Copy port names from a different hardware platform without checking physical assignments.
  4. Assume the logical device automatically creates additional physical interfaces on undersized hardware.

Explanation

Correct Answer

B:

This is the unsafe shortcut to avoid: force a 100G logical port onto unsupported breakout lanes and rely on autonegotiation to fix the design. It violates the principle that interface maps and device profiles define which supported physical ports and speeds satisfy logical device connectivity. An appropriate alternative is to choose a compatible interface map or adjust the approved breakout and device profile.

Incorrect Answers

A:

“Disable interface conflict checks rather than correcting the physical resource plan” is associated with a distinct issue: A fabric build fails because one interface was assigned to both an uplink and a server-facing logical port. By contrast, the actual problem is: A rack type requests a 100G leaf uplink but the selected switch's physical port profile only exposes that interface as four 25G breakout channels. Interface maps and device profiles define which supported physical ports and speeds satisfy logical device connectivity. The directly relevant unsafe shortcut is “Force a 100G logical port onto unsupported breakout lanes and rely on autonegotiation to fix the design”.

C:

“Copy port names from a different hardware platform without checking physical assignments” is relevant to a different condition: A data center expansion reuses a logical device definition on a switch with a distinct interface numbering scheme. The stated question instead concerns: A rack type requests a 100G leaf uplink but the selected switch's physical port profile only exposes that interface as four 25G breakout channels. Interface maps and device profiles define which supported physical ports and speeds satisfy logical device connectivity. The directly relevant unsafe shortcut is “Force a 100G logical port onto unsupported breakout lanes and rely on autonegotiation to fix the design”.

D:

That choice—“Assume the logical device automatically creates additional physical interfaces on undersized hardware”—addresses this other problem: A site models 48 server attachments using a logical device profile that exposes only 32 suitable host interfaces. Here the scenario is: A rack type requests a 100G leaf uplink but the selected switch's physical port profile only exposes that interface as four 25G breakout channels. Interface maps and device profiles define which supported physical ports and speeds satisfy logical device connectivity. The directly relevant unsafe shortcut is “Force a 100G logical port onto unsupported breakout lanes and rely on autonegotiation to fix the design”.

Question 150

A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. Which initial check would most directly distinguish the likely cause?

  1. Inspect underlay routing adjacency, interface addressing and reachability to the spine or leaf loopback endpoints.
  2. Inspect routing tables and underlay advertisements for each intended VTEP address.
  3. Check interface state, routing convergence and forwarding entries following the simulated spine-link loss.
  4. Compare the proposed physical topology with the selected reference design and expected leaf-spine connectivity.

Explanation

Correct Answer

A:

This checks the relevant evidence first: inspect underlay routing adjacency, interface addressing and reachability to the spine or leaf loopback endpoints. The underlying concept is that an IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly. After confirming the finding, a controlled remediation is to repair the routed underlay addressing or protocol configuration and then validate overlay sessions.

Incorrect Answers

B:

“Inspect routing tables and underlay advertisements for each intended VTEP address” is associated with a distinct issue: A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. 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. The relevant inspection is: Inspect underlay routing adjacency, interface addressing and reachability to the spine or leaf loopback endpoints. The most discriminating first check is “Inspect underlay routing adjacency, interface addressing and reachability to the spine or leaf loopback endpoints”.

C:

The option “Check interface state, routing convergence and forwarding entries following the simulated spine-link loss” is useful in a different setting: A fabric uses two equal-cost underlay next hops yet packets continue toward a failed path following a port outage. 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. The relevant inspection is: Inspect underlay routing adjacency, interface addressing and reachability to the spine or leaf loopback endpoints. The most discriminating first check is “Inspect underlay routing adjacency, interface addressing and reachability to the spine or leaf loopback endpoints”.

D:

“Compare the proposed physical topology with the selected reference design and expected leaf-spine connectivity” 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. The relevant inspection is: Inspect underlay routing adjacency, interface addressing and reachability to the spine or leaf loopback endpoints. The most discriminating first check is “Inspect underlay routing adjacency, interface addressing and reachability to the spine or leaf loopback endpoints”.

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