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 22

Question 210

A support engineer assumes every anomaly is a device-down alarm even when the affected rule is a tenant connectivity expectation. Which initial check would most directly distinguish the likely cause?

  1. Inspect the specific service anomaly, affected objects and intended virtual-network configuration and state.
  2. Inspect anomaly type and affected graph nodes before selecting the next technical investigation.
  3. Inspect the probe's monitored metric, stage, threshold and underlying samples before correlating service state.
  4. Inspect object types, graph relationship properties and returned identities for the intended rack.

Explanation

Correct Answer

B:

This checks the relevant evidence first: inspect anomaly type and affected graph nodes before selecting the next technical investigation. The underlying concept is that Apstra anomaly categories distinguish service intent violations, device issues and analytics-detected deviations. After confirming the finding, a controlled remediation is to route the issue to the correct service, telemetry or device workflow based on the observed anomaly evidence.

Incorrect Answers

A:

That choice—“Inspect the specific service anomaly, affected objects and intended virtual-network configuration and state”—addresses this other problem: A blueprint raises a service anomaly for a virtual network even though all interfaces in its rack are administratively up. Here the scenario is: A support engineer assumes every anomaly is a device-down alarm even when the affected rule is a tenant connectivity expectation. The relevant inspection is: Inspect anomaly type and affected graph nodes before selecting the next technical investigation. The most discriminating first check is “Inspect anomaly type and affected graph nodes before selecting the next technical investigation”.

C:

The option “Inspect the probe's monitored metric, stage, threshold and underlying samples before correlating service state” is useful in a different setting: A custom telemetry probe flags a latency anomaly but the blueprint shows no service configuration errors. The case being tested is: A support engineer assumes every anomaly is a device-down alarm even when the affected rule is a tenant connectivity expectation. The relevant inspection is: Inspect anomaly type and affected graph nodes before selecting the next technical investigation. The most discriminating first check is “Inspect anomaly type and affected graph nodes before selecting the next technical investigation”.

D:

“Inspect object types, graph relationship properties and returned identities for the intended rack” is relevant to a different condition: An operator wants to identify managed nodes by rack and role in the blueprint graph. The stated question instead concerns: A support engineer assumes every anomaly is a device-down alarm even when the affected rule is a tenant connectivity expectation. The relevant inspection is: Inspect anomaly type and affected graph nodes before selecting the next technical investigation. The most discriminating first check is “Inspect anomaly type and affected graph nodes before selecting the next technical investigation”.

Question 211

A VMware workload migration succeeds at compute level but its new host port cannot reach the expected tenant virtual network. Which shortcut would be most likely to undermine this objective?

  1. Treat the interconnect as a trunk carrying all tenant networks with no import controls.
  2. Assume the virtualization manager's displayed port-group name automatically configures leaf networking.
  3. Leak all tenant routes into one global routing table because only one shared DNS server is needed.
  4. Assume a unique VLAN number alone guarantees Layer 3 tenant isolation.

Explanation

Correct Answer

B:

This is the unsafe shortcut to avoid: assume the virtualization manager's displayed port-group name automatically configures leaf networking. It violates the principle that hypervisor network labels and Apstra fabric virtual-network connectivity must both represent the intended tenant service. An appropriate alternative is to correct the approved virtual-network attachment and associated host-facing VLAN primitives.

Incorrect Answers

A:

“Treat the interconnect as a trunk carrying all tenant networks with no import controls” is relevant to a different condition: A data-center interconnect extends selected tenant segments between two sites but one site imports unrelated virtual networks. The stated question instead concerns: A VMware workload migration succeeds at compute level but its new host port cannot reach the expected tenant virtual network. Hypervisor network labels and Apstra fabric virtual-network connectivity must both represent the intended tenant service. The directly relevant unsafe shortcut is “Assume the virtualization manager's displayed port-group name automatically configures leaf networking”.

C:

“Leak all tenant routes into one global routing table because only one shared DNS server is needed” is associated with a distinct issue: Two tenants require a controlled shared service, and a proposal suggests importing every route into each tenant VRF. By contrast, the actual problem is: A VMware workload migration succeeds at compute level but its new host port cannot reach the expected tenant virtual network. Hypervisor network labels and Apstra fabric virtual-network connectivity must both represent the intended tenant service. The directly relevant unsafe shortcut is “Assume the virtualization manager's displayed port-group name automatically configures leaf networking”.

D:

The option “Assume a unique VLAN number alone guarantees Layer 3 tenant isolation” is useful in a different setting: A development VN is accidentally assigned to the wrong routing zone during a project migration. The case being tested is: A VMware workload migration succeeds at compute level but its new host port cannot reach the expected tenant virtual network. Hypervisor network labels and Apstra fabric virtual-network connectivity must both represent the intended tenant service. The directly relevant unsafe shortcut is “Assume the virtualization manager's displayed port-group name automatically configures leaf networking”.

Question 212

An EVPN network learns a host MAC address and associated IP binding from a remote VTEP. Which design or operational principle best explains this behavior?

  1. EVPN Type 5 IP prefix routes represent routed IP reachability, complementing Type 2 endpoint advertisements.
  2. Matching import and export policy for the intended virtual network governs whether EVPN route distribution creates usable reachability.
  3. EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning.
  4. EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability.

Explanation

Correct Answer

C:

EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning. Here, an EVPN network learns a host MAC address and associated IP binding from a remote VTEP. A useful discriminating check is to inspect the EVPN route database for Type 2 MAC or MAC-IP advertisements and associated VNI or next hop.

Incorrect Answers

A:

The option “EVPN Type 5 IP prefix routes represent routed IP reachability, complementing Type 2 endpoint advertisements” is useful in a different setting: A fabric exchanges IP prefixes between tenant routing zones without requiring every remote subnet to be represented as an individual MAC. The case being tested is: An EVPN network learns a host MAC address and associated IP binding from a remote VTEP. EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning. The controlling principle is “EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning”.

B:

“Matching import and export policy for the intended virtual network governs whether EVPN route distribution creates usable reachability” 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: An EVPN network learns a host MAC address and associated IP binding from a remote VTEP. EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning. The controlling principle is “EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning”.

D:

“EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability” is associated with a distinct issue: An EVPN multihomed endpoint exhibits unstable forwarding after both attachment leafs advertise the same segment independently. By contrast, the actual problem is: An EVPN network learns a host MAC address and associated IP binding from a remote VTEP. EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning. The controlling principle is “EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning”.

Question 213

Two tenants require a controlled shared service, and a proposal suggests importing every route into each tenant VRF. Which initial check would most directly distinguish the likely cause?

  1. Inspect DCI route targets, participating VN or VRF memberships and cross-site advertisements.
  2. Inspect the proposed external or shared-services routing path, import policy and required security controls.
  3. Compare the host attachment, hypervisor port-group mapping and Apstra VN or connectivity-template assignment.
  4. Inspect border-leaf interfaces, attached connectivity template and tenant-specific routing policy.

Explanation

Correct Answer

B:

This checks the relevant evidence first: inspect the proposed external or shared-services routing path, import policy and required security controls. The underlying concept is that shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation. After confirming the finding, a controlled remediation is to create a controlled service insertion or external routing policy permitting only approved shared-service prefixes.

Incorrect Answers

A:

“Inspect DCI route targets, participating VN or VRF memberships and cross-site advertisements” is associated with a distinct issue: A data-center interconnect extends selected tenant segments between two sites but one site imports unrelated virtual networks. By contrast, the actual problem is: Two tenants require a controlled shared service, and a proposal suggests importing every route into each tenant VRF. The relevant inspection is: Inspect the proposed external or shared-services routing path, import policy and required security controls. The most discriminating first check is “Inspect the proposed external or shared-services routing path, import policy and required security controls”.

C:

“Compare the host attachment, hypervisor port-group mapping and Apstra VN or connectivity-template assignment” is relevant to a different condition: A VMware workload migration succeeds at compute level but its new host port cannot reach the expected tenant virtual network. The stated question instead concerns: Two tenants require a controlled shared service, and a proposal suggests importing every route into each tenant VRF. The relevant inspection is: Inspect the proposed external or shared-services routing path, import policy and required security controls. The most discriminating first check is “Inspect the proposed external or shared-services routing path, import policy and required security controls”.

D:

That choice—“Inspect border-leaf interfaces, attached connectivity template and tenant-specific routing policy”—addresses this other problem: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Here the scenario is: Two tenants require a controlled shared service, and a proposal suggests importing every route into each tenant VRF. The relevant inspection is: Inspect the proposed external or shared-services routing path, import policy and required security controls. The most discriminating first check is “Inspect the proposed external or shared-services routing path, import policy and required security controls”.

Question 214

A generic system connects to a leaf with one untagged network and a small approved list of tagged VNs. Which controlled change best addresses the described requirement?

  1. Create or correct a scoped connectivity template and routing policy for the authorized VRF.
  2. Constrain the external peering policy to explicitly permitted prefixes and verify intended attachment.
  3. Apply documented DCI policies for only authorized tenant prefixes and virtual-network reachability.
  4. Bind only authorized tagged and untagged VN attachments to the selected generic-system port.

Explanation

Correct Answer

D:

This action addresses the stated defect: bind only authorized tagged and untagged VN attachments to the selected generic-system port. The underlying constraint is that connectivity templates define host-facing virtual-network endpoint membership and tagging behavior. Verify rather than assume success: confirm the host receives exactly the intended VLANs and no unrelated tenant traffic.

Incorrect Answers

A:

That choice—“Create or correct a scoped connectivity template and routing policy for the authorized VRF”—addresses this other problem: A routed external firewall must exchange routes with a border leaf for only one tenant VRF. Here the scenario is: A generic system connects to a leaf with one untagged network and a small approved list of tagged VNs. Bind only authorized tagged and untagged VN attachments to the selected generic-system port. The most relevant correction is “Bind only authorized tagged and untagged VN attachments to the selected generic-system port”.

B:

“Constrain the external peering policy to explicitly permitted prefixes and verify intended attachment” 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 generic system connects to a leaf with one untagged network and a small approved list of tagged VNs. Bind only authorized tagged and untagged VN attachments to the selected generic-system port. The most relevant correction is “Bind only authorized tagged and untagged VN attachments to the selected generic-system port”.

C:

The option “Apply documented DCI policies for only authorized tenant prefixes and virtual-network reachability” is useful in a different setting: A data-center interconnect extends selected tenant segments between two sites but one site imports unrelated virtual networks. The case being tested is: A generic system connects to a leaf with one untagged network and a small approved list of tagged VNs. Bind only authorized tagged and untagged VN attachments to the selected generic-system port. The most relevant correction is “Bind only authorized tagged and untagged VN attachments to the selected generic-system port”.

Question 215

A Juniper Apstra controller is restored following a failure and some device configurations no longer match its database. Which controlled change best addresses the described requirement?

  1. Restore the supported device-agent connection and management credentials without bypassing security checks.
  2. Grant the minimum documented blueprint role permissions through the approved access-review process.
  3. Coordinate change ownership and apply role or process controls to prevent conflicting unreviewed commits.
  4. Use the documented recovery and reconciliation procedure before attempting broad deployment changes.

Explanation

Correct Answer

D:

This action addresses the stated defect: use the documented recovery and reconciliation procedure before attempting broad deployment changes. The underlying constraint is that the controller's intended blueprint state and deployed device configurations must be reconciled after an out-of-band restore. Verify rather than assume success: confirm intended and running configurations are consistent and the fabric's critical paths remain operational.

Incorrect Answers

A:

“Restore the supported device-agent connection and management credentials without bypassing security checks” is relevant to a different condition: A managed leaf is physically reachable but its Apstra device agent no longer reports state to the controller. The stated question instead concerns: A Juniper Apstra controller is restored following a failure and some device configurations no longer match its database. The governing requirement is to use the documented recovery and reconciliation procedure before attempting broad deployment changes. The most relevant correction is “Use the documented recovery and reconciliation procedure before attempting broad deployment changes”.

B:

That choice—“Grant the minimum documented blueprint role permissions through the approved access-review process”—addresses this other problem: A new operations account can open the Apstra UI yet receives authorization errors when trying to manage device blueprints. Here the scenario is: A Juniper Apstra controller is restored following a failure and some device configurations no longer match its database. The governing requirement is to use the documented recovery and reconciliation procedure before attempting broad deployment changes. The most relevant correction is “Use the documented recovery and reconciliation procedure before attempting broad deployment changes”.

C:

“Coordinate change ownership and apply role or process controls to prevent conflicting unreviewed commits” is associated with a distinct issue: Two on-call staff attempt to stage modifications for the same fabric without a documented approval process. By contrast, the actual problem is: A Juniper Apstra controller is restored following a failure and some device configurations no longer match its database. The governing requirement is to use the documented recovery and reconciliation procedure before attempting broad deployment changes. The most relevant correction is “Use the documented recovery and reconciliation procedure before attempting broad deployment changes”.

Question 216

A large fabric includes many repeated physical device names and an operator needs the exact topology relationship for one rack. Which design or operational principle best explains this behavior?

  1. Graph Explorer and relationship-aware graph queries help identify modeled nodes and edges within a blueprint.
  2. Apstra graph queries can combine object attributes and topological relationships for precise selection.
  3. Graph query results reflect the modeled topology and may reveal missing or misassigned relationships that need validation.
  4. Graph and probe context can correlate multiple anomalies to a shared physical or logical source.

Explanation

Correct Answer

A:

graph Explorer and relationship-aware graph queries help identify modeled nodes and edges within a blueprint. Here, a large fabric includes many repeated physical device names and an operator needs the exact topology relationship for one rack. A useful discriminating check is to inspect the graph query's node types, filters and returned relationship paths for the intended rack.

Incorrect Answers

B:

“Apstra graph queries can combine object attributes and topological relationships for precise selection” is relevant to a different condition: A team needs to locate generic systems attached to leafs in a single application tag group. The stated question instead concerns: A large fabric includes many repeated physical device names and an operator needs the exact topology relationship for one rack. Graph Explorer and relationship-aware graph queries help identify modeled nodes and edges within a blueprint. The controlling principle is “Graph Explorer and relationship-aware graph queries help identify modeled nodes and edges within a blueprint”.

C:

That choice—“Graph query results reflect the modeled topology and may reveal missing or misassigned relationships that need validation”—addresses this other problem: An Apstra graph search reveals a workload object disconnected from its expected virtual-network relation. Here the scenario is: A large fabric includes many repeated physical device names and an operator needs the exact topology relationship for one rack. Graph Explorer and relationship-aware graph queries help identify modeled nodes and edges within a blueprint. The controlling principle is “Graph Explorer and relationship-aware graph queries help identify modeled nodes and edges within a blueprint”.

D:

“Graph and probe context can correlate multiple anomalies to a shared physical or logical source” is associated with a distinct issue: A site sees hundreds of anomaly events from one failing uplink and wants to distinguish one root cause from many symptoms. By contrast, the actual problem is: A large fabric includes many repeated physical device names and an operator needs the exact topology relationship for one rack. Graph Explorer and relationship-aware graph queries help identify modeled nodes and edges within a blueprint. The controlling principle is “Graph Explorer and relationship-aware graph queries help identify modeled nodes and edges within a blueprint”.

Question 217

A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. 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. Confirm each leaf reaches other leaves via expected spine paths and no unintended data-center transit loops exist.
  3. Demonstrate aggregate load sharing across many five-tuple flows while a single flow remains stable on one path.
  4. Observe established underlay peers and reachability of every intended VTEP loopback before testing virtual networks.

Explanation

Correct Answer

B:

This directly tests the desired result: confirm each leaf reaches other leaves via expected spine paths and no unintended data-center transit loops exist. The decisive investigation is to compare the proposed physical topology with the selected reference design and expected leaf-spine connectivity. The governing principle is that in a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling.

Incorrect Answers

A:

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

C:

“Demonstrate aggregate load sharing across many five-tuple flows while a single flow remains stable on one path” is relevant to a different condition: An operator finds two equal-cost fabric paths but a single large traffic flow consistently traverses only one link. The stated question instead concerns: A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. In a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling. The direct acceptance evidence is “Confirm each leaf reaches other leaves via expected spine paths and no unintended data-center transit loops exist”.

D:

That choice—“Observe established underlay peers and reachability of every intended VTEP loopback before testing virtual networks”—addresses this other problem: A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. Here the scenario is: A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. In a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling. The direct acceptance evidence is “Confirm each leaf reaches other leaves via expected spine paths and no unintended data-center transit loops exist”.

Question 218

A development VN is accidentally assigned to the wrong routing zone during a project migration. Which evidence most directly verifies the intended network outcome?

  1. Confirm each tenant uses its own routing table and no unapproved inter-tenant connectivity occurs.
  2. Confirm both VN endpoints are isolated at Layer 2 but routed according to tenant policy within the VRF.
  3. Confirm the application subnet uses the expected tenant VRF and other tenants remain isolated.
  4. Confirm migrated VMs communicate over the intended tenant VN while unauthorized networks remain unreachable.

Explanation

Correct Answer

C:

This directly tests the desired result: confirm the application subnet uses the expected tenant VRF and other tenants remain isolated. The decisive investigation is to inspect the VN's routing-zone binding, SVI and VRF route lookup on the affected leaf. The governing principle is that a virtual network's routed gateway and routing-zone association determine its Layer 3 tenant boundary.

Incorrect Answers

A:

That choice—“Confirm each tenant uses its own routing table and no unapproved inter-tenant connectivity occurs”—addresses this other problem: Two tenants require identical subnet ranges in a shared physical fabric while remaining isolated. Here the scenario is: A development VN is accidentally assigned to the wrong routing zone during a project migration. A virtual network's routed gateway and routing-zone association determine its Layer 3 tenant boundary. The direct acceptance evidence is “Confirm the application subnet uses the expected tenant VRF and other tenants remain isolated”.

B:

“Confirm both VN endpoints are isolated at Layer 2 but routed according to tenant policy within the VRF” is associated with a distinct issue: A user asks whether a single tenant routing zone can include multiple Layer 2 VNs attached to different racks. By contrast, the actual problem is: A development VN is accidentally assigned to the wrong routing zone during a project migration. A virtual network's routed gateway and routing-zone association determine its Layer 3 tenant boundary. The direct acceptance evidence is “Confirm the application subnet uses the expected tenant VRF and other tenants remain isolated”.

D:

“Confirm migrated VMs communicate over the intended tenant VN while unauthorized networks remain unreachable” is relevant to a different condition: A VMware workload migration succeeds at compute level but its new host port cannot reach the expected tenant virtual network. The stated question instead concerns: A development VN is accidentally assigned to the wrong routing zone during a project migration. A virtual network's routed gateway and routing-zone association determine its Layer 3 tenant boundary. The direct acceptance evidence is “Confirm the application subnet uses the expected tenant VRF and other tenants remain isolated”.

Question 219

A server's VLAN 210 is accidentally bound to the wrong VXLAN segment on one leaf. Which evidence most directly verifies the intended network outcome?

  1. Observe valid endpoint advertisements with less dependence on unknown-destination flooding for known endpoints.
  2. Confirm representative maximum-size payloads traverse the VXLAN overlay without fragmentation-related drops.
  3. Confirm encapsulated packets reach the intended VTEP and are decapsulated to the authorized bridge domain.
  4. Verify same-tenant endpoints communicate and traffic is not delivered to the unrelated tenant VNI.

Explanation

Correct Answer

D:

This directly tests the desired result: verify same-tenant endpoints communicate and traffic is not delivered to the unrelated tenant VNI. The decisive investigation is to inspect the VLAN-to-VNI bindings on both local and remote VTEPs and compare the blueprint virtual-network intent. The governing principle is that the VNI associates overlay VXLAN traffic with the intended virtual network, so inconsistent VLAN-to-VNI mapping breaks isolation or connectivity.

Incorrect Answers

A:

“Observe valid endpoint advertisements with less dependence on unknown-destination flooding for known endpoints” 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 server's VLAN 210 is accidentally bound to the wrong VXLAN segment on one leaf. The VNI associates overlay VXLAN traffic with the intended virtual network, so inconsistent VLAN-to-VNI mapping breaks isolation or connectivity. The direct acceptance evidence is “Verify same-tenant endpoints communicate and traffic is not delivered to the unrelated tenant VNI”.

B:

That choice—“Confirm representative maximum-size payloads traverse the VXLAN overlay without fragmentation-related drops”—addresses this other problem: An east-west application works without tunneling but drops large payloads after VXLAN overlay migration. Here the scenario is: A server's VLAN 210 is accidentally bound to the wrong VXLAN segment on one leaf. The VNI associates overlay VXLAN traffic with the intended virtual network, so inconsistent VLAN-to-VNI mapping breaks isolation or connectivity. The direct acceptance evidence is “Verify same-tenant endpoints communicate and traffic is not delivered to the unrelated tenant VNI”.

C:

“Confirm encapsulated packets reach the intended VTEP and are decapsulated to the authorized bridge domain” is associated with a distinct issue: An endpoint's remote leaf cannot deliver traffic even though the local access VLAN is assigned correctly because the tunnel endpoint is unreachable. By contrast, the actual problem is: A server's VLAN 210 is accidentally bound to the wrong VXLAN segment on one leaf. The VNI associates overlay VXLAN traffic with the intended virtual network, so inconsistent VLAN-to-VNI mapping breaks isolation or connectivity. The direct acceptance evidence is “Verify same-tenant endpoints communicate and traffic is not delivered to the unrelated tenant VNI”.

Question 220

A server VLAN is created on two racks but remote EVPN routes cannot be imported because their route targets do not align. Which design or operational principle best explains this behavior?

  1. EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution.
  2. EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning.
  3. EVPN Type 5 IP prefix routes represent routed IP reachability, complementing Type 2 endpoint advertisements.
  4. Matching import and export policy for the intended virtual network governs whether EVPN route distribution creates usable reachability.

Explanation

Correct Answer

D:

matching import and export policy for the intended virtual network governs whether EVPN route distribution creates usable reachability. Here, a server VLAN is created on two racks but remote EVPN routes cannot be imported because their route targets do not align. A useful discriminating check is to inspect per-VRF and per-virtual-network route target communities and import/export decisions.

Incorrect Answers

A:

The option “EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution” is useful in a different setting: Two tenants use overlapping private subnets and the team fears one tenant's routes will be mistaken for the other. The case being tested is: A server VLAN is created on two racks but remote EVPN routes cannot be imported because their route targets do not align. Matching import and export policy for the intended virtual network governs whether EVPN route distribution creates usable reachability. The controlling principle is “Matching import and export policy for the intended virtual network governs whether EVPN route distribution creates usable reachability”.

B:

“EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning” is relevant to a different condition: An EVPN network learns a host MAC address and associated IP binding from a remote VTEP. The stated question instead concerns: A server VLAN is created on two racks but remote EVPN routes cannot be imported because their route targets do not align. Matching import and export policy for the intended virtual network governs whether EVPN route distribution creates usable reachability. The controlling principle is “Matching import and export policy for the intended virtual network governs whether EVPN route distribution creates usable reachability”.

C:

That choice—“EVPN Type 5 IP prefix routes represent routed IP reachability, complementing Type 2 endpoint advertisements”—addresses this other problem: A fabric exchanges IP prefixes between tenant routing zones without requiring every remote subnet to be represented as an individual MAC. Here the scenario is: A server VLAN is created on two racks but remote EVPN routes cannot be imported because their route targets do not align. Matching import and export policy for the intended virtual network governs whether EVPN route distribution creates usable reachability. The controlling principle is “Matching import and export policy for the intended virtual network governs whether EVPN route distribution creates usable reachability”.

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