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 35

Question 340

A fabric sees unexpectedly broad BUM traffic after a new VXLAN virtual network is provisioned. Which design or operational principle best explains this behavior?

  1. A VTEP provides VXLAN encapsulation and decapsulation and its IP reachability must exist independently of bridge membership.
  2. BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership.
  3. EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data.
  4. The VNI associates overlay VXLAN traffic with the intended virtual network, so inconsistent VLAN-to-VNI mapping breaks isolation or connectivity.

Explanation

Correct Answer

B:

BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership. Here, a fabric sees unexpectedly broad BUM traffic after a new VXLAN virtual network is provisioned. A useful discriminating check is to inspect broadcast, unknown-unicast and multicast handling and participating VTEPs for the affected VNI.

Incorrect Answers

A:

The option “A VTEP provides VXLAN encapsulation and decapsulation and its IP reachability must exist independently of bridge membership” is useful in a different setting: A virtualization cluster is moved to another rack and its EVPN routes exist but the remote VXLAN encapsulation next hop fails. The case being tested is: A fabric sees unexpectedly broad BUM traffic after a new VXLAN virtual network is provisioned. BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership. The controlling principle is “BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership”.

C:

That choice—“EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data”—addresses this other problem: A team wants scalable MAC learning across the fabric rather than sending every remote MAC advertisement by flood. Here the scenario is: A fabric sees unexpectedly broad BUM traffic after a new VXLAN virtual network is provisioned. BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership. The controlling principle is “BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership”.

D:

“The VNI associates overlay VXLAN traffic with the intended virtual network, so inconsistent VLAN-to-VNI mapping breaks isolation or connectivity” is associated with a distinct issue: A rack migration assigns the correct switch access VLAN but places the VTEP into another tenant's virtual network identifier. By contrast, the actual problem is: A fabric sees unexpectedly broad BUM traffic after a new VXLAN virtual network is provisioned. BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership. The controlling principle is “BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership”.

Question 341

A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. Which design or operational principle best explains this behavior?

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

Explanation

Correct Answer

C:

reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision. Here, a team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. A useful discriminating check is to determine whether the unwanted modification exists only in Staged or in the Active revision.

Incorrect Answers

A:

“Apstra Time Voyager supports controlled movement to retained blueprint revisions, subject to compatibility and staged-change constraints” is associated with a distinct issue: A new fabric commit causes service degradation and the team wants to return to a known earlier revision with minimal manual reconstruction. By contrast, the actual problem is: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision. The controlling principle is “Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision”.

B:

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

D:

That choice—“Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory”—addresses this other problem: A historical revision would restore a system ID that has been reassigned to another device since it was first recorded. Here the scenario is: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision. The controlling principle is “Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision”.

Question 342

A historical revision would restore a system ID that has been reassigned to another device since it was first recorded. 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. Apstra Time Voyager supports controlled movement to retained blueprint revisions, subject to compatibility and staged-change constraints.
  3. Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision.
  4. Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory.

Explanation

Correct Answer

D:

Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory. Here, a historical revision would restore a system ID that has been reassigned to another device since it was first recorded. A useful discriminating check is to inspect historical identifiers, resource assignments, device availability and supported rollback constraints.

Incorrect Answers

A:

That choice—“A Time Voyager rollback can discard current uncommitted staging and must be coordinated with change owners”—addresses this other problem: An operator has valuable staged changes when another administrator proposes jumping to an older blueprint revision. Here the scenario is: A historical revision would restore a system ID that has been reassigned to another device since it was first recorded. Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory. The controlling principle is “Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory”.

B:

“Apstra Time Voyager supports controlled movement to retained blueprint revisions, subject to compatibility and staged-change constraints” is associated with a distinct issue: A new fabric commit causes service degradation and the team wants to return to a known earlier revision with minimal manual reconstruction. By contrast, the actual problem is: A historical revision would restore a system ID that has been reassigned to another device since it was first recorded. Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory. The controlling principle is “Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory”.

C:

The option “Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision” is useful in a different setting: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. The case being tested is: A historical revision would restore a system ID that has been reassigned to another device since it was first recorded. Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory. The controlling principle is “Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory”.

Question 343

A rack designer wants a redundant host attachment pattern for critical appliances. Which initial check would most directly distinguish the likely cause?

  1. Inspect the rack type's expected spine attachment graph and actual cable endpoints.
  2. Inspect rack type properties and compare the proposed rack's connectivity with its validated peers.
  3. Review single-versus-dual leaf rack settings and server connectivity requirements.
  4. Review consumed spine port counts, interface maps and oversubscription projections.

Explanation

Correct Answer

C:

This checks the relevant evidence first: review single-versus-dual leaf rack settings and server connectivity requirements. The underlying concept is that rack type and leaf selection must support the intended redundant attachment topology and host interface roles. After confirming the finding, a controlled remediation is to select a supported redundant leaf rack type and document host LAG or independent paths as appropriate.

Incorrect Answers

A:

“Inspect the rack type's expected spine attachment graph and actual cable endpoints” is relevant to a different condition: A data center cabling plan repeats one spine endpoint for all redundant paths from a critical rack. The stated question instead concerns: A rack designer wants a redundant host attachment pattern for critical appliances. The relevant inspection is: Review single-versus-dual leaf rack settings and server connectivity requirements. The most discriminating first check is “Review single-versus-dual leaf rack settings and server connectivity requirements”.

B:

That choice—“Inspect rack type properties and compare the proposed rack's connectivity with its validated peers”—addresses this other problem: A new leaf rack should use a repeatable single-leaf topology but its manually modeled connections differ from existing identical racks. Here the scenario is: A rack designer wants a redundant host attachment pattern for critical appliances. The relevant inspection is: Review single-versus-dual leaf rack settings and server connectivity requirements. The most discriminating first check is “Review single-versus-dual leaf rack settings and server connectivity requirements”.

D:

The option “Review consumed spine port counts, interface maps and oversubscription projections” is useful in a different setting: A planned rack addition fails because the spine layer has no compatible free ports at the required link speed. The case being tested is: A rack designer wants a redundant host attachment pattern for critical appliances. The relevant inspection is: Review single-versus-dual leaf rack settings and server connectivity requirements. The most discriminating first check is “Review single-versus-dual leaf rack settings and server connectivity requirements”.

Question 344

A network engineer views valid proposed changes under Staged and mistakenly assumes all devices were updated. Which shortcut would be most likely to undermine this objective?

  1. Assume every configuration view is identical and blindly paste one into the device CLI.
  2. Skip diff review and declare the change complete as soon as the design editor saves it.
  3. Treat the existence of a rendered config file as proof of deployment to every switch.
  4. Delete the old blueprint and recreate every tenant because one hardware identifier changed.

Explanation

Correct Answer

C:

This is the unsafe shortcut to avoid: treat the existence of a rendered config file as proof of deployment to every switch. It violates the principle that staging and rendering intended configuration are distinct from committing and deploying the active blueprint. An appropriate alternative is to review and commit the approved staged change using the documented deployment process.

Incorrect Answers

A:

The option “Assume every configuration view is identical and blindly paste one into the device CLI” is useful in a different setting: A new Apstra deployment includes baseline settings, platform-specific changes and generated overlay commands that an engineer wants to distinguish. 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 directly relevant unsafe shortcut is “Treat the existence of a rendered config file as proof of deployment to every switch”.

B:

“Skip diff review and declare the change complete as soon as the design editor saves it” is relevant to a different condition: An Apstra operator wants to distinguish blueprint validation from the actual deployment to managed switches. The stated question instead concerns: 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 directly relevant unsafe shortcut is “Treat the existence of a rendered config file as proof of deployment to every switch”.

D:

“Delete the old blueprint and recreate every tenant because one hardware identifier changed” is associated with a distinct issue: A failed managed switch is swapped physically yet Apstra refuses deployment to the replacement inventory device. 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 directly relevant unsafe shortcut is “Treat the existence of a rendered config file as proof of deployment to every switch”.

Question 345

A data center runs a centralized SOC and requests appliance event forwarding without sharing administrator credentials. Which design or operational principle best explains this behavior?

  1. Controller event logs and deployment records should be correlated with intent revisions and change approvals.
  2. Apstra event and audit records provide change accountability distinct from raw packet telemetry.
  3. Syslog forwarding can export relevant controller and device operational events for independent correlation and retention.
  4. Monitoring conclusions depend on fresh telemetry, so absence of alarms is not proof of healthy collection.

Explanation

Correct Answer

C:

syslog forwarding can export relevant controller and device operational events for independent correlation and retention. Here, a data center runs a centralized SOC and requests appliance event forwarding without sharing administrator credentials. A useful discriminating check is to inspect supported syslog configuration, transport reachability and receiving collector parsing.

Incorrect Answers

A:

“Controller event logs and deployment records should be correlated with intent revisions and change approvals” 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 data center runs a centralized SOC and requests appliance event forwarding without sharing administrator credentials. Syslog forwarding can export relevant controller and device operational events for independent correlation and retention. The controlling principle is “Syslog forwarding can export relevant controller and device operational events for independent correlation and retention”.

B:

The option “Apstra event and audit records provide change accountability distinct from raw packet telemetry” is useful in a different setting: A team investigates whether a blueprint revision was created by automation or by an administrator. The case being tested is: A data center runs a centralized SOC and requests appliance event forwarding without sharing administrator credentials. Syslog forwarding can export relevant controller and device operational events for independent correlation and retention. The controlling principle is “Syslog forwarding can export relevant controller and device operational events for independent correlation and retention”.

D:

That choice—“Monitoring conclusions depend on fresh telemetry, so absence of alarms is not proof of healthy collection”—addresses this other problem: A monitoring dashboard shows a device as green but telemetry timestamps stopped updating 20 minutes earlier. Here the scenario is: A data center runs a centralized SOC and requests appliance event forwarding without sharing administrator credentials. Syslog forwarding can export relevant controller and device operational events for independent correlation and retention. The controlling principle is “Syslog forwarding can export relevant controller and device operational events for independent correlation and retention”.

Question 346

A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Which design or operational principle best explains this behavior?

  1. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone.
  2. Routing policy and connectivity-template scope determine which tenant prefixes cross external boundaries.
  3. Connectivity templates define host-facing virtual-network endpoint membership and tagging behavior.
  4. A routing zone can contain multiple virtual networks that share the intended tenant Layer 3 routing context.

Explanation

Correct Answer

A:

connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. Here, a tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. A useful discriminating check is to inspect border-leaf interfaces, attached connectivity template and tenant-specific routing policy.

Incorrect Answers

B:

“Routing policy and connectivity-template scope determine which tenant prefixes cross external boundaries” is associated with a distinct issue: An external peer receives a tenant's internal subnets that were supposed to stay private. By contrast, the actual problem is: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. The controlling principle is “Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone”.

C:

The option “Connectivity templates define host-facing virtual-network endpoint membership and tagging behavior” is useful in a different setting: A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. The case being tested is: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. The controlling principle is “Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone”.

D:

“A routing zone can contain multiple virtual networks that share the intended tenant Layer 3 routing context” is relevant to a different condition: A multirack tenant needs two segmented application subnets while sharing a common VRF routing domain. The stated question instead concerns: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. The controlling principle is “Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone”.

Question 347

A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. Which initial check would most directly distinguish the likely cause?

  1. Inspect underlay routing adjacency, interface addressing and reachability to the spine or leaf loopback endpoints.
  2. Check interface state, routing convergence and forwarding entries following the simulated spine-link loss.
  3. Inspect installed ECMP next hops and compare per-link counters across multiple distinct flows.
  4. Inspect routing tables and underlay advertisements for each intended VTEP address.

Explanation

Correct Answer

D:

This checks the relevant evidence first: inspect routing tables and underlay advertisements for each intended VTEP address. The underlying concept is that overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes. After confirming the finding, a controlled remediation is to advertise the approved VTEP loopbacks through the fabric underlay and check next-hop reachability.

Incorrect Answers

A:

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

B:

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

C:

“Inspect installed ECMP next hops and compare per-link counters across multiple distinct flows” is associated with a distinct issue: An operator finds two equal-cost fabric paths but a single large traffic flow consistently traverses only one link. By contrast, the actual problem is: A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. The relevant inspection is: Inspect routing tables and underlay advertisements for each intended VTEP address. The most discriminating first check is “Inspect routing tables and underlay advertisements for each intended VTEP address”.

Question 348

A custom telemetry probe flags a latency anomaly but the blueprint shows no service configuration errors. Which evidence most directly verifies the intended network outcome?

  1. Confirm the service anomaly clears and the affected workload network passes functional tests.
  2. Confirm the corrective workflow resolves the specific anomaly class without hiding unrelated alarms.
  3. Confirm live telemetry returns inside accepted bounds and the probe alert clears with supporting samples.
  4. Confirm only approved target devices receive the supplemental command after commit.

Explanation

Correct Answer

C:

This directly tests the desired result: confirm live telemetry returns inside accepted bounds and the probe alert clears with supporting samples. The decisive investigation is to inspect the probe's monitored metric, stage, threshold and underlying samples before correlating service state. The governing principle is that probe anomalies can reflect telemetry thresholds or conditions independently of blueprint service configuration anomalies.

Incorrect Answers

A:

The option “Confirm the service anomaly clears and the affected workload network passes functional tests” is useful in a different setting: A blueprint raises a service anomaly for a virtual network even though all interfaces in its rack are administratively up. The case being tested is: A custom telemetry probe flags a latency anomaly but the blueprint shows no service configuration errors. Probe anomalies can reflect telemetry thresholds or conditions independently of blueprint service configuration anomalies. The direct acceptance evidence is “Confirm live telemetry returns inside accepted bounds and the probe alert clears with supporting samples”.

B:

“Confirm the corrective workflow resolves the specific anomaly class without hiding unrelated alarms” is relevant to a different condition: A support engineer assumes every anomaly is a device-down alarm even when the affected rule is a tenant connectivity expectation. The stated question instead concerns: A custom telemetry probe flags a latency anomaly but the blueprint shows no service configuration errors. Probe anomalies can reflect telemetry thresholds or conditions independently of blueprint service configuration anomalies. The direct acceptance evidence is “Confirm live telemetry returns inside accepted bounds and the probe alert clears with supporting samples”.

D:

“Confirm only approved target devices receive the supplemental command after commit” is associated with a distinct issue: An engineer discovers that a supplemental configuration template was bound to an overly broad tag. By contrast, the actual problem is: A custom telemetry probe flags a latency anomaly but the blueprint shows no service configuration errors. Probe anomalies can reflect telemetry thresholds or conditions independently of blueprint service configuration anomalies. The direct acceptance evidence is “Confirm live telemetry returns inside accepted bounds and the probe alert clears with supporting samples”.

Question 349

A leaf needs to advertise a workload endpoint location to remote EVPN participants across the VXLAN fabric. Which evidence most directly verifies the intended network outcome?

  1. Confirm the destination subnet appears as an imported Type 5 route and routes end-to-end in the intended VRF.
  2. Confirm the remote VTEP has a correctly imported Type 2 endpoint route and can deliver host traffic.
  3. Observe valid imported EVPN routes and bidirectional host reachability only within the authorized virtual network.
  4. Confirm stable multihoming advertisements and appropriate forwarding when each server attachment is tested.

Explanation

Correct Answer

B:

This directly tests the desired result: confirm the remote VTEP has a correctly imported Type 2 endpoint route and can deliver host traffic. The decisive investigation is to inspect the EVPN route database for Type 2 MAC or MAC-IP advertisements and associated VNI or next hop. The governing principle is that EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning.

Incorrect Answers

A:

“Confirm the destination subnet appears as an imported Type 5 route and routes end-to-end in the intended VRF” is associated with a distinct issue: An operator advertises an external IPv4 subnet into an EVPN routing domain for routed reachability. By contrast, the actual problem is: A leaf needs to advertise a workload endpoint location to remote EVPN participants across the VXLAN fabric. EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning. The direct acceptance evidence is “Confirm the remote VTEP has a correctly imported Type 2 endpoint route and can deliver host traffic”.

C:

“Observe valid imported EVPN routes and bidirectional host reachability only within the authorized virtual network” is relevant to a different condition: A server VLAN is created on two racks but remote EVPN routes cannot be imported because their route targets do not align. The stated question instead concerns: A leaf needs to advertise a workload endpoint location to remote EVPN participants across the VXLAN fabric. EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning. The direct acceptance evidence is “Confirm the remote VTEP has a correctly imported Type 2 endpoint route and can deliver host traffic”.

D:

That choice—“Confirm stable multihoming advertisements and appropriate forwarding when each server attachment is tested”—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. EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning. The direct acceptance evidence is “Confirm the remote VTEP has a correctly imported Type 2 endpoint route and can deliver host traffic”.

Question 350

An EVPN multihomed endpoint exhibits unstable forwarding after both attachment leafs advertise the same segment independently. Which controlled change best addresses the described requirement?

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

Explanation

Correct Answer

D:

This action addresses the stated defect: align approved Ethernet segment and multihoming configuration on the participating leaf devices. The underlying constraint is that EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability. Verify rather than assume success: confirm stable multihoming advertisements and appropriate forwarding when each server attachment is tested.

Incorrect Answers

A:

That choice—“Repair EVPN endpoint advertisement and import eligibility for the affected virtual network”—addresses this other problem: A leaf needs to advertise a workload endpoint location to remote EVPN participants across the VXLAN fabric. Here the scenario is: An EVPN multihomed endpoint exhibits unstable forwarding after both attachment leafs advertise the same segment independently. Align approved Ethernet segment and multihoming configuration on the participating leaf devices. The most relevant correction is “Align approved Ethernet segment and multihoming configuration on the participating leaf devices”.

B:

“Correct the intended route target mapping and import policies while preserving tenant isolation” is associated with a distinct issue: Two leaves advertise the same virtual network yet one leaf rejects the other's EVPN MAC routes. By contrast, the actual problem is: An EVPN multihomed endpoint exhibits unstable forwarding after both attachment leafs advertise the same segment independently. Align approved Ethernet segment and multihoming configuration on the participating leaf devices. The most relevant correction is “Align approved Ethernet segment and multihoming configuration on the participating leaf devices”.

C:

The option “Correct prefix export/import and next-hop resolution for the routed EVPN IP prefix” is useful in a different setting: An operator advertises an external IPv4 subnet into an EVPN routing domain for routed reachability. The case being tested is: An EVPN multihomed endpoint exhibits unstable forwarding after both attachment leafs advertise the same segment independently. Align approved Ethernet segment and multihoming configuration on the participating leaf devices. The most relevant correction is “Align approved Ethernet segment and multihoming configuration on the participating leaf devices”.

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