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 24

Question 230

A data center needs to add another rack to a production fabric without replacing the existing blueprint. Which evidence most directly verifies the intended network outcome?

  1. Verify both expected server interfaces and VLAN or routing attachments appear in active intent and measured connectivity.
  2. Confirm the rack is represented in active intent and all expected uplinks and tenant services work.
  3. Confirm the installed device configuration reconciles with the intended active config and authorized baseline.
  4. Confirm active blueprint state matches the intended retained revision and critical services recover.

Explanation

Correct Answer

B:

This directly tests the desired result: confirm the rack is represented in active intent and all expected uplinks and tenant services work. The decisive investigation is to check current spine port availability, resource pools and the proposed rack type against the active blueprint. The governing principle is that Apstra supports controlled blueprint day-two rack additions using supported rack types, resources and spine capacity.

Incorrect Answers

A:

That choice—“Verify both expected server interfaces and VLAN or routing attachments appear in active intent and measured connectivity”—addresses this other problem: A new dual-homed application server is physically connected but its logical attachment is absent from the active blueprint. Here the scenario is: A data center needs to add another rack to a production fabric without replacing the existing blueprint. Apstra supports controlled blueprint day-two rack additions using supported rack types, resources and spine capacity. The direct acceptance evidence is “Confirm the rack is represented in active intent and all expected uplinks and tenant services work”.

C:

The option “Confirm the installed device configuration reconciles with the intended active config and authorized baseline” is useful in a different setting: An audit asks why some device commands come from the baseline while others appear from intended virtual-network configuration. The case being tested is: A data center needs to add another rack to a production fabric without replacing the existing blueprint. Apstra supports controlled blueprint day-two rack additions using supported rack types, resources and spine capacity. The direct acceptance evidence is “Confirm the rack is represented in active intent and all expected uplinks and tenant services work”.

D:

“Confirm active blueprint state matches the intended retained revision and critical services recover” is relevant to a different condition: An administrator discovers a bad blueprint deployment and needs to restore a prior retained intent state. The stated question instead concerns: A data center needs to add another rack to a production fabric without replacing the existing blueprint. Apstra supports controlled blueprint day-two rack additions using supported rack types, resources and spine capacity. The direct acceptance evidence is “Confirm the rack is represented in active intent and all expected uplinks and tenant services work”.

Question 231

A new blueprint shows red validation errors before any managed device has received configuration. Which shortcut would be most likely to undermine this objective?

  1. Force generated configuration onto an unsupported NOS and disable syntax checking.
  2. Assume every active fabric instantly adopts an edited global template without a staged change.
  3. Depend on later untracked switch CLI changes to supply all missing external links.
  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:

“Force generated configuration onto an unsupported NOS and disable syntax checking” is relevant to a different condition: A team assigns a device image and platform combination not supported by the chosen Apstra reference design. The stated question instead concerns: A new blueprint shows red validation errors before any managed device has received configuration. 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:

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: A new blueprint shows red validation errors before any managed device has received configuration. 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:

“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: A new blueprint shows red validation errors before any managed device has received configuration. 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 232

A design template was edited after the first rack was built and an engineer assumes existing active blueprints are retroactively rewritten. Which shortcut would be most likely to undermine this objective?

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

Explanation

Correct Answer

D:

This is the unsafe shortcut to avoid: assume every active fabric instantly adopts an edited global template without a staged change. It violates the principle that blueprint design inheritance and change management must be validated; editing a design object does not prove all deployed fabrics changed. An appropriate alternative is to stage and review each intended blueprint update through an approved migration or change process.

Incorrect Answers

A:

The option “Depend on later untracked switch CLI changes to supply all missing external links” 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 directly relevant unsafe shortcut is “Assume every active fabric instantly adopts an edited global template without a staged change”.

B:

“Ignore design validation failures and push partial configurations directly to switches” is relevant to a different condition: An Apstra designer tries to deploy a rack without allocating required underlay interface and IP pools. The stated question instead concerns: 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 directly relevant unsafe shortcut is “Assume every active fabric instantly adopts an edited global template without a staged change”.

C:

That choice—“Force generated configuration onto an unsupported NOS and disable syntax checking”—addresses this other problem: A team assigns a device image and platform combination not supported by the chosen Apstra reference design. 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 directly relevant unsafe shortcut is “Assume every active fabric instantly adopts an edited global template without a staged change”.

Question 233

An engineer edits a virtual network in a blueprint but cannot see the change reflected in the active switch configuration. Which controlled change best addresses the described requirement?

  1. Complete review and commit of the authorized staged change, then monitor device convergence.
  2. Separate, revert or review unrelated staged edits before an authorized commit according to process.
  3. Use each blueprint tab for its intended lifecycle step and deploy changes only after authorized review.
  4. Resolve outstanding staged work, then perform the approved Time Voyager workflow.

Explanation

Correct Answer

A:

This action addresses the stated defect: complete review and commit of the authorized staged change, then monitor device convergence. The underlying constraint is that staged blueprint intent can differ from the deployed active revision until approved changes are committed. Verify rather than assume success: observe the updated active blueprint and running device configuration reflect the approved new virtual network.

Incorrect Answers

B:

The option “Separate, revert or review unrelated staged edits before an authorized commit according to process” is useful in a different setting: A blueprint has accumulated unrelated uncommitted routing and rack modifications from different change windows. The case being tested is: An engineer edits a virtual network in a blueprint but cannot see the change reflected in the active switch configuration. Complete review and commit of the authorized staged change, then monitor device convergence. The most relevant correction is “Complete review and commit of the authorized staged change, then monitor device convergence”.

C:

“Use each blueprint tab for its intended lifecycle step and deploy changes only after authorized review” is relevant to a different condition: A dashboard reports that all switches are reachable while a recent staged policy change has not been deployed. The stated question instead concerns: An engineer edits a virtual network in a blueprint but cannot see the change reflected in the active switch configuration. Complete review and commit of the authorized staged change, then monitor device convergence. The most relevant correction is “Complete review and commit of the authorized staged change, then monitor device convergence”.

D:

That choice—“Resolve outstanding staged work, then perform the approved Time Voyager workflow”—addresses this other problem: A scheduled rollback would occur while an unrelated approved feature configuration remains uncommitted. Here the scenario is: An engineer edits a virtual network in a blueprint but cannot see the change reflected in the active switch configuration. Complete review and commit of the authorized staged change, then monitor device convergence. The most relevant correction is “Complete review and commit of the authorized staged change, then monitor device convergence”.

Question 234

A new switch reports Ready while its peers remain in a deployment-failed state after committing fabric intent. Which initial check would most directly distinguish the likely cause?

  1. Check each device's state, failed action details and intended-versus-running configuration revision.
  2. Compare LLDP-discovered endpoints and physical interface identifiers against the generated cable map.
  3. Review the intended cable-map endpoints, device identities and actual discovered LLDP neighbors.
  4. Inspect the Staged, Uncommitted and Active states and per-device deployment status.

Explanation

Correct Answer

A:

This checks the relevant evidence first: check each device's state, failed action details and intended-versus-running configuration revision. The underlying concept is that per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly. After confirming the finding, a controlled remediation is to resolve the specific failed device deployment and reapply the approved configuration to that device.

Incorrect Answers

B:

“Compare LLDP-discovered endpoints and physical interface identifiers against the generated cable map” 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: A new switch reports Ready while its peers remain in a deployment-failed state after committing fabric intent. The relevant inspection is: Check each device's state, failed action details and intended-versus-running configuration revision. The most discriminating first check is “Check each device's state, failed action details and intended-versus-running configuration revision”.

C:

The option “Review the intended cable-map endpoints, device identities and actual discovered LLDP neighbors” is useful in a different setting: An Apstra blueprint expects a set of spine interfaces but physical inventory maps uplinks to different ports. The case being tested is: A new switch reports Ready while its peers remain in a deployment-failed state after committing fabric intent. The relevant inspection is: Check each device's state, failed action details and intended-versus-running configuration revision. The most discriminating first check is “Check each device's state, failed action details and intended-versus-running configuration revision”.

D:

“Inspect the Staged, Uncommitted and Active states and per-device deployment status” is relevant to a different condition: A design is staged and rendered correctly, but a production switch still uses the previous running configuration. The stated question instead concerns: A new switch reports Ready while its peers remain in a deployment-failed state after committing fabric intent. The relevant inspection is: Check each device's state, failed action details and intended-versus-running configuration revision. The most discriminating first check is “Check each device's state, failed action details and intended-versus-running configuration revision”.

Question 235

A blueprint has accumulated unrelated uncommitted routing and rack modifications from different change windows. Which shortcut would be most likely to undermine this objective?

  1. Commit blindly and assume every outstanding uncommitted change belongs to the current ticket.
  2. Assume that viewing a change under Staged applies it instantly across the entire fabric.
  3. Interpret a green dashboard as proof that every staged change has already been committed.
  4. Use a historical revision rollback for every minor uncommitted typo without inspecting scope.

Explanation

Correct Answer

A:

This is the unsafe shortcut to avoid: commit blindly and assume every outstanding uncommitted change belongs to the current ticket. It violates the principle that the set of uncommitted changes must be reviewed as a whole before deployment because committing may include multiple intended modifications. An appropriate alternative is to separate, revert or review unrelated staged edits before an authorized commit according to process.

Incorrect Answers

B:

That choice—“Assume that viewing a change under Staged applies it instantly across the entire fabric”—addresses this other problem: A service owner tests a new VRF assignment while the proposed change appears only in the Staged view. Here the scenario is: A blueprint has accumulated unrelated uncommitted routing and rack modifications from different change windows. The set of uncommitted changes must be reviewed as a whole before deployment because committing may include multiple intended modifications. The directly relevant unsafe shortcut is “Commit blindly and assume every outstanding uncommitted change belongs to the current ticket”.

C:

“Interpret a green dashboard as proof that every staged change has already been committed” is associated with a distinct issue: A network team needs to distinguish observed operational health from whether the desired blueprint configuration is active. By contrast, the actual problem is: A blueprint has accumulated unrelated uncommitted routing and rack modifications from different change windows. The set of uncommitted changes must be reviewed as a whole before deployment because committing may include multiple intended modifications. The directly relevant unsafe shortcut is “Commit blindly and assume every outstanding uncommitted change belongs to the current ticket”.

D:

The option “Use a historical revision rollback for every minor uncommitted typo without inspecting scope” is useful in a different setting: A designer notices an accidental rack parameter change before any blueprint commit has occurred. The case being tested is: A blueprint has accumulated unrelated uncommitted routing and rack modifications from different change windows. The set of uncommitted changes must be reviewed as a whole before deployment because committing may include multiple intended modifications. The directly relevant unsafe shortcut is “Commit blindly and assume every outstanding uncommitted change belongs to the current ticket”.

Question 236

Two racks advertise the same distributed gateway virtual address but clients see intermittent first-hop behavior after a deployment. Which shortcut would be most likely to undermine this objective?

  1. Configure unrelated virtual gateway identities per rack while claiming a single anycast first hop.
  2. Force all inter-VLAN application traffic through an unmanaged central hairpin without validating the gateway design.
  3. Assume every EVPN route type is interchangeable merely because it carries a network address.
  4. Treat the two legs of a multihomed Ethernet segment as unrelated unmanaged single-homed endpoints.

Explanation

Correct Answer

A:

This is the unsafe shortcut to avoid: configure unrelated virtual gateway identities per rack while claiming a single anycast first hop. It violates the principle that a distributed anycast gateway needs consistent gateway identity and virtual network association across participating leaf devices. An appropriate alternative is to align the authorized distributed gateway configuration across participating VTEPs.

Incorrect Answers

B:

“Force all inter-VLAN application traffic through an unmanaged central hairpin without validating the gateway design” is relevant to a different condition: An architect wants gateway functions distributed across tenant leafs in an EVPN-VXLAN fabric. The stated question instead concerns: Two racks advertise the same distributed gateway virtual address but clients see intermittent first-hop behavior after a deployment. A distributed anycast gateway needs consistent gateway identity and virtual network association across participating leaf devices. The directly relevant unsafe shortcut is “Configure unrelated virtual gateway identities per rack while claiming a single anycast first hop”.

C:

That choice—“Assume every EVPN route type is interchangeable merely because it carries a network address”—addresses this other problem: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. Here the scenario is: Two racks advertise the same distributed gateway virtual address but clients see intermittent first-hop behavior after a deployment. A distributed anycast gateway needs consistent gateway identity and virtual network association across participating leaf devices. The directly relevant unsafe shortcut is “Configure unrelated virtual gateway identities per rack while claiming a single anycast first hop”.

D:

“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: Two racks advertise the same distributed gateway virtual address but clients see intermittent first-hop behavior after a deployment. A distributed anycast gateway needs consistent gateway identity and virtual network association across participating leaf devices. The directly relevant unsafe shortcut is “Configure unrelated virtual gateway identities per rack while claiming a single anycast first hop”.

Question 237

A virtualization cluster is moved to another rack and its EVPN routes exist but the remote VXLAN encapsulation next hop fails. Which shortcut would be most likely to undermine this objective?

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

Explanation

Correct Answer

A:

This is the unsafe shortcut to avoid: replace the tenant VLAN ID repeatedly without checking VXLAN endpoint reachability. It violates the principle that a VTEP provides VXLAN encapsulation and decapsulation and its IP reachability must exist independently of bridge membership. An appropriate alternative is to restore routed reachability to the advertised VTEP and the correct tunnel forwarding state.

Incorrect Answers

B:

The option “Map every rack's VLAN 210 to an arbitrary shared VNI without checking tenant boundaries” is useful in a different setting: A server's VLAN 210 is accidentally bound to the wrong VXLAN segment on one leaf. The case being tested is: A virtualization cluster is moved to another rack and its EVPN routes exist but the remote VXLAN encapsulation next hop fails. A VTEP provides VXLAN encapsulation and decapsulation and its IP reachability must exist independently of bridge membership. The directly relevant unsafe shortcut is “Replace the tenant VLAN ID repeatedly without checking VXLAN endpoint reachability”.

C:

“Disable the EVPN control plane and assume every remote endpoint is learned optimally from normal TCP traffic” 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: A virtualization cluster is moved to another rack and its EVPN routes exist but the remote VXLAN encapsulation next hop fails. A VTEP provides VXLAN encapsulation and decapsulation and its IP reachability must exist independently of bridge membership. The directly relevant unsafe shortcut is “Replace the tenant VLAN ID repeatedly without checking VXLAN endpoint reachability”.

D:

That choice—“Assume the underlay can carry the original maximum Ethernet frame unchanged after VXLAN headers are added”—addresses this other problem: An east-west application works without tunneling but drops large payloads after VXLAN overlay migration. Here the scenario is: A virtualization cluster is moved to another rack and its EVPN routes exist but the remote VXLAN encapsulation next hop fails. A VTEP provides VXLAN encapsulation and decapsulation and its IP reachability must exist independently of bridge membership. The directly relevant unsafe shortcut is “Replace the tenant VLAN ID repeatedly without checking VXLAN endpoint reachability”.

Question 238

A blueprint operator maintains repeated data center operational variables that should have a single validated definition. Which controlled change best addresses the described requirement?

  1. Narrow configlet selectors or tags and stage a validated corrective revision.
  2. Create a narrowly scoped reviewed configlet and validate the resulting generated device configuration.
  3. Update the approved property set and stage dependent configurations through normal blueprint review.
  4. Stage the new rack, assign valid devices and resources, validate, then commit through change control.

Explanation

Correct Answer

C:

This action addresses the stated defect: update the approved property set and stage dependent configurations through normal blueprint review. The underlying constraint is that Apstra property sets can centralize reusable named parameters referenced by supported configuration templates. Verify rather than assume success: confirm every intended consumer receives the updated value and unrelated devices retain their settings.

Incorrect Answers

A:

That choice—“Narrow configlet selectors or tags and stage a validated corrective revision”—addresses this other problem: A new configlet unexpectedly adds a command to spine switches when it was intended for a single border leaf. Here the scenario is: A blueprint operator maintains repeated data center operational variables that should have a single validated definition. Update the approved property set and stage dependent configurations through normal blueprint review. The most relevant correction is “Update the approved property set and stage dependent configurations through normal blueprint review”.

B:

“Create a narrowly scoped reviewed configlet and validate the resulting generated device configuration” is associated with a distinct issue: An application requires a supported vendor-specific setting absent from the blueprint's default rendered commands. By contrast, the actual problem is: A blueprint operator maintains repeated data center operational variables that should have a single validated definition. Update the approved property set and stage dependent configurations through normal blueprint review. The most relevant correction is “Update the approved property set and stage dependent configurations through normal blueprint review”.

D:

“Stage the new rack, assign valid devices and resources, validate, then commit through change control” is relevant to a different condition: An organization expands a Clos topology and wants newly created racks to inherit validated patterns and allocations. The stated question instead concerns: A blueprint operator maintains repeated data center operational variables that should have a single validated definition. Update the approved property set and stage dependent configurations through normal blueprint review. The most relevant correction is “Update the approved property set and stage dependent configurations through normal blueprint review”.

Question 239

A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. Which evidence most directly verifies the intended network outcome?

  1. Prove design-stage topology and resource validation before committing to hardware procurement.
  2. Confirm topology validation succeeds and the planned rack connections fit the chosen design.
  3. Show the design can add the forecast leaf ports without violating supported interface maps or capacity assumptions.
  4. Validate that physical port assignments and supported speeds match the rack design without resource conflicts.

Explanation

Correct Answer

A:

This directly tests the desired result: prove design-stage topology and resource validation before committing to hardware procurement. The decisive investigation is to review intended external service connectivity and supported blueprint reference-design capabilities. The governing principle is that reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements.

Incorrect Answers

B:

That choice—“Confirm topology validation succeeds and the planned rack connections fit the chosen design”—addresses this other problem: A new pod requires a repeatable three-stage Clos layout but its design draft mixes unsupported spine counts and random cabling. Here the scenario is: A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. Reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements. The direct acceptance evidence is “Prove design-stage topology and resource validation before committing to hardware procurement”.

C:

“Show the design can add the forecast leaf ports without violating supported interface maps or capacity assumptions” is associated with a distinct issue: A planned Apstra fabric includes future rack growth but the initial design leaves no capacity for additional spine downlinks. By contrast, the actual problem is: A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. Reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements. The direct acceptance evidence is “Prove design-stage topology and resource validation before committing to hardware procurement”.

D:

The option “Validate that physical port assignments and supported speeds match the rack design without resource conflicts” is useful in a different setting: An Apstra design refuses a proposed uplink because its interface map does not match hardware port mode. The case being tested is: A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. Reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements. The direct acceptance evidence is “Prove design-stage topology and resource validation before committing to hardware procurement”.

Question 240

An engineer brings up BGP peers to the spines but omits export of the overlay endpoint loopbacks. Which evidence most directly verifies the intended network outcome?

  1. Confirm remote VTEP loopbacks resolve to healthy fabric routes and VXLAN tunnel traffic succeeds.
  2. Observe established underlay peers and reachability of every intended VTEP loopback before testing virtual networks.
  3. Prove traffic moves to remaining healthy ECMP next hops within the accepted convergence objective.
  4. Confirm each leaf reaches other leaves via expected spine paths and no unintended data-center transit loops exist.

Explanation

Correct Answer

A:

This directly tests the desired result: confirm remote VTEP loopbacks resolve to healthy fabric routes and VXLAN tunnel traffic succeeds. The decisive investigation is to inspect routing tables and underlay advertisements for each intended VTEP address. The governing principle is that overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes.

Incorrect Answers

B:

“Observe established underlay peers and reachability of every intended VTEP loopback before testing virtual networks” is relevant to a different condition: An additional rack joins a Clos fabric with healthy physical interfaces but fails to form underlay neighbor sessions. The stated question instead concerns: An engineer brings up BGP peers to the spines but omits export of the overlay endpoint loopbacks. Overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes. The direct acceptance evidence is “Confirm remote VTEP loopbacks resolve to healthy fabric routes and VXLAN tunnel traffic succeeds”.

C:

That choice—“Prove traffic moves to remaining healthy ECMP next hops within the accepted convergence objective”—addresses this other problem: A two-spine fabric can tolerate one path failure but the application sees blackholing for several minutes after a spine uplink drops. Here the scenario is: An engineer brings up BGP peers to the spines but omits export of the overlay endpoint loopbacks. Overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes. The direct acceptance evidence is “Confirm remote VTEP loopbacks resolve to healthy fabric routes and VXLAN tunnel traffic succeeds”.

D:

“Confirm each leaf reaches other leaves via expected spine paths and no unintended data-center transit loops exist” is associated with a distinct issue: A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. By contrast, the actual problem is: An engineer brings up BGP peers to the spines but omits export of the overlay endpoint loopbacks. Overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes. The direct acceptance evidence is “Confirm remote VTEP loopbacks resolve to healthy fabric routes and VXLAN tunnel traffic succeeds”.

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