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 77

Question 760

A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Which shortcut would be most likely to undermine this objective?

  1. Announce every local routing-zone prefix to all external peers instead of reviewing policy.
  2. Configure every virtual network as a tagged VLAN on the server trunk for convenience.
  3. Enable unrestricted route redistribution for every tenant to make a single external peering session work.
  4. Create an unrelated VRF for each VLAN without validating the tenant's routing requirements.

Explanation

Correct Answer

C:

This is the unsafe shortcut to avoid: enable unrestricted route redistribution for every tenant to make a single external peering session work. It violates the principle that connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. An appropriate alternative is to create or correct a scoped connectivity template and routing policy for the authorized VRF.

Incorrect Answers

A:

The option “Announce every local routing-zone prefix to all external peers instead of reviewing policy” is useful in a different setting: A route export template applied to a border device advertises all tenant prefixes beyond the data center. 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 directly relevant unsafe shortcut is “Enable unrestricted route redistribution for every tenant to make a single external peering session work”.

B:

“Configure every virtual network as a tagged VLAN on the server trunk for convenience” is relevant to a different condition: A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. 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 directly relevant unsafe shortcut is “Enable unrestricted route redistribution for every tenant to make a single external peering session work”.

D:

“Create an unrelated VRF for each VLAN without validating the tenant's routing requirements” is associated with a distinct issue: A multirack tenant needs two segmented application subnets while sharing a common VRF routing domain. 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 directly relevant unsafe shortcut is “Enable unrestricted route redistribution for every tenant to make a single external peering session work”.

Question 761

A new Apstra deployment includes baseline settings, platform-specific changes and generated overlay commands that an engineer wants to distinguish. 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. Delete the old blueprint and recreate every tenant because one hardware identifier changed.

Explanation

Correct Answer

C:

This is the unsafe shortcut to avoid: assume every configuration view is identical and blindly paste one into the device CLI. It violates the principle that configuration views represent different aspects of the managed device configuration and should be interpreted in their proper context. An appropriate alternative is to select the approved deployment or diagnostic view before reviewing and applying configuration diffs.

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 network engineer views valid proposed changes under Staged and mistakenly assumes all devices were updated. By contrast, the actual problem is: A new Apstra deployment includes baseline settings, platform-specific changes and generated overlay commands that an engineer wants to distinguish. Configuration views represent different aspects of the managed device configuration and should be interpreted in their proper context. The directly relevant unsafe shortcut is “Assume every configuration view is identical and blindly paste one into the device CLI”.

B:

The option “Skip diff review and declare the change complete as soon as the design editor saves it” is useful in a different setting: An Apstra operator wants to distinguish blueprint validation from the actual deployment to managed switches. The case being tested is: A new Apstra deployment includes baseline settings, platform-specific changes and generated overlay commands that an engineer wants to distinguish. Configuration views represent different aspects of the managed device configuration and should be interpreted in their proper context. The directly relevant unsafe shortcut is “Assume every configuration view is identical and blindly paste one into the device CLI”.

D:

That choice—“Delete the old blueprint and recreate every tenant because one hardware identifier changed”—addresses this other problem: A failed managed switch is swapped physically yet Apstra refuses deployment to the replacement inventory device. Here the scenario is: A new Apstra deployment includes baseline settings, platform-specific changes and generated overlay commands that an engineer wants to distinguish. Configuration views represent different aspects of the managed device configuration and should be interpreted in their proper context. The directly relevant unsafe shortcut is “Assume every configuration view is identical and blindly paste one into the device CLI”.

Question 762

An Apstra design runs out of loopback addresses when adding an additional leaf group. Which initial check would most directly distinguish the likely cause?

  1. Inspect object tags and query results before selecting the intended device set.
  2. Inspect pool size, consumed allocations and required identifiers for all logical devices.
  3. Check the VNI resource pool, existing reservations and intended tenant-to-VN mappings.
  4. Compare the selected logical device's interface count, speeds and connection roles with rack requirements.

Explanation

Correct Answer

B:

This checks the relevant evidence first: inspect pool size, consumed allocations and required identifiers for all logical devices. The underlying concept is that resource pools need sufficient unique allocations for loopback, fabric subnet and other network identifiers. After confirming the finding, a controlled remediation is to expand or assign a correctly scoped resource pool without overlapping existing allocations.

Incorrect Answers

A:

That choice—“Inspect object tags and query results before selecting the intended device set”—addresses this other problem: A team needs to group rack devices for maintenance based on operational ownership without renaming every node. Here the scenario is: An Apstra design runs out of loopback addresses when adding an additional leaf group. The relevant inspection is: Inspect pool size, consumed allocations and required identifiers for all logical devices. The most discriminating first check is “Inspect pool size, consumed allocations and required identifiers for all logical devices”.

C:

The option “Check the VNI resource pool, existing reservations and intended tenant-to-VN mappings” is useful in a different setting: A data center creates two tenants with conflicting VNI allocations despite using a shared Apstra resource service. The case being tested is: An Apstra design runs out of loopback addresses when adding an additional leaf group. The relevant inspection is: Inspect pool size, consumed allocations and required identifiers for all logical devices. The most discriminating first check is “Inspect pool size, consumed allocations and required identifiers for all logical devices”.

D:

“Compare the selected logical device's interface count, speeds and connection roles with rack requirements” is relevant to a different condition: A site models 48 server attachments using a logical device profile that exposes only 32 suitable host interfaces. The stated question instead concerns: An Apstra design runs out of loopback addresses when adding an additional leaf group. The relevant inspection is: Inspect pool size, consumed allocations and required identifiers for all logical devices. The most discriminating first check is “Inspect pool size, consumed allocations and required identifiers for all logical devices”.

Question 763

A custom telemetry probe flags a latency anomaly but the blueprint shows no service configuration errors. 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 configlet attachment criteria and generated configuration diffs for all matching targets.
  4. Inspect the probe's monitored metric, stage, threshold and underlying samples before correlating service state.

Explanation

Correct Answer

D:

This checks the relevant evidence first: inspect the probe's monitored metric, stage, threshold and underlying samples before correlating service state. The underlying concept is that probe anomalies can reflect telemetry thresholds or conditions independently of blueprint service configuration anomalies. After confirming the finding, a controlled remediation is to investigate the measured condition and adjust the approved monitored system or justified probe threshold.

Incorrect Answers

A:

“Inspect the specific service anomaly, affected objects and intended virtual-network configuration and state” is relevant to a different condition: An operator sees a tenant-service warning while physical switch availability indicators remain green. The stated question instead concerns: A custom telemetry probe flags a latency anomaly but the blueprint shows no service configuration errors. The relevant inspection is: Inspect the probe's monitored metric, stage, threshold and underlying samples before correlating service state. The most discriminating first check is “Inspect the probe's monitored metric, stage, threshold and underlying samples before correlating service state”.

B:

That choice—“Inspect anomaly type and affected graph nodes before selecting the next technical investigation”—addresses this other problem: A support engineer assumes every anomaly is a device-down alarm even when the affected rule is a tenant connectivity expectation. Here the scenario is: A custom telemetry probe flags a latency anomaly but the blueprint shows no service configuration errors. The relevant inspection is: Inspect the probe's monitored metric, stage, threshold and underlying samples before correlating service state. The most discriminating first check is “Inspect the probe's monitored metric, stage, threshold and underlying samples before correlating service state”.

C:

“Inspect configlet attachment criteria and generated configuration diffs for all matching targets” 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. The relevant inspection is: Inspect the probe's monitored metric, stage, threshold and underlying samples before correlating service state. The most discriminating first check is “Inspect the probe's monitored metric, stage, threshold and underlying samples before correlating service state”.

Question 764

An engineer wants to return to a blueprint commit created before several resource pool and hardware changes. Which evidence most directly verifies the intended network outcome?

  1. Confirm active blueprint state matches the intended retained revision and critical services recover.
  2. Prove the revised blueprint builds with valid allocations and switches converge on intended active state.
  3. Confirm the pending diff no longer includes the bad edit and the active blueprint is unchanged.
  4. Confirm no required pending work was silently lost and the correct historical revision became active.

Explanation

Correct Answer

B:

This directly tests the desired result: prove the revised blueprint builds with valid allocations and switches converge on intended active state. The decisive investigation is to inspect historical identifiers, resource assignments, device availability and supported rollback constraints. The governing principle is that Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory.

Incorrect Answers

A:

The option “Confirm active blueprint state matches the intended retained revision and critical services recover” is useful in a different setting: A new fabric commit causes service degradation and the team wants to return to a known earlier revision with minimal manual reconstruction. The case being tested is: An engineer wants to return to a blueprint commit created before several resource pool and hardware changes. Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory. The direct acceptance evidence is “Prove the revised blueprint builds with valid allocations and switches converge on intended active state”.

C:

That choice—“Confirm the pending diff no longer includes the bad edit and the active blueprint is unchanged”—addresses this other problem: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. Here the scenario is: An engineer wants to return to a blueprint commit created before several resource pool and hardware changes. Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory. The direct acceptance evidence is “Prove the revised blueprint builds with valid allocations and switches converge on intended active state”.

D:

“Confirm no required pending work was silently lost and the correct historical revision became active” is associated with a distinct issue: An operator has valuable staged changes when another administrator proposes jumping to an older blueprint revision. By contrast, the actual problem is: An engineer wants to return to a blueprint commit created before several resource pool and hardware changes. Time Voyager restoration can fail or require reconciliation when historical resource allocations or device identities conflict with current inventory. The direct acceptance evidence is “Prove the revised blueprint builds with valid allocations and switches converge on intended active state”.

Question 765

An operations dashboard must report which workload attachments inherit a specific project label. Which evidence most directly verifies the intended network outcome?

  1. Confirm the graph shows the intended node relationships and end-to-end attachment tests pass.
  2. Compare query results with a known inventory sample and correct false-positive attachments.
  3. Confirm the result contains all intended rack uplinks and excludes unrelated interface objects.
  4. Confirm only the intended rack or tenant objects generate results and anomalies on repeat tests.

Explanation

Correct Answer

B:

This directly tests the desired result: compare query results with a known inventory sample and correct false-positive attachments. The decisive investigation is to test a query for tag attributes and related generic-system attachments in the target blueprint. The governing principle is that Apstra graph queries can combine object attributes and topological relationships for precise selection.

Incorrect Answers

A:

“Confirm the graph shows the intended node relationships and end-to-end attachment tests pass” is associated with a distinct issue: An Apstra graph search reveals a workload object disconnected from its expected virtual-network relation. By contrast, the actual problem is: An operations dashboard must report which workload attachments inherit a specific project label. Apstra graph queries can combine object attributes and topological relationships for precise selection. The direct acceptance evidence is “Compare query results with a known inventory sample and correct false-positive attachments”.

C:

“Confirm the result contains all intended rack uplinks and excludes unrelated interface objects” is relevant to a different condition: An analyst wants to find all uplinks belonging to a specific rack while avoiding assumptions based on interface names. The stated question instead concerns: An operations dashboard must report which workload attachments inherit a specific project label. Apstra graph queries can combine object attributes and topological relationships for precise selection. The direct acceptance evidence is “Compare query results with a known inventory sample and correct false-positive attachments”.

D:

That choice—“Confirm only the intended rack or tenant objects generate results and anomalies on repeat tests”—addresses this other problem: A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. Here the scenario is: An operations dashboard must report which workload attachments inherit a specific project label. Apstra graph queries can combine object attributes and topological relationships for precise selection. The direct acceptance evidence is “Compare query results with a known inventory sample and correct false-positive attachments”.

Question 766

A proposed rack blueprint includes all needed devices but its graph does not represent an external border connection required by applications. 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. Stage and review each intended blueprint update through an approved migration or change process.
  4. Choose an officially supported template and platform combination and regenerate the blueprint configuration.

Explanation

Correct Answer

A:

This action addresses the stated defect: extend the approved blueprint design to include appropriate border connectivity and associated resources. The underlying constraint is that blueprint design intent must model necessary fabric roles and external connectivity before deployment. Verify rather than assume success: confirm the modeled external links and routing connectivity satisfy the acceptance topology.

Incorrect Answers

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 proposed rack blueprint includes all needed devices but its graph does not represent an external border connection required by applications. Extend the approved blueprint design to include appropriate border connectivity and associated resources. The most relevant correction is “Extend the approved blueprint design to include appropriate border connectivity and associated resources”.

C:

The option “Stage and review each intended blueprint update through an approved migration or change process” is useful in a different setting: A design template was edited after the first rack was built and an engineer assumes existing active blueprints are retroactively rewritten. The case being tested is: A proposed rack blueprint includes all needed devices but its graph does not represent an external border connection required by applications. Extend the approved blueprint design to include appropriate border connectivity and associated resources. The most relevant correction is “Extend the approved blueprint design to include appropriate border connectivity and associated resources”.

D:

“Choose an officially supported template and platform combination and regenerate the blueprint configuration” is relevant to a different condition: A team assigns a device image and platform combination not supported by the chosen Apstra reference design. The stated question instead concerns: A proposed rack blueprint includes all needed devices but its graph does not represent an external border connection required by applications. Extend the approved blueprint design to include appropriate border connectivity and associated resources. The most relevant correction is “Extend the approved blueprint design to include appropriate border connectivity and associated resources”.

Question 767

A new Apstra deployment includes baseline settings, platform-specific changes and generated overlay commands that an engineer wants to distinguish. Which initial check would most directly distinguish the likely cause?

  1. Inspect pending differences and deploy status from the blueprint UI before accepting the change.
  2. Compare pristine, incremental and rendered configuration artifacts for the targeted device and intended change.
  3. Inspect the Staged, Uncommitted and Active states and per-device deployment status.
  4. Compare LLDP-discovered endpoints and physical interface identifiers against the generated cable map.

Explanation

Correct Answer

B:

This checks the relevant evidence first: compare pristine, incremental and rendered configuration artifacts for the targeted device and intended change. The underlying concept is that configuration views represent different aspects of the managed device configuration and should be interpreted in their proper context. After confirming the finding, a controlled remediation is to select the approved deployment or diagnostic view before reviewing and applying configuration diffs.

Incorrect Answers

A:

“Inspect pending differences and deploy status from the blueprint UI before accepting the change” 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 new Apstra deployment includes baseline settings, platform-specific changes and generated overlay commands that an engineer wants to distinguish. The relevant inspection is: Compare pristine, incremental and rendered configuration artifacts for the targeted device and intended change. The most discriminating first check is “Compare pristine, incremental and rendered configuration artifacts for the targeted device and intended change”.

C:

“Inspect the Staged, Uncommitted and Active states and per-device deployment status” is associated with a distinct issue: A network engineer views valid proposed changes under Staged and mistakenly assumes all devices were updated. By contrast, the actual problem is: A new Apstra deployment includes baseline settings, platform-specific changes and generated overlay commands that an engineer wants to distinguish. The relevant inspection is: Compare pristine, incremental and rendered configuration artifacts for the targeted device and intended change. The most discriminating first check is “Compare pristine, incremental and rendered configuration artifacts for the targeted device and intended change”.

D:

The option “Compare LLDP-discovered endpoints and physical interface identifiers against the generated cable map” is useful in a different setting: A live rack cable is connected to the wrong spine port compared with the blueprint's intended cable map. The case being tested is: A new Apstra deployment includes baseline settings, platform-specific changes and generated overlay commands that an engineer wants to distinguish. The relevant inspection is: Compare pristine, incremental and rendered configuration artifacts for the targeted device and intended change. The most discriminating first check is “Compare pristine, incremental and rendered configuration artifacts for the targeted device and intended change”.

Question 768

Two tenants use overlapping private subnets and the team fears one tenant's routes will be mistaken for the other. Which initial check would most directly distinguish the likely cause?

  1. Inspect per-VRF and per-virtual-network route target communities and import/export decisions.
  2. Compare route distinguishers, route targets and actual VRF import policy for each tenant.
  3. Inspect Type 5 prefix advertisements, route-target import and resolving next hops for the tenant VRF.
  4. Inspect the EVPN route database for Type 2 MAC or MAC-IP advertisements and associated VNI or next hop.

Explanation

Correct Answer

B:

This checks the relevant evidence first: compare route distinguishers, route targets and actual VRF import policy for each tenant. The underlying concept is that EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution. After confirming the finding, a controlled remediation is to assign unique route distinguishing context and appropriate route target import and export policy without leaking tenants.

Incorrect Answers

A:

The option “Inspect per-VRF and per-virtual-network route target communities and import/export decisions” 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. The relevant inspection is: Compare route distinguishers, route targets and actual VRF import policy for each tenant. The most discriminating first check is “Compare route distinguishers, route targets and actual VRF import policy for each tenant”.

C:

That choice—“Inspect Type 5 prefix advertisements, route-target import and resolving next hops for the tenant VRF”—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: Two tenants use overlapping private subnets and the team fears one tenant's routes will be mistaken for the other. The relevant inspection is: Compare route distinguishers, route targets and actual VRF import policy for each tenant. The most discriminating first check is “Compare route distinguishers, route targets and actual VRF import policy for each tenant”.

D:

“Inspect the EVPN route database for Type 2 MAC or MAC-IP advertisements and associated VNI or next hop” is associated with a distinct issue: An EVPN network learns a host MAC address and associated IP binding from a remote VTEP. By contrast, the actual problem is: Two tenants use overlapping private subnets and the team fears one tenant's routes will be mistaken for the other. The relevant inspection is: Compare route distinguishers, route targets and actual VRF import policy for each tenant. The most discriminating first check is “Compare route distinguishers, route targets and actual VRF import policy for each tenant”.

Question 769

A fabric exchanges IP prefixes between tenant routing zones without requiring every remote subnet to be represented as an individual MAC. Which initial check would most directly distinguish the likely cause?

  1. Inspect the EVPN route database for Type 2 MAC or MAC-IP advertisements and associated VNI or next hop.
  2. Inspect per-VRF and per-virtual-network route target communities and import/export decisions.
  3. Inspect Type 5 prefix advertisements, route-target import and resolving next hops for the tenant VRF.
  4. Compare route distinguishers, route targets and actual VRF import policy for each tenant.

Explanation

Correct Answer

C:

This checks the relevant evidence first: inspect Type 5 prefix advertisements, route-target import and resolving next hops for the tenant VRF. The underlying concept is that EVPN Type 5 IP prefix routes represent routed IP reachability, complementing Type 2 endpoint advertisements. After confirming the finding, a controlled remediation is to correct prefix export/import and next-hop resolution for the routed EVPN IP prefix.

Incorrect Answers

A:

“Inspect the EVPN route database for Type 2 MAC or MAC-IP advertisements and associated VNI or next hop” is associated with a distinct issue: A leaf needs to advertise a workload endpoint location to remote EVPN participants across the VXLAN fabric. By contrast, the actual problem is: A fabric exchanges IP prefixes between tenant routing zones without requiring every remote subnet to be represented as an individual MAC. The relevant inspection is: Inspect Type 5 prefix advertisements, route-target import and resolving next hops for the tenant VRF. The most discriminating first check is “Inspect Type 5 prefix advertisements, route-target import and resolving next hops for the tenant VRF”.

B:

The option “Inspect per-VRF and per-virtual-network route target communities and import/export decisions” is useful in a different setting: A server VLAN is created on two racks but remote EVPN routes cannot be imported because their route targets do not align. The case being tested is: A fabric exchanges IP prefixes between tenant routing zones without requiring every remote subnet to be represented as an individual MAC. The relevant inspection is: Inspect Type 5 prefix advertisements, route-target import and resolving next hops for the tenant VRF. The most discriminating first check is “Inspect Type 5 prefix advertisements, route-target import and resolving next hops for the tenant VRF”.

D:

That choice—“Compare route distinguishers, route targets and actual VRF import policy for each tenant”—addresses this other problem: A provider deploys two isolated VRFs containing identical IP prefixes in distinct tenant spaces. Here the scenario is: A fabric exchanges IP prefixes between tenant routing zones without requiring every remote subnet to be represented as an individual MAC. The relevant inspection is: Inspect Type 5 prefix advertisements, route-target import and resolving next hops for the tenant VRF. The most discriminating first check is “Inspect Type 5 prefix advertisements, route-target import and resolving next hops for the tenant VRF”.

Question 770

A leaf needs to advertise a workload endpoint location to remote EVPN participants across the VXLAN fabric. Which initial check would most directly distinguish the likely cause?

  1. Inspect Type 5 prefix advertisements, route-target import and resolving next hops for the tenant VRF.
  2. Inspect the EVPN route database for Type 2 MAC or MAC-IP advertisements and associated VNI or next hop.
  3. Inspect Ethernet segment identifiers, multihoming state and designated-forwarder election on the relevant leafs.
  4. Inspect per-VRF and per-virtual-network route target communities and import/export decisions.

Explanation

Correct Answer

B:

This checks the relevant evidence first: inspect the EVPN route database for Type 2 MAC or MAC-IP advertisements and associated VNI or next hop. The underlying concept is that EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning. After confirming the finding, a controlled remediation is to repair EVPN endpoint advertisement and import eligibility for the affected virtual network.

Incorrect Answers

A:

That choice—“Inspect Type 5 prefix advertisements, route-target import and resolving next hops for the tenant VRF”—addresses this other problem: An operator advertises an external IPv4 subnet into an EVPN routing domain for routed reachability. Here the scenario is: A leaf needs to advertise a workload endpoint location to remote EVPN participants across the VXLAN fabric. The relevant inspection is: Inspect the EVPN route database for Type 2 MAC or MAC-IP advertisements and associated VNI or next hop. The most discriminating first check is “Inspect the EVPN route database for Type 2 MAC or MAC-IP advertisements and associated VNI or next hop”.

C:

The option “Inspect Ethernet segment identifiers, multihoming state and designated-forwarder election on the relevant leafs” is useful in a different setting: An EVPN multihomed endpoint exhibits unstable forwarding after both attachment leafs advertise the same segment independently. The case being tested is: A leaf needs to advertise a workload endpoint location to remote EVPN participants across the VXLAN fabric. The relevant inspection is: Inspect the EVPN route database for Type 2 MAC or MAC-IP advertisements and associated VNI or next hop. The most discriminating first check is “Inspect the EVPN route database for Type 2 MAC or MAC-IP advertisements and associated VNI or next hop”.

D:

“Inspect per-VRF and per-virtual-network route target communities and import/export decisions” 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. The relevant inspection is: Inspect the EVPN route database for Type 2 MAC or MAC-IP advertisements and associated VNI or next hop. The most discriminating first check is “Inspect the EVPN route database for Type 2 MAC or MAC-IP advertisements and associated VNI or next hop”.

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