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 56

Question 550

An operator needs to explain who committed a change after a rack lost connectivity overnight. Which controlled change best addresses the described requirement?

  1. Document the causal change and correct the failed deployment through an auditable workflow.
  2. Preserve audit records and review the specific committed change before a controlled correction.
  3. Configure a supported protected syslog destination with the required log categories and retention policy.
  4. Restore data collection and mark stale measurements as unknown rather than healthy.

Explanation

Correct Answer

B:

This action addresses the stated defect: preserve audit records and review the specific committed change before a controlled correction. The underlying constraint is that Apstra event and audit records provide change accountability distinct from raw packet telemetry. Verify rather than assume success: produce a traceable operator or automation event associated with the observed revision and change window.

Incorrect Answers

A:

That choice—“Document the causal change and correct the failed deployment through an auditable workflow”—addresses this other problem: A new rack is partially configured and the change ticket lacks a clear record of who initiated its commit. Here the scenario is: An operator needs to explain who committed a change after a rack lost connectivity overnight. Preserve audit records and review the specific committed change before a controlled correction. The most relevant correction is “Preserve audit records and review the specific committed change before a controlled correction”.

C:

The option “Configure a supported protected syslog destination with the required log categories and retention policy” is useful in a different setting: A security team needs Apstra events delivered to its central log monitoring platform for long-term investigation. The case being tested is: An operator needs to explain who committed a change after a rack lost connectivity overnight. Preserve audit records and review the specific committed change before a controlled correction. The most relevant correction is “Preserve audit records and review the specific committed change before a controlled correction”.

D:

“Restore data collection and mark stale measurements as unknown rather than healthy” is relevant to a different condition: An Apstra operator sees no current alerts after a telemetry collector became unreachable. The stated question instead concerns: An operator needs to explain who committed a change after a rack lost connectivity overnight. Preserve audit records and review the specific committed change before a controlled correction. The most relevant correction is “Preserve audit records and review the specific committed change before a controlled correction”.

Question 551

A built-in analytics probe reports a metric but cannot identify why the value changed after a rack migration. Which controlled change best addresses the described requirement?

  1. Configure an approved probe or probe-stage threshold for the scoped leaf group and validate its data collection.
  2. Narrow the query and probe stages to the correct blueprint nodes and monitored metrics.
  3. Configure the supported aggregation and alert conditions with documented baseline behavior.
  4. Correlate the observed metrics with topology and tune or remediate the validated underlying condition.

Explanation

Correct Answer

B:

This action addresses the stated defect: narrow the query and probe stages to the correct blueprint nodes and monitored metrics. The underlying constraint is that an IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope. Verify rather than assume success: confirm only the intended rack or tenant objects generate results and anomalies on repeat tests.

Incorrect Answers

A:

“Configure an approved probe or probe-stage threshold for the scoped leaf group and validate its data collection” is relevant to a different condition: A monitoring team wants to detect rising discards on the uplinks of one specific leaf group. The stated question instead concerns: A built-in analytics probe reports a metric but cannot identify why the value changed after a rack migration. Narrow the query and probe stages to the correct blueprint nodes and monitored metrics. The most relevant correction is “Narrow the query and probe stages to the correct blueprint nodes and monitored metrics”.

C:

“Configure the supported aggregation and alert conditions with documented baseline behavior” is associated with a distinct issue: A team wants an analytics alert if interface utilization deviates from baseline while still retaining raw evidence. By contrast, the actual problem is: A built-in analytics probe reports a metric but cannot identify why the value changed after a rack migration. Narrow the query and probe stages to the correct blueprint nodes and monitored metrics. The most relevant correction is “Narrow the query and probe stages to the correct blueprint nodes and monitored metrics”.

D:

The option “Correlate the observed metrics with topology and tune or remediate the validated underlying condition” is useful in a different setting: An IBA probe reports intermittent latency spikes but application errors are not visible in basic device health summaries. The case being tested is: A built-in analytics probe reports a metric but cannot identify why the value changed after a rack migration. Narrow the query and probe stages to the correct blueprint nodes and monitored metrics. The most relevant correction is “Narrow the query and probe stages to the correct blueprint nodes and monitored metrics”.

Question 552

A design template was edited after the first rack was built and an engineer assumes existing active blueprints are retroactively rewritten. Which evidence most directly verifies the intended network outcome?

  1. Confirm the modeled external links and routing connectivity satisfy the acceptance topology.
  2. Confirm each targeted blueprint reflects the expected revision and existing production services remain healthy.
  3. Confirm the blueprint build validation clears and expected rendered configurations are available for review.
  4. Verify syntax validation and successful controlled deployment to representative supported devices.

Explanation

Correct Answer

B:

This directly tests the desired result: confirm each targeted blueprint reflects the expected revision and existing production services remain healthy. The decisive investigation is to compare the referenced template version and current active blueprint state before propagating design changes. The governing principle is that blueprint design inheritance and change management must be validated; editing a design object does not prove all deployed fabrics changed.

Incorrect Answers

A:

The option “Confirm the modeled external links and routing connectivity satisfy the acceptance topology” is useful in a different setting: An engineer finishes a fabric template without any modeled north-south peering attachment points. The case being tested is: A design template was edited after the first rack was built and an engineer assumes existing active blueprints are retroactively rewritten. Blueprint design inheritance and change management must be validated; editing a design object does not prove all deployed fabrics changed. The direct acceptance evidence is “Confirm each targeted blueprint reflects the expected revision and existing production services remain healthy”.

C:

That choice—“Confirm the blueprint build validation clears and expected rendered configurations are available for review”—addresses this other problem: An Apstra designer tries to deploy a rack without allocating required underlay interface and IP pools. Here the scenario is: A design template was edited after the first rack was built and an engineer assumes existing active blueprints are retroactively rewritten. Blueprint design inheritance and change management must be validated; editing a design object does not prove all deployed fabrics changed. The direct acceptance evidence is “Confirm each targeted blueprint reflects the expected revision and existing production services remain healthy”.

D:

“Verify syntax validation and successful controlled deployment to representative supported devices” is associated with a distinct issue: A team assigns a device image and platform combination not supported by the chosen Apstra reference design. By contrast, the actual problem is: A design template was edited after the first rack was built and an engineer assumes existing active blueprints are retroactively rewritten. Blueprint design inheritance and change management must be validated; editing a design object does not prove all deployed fabrics changed. The direct acceptance evidence is “Confirm each targeted blueprint reflects the expected revision and existing production services remain healthy”.

Question 553

An operator has valuable staged changes when another administrator proposes jumping to an older blueprint revision. Which design or operational principle best explains this behavior?

  1. A Time Voyager rollback can discard current uncommitted staging and must be coordinated with change owners.
  2. Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory.
  3. Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision.
  4. Apstra Time Voyager supports controlled movement to retained blueprint revisions, subject to compatibility and staged-change constraints.

Explanation

Correct Answer

A:

a Time Voyager rollback can discard current uncommitted staging and must be coordinated with change owners. Here, an operator has valuable staged changes when another administrator proposes jumping to an older blueprint revision. A useful discriminating check is to inspect and preserve or commit required pending modifications before initiating a revision jump.

Incorrect Answers

B:

The option “Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory” is useful in a different setting: A historical revision would restore a system ID that has been reassigned to another device since it was first recorded. The case being tested is: An operator has valuable staged changes when another administrator proposes jumping to an older blueprint revision. A Time Voyager rollback can discard current uncommitted staging and must be coordinated with change owners. The controlling principle is “A Time Voyager rollback can discard current uncommitted staging and must be coordinated with change owners”.

C:

“Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision” is relevant to a different condition: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. The stated question instead concerns: An operator has valuable staged changes when another administrator proposes jumping to an older blueprint revision. A Time Voyager rollback can discard current uncommitted staging and must be coordinated with change owners. The controlling principle is “A Time Voyager rollback can discard current uncommitted staging and must be coordinated with change owners”.

D:

That choice—“Apstra Time Voyager supports controlled movement to retained blueprint revisions, subject to compatibility and staged-change constraints”—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: An operator has valuable staged changes when another administrator proposes jumping to an older blueprint revision. A Time Voyager rollback can discard current uncommitted staging and must be coordinated with change owners. The controlling principle is “A Time Voyager rollback can discard current uncommitted staging and must be coordinated with change owners”.

Question 554

A team wants to reuse the same approved DNS and NTP settings across multiple racks without editing every switch individually. Which design or operational principle best explains this behavior?

  1. Configlets can extend generated device configuration through controlled, scoped supplemental configuration.
  2. Apstra property sets can centralize reusable named parameters referenced by supported configuration templates.
  3. Configlet applicability must be scoped precisely to affected devices and interfaces.
  4. Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision.

Explanation

Correct Answer

B:

Apstra property sets can centralize reusable named parameters referenced by supported configuration templates. Here, a team wants to reuse the same approved DNS and NTP settings across multiple racks without editing every switch individually. A useful discriminating check is to inspect property-set values, consumers and intended scope before updating a shared parameter.

Incorrect Answers

A:

That choice—“Configlets can extend generated device configuration through controlled, scoped supplemental configuration”—addresses this other problem: An application requires a supported vendor-specific setting absent from the blueprint's default rendered commands. Here the scenario is: A team wants to reuse the same approved DNS and NTP settings across multiple racks without editing every switch individually. Apstra property sets can centralize reusable named parameters referenced by supported configuration templates. The controlling principle is “Apstra property sets can centralize reusable named parameters referenced by supported configuration templates”.

C:

The option “Configlet applicability must be scoped precisely to affected devices and interfaces” is useful in a different setting: An engineer discovers that a supplemental configuration template was bound to an overly broad tag. The case being tested is: A team wants to reuse the same approved DNS and NTP settings across multiple racks without editing every switch individually. Apstra property sets can centralize reusable named parameters referenced by supported configuration templates. The controlling principle is “Apstra property sets can centralize reusable named parameters referenced by supported configuration templates”.

D:

“Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision” is relevant to a different condition: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. The stated question instead concerns: A team wants to reuse the same approved DNS and NTP settings across multiple racks without editing every switch individually. Apstra property sets can centralize reusable named parameters referenced by supported configuration templates. The controlling principle is “Apstra property sets can centralize reusable named parameters referenced by supported configuration templates”.

Question 555

An EVPN network learns a host MAC address and associated IP binding from a remote VTEP. Which shortcut would be most likely to undermine this objective?

  1. Try to solve missing host MAC advertisements solely by creating unrelated Type 5 subnet prefixes.
  2. Assume Type 2 MAC advertisements alone always provide every external routed subnet.
  3. Treat the two legs of a multihomed Ethernet segment as unrelated unmanaged single-homed endpoints.
  4. Disable tenant-specific route import controls globally as a quick way to make MAC routes appear.

Explanation

Correct Answer

A:

This is the unsafe shortcut to avoid: try to solve missing host MAC advertisements solely by creating unrelated Type 5 subnet prefixes. It violates the principle that EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning. An appropriate alternative is to repair EVPN endpoint advertisement and import eligibility for the affected virtual network.

Incorrect Answers

B:

That choice—“Assume Type 2 MAC advertisements alone always provide every external routed subnet”—addresses this other problem: A fabric exchanges IP prefixes between tenant routing zones without requiring every remote subnet to be represented as an individual MAC. Here the scenario is: An EVPN network learns a host MAC address and associated IP binding from a remote VTEP. EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning. The directly relevant unsafe shortcut is “Try to solve missing host MAC advertisements solely by creating unrelated Type 5 subnet prefixes”.

C:

“Treat the two legs of a multihomed Ethernet segment as unrelated unmanaged single-homed endpoints” is associated with a distinct issue: An EVPN multihomed endpoint exhibits unstable forwarding after both attachment leafs advertise the same segment independently. By contrast, the actual problem is: An EVPN network learns a host MAC address and associated IP binding from a remote VTEP. EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning. The directly relevant unsafe shortcut is “Try to solve missing host MAC advertisements solely by creating unrelated Type 5 subnet prefixes”.

D:

The option “Disable tenant-specific route import controls globally as a quick way to make MAC routes appear” is useful in a different setting: A server VLAN is created on two racks but remote EVPN routes cannot be imported because their route targets do not align. The case being tested is: An EVPN network learns a host MAC address and associated IP binding from a remote VTEP. EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning. The directly relevant unsafe shortcut is “Try to solve missing host MAC advertisements solely by creating unrelated Type 5 subnet prefixes”.

Question 556

A data center offers centralized DNS across isolated customers while requiring strict east-west access boundaries. Which shortcut would be most likely to undermine this objective?

  1. Leak all tenant routes into one global routing table because only one shared DNS server is needed.
  2. Treat the interconnect as a trunk carrying all tenant networks with no import controls.
  3. Assume the virtualization manager's displayed port-group name automatically configures leaf networking.
  4. Enable unrestricted route redistribution for every tenant to make a single external peering session work.

Explanation

Correct Answer

A:

This is the unsafe shortcut to avoid: leak all tenant routes into one global routing table because only one shared DNS server is needed. It violates the principle that shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation. An appropriate alternative is to create a controlled service insertion or external routing policy permitting only approved shared-service prefixes.

Incorrect Answers

B:

“Treat the interconnect as a trunk carrying all tenant networks with no import controls” is relevant to a different condition: A multiregion deployment needs to preserve tenant boundaries while propagating specific data center routes across a DCI. The stated question instead concerns: 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 directly relevant unsafe shortcut is “Leak all tenant routes into one global routing table because only one shared DNS server is needed”.

C:

That choice—“Assume the virtualization manager's displayed port-group name automatically configures leaf networking”—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 directly relevant unsafe shortcut is “Leak all tenant routes into one global routing table because only one shared DNS server is needed”.

D:

“Enable unrestricted route redistribution for every tenant to make a single external peering session work” is associated with a distinct issue: A routed external firewall must exchange routes with a border leaf for only one tenant VRF. 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 directly relevant unsafe shortcut is “Leak all tenant routes into one global routing table because only one shared DNS server is needed”.

Question 557

A dual leaf rack is expected to provide application diversity but both uplinks terminate on the same physical spine. Which design or operational principle best explains this behavior?

  1. Total spine capacity includes available physical ports and supported link-speed and topology constraints.
  2. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required.
  3. Rack type and leaf selection must support the intended redundant attachment topology and host interface roles.
  4. Rack types are reusable logical patterns for leaf topology and attached systems within a blueprint.

Explanation

Correct Answer

B:

physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. Here, a dual leaf rack is expected to provide application diversity but both uplinks terminate on the same physical spine. A useful discriminating check is to inspect the rack type's expected spine attachment graph and actual cable endpoints.

Incorrect Answers

A:

“Total spine capacity includes available physical ports and supported link-speed and topology constraints” is associated with a distinct issue: A planned rack addition fails because the spine layer has no compatible free ports at the required link speed. By contrast, the actual problem is: A dual leaf rack is expected to provide application diversity but both uplinks terminate on the same physical spine. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. The controlling principle is “Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required”.

C:

“Rack type and leaf selection must support the intended redundant attachment topology and host interface roles” is relevant to a different condition: A storage workload requires dual-homed servers but a proposed rack type provides only one access leaf. The stated question instead concerns: A dual leaf rack is expected to provide application diversity but both uplinks terminate on the same physical spine. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. The controlling principle is “Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required”.

D:

That choice—“Rack types are reusable logical patterns for leaf topology and attached systems within a blueprint”—addresses this other problem: An Apstra design must deploy 12 racks with uniform leaf roles and uplink constraints. Here the scenario is: A dual leaf rack is expected to provide application diversity but both uplinks terminate on the same physical spine. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. The controlling principle is “Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required”.

Question 558

An automation wants to select switches tagged with a particular site and deployment tier. Which design or operational principle best explains this behavior?

  1. Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity.
  2. Logical device definitions represent required interface roles and capacities, independent of hardware SKU details.
  3. Managed VNI and other logical resource pools reduce collision risk when correctly partitioned and allocated.
  4. Resource pools need sufficient unique allocations for loopback, fabric subnet and other network identifiers.

Explanation

Correct Answer

A:

Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity. Here, an automation wants to select switches tagged with a particular site and deployment tier. A useful discriminating check is to inspect object tags and query results before selecting the intended device set.

Incorrect Answers

B:

“Logical device definitions represent required interface roles and capacities, independent of hardware SKU details” is associated with a distinct issue: A site models 48 server attachments using a logical device profile that exposes only 32 suitable host interfaces. By contrast, the actual problem is: An automation wants to select switches tagged with a particular site and deployment tier. Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity. The controlling principle is “Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity”.

C:

The option “Managed VNI and other logical resource pools reduce collision risk when correctly partitioned and allocated” is useful in a different setting: An expansion accidentally reuses a virtual network identifier assigned to another isolated overlay segment. The case being tested is: An automation wants to select switches tagged with a particular site and deployment tier. Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity. The controlling principle is “Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity”.

D:

“Resource pools need sufficient unique allocations for loopback, fabric subnet and other network identifiers” is relevant to a different condition: An Apstra design runs out of loopback addresses when adding an additional leaf group. The stated question instead concerns: An automation wants to select switches tagged with a particular site and deployment tier. Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity. The controlling principle is “Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity”.

Question 559

A new operations account can open the Apstra UI yet receives authorization errors when trying to manage device blueprints. Which evidence most directly verifies the intended network outcome?

  1. Confirm intended and running configurations are consistent and the fabric's critical paths remain operational.
  2. Confirm the account performs only its assigned blueprint tasks and unauthorized functions remain denied.
  3. Confirm the server receives fresh device state and reconciles inventory and blueprint expectations.
  4. Prove the switch joins managed inventory and supports required rendered configuration under the selected blueprint.

Explanation

Correct Answer

B:

This directly tests the desired result: confirm the account performs only its assigned blueprint tasks and unauthorized functions remain denied. The decisive investigation is to inspect the user's role assignments and denied operation in the Apstra access and audit records. The governing principle is that Apstra role-based access control separates read visibility from permissions to change managed fabric objects.

Incorrect Answers

A:

“Confirm intended and running configurations are consistent and the fabric's critical paths remain operational” is relevant to a different condition: An operations team recovers a backup of the controller taken before the most recent fabric changes. The stated question instead concerns: A new operations account can open the Apstra UI yet receives authorization errors when trying to manage device blueprints. Apstra role-based access control separates read visibility from permissions to change managed fabric objects. The direct acceptance evidence is “Confirm the account performs only its assigned blueprint tasks and unauthorized functions remain denied”.

C:

“Confirm the server receives fresh device state and reconciles inventory and blueprint expectations” is associated with a distinct issue: A control-plane service is healthy yet one switch disappears from the Apstra device inventory after a management-network change. By contrast, the actual problem is: A new operations account can open the Apstra UI yet receives authorization errors when trying to manage device blueprints. Apstra role-based access control separates read visibility from permissions to change managed fabric objects. The direct acceptance evidence is “Confirm the account performs only its assigned blueprint tasks and unauthorized functions remain denied”.

D:

The option “Prove the switch joins managed inventory and supports required rendered configuration under the selected blueprint” is useful in a different setting: A new leaf model arrives with an unsupported operating-system image while the Apstra server still shows available inventory capacity. The case being tested is: A new operations account can open the Apstra UI yet receives authorization errors when trying to manage device blueprints. Apstra role-based access control separates read visibility from permissions to change managed fabric objects. The direct acceptance evidence is “Confirm the account performs only its assigned blueprint tasks and unauthorized functions remain denied”.

Question 560

A fabric uses two equal-cost underlay next hops yet packets continue toward a failed path following a port outage. Which initial check would most directly distinguish the likely cause?

  1. Inspect installed ECMP next hops and compare per-link counters across multiple distinct flows.
  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. Inspect underlay routing adjacency, interface addressing and reachability to the spine or leaf loopback endpoints.

Explanation

Correct Answer

C:

This checks the relevant evidence first: check interface state, routing convergence and forwarding entries following the simulated spine-link loss. The underlying concept is that path redundancy only improves availability when failed underlay next hops are withdrawn or detected promptly. After confirming the finding, a controlled remediation is to correct underlay failure detection and routing convergence within the approved topology and timer policy.

Incorrect Answers

A:

The option “Inspect installed ECMP next hops and compare per-link counters across multiple distinct flows” is useful in a different setting: An operator finds two equal-cost fabric paths but a single large traffic flow consistently traverses only one link. The case being tested is: A fabric uses two equal-cost underlay next hops yet packets continue toward a failed path following a port outage. The relevant inspection is: Check interface state, routing convergence and forwarding entries following the simulated spine-link loss. The most discriminating first check is “Check interface state, routing convergence and forwarding entries following the simulated spine-link loss”.

B:

“Inspect routing tables and underlay advertisements for each intended VTEP address” is relevant to a different condition: A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. The stated question instead concerns: A fabric uses two equal-cost underlay next hops yet packets continue toward a failed path following a port outage. The relevant inspection is: Check interface state, routing convergence and forwarding entries following the simulated spine-link loss. The most discriminating first check is “Check interface state, routing convergence and forwarding entries following the simulated spine-link loss”.

D:

“Inspect underlay routing adjacency, interface addressing and reachability to the spine or leaf loopback endpoints” is associated with a distinct issue: A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. By contrast, the actual problem is: A fabric uses two equal-cost underlay next hops yet packets continue toward a failed path following a port outage. The relevant inspection is: Check interface state, routing convergence and forwarding entries following the simulated spine-link loss. The most discriminating first check is “Check interface state, routing convergence and forwarding entries following the simulated spine-link loss”.

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