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 84

Question 830

A security team needs Apstra events delivered to its central log monitoring platform for long-term investigation. Which initial check would most directly distinguish the likely cause?

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

Explanation

Correct Answer

C:

This checks the relevant evidence first: inspect supported syslog configuration, transport reachability and receiving collector parsing. The underlying concept is that syslog forwarding can export relevant controller and device operational events for independent correlation and retention. After confirming the finding, a controlled remediation is to configure a supported protected syslog destination with the required log categories and retention policy.

Incorrect Answers

A:

That choice—“Review the event timeline, blueprint commit notes, deployment status and actor records”—addresses this other problem: A team needs to identify whether a failed deployment arose from system automation or an approved human change. Here the scenario is: A security team needs Apstra events delivered to its central log monitoring platform for long-term investigation. The relevant inspection is: Inspect supported syslog configuration, transport reachability and receiving collector parsing. The most discriminating first check is “Inspect supported syslog configuration, transport reachability and receiving collector parsing”.

B:

“Check collector or agent timestamps, sample rates and ingestion connectivity before trusting status” is associated with a distinct issue: A monitoring dashboard shows a device as green but telemetry timestamps stopped updating 20 minutes earlier. By contrast, the actual problem is: A security team needs Apstra events delivered to its central log monitoring platform for long-term investigation. The relevant inspection is: Inspect supported syslog configuration, transport reachability and receiving collector parsing. The most discriminating first check is “Inspect supported syslog configuration, transport reachability and receiving collector parsing”.

D:

“Correlate blueprint revision history, actor identity and event logs around the failure timestamp” is relevant to a different condition: A team investigates whether a blueprint revision was created by automation or by an administrator. The stated question instead concerns: A security team needs Apstra events delivered to its central log monitoring platform for long-term investigation. The relevant inspection is: Inspect supported syslog configuration, transport reachability and receiving collector parsing. The most discriminating first check is “Inspect supported syslog configuration, transport reachability and receiving collector parsing”.

Question 831

A monitoring dashboard shows a device as green but telemetry timestamps stopped updating 20 minutes earlier. Which evidence most directly verifies the intended network outcome?

  1. Confirm timestamped Apstra events arrive at the collector and retain source attribution.
  2. Produce a traceable operator or automation event associated with the observed revision and change window.
  3. Confirm logs identify the affected blueprint revision, device and operator or automation identity.
  4. Verify current samples arrive and synthetic test conditions create expected alarms.

Explanation

Correct Answer

D:

This directly tests the desired result: verify current samples arrive and synthetic test conditions create expected alarms. The decisive investigation is to check collector or agent timestamps, sample rates and ingestion connectivity before trusting status. The governing principle is that monitoring conclusions depend on fresh telemetry, so absence of alarms is not proof of healthy collection.

Incorrect Answers

A:

“Confirm timestamped Apstra events arrive at the collector and retain source attribution” is relevant to a different condition: A security team needs Apstra events delivered to its central log monitoring platform for long-term investigation. The stated question instead concerns: A monitoring dashboard shows a device as green but telemetry timestamps stopped updating 20 minutes earlier. Monitoring conclusions depend on fresh telemetry, so absence of alarms is not proof of healthy collection. The direct acceptance evidence is “Verify current samples arrive and synthetic test conditions create expected alarms”.

B:

That choice—“Produce a traceable operator or automation event associated with the observed revision and change window”—addresses this other problem: An operator needs to explain who committed a change after a rack lost connectivity overnight. Here the scenario is: A monitoring dashboard shows a device as green but telemetry timestamps stopped updating 20 minutes earlier. Monitoring conclusions depend on fresh telemetry, so absence of alarms is not proof of healthy collection. The direct acceptance evidence is “Verify current samples arrive and synthetic test conditions create expected alarms”.

C:

“Confirm logs identify the affected blueprint revision, device and operator or automation identity” is associated with a distinct issue: A team needs to identify whether a failed deployment arose from system automation or an approved human change. By contrast, the actual problem is: A monitoring dashboard shows a device as green but telemetry timestamps stopped updating 20 minutes earlier. Monitoring conclusions depend on fresh telemetry, so absence of alarms is not proof of healthy collection. The direct acceptance evidence is “Verify current samples arrive and synthetic test conditions create expected alarms”.

Question 832

A VXLAN packet encapsulation crosses a routed fabric but is discarded along the path due to frame size. Which shortcut would be most likely to undermine this objective?

  1. Disable the EVPN control plane and assume every remote endpoint is learned optimally from normal TCP traffic.
  2. Assume the underlay can carry the original maximum Ethernet frame unchanged after VXLAN headers are added.
  3. Replace the tenant VLAN ID repeatedly without checking VXLAN endpoint reachability.
  4. Map every rack's VLAN 210 to an arbitrary shared VNI without checking tenant boundaries.

Explanation

Correct Answer

B:

This is the unsafe shortcut to avoid: assume the underlay can carry the original maximum Ethernet frame unchanged after VXLAN headers are added. It violates the principle that VXLAN adds encapsulation overhead and requires adequate path MTU or effective payload sizing. An appropriate alternative is to configure sufficient supported underlay MTU along the fabric path or safely adjust payload MTU.

Incorrect Answers

A:

The option “Disable the EVPN control plane and assume every remote endpoint is learned optimally from normal TCP traffic” is useful in a different setting: An architect compares an EVPN control plane with reliance on data-plane flood-and-learn for VXLAN workloads. The case being tested is: A VXLAN packet encapsulation crosses a routed fabric but is discarded along the path due to frame size. VXLAN adds encapsulation overhead and requires adequate path MTU or effective payload sizing. The directly relevant unsafe shortcut is “Assume the underlay can carry the original maximum Ethernet frame unchanged after VXLAN headers are added”.

C:

That choice—“Replace the tenant VLAN ID repeatedly without checking VXLAN endpoint reachability”—addresses this other problem: A virtualization cluster is moved to another rack and its EVPN routes exist but the remote VXLAN encapsulation next hop fails. Here the scenario is: A VXLAN packet encapsulation crosses a routed fabric but is discarded along the path due to frame size. VXLAN adds encapsulation overhead and requires adequate path MTU or effective payload sizing. The directly relevant unsafe shortcut is “Assume the underlay can carry the original maximum Ethernet frame unchanged after VXLAN headers are added”.

D:

“Map every rack's VLAN 210 to an arbitrary shared VNI without checking tenant boundaries” is associated with a distinct issue: A server's VLAN 210 is accidentally bound to the wrong VXLAN segment on one leaf. By contrast, the actual problem is: A VXLAN packet encapsulation crosses a routed fabric but is discarded along the path due to frame size. VXLAN adds encapsulation overhead and requires adequate path MTU or effective payload sizing. The directly relevant unsafe shortcut is “Assume the underlay can carry the original maximum Ethernet frame unchanged after VXLAN headers are added”.

Question 833

A network engineer views valid proposed changes under Staged and mistakenly assumes all devices were updated. Which evidence most directly verifies the intended network outcome?

  1. Confirm deployed device state matches the resulting active configuration and authorized baseline.
  2. Confirm active intent, device configuration and required network tests agree on the intended result.
  3. Confirm the active revision and target device running configuration reflect the approved change.
  4. Confirm all affected devices converge on the active blueprint revision without config drift.

Explanation

Correct Answer

C:

This directly tests the desired result: confirm the active revision and target device running configuration reflect the approved change. The decisive investigation is to inspect the Staged, Uncommitted and Active states and per-device deployment status. The governing principle is that staging and rendering intended configuration are distinct from committing and deploying the active blueprint.

Incorrect Answers

A:

“Confirm deployed device state matches the resulting active configuration and authorized baseline” is associated with a distinct issue: A new Apstra deployment includes baseline settings, platform-specific changes and generated overlay commands that an engineer wants to distinguish. By contrast, the actual problem is: A network engineer views valid proposed changes under Staged and mistakenly assumes all devices were updated. Staging and rendering intended configuration are distinct from committing and deploying the active blueprint. The direct acceptance evidence is “Confirm the active revision and target device running configuration reflect the approved change”.

B:

The option “Confirm active intent, device configuration and required network tests agree on the intended result” is useful in a different setting: A team needs to roll out a fabric change safely but its change record mixes staging a modification with committing the active state. The case being tested is: A network engineer views valid proposed changes under Staged and mistakenly assumes all devices were updated. Staging and rendering intended configuration are distinct from committing and deploying the active blueprint. The direct acceptance evidence is “Confirm the active revision and target device running configuration reflect the approved change”.

D:

That choice—“Confirm all affected devices converge on the active blueprint revision without config drift”—addresses this other problem: An operator sees devices in mixed managed states and cannot tell which switches received the new active configuration. Here the scenario is: A network engineer views valid proposed changes under Staged and mistakenly assumes all devices were updated. Staging and rendering intended configuration are distinct from committing and deploying the active blueprint. The direct acceptance evidence is “Confirm the active revision and target device running configuration reflect the approved change”.

Question 834

An engineer wants to return to a blueprint commit created before several resource pool and hardware changes. Which initial check would most directly distinguish the likely cause?

  1. Inspect available retained revisions, current uncommitted changes and the revision's applicability to present devices.
  2. Inspect historical identifiers, resource assignments, device availability and supported rollback constraints.
  3. Inspect and preserve or commit required pending modifications before initiating a revision jump.
  4. Determine whether the unwanted modification exists only in Staged or in the Active revision.

Explanation

Correct Answer

B:

This checks the relevant evidence first: inspect historical identifiers, resource assignments, device availability and supported rollback constraints. The underlying concept is that Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory. After confirming the finding, a controlled remediation is to resolve conflicting device and resource mappings before committing a controlled rollback.

Incorrect Answers

A:

That choice—“Inspect available retained revisions, current uncommitted changes and the revision's applicability to present devices”—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 engineer wants to return to a blueprint commit created before several resource pool and hardware changes. The relevant inspection is: Inspect historical identifiers, resource assignments, device availability and supported rollback constraints. The most discriminating first check is “Inspect historical identifiers, resource assignments, device availability and supported rollback constraints”.

C:

The option “Inspect and preserve or commit required pending modifications before initiating a revision jump” 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: An engineer wants to return to a blueprint commit created before several resource pool and hardware changes. The relevant inspection is: Inspect historical identifiers, resource assignments, device availability and supported rollback constraints. The most discriminating first check is “Inspect historical identifiers, resource assignments, device availability and supported rollback constraints”.

D:

“Determine whether the unwanted modification exists only in Staged or in the Active revision” is relevant to a different condition: A designer notices an accidental rack parameter change before any blueprint commit has occurred. The stated question instead concerns: An engineer wants to return to a blueprint commit created before several resource pool and hardware changes. The relevant inspection is: Inspect historical identifiers, resource assignments, device availability and supported rollback constraints. The most discriminating first check is “Inspect historical identifiers, resource assignments, device availability and supported rollback constraints”.

Question 835

A replacement leaf has a new serial number, but the blueprint still associates the old unavailable hardware with its logical role. Which evidence most directly verifies the intended network outcome?

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

Explanation

Correct Answer

A:

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

B:

That choice—“Confirm each device has one accurate unique inventory record and intended blueprint role”—addresses this other problem: Two appliances appear as one managed system after inventory import because their identifiers were copied from a template. Here the scenario is: A replacement leaf has a new serial number, but the blueprint still associates the old unavailable hardware with its logical role. 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 device appears healthy, available and uniquely identified for blueprint assignment” is associated with a distinct issue: A new QFX leaf responds to management pings while the Apstra device manager reports no valid agent identity. By contrast, the actual problem is: A replacement leaf has a new serial number, but the blueprint still associates the old unavailable hardware with its logical role. 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”.

D:

The option “Confirm the active revision and target device running configuration reflect the approved change” is useful in a different setting: A design is staged and rendered correctly, but a production switch still uses the previous running configuration. The case being tested is: A replacement leaf has a new serial number, but the blueprint still associates the old unavailable hardware with its logical role. 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 836

A leaf needs to advertise a workload endpoint location to remote EVPN participants across the VXLAN fabric. Which controlled change best addresses the described requirement?

  1. Correct the intended route target mapping and import policies while preserving tenant isolation.
  2. Correct prefix export/import and next-hop resolution for the routed EVPN IP prefix.
  3. Align approved Ethernet segment and multihoming configuration on the participating leaf devices.
  4. Repair EVPN endpoint advertisement and import eligibility for the affected virtual network.

Explanation

Correct Answer

D:

This action addresses the stated defect: repair EVPN endpoint advertisement and import eligibility for the affected virtual network. The underlying constraint is that EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning. Verify rather than assume success: confirm the remote VTEP has a correctly imported Type 2 endpoint route and can deliver host traffic.

Incorrect Answers

A:

The option “Correct the intended route target mapping and import policies while preserving tenant isolation” 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: A leaf needs to advertise a workload endpoint location to remote EVPN participants across the VXLAN fabric. Repair EVPN endpoint advertisement and import eligibility for the affected virtual network. The most relevant correction is “Repair EVPN endpoint advertisement and import eligibility for the affected virtual network”.

B:

“Correct prefix export/import and next-hop resolution for the routed EVPN IP prefix” is relevant to a different condition: A fabric exchanges IP prefixes between tenant routing zones without requiring every remote subnet to be represented as an individual MAC. The stated question instead concerns: A leaf needs to advertise a workload endpoint location to remote EVPN participants across the VXLAN fabric. Repair EVPN endpoint advertisement and import eligibility for the affected virtual network. The most relevant correction is “Repair EVPN endpoint advertisement and import eligibility for the affected virtual network”.

C:

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: A leaf needs to advertise a workload endpoint location to remote EVPN participants across the VXLAN fabric. Repair EVPN endpoint advertisement and import eligibility for the affected virtual network. The most relevant correction is “Repair EVPN endpoint advertisement and import eligibility for the affected virtual network”.

Question 837

A two-spine fabric can tolerate one path failure but the application sees blackholing for several minutes after a spine uplink drops. Which controlled change best addresses the described requirement?

  1. Validate resilient ECMP and, if required, test multiple flows or adjust workload distribution within approved designs.
  2. Advertise the approved VTEP loopbacks through the fabric underlay and check next-hop reachability.
  3. Correct underlay failure detection and routing convergence within the approved topology and timer policy.
  4. Use validated spine-leaf cabling and routing relationships rather than ad hoc lateral transit links.

Explanation

Correct Answer

C:

This action addresses the stated defect: correct underlay failure detection and routing convergence within the approved topology and timer policy. The underlying constraint is that path redundancy only improves availability when failed underlay next hops are withdrawn or detected promptly. Verify rather than assume success: prove traffic moves to remaining healthy ECMP next hops within the accepted convergence objective.

Incorrect Answers

A:

“Validate resilient ECMP and, if required, test multiple flows or adjust workload distribution within approved designs” is associated with a distinct issue: A customer asks why adding a second spine path does not necessarily double the rate of one elephant-flow TCP session. By contrast, the actual problem is: A two-spine fabric can tolerate one path failure but the application sees blackholing for several minutes after a spine uplink drops. Correct underlay failure detection and routing convergence within the approved topology and timer policy. The most relevant correction is “Correct underlay failure detection and routing convergence within the approved topology and timer policy”.

B:

The option “Advertise the approved VTEP loopbacks through the fabric underlay and check next-hop reachability” is useful in a different setting: A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. The case being tested is: A two-spine fabric can tolerate one path failure but the application sees blackholing for several minutes after a spine uplink drops. Correct underlay failure detection and routing convergence within the approved topology and timer policy. The most relevant correction is “Correct underlay failure detection and routing convergence within the approved topology and timer policy”.

D:

That choice—“Use validated spine-leaf cabling and routing relationships rather than ad hoc lateral transit links”—addresses this other problem: A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. Here the scenario is: A two-spine fabric can tolerate one path failure but the application sees blackholing for several minutes after a spine uplink drops. Correct underlay failure detection and routing convergence within the approved topology and timer policy. The most relevant correction is “Correct underlay failure detection and routing convergence within the approved topology and timer policy”.

Question 838

An architect compares an EVPN control plane with reliance on data-plane flood-and-learn for VXLAN workloads. Which evidence most directly verifies the intended network outcome?

  1. Measure expected BUM replication only among authorized VTEPs and improved traffic counters.
  2. Confirm encapsulated packets reach the intended VTEP and are decapsulated to the authorized bridge domain.
  3. Observe valid endpoint advertisements with less dependence on unknown-destination flooding for known endpoints.
  4. Verify same-tenant endpoints communicate and traffic is not delivered to the unrelated tenant VNI.

Explanation

Correct Answer

C:

This directly tests the desired result: observe valid endpoint advertisements with less dependence on unknown-destination flooding for known endpoints. The decisive investigation is to inspect EVPN route exchange and the selected VTEP's learned endpoint state instead of inferring learning from floods. The governing principle is that EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data.

Incorrect Answers

A:

That choice—“Measure expected BUM replication only among authorized VTEPs and improved traffic counters”—addresses this other problem: An overlay virtual network has the correct VNI but unknown destination traffic continues to flood farther than intended. Here the scenario is: An architect compares an EVPN control plane with reliance on data-plane flood-and-learn for VXLAN workloads. EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data. The direct acceptance evidence is “Observe valid endpoint advertisements with less dependence on unknown-destination flooding for known endpoints”.

B:

“Confirm encapsulated packets reach the intended VTEP and are decapsulated to the authorized bridge domain” is associated with a distinct issue: A virtualization cluster is moved to another rack and its EVPN routes exist but the remote VXLAN encapsulation next hop fails. By contrast, the actual problem is: An architect compares an EVPN control plane with reliance on data-plane flood-and-learn for VXLAN workloads. EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data. The direct acceptance evidence is “Observe valid endpoint advertisements with less dependence on unknown-destination flooding for known endpoints”.

D:

“Verify same-tenant endpoints communicate and traffic is not delivered to the unrelated tenant VNI” is relevant to a different condition: A server's VLAN 210 is accidentally bound to the wrong VXLAN segment on one leaf. The stated question instead concerns: An architect compares an EVPN control plane with reliance on data-plane flood-and-learn for VXLAN workloads. EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data. The direct acceptance evidence is “Observe valid endpoint advertisements with less dependence on unknown-destination flooding for known endpoints”.

Question 839

An operator sees devices in mixed managed states and cannot tell which switches received the new active configuration. Which controlled change best addresses the described requirement?

  1. Resolve the specific failed device deployment and reapply the approved configuration to that device.
  2. Update the correct physical patching or approved blueprint mapping in one controlled change.
  3. Correct physical cabling or update the approved design only after confirming the intended topology.
  4. Review the changes, commit the authorized revision and monitor the resulting device deployments.

Explanation

Correct Answer

A:

This action addresses the stated defect: resolve the specific failed device deployment and reapply the approved configuration to that device. The underlying constraint is that per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly. Verify rather than assume success: confirm all affected devices converge on the active blueprint revision without config drift.

Incorrect Answers

B:

That choice—“Update the correct physical patching or approved blueprint mapping in one controlled change”—addresses this other problem: A staging team has different cable-map snapshots from design and observed discovery data. Here the scenario is: An operator sees devices in mixed managed states and cannot tell which switches received the new active configuration. Resolve the specific failed device deployment and reapply the approved configuration to that device. The most relevant correction is “Resolve the specific failed device deployment and reapply the approved configuration to that device”.

C:

“Correct physical cabling or update the approved design only after confirming the intended topology” is associated with a distinct issue: A live rack cable is connected to the wrong spine port compared with the blueprint's intended cable map. By contrast, the actual problem is: An operator sees devices in mixed managed states and cannot tell which switches received the new active configuration. Resolve the specific failed device deployment and reapply the approved configuration to that device. The most relevant correction is “Resolve the specific failed device deployment and reapply the approved configuration to that device”.

D:

The option “Review the changes, commit the authorized revision and monitor the resulting device deployments” is useful in a different setting: An Apstra operator wants to distinguish blueprint validation from the actual deployment to managed switches. The case being tested is: An operator sees devices in mixed managed states and cannot tell which switches received the new active configuration. Resolve the specific failed device deployment and reapply the approved configuration to that device. The most relevant correction is “Resolve the specific failed device deployment and reapply the approved configuration to that device”.

Question 840

A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. Which design or operational principle best explains this behavior?

  1. Overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes.
  2. An IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly.
  3. In a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling.
  4. Path redundancy only improves availability when failed underlay next hops are withdrawn or detected promptly.

Explanation

Correct Answer

B:

an IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly. Here, a data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. A useful discriminating check is to inspect underlay routing adjacency, interface addressing and reachability to the spine or leaf loopback endpoints.

Incorrect Answers

A:

The option “Overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes” 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. An IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly. The controlling principle is “An IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly”.

C:

That choice—“In a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling”—addresses this other problem: A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. Here the scenario is: A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. An IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly. The controlling principle is “An IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly”.

D:

“Path redundancy only improves availability when failed underlay next hops are withdrawn or detected promptly” is associated with a distinct issue: A fabric uses two equal-cost underlay next hops yet packets continue toward a failed path following a port outage. 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. An IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly. The controlling principle is “An IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly”.

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