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 50

Question 490

A data center cabling plan repeats one spine endpoint for all redundant paths from a critical rack. Which controlled change best addresses the described requirement?

  1. Select a supported redundant leaf rack type and document host LAG or independent paths as appropriate.
  2. Expand spine capacity or rescope rack additions under a supported topology design.
  3. Create or select the approved reusable rack type and instantiate the rack consistently.
  4. Correct the cable plan to use approved physically independent spine paths.

Explanation

Correct Answer

D:

This action addresses the stated defect: correct the cable plan to use approved physically independent spine paths. The underlying constraint is that physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. Verify rather than assume success: validate intended path diversity against the generated cable map and a controlled spine failure test.

Incorrect Answers

A:

That choice—“Select a supported redundant leaf rack type and document host LAG or independent paths as appropriate”—addresses this other problem: A rack designer wants a redundant host attachment pattern for critical appliances. Here the scenario is: A data center cabling plan repeats one spine endpoint for all redundant paths from a critical rack. Correct the cable plan to use approved physically independent spine paths. The most relevant correction is “Correct the cable plan to use approved physically independent spine paths”.

B:

“Expand spine capacity or rescope rack additions under a supported topology design” is associated with a distinct issue: A new tenant floor requests six leaf uplinks but fabric spines are fully committed to existing racks. By contrast, the actual problem is: A data center cabling plan repeats one spine endpoint for all redundant paths from a critical rack. Correct the cable plan to use approved physically independent spine paths. The most relevant correction is “Correct the cable plan to use approved physically independent spine paths”.

C:

The option “Create or select the approved reusable rack type and instantiate the rack consistently” is useful in a different setting: A new leaf rack should use a repeatable single-leaf topology but its manually modeled connections differ from existing identical racks. The case being tested is: A data center cabling plan repeats one spine endpoint for all redundant paths from a critical rack. Correct the cable plan to use approved physically independent spine paths. The most relevant correction is “Correct the cable plan to use approved physically independent spine paths”.

Question 491

A generic system connects to a leaf with one untagged network and a small approved list of tagged VNs. Which initial check would most directly distinguish the likely cause?

  1. Inspect border-leaf interfaces, attached connectivity template and tenant-specific routing policy.
  2. Inspect the generic-system interface and assigned VN tagging primitives in the relevant connectivity template.
  3. Inspect the route export/import policy and observed advertised routes for the affected VRF.
  4. Compare the host attachment, hypervisor port-group mapping and Apstra VN or connectivity-template assignment.

Explanation

Correct Answer

B:

This checks the relevant evidence first: inspect the generic-system interface and assigned VN tagging primitives in the relevant connectivity template. The underlying concept is that connectivity templates define host-facing virtual-network endpoint membership and tagging behavior. After confirming the finding, a controlled remediation is to bind only authorized tagged and untagged VN attachments to the selected generic-system port.

Incorrect Answers

A:

“Inspect border-leaf interfaces, attached connectivity template and tenant-specific routing policy” is relevant to a different condition: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. The stated question instead concerns: A generic system connects to a leaf with one untagged network and a small approved list of tagged VNs. The relevant inspection is: Inspect the generic-system interface and assigned VN tagging primitives in the relevant connectivity template. The most discriminating first check is “Inspect the generic-system interface and assigned VN tagging primitives in the relevant connectivity template”.

C:

“Inspect the route export/import policy and observed advertised routes for the affected VRF” is associated with a distinct issue: A route export template applied to a border device advertises all tenant prefixes beyond the data center. 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. The relevant inspection is: Inspect the generic-system interface and assigned VN tagging primitives in the relevant connectivity template. The most discriminating first check is “Inspect the generic-system interface and assigned VN tagging primitives in the relevant connectivity template”.

D:

The option “Compare the host attachment, hypervisor port-group mapping and Apstra VN or connectivity-template assignment” is useful in a different setting: A virtualized server moves to another rack and vCenter shows the correct network label while the fabric lacks the required VN attachment. The case being tested is: A generic system connects to a leaf with one untagged network and a small approved list of tagged VNs. The relevant inspection is: Inspect the generic-system interface and assigned VN tagging primitives in the relevant connectivity template. The most discriminating first check is “Inspect the generic-system interface and assigned VN tagging primitives in the relevant connectivity template”.

Question 492

A team needs to group rack devices for maintenance based on operational ownership without renaming every node. Which design or operational principle best explains this behavior?

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

Explanation

Correct Answer

A:

Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity. Here, a team needs to group rack devices for maintenance based on operational ownership without renaming every node. A useful discriminating check is to inspect object tags and query results before selecting the intended device set.

Incorrect Answers

B:

“Logical device definitions represent required interface roles and capacities, independent of hardware SKU details” is relevant to a different condition: A rack template chooses a logical device with insufficient server ports for its planned generic systems. The stated question instead concerns: A team needs to group rack devices for maintenance based on operational ownership without renaming every node. Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity. The controlling principle is “Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity”.

C:

That choice—“Resource pools need sufficient unique allocations for loopback, fabric subnet and other network identifiers”—addresses this other problem: A new blueprint assigns every VTEP from a resource pool that is too small for the proposed rack count. Here the scenario is: A team needs to group rack devices for maintenance based on operational ownership without renaming every node. Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity. The controlling principle is “Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity”.

D:

“Managed VNI and other logical resource pools reduce collision risk when correctly partitioned and allocated” is associated with a distinct issue: An expansion accidentally reuses a virtual network identifier assigned to another isolated overlay segment. By contrast, the actual problem is: A team needs to group rack devices for maintenance based on operational ownership without renaming every node. Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity. The controlling principle is “Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity”.

Question 493

An engineer wants both endpoint reachability and aggregated routed prefixes but is uncertain which EVPN routes serve each purpose. Which controlled change best addresses the described requirement?

  1. Implement an authorized distributed gateway design and ensure the overlay advertises the required endpoint or prefix routes.
  2. Align the authorized distributed gateway configuration across participating VTEPs.
  3. Advertise and import the required host or prefix routes according to the approved ERB routing design.
  4. Correct prefix export/import and next-hop resolution for the routed EVPN IP prefix.

Explanation

Correct Answer

C:

This action addresses the stated defect: advertise and import the required host or prefix routes according to the approved ERB routing design. The underlying constraint is that EVPN endpoint and routed-prefix reachability use different route types and their import policy must match the data path. Verify rather than assume success: confirm both host resolution and inter-subnet routed reachability use the expected EVPN routes.

Incorrect Answers

A:

“Implement an authorized distributed gateway design and ensure the overlay advertises the required endpoint or prefix routes” is associated with a distinct issue: An architect wants gateway functions distributed across tenant leafs in an EVPN-VXLAN fabric. By contrast, the actual problem is: An engineer wants both endpoint reachability and aggregated routed prefixes but is uncertain which EVPN routes serve each purpose. Advertise and import the required host or prefix routes according to the approved ERB routing design. The most relevant correction is “Advertise and import the required host or prefix routes according to the approved ERB routing design”.

B:

The option “Align the authorized distributed gateway configuration across participating VTEPs” is useful in a different setting: An anycast gateway design uses inconsistent SVI gateway parameters on two participating leafs. The case being tested is: An engineer wants both endpoint reachability and aggregated routed prefixes but is uncertain which EVPN routes serve each purpose. Advertise and import the required host or prefix routes according to the approved ERB routing design. The most relevant correction is “Advertise and import the required host or prefix routes according to the approved ERB routing design”.

D:

That choice—“Correct prefix export/import and next-hop resolution for the routed EVPN IP prefix”—addresses this other problem: A fabric exchanges IP prefixes between tenant routing zones without requiring every remote subnet to be represented as an individual MAC. Here the scenario is: An engineer wants both endpoint reachability and aggregated routed prefixes but is uncertain which EVPN routes serve each purpose. Advertise and import the required host or prefix routes according to the approved ERB routing design. The most relevant correction is “Advertise and import the required host or prefix routes according to the approved ERB routing design”.

Question 494

A dual leaf rack is expected to provide application diversity but both uplinks terminate on the same physical spine. Which shortcut would be most likely to undermine this objective?

  1. Label a single-leaf rack as redundant merely because it has two host-facing ports.
  2. Create a new ad hoc rack type for every identical rack without checking design drift.
  3. Ignore port and oversubscription limits because Apstra can generate logical connections automatically.
  4. Count two cables as independent redundancy even when both share the same single upstream switch.

Explanation

Correct Answer

D:

This is the unsafe shortcut to avoid: count two cables as independent redundancy even when both share the same single upstream switch. It violates the principle that physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. An appropriate alternative is to correct the cable plan to use approved physically independent spine paths.

Incorrect Answers

A:

That choice—“Label a single-leaf rack as redundant merely because it has two host-facing ports”—addresses this other problem: A storage workload requires dual-homed servers but a proposed rack type provides only one access leaf. Here the scenario is: A dual leaf rack is expected to provide application diversity but both uplinks terminate on the same physical spine. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. The directly relevant unsafe shortcut is “Count two cables as independent redundancy even when both share the same single upstream switch”.

B:

“Create a new ad hoc rack type for every identical rack without checking design drift” is associated with a distinct issue: A new leaf rack should use a repeatable single-leaf topology but its manually modeled connections differ from existing identical racks. By contrast, the actual problem is: A dual leaf rack is expected to provide application diversity but both uplinks terminate on the same physical spine. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. The directly relevant unsafe shortcut is “Count two cables as independent redundancy even when both share the same single upstream switch”.

C:

The option “Ignore port and oversubscription limits because Apstra can generate logical connections automatically” 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 dual leaf rack is expected to provide application diversity but both uplinks terminate on the same physical spine. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. The directly relevant unsafe shortcut is “Count two cables as independent redundancy even when both share the same single upstream switch”.

Question 495

An Apstra dashboard shows probe anomalies while fabric service topology and device reachability stay normal. Which evidence most directly verifies the intended network outcome?

  1. Verify objective service and interface measurements improve and a valid probe no longer detects an anomaly.
  2. Confirm the root metric stabilizes and correlated anomalies across dependent probes clear.
  3. Confirm only the intended rack or tenant objects generate results and anomalies on repeat tests.
  4. Confirm latency measurements and anomaly state return within accepted bounds under representative traffic.

Explanation

Correct Answer

D:

This directly tests the desired result: confirm latency measurements and anomaly state return within accepted bounds under representative traffic. The decisive investigation is to inspect affected probe stages, timestamps and source telemetry along the application path. The governing principle is that analytics anomalies can indicate measured performance deviations that do not coincide with configuration intent mismatches.

Incorrect Answers

A:

“Verify objective service and interface measurements improve and a valid probe no longer detects an anomaly” is relevant to a different condition: A data center dashboard becomes green immediately after an engineer increases alert thresholds without addressing failing application traffic. The stated question instead concerns: An Apstra dashboard shows probe anomalies while fabric service topology and device reachability stay normal. Analytics anomalies can indicate measured performance deviations that do not coincide with configuration intent mismatches. The direct acceptance evidence is “Confirm latency measurements and anomaly state return within accepted bounds under representative traffic”.

B:

That choice—“Confirm the root metric stabilizes and correlated anomalies across dependent probes clear”—addresses this other problem: An operations team receives repeated probe-stage alerts after an optic begins incrementing errors. Here the scenario is: An Apstra dashboard shows probe anomalies while fabric service topology and device reachability stay normal. Analytics anomalies can indicate measured performance deviations that do not coincide with configuration intent mismatches. The direct acceptance evidence is “Confirm latency measurements and anomaly state return within accepted bounds under representative traffic”.

C:

“Confirm only the intended rack or tenant objects generate results and anomalies on repeat tests” is associated with a distinct issue: A built-in analytics probe reports a metric but cannot identify why the value changed after a rack migration. By contrast, the actual problem is: An Apstra dashboard shows probe anomalies while fabric service topology and device reachability stay normal. Analytics anomalies can indicate measured performance deviations that do not coincide with configuration intent mismatches. The direct acceptance evidence is “Confirm latency measurements and anomaly state return within accepted bounds under representative traffic”.

Question 496

An EVPN multihomed endpoint exhibits unstable forwarding after both attachment leafs advertise the same segment independently. Which evidence most directly verifies the intended network outcome?

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

Explanation

Correct Answer

D:

This directly tests the desired result: confirm stable multihoming advertisements and appropriate forwarding when each server attachment is tested. The decisive investigation is to inspect Ethernet segment identifiers, multihoming state and designated-forwarder election on the relevant leafs. The governing principle is that EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability.

Incorrect Answers

A:

The option “Confirm the remote VTEP has a correctly imported Type 2 endpoint route and can deliver host traffic” is useful in a different setting: A leaf needs to advertise a workload endpoint location to remote EVPN participants across the VXLAN fabric. The case being tested is: An EVPN multihomed endpoint exhibits unstable forwarding after both attachment leafs advertise the same segment independently. EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability. The direct acceptance evidence is “Confirm stable multihoming advertisements and appropriate forwarding when each server attachment is tested”.

B:

“Observe valid imported EVPN routes and bidirectional host reachability only within the authorized virtual network” is relevant to a different condition: Two leaves advertise the same virtual network yet one leaf rejects the other's EVPN MAC routes. The stated question instead concerns: An EVPN multihomed endpoint exhibits unstable forwarding after both attachment leafs advertise the same segment independently. EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability. The direct acceptance evidence is “Confirm stable multihoming advertisements and appropriate forwarding when each server attachment is tested”.

C:

That choice—“Confirm the destination subnet appears as an imported Type 5 route and routes end-to-end in the intended VRF”—addresses this other problem: An operator advertises an external IPv4 subnet into an EVPN routing domain for routed reachability. Here the scenario is: An EVPN multihomed endpoint exhibits unstable forwarding after both attachment leafs advertise the same segment independently. EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability. The direct acceptance evidence is “Confirm stable multihoming advertisements and appropriate forwarding when each server attachment is tested”.

Question 497

A team needs to roll out a fabric change safely but its change record mixes staging a modification with committing the active state. Which shortcut would be most likely to undermine this objective?

  1. Treat the existence of a rendered config file as proof of deployment to every switch.
  2. Skip diff review and declare the change complete as soon as the design editor saves it.
  3. Assume every configuration view is identical and blindly paste one into the device CLI.
  4. Swap arbitrary port assignments in production without reviewing topology role requirements.

Explanation

Correct Answer

B:

This is the unsafe shortcut to avoid: skip diff review and declare the change complete as soon as the design editor saves it. It violates the principle that controlled build and deploy phases separate design validation, reviewed staged changes and active device updates. An appropriate alternative is to review the changes, commit the authorized revision and monitor the resulting device deployments.

Incorrect Answers

A:

“Treat the existence of a rendered config file as proof of deployment to every switch” is associated with a distinct issue: A design is staged and rendered correctly, but a production switch still uses the previous running configuration. By contrast, the actual problem is: A team needs to roll out a fabric change safely but its change record mixes staging a modification with committing the active state. Controlled build and deploy phases separate design validation, reviewed staged changes and active device updates. The directly relevant unsafe shortcut is “Skip diff review and declare the change complete as soon as the design editor saves it”.

C:

“Assume every configuration view is identical and blindly paste one into the device CLI” is relevant to a different condition: An operations team must compare pristine, incremental and rendered configuration views before a planned device update. The stated question instead concerns: A team needs to roll out a fabric change safely but its change record mixes staging a modification with committing the active state. Controlled build and deploy phases separate design validation, reviewed staged changes and active device updates. The directly relevant unsafe shortcut is “Skip diff review and declare the change complete as soon as the design editor saves it”.

D:

That choice—“Swap arbitrary port assignments in production without reviewing topology role requirements”—addresses this other problem: A staging team has different cable-map snapshots from design and observed discovery data. Here the scenario is: A team needs to roll out a fabric change safely but its change record mixes staging a modification with committing the active state. Controlled build and deploy phases separate design validation, reviewed staged changes and active device updates. The directly relevant unsafe shortcut is “Skip diff review and declare the change complete as soon as the design editor saves it”.

Question 498

A design template was edited after the first rack was built and an engineer assumes existing active blueprints are retroactively rewritten. Which controlled change best addresses the described requirement?

  1. Extend the approved blueprint design to include appropriate border connectivity and associated resources.
  2. Resolve the specific design and resource conflicts and regenerate intended configuration.
  3. Choose an officially supported template and platform combination and regenerate the blueprint configuration.
  4. Stage and review each intended blueprint update through an approved migration or change process.

Explanation

Correct Answer

D:

This action addresses the stated defect: stage and review each intended blueprint update through an approved migration or change process. The underlying constraint is that blueprint design inheritance and change management must be validated; editing a design object does not prove all deployed fabrics changed. Verify rather than assume success: confirm each targeted blueprint reflects the expected revision and existing production services remain healthy.

Incorrect Answers

A:

That choice—“Extend the approved blueprint design to include appropriate border connectivity and associated resources”—addresses this other problem: An engineer finishes a fabric template without any modeled north-south peering attachment points. 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. Stage and review each intended blueprint update through an approved migration or change process. The most relevant correction is “Stage and review each intended blueprint update through an approved migration or change process”.

B:

“Resolve the specific design and resource conflicts and regenerate intended configuration” is associated with a distinct issue: An Apstra designer tries to deploy a rack without allocating required underlay interface and IP pools. By contrast, the actual problem is: A design template was edited after the first rack was built and an engineer assumes existing active blueprints are retroactively rewritten. Stage and review each intended blueprint update through an approved migration or change process. The most relevant correction is “Stage and review each intended blueprint update through an approved migration or change process”.

C:

The option “Choose an officially supported template and platform combination and regenerate the blueprint configuration” is useful in a different setting: A blueprint uses a template intended for a different network OS and generated configuration contains unsupported syntax. 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. Stage and review each intended blueprint update through an approved migration or change process. The most relevant correction is “Stage and review each intended blueprint update through an approved migration or change process”.

Question 499

A historical revision would restore a system ID that has been reassigned to another device since it was first recorded. Which controlled change best addresses the described requirement?

  1. Select the approved prior revision, review resulting uncommitted differences and commit the rollback following change control.
  2. Resolve outstanding staged work, then perform the approved Time Voyager workflow.
  3. Resolve conflicting device and resource mappings before committing a controlled rollback.
  4. Revert the specific uncommitted edit rather than rolling back an unrelated committed revision.

Explanation

Correct Answer

C:

This action addresses the stated defect: resolve conflicting device and resource mappings before committing a controlled rollback. The underlying constraint is that Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory. Verify rather than assume success: prove the revised blueprint builds with valid allocations and switches converge on intended active state.

Incorrect Answers

A:

“Select the approved prior revision, review resulting uncommitted differences and commit the rollback following change control” 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 historical revision would restore a system ID that has been reassigned to another device since it was first recorded. Resolve conflicting device and resource mappings before committing a controlled rollback. The most relevant correction is “Resolve conflicting device and resource mappings before committing a controlled rollback”.

B:

That choice—“Resolve outstanding staged work, then perform the approved Time Voyager workflow”—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. Resolve conflicting device and resource mappings before committing a controlled rollback. The most relevant correction is “Resolve conflicting device and resource mappings before committing a controlled rollback”.

D:

The option “Revert the specific uncommitted edit rather than rolling back an unrelated committed 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. Resolve conflicting device and resource mappings before committing a controlled rollback. The most relevant correction is “Resolve conflicting device and resource mappings before committing a controlled rollback”.

Question 500

Two tenants use overlapping private subnets and the team fears one tenant's routes will be mistaken for the other. Which evidence most directly verifies the intended network outcome?

  1. Observe valid imported EVPN routes and bidirectional host reachability only within the authorized virtual network.
  2. Confirm the destination subnet appears as an imported Type 5 route and routes end-to-end in the intended VRF.
  3. Confirm the remote VTEP has a correctly imported Type 2 endpoint route and can deliver host traffic.
  4. Observe each VRF learns only the intended tenant routes despite overlapping address space.

Explanation

Correct Answer

D:

This directly tests the desired result: observe each VRF learns only the intended tenant routes despite overlapping address space. The decisive investigation is to compare route distinguishers, route targets and actual VRF import policy for each tenant. The governing principle is that EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution.

Incorrect Answers

A:

The option “Observe valid imported EVPN routes and bidirectional host reachability only within the authorized virtual network” is useful in a different setting: Two leaves advertise the same virtual network yet one leaf rejects the other's EVPN MAC routes. The case being tested is: Two tenants use overlapping private subnets and the team fears one tenant's routes will be mistaken for the other. EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution. The direct acceptance evidence is “Observe each VRF learns only the intended tenant routes despite overlapping address space”.

B:

“Confirm the destination subnet appears as an imported Type 5 route and routes end-to-end in the intended VRF” is relevant to a different condition: A fabric exchanges IP prefixes between tenant routing zones without requiring every remote subnet to be represented as an individual MAC. The stated question instead concerns: Two tenants use overlapping private subnets and the team fears one tenant's routes will be mistaken for the other. EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution. The direct acceptance evidence is “Observe each VRF learns only the intended tenant routes despite overlapping address space”.

C:

That choice—“Confirm the remote VTEP has a correctly imported Type 2 endpoint route and can deliver host traffic”—addresses this other problem: An EVPN network learns a host MAC address and associated IP binding from a remote VTEP. Here the scenario is: Two tenants use overlapping private subnets and the team fears one tenant's routes will be mistaken for the other. EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution. The direct acceptance evidence is “Observe each VRF learns only the intended tenant routes despite overlapping address space”.

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