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 88

Question 870

An Apstra graph search reveals a workload object disconnected from its expected virtual-network relation. 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. Confirm the result contains all intended rack uplinks and excludes unrelated interface objects.
  3. Compare query results with a known inventory sample and correct false-positive attachments.
  4. Confirm only the intended rack or tenant objects generate results and anomalies on repeat tests.

Explanation

Correct Answer

A:

This directly tests the desired result: confirm the graph shows the intended node relationships and end-to-end attachment tests pass. The decisive investigation is to inspect the actual node properties, expected connected edges and corresponding blueprint intent. The governing principle is that graph query results reflect the modeled topology and may reveal missing or misassigned relationships that need validation.

Incorrect Answers

B:

“Confirm the result contains all intended rack uplinks and excludes unrelated interface objects” is associated with a distinct issue: A large fabric includes many repeated physical device names and an operator needs the exact topology relationship for one rack. By contrast, the actual problem is: An Apstra graph search reveals a workload object disconnected from its expected virtual-network relation. Graph query results reflect the modeled topology and may reveal missing or misassigned relationships that need validation. The direct acceptance evidence is “Confirm the graph shows the intended node relationships and end-to-end attachment tests pass”.

C:

The option “Compare query results with a known inventory sample and correct false-positive attachments” is useful in a different setting: An operations dashboard must report which workload attachments inherit a specific project label. The case being tested is: An Apstra graph search reveals a workload object disconnected from its expected virtual-network relation. Graph query results reflect the modeled topology and may reveal missing or misassigned relationships that need validation. The direct acceptance evidence is “Confirm the graph shows the intended node relationships and end-to-end attachment tests pass”.

D:

“Confirm only the intended rack or tenant objects generate results and anomalies on repeat tests” is relevant to a different condition: A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. The stated question instead concerns: An Apstra graph search reveals a workload object disconnected from its expected virtual-network relation. Graph query results reflect the modeled topology and may reveal missing or misassigned relationships that need validation. The direct acceptance evidence is “Confirm the graph shows the intended node relationships and end-to-end attachment tests pass”.

Question 871

A provider deploys two isolated VRFs containing identical IP prefixes in distinct tenant spaces. Which design or operational principle best explains this behavior?

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

Explanation

Correct Answer

C:

EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution. Here, a provider deploys two isolated VRFs containing identical IP prefixes in distinct tenant spaces. A useful discriminating check is to compare route distinguishers, route targets and actual VRF import policy for each tenant.

Incorrect Answers

A:

“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: A provider deploys two isolated VRFs containing identical IP prefixes in distinct tenant spaces. EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution. The controlling principle is “EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution”.

B:

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 provider deploys two isolated VRFs containing identical IP prefixes in distinct tenant spaces. EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution. The controlling principle is “EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution”.

D:

The option “EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning” 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: A provider deploys two isolated VRFs containing identical IP prefixes in distinct tenant spaces. EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution. The controlling principle is “EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution”.

Question 872

An operator advertises an external IPv4 subnet into an EVPN routing domain for routed reachability. Which design or operational principle best explains this behavior?

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

Explanation

Correct Answer

B:

EVPN Type 5 IP prefix routes represent routed IP reachability, complementing Type 2 endpoint advertisements. Here, an operator advertises an external IPv4 subnet into an EVPN routing domain for routed reachability. A useful discriminating check is to inspect Type 5 prefix advertisements, route-target import and resolving next hops for the tenant VRF.

Incorrect Answers

A:

The option “EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning” is useful in a different setting: An EVPN network learns a host MAC address and associated IP binding from a remote VTEP. The case being tested is: An operator advertises an external IPv4 subnet into an EVPN routing domain for routed reachability. EVPN Type 5 IP prefix routes represent routed IP reachability, complementing Type 2 endpoint advertisements. The controlling principle is “EVPN Type 5 IP prefix routes represent routed IP reachability, complementing Type 2 endpoint advertisements”.

C:

That choice—“Matching import and export policy for the intended virtual network governs whether EVPN route distribution creates usable reachability”—addresses this other problem: Two leaves advertise the same virtual network yet one leaf rejects the other's EVPN MAC routes. Here the scenario is: An operator advertises an external IPv4 subnet into an EVPN routing domain for routed reachability. EVPN Type 5 IP prefix routes represent routed IP reachability, complementing Type 2 endpoint advertisements. The controlling principle is “EVPN Type 5 IP prefix routes represent routed IP reachability, complementing Type 2 endpoint advertisements”.

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 operator advertises an external IPv4 subnet into an EVPN routing domain for routed reachability. EVPN Type 5 IP prefix routes represent routed IP reachability, complementing Type 2 endpoint advertisements. The controlling principle is “EVPN Type 5 IP prefix routes represent routed IP reachability, complementing Type 2 endpoint advertisements”.

Question 873

A team wants to locate every virtual network owned by a particular application during a migration. Which shortcut would be most likely to undermine this objective?

  1. Apply the maintenance operation to all devices whose names happen to include the rack number.
  2. Identify tenant networks solely from informal naming conventions and ignore their actual graph relationships.
  3. Change a shared variable without reviewing all devices and templates that reference it.
  4. Assume a Time Voyager selection automatically and safely restores every external system without review.

Explanation

Correct Answer

B:

This is the unsafe shortcut to avoid: identify tenant networks solely from informal naming conventions and ignore their actual graph relationships. It violates the principle that blueprint object tags and query filters support targeted discovery and operational reporting. An appropriate alternative is to apply consistent tags and use targeted graph or blueprint searches to generate the migration inventory.

Incorrect Answers

A:

“Apply the maintenance operation to all devices whose names happen to include the rack number” is associated with a distinct issue: An operator wants to identify managed nodes by rack and role in the blueprint graph. By contrast, the actual problem is: A team wants to locate every virtual network owned by a particular application during a migration. Blueprint object tags and query filters support targeted discovery and operational reporting. The directly relevant unsafe shortcut is “Identify tenant networks solely from informal naming conventions and ignore their actual graph relationships”.

C:

“Change a shared variable without reviewing all devices and templates that reference it” is relevant to a different condition: A team wants to reuse the same approved DNS and NTP settings across multiple racks without editing every switch individually. The stated question instead concerns: A team wants to locate every virtual network owned by a particular application during a migration. Blueprint object tags and query filters support targeted discovery and operational reporting. The directly relevant unsafe shortcut is “Identify tenant networks solely from informal naming conventions and ignore their actual graph relationships”.

D:

That choice—“Assume a Time Voyager selection automatically and safely restores every external system without review”—addresses this other problem: A new fabric commit causes service degradation and the team wants to return to a known earlier revision with minimal manual reconstruction. Here the scenario is: A team wants to locate every virtual network owned by a particular application during a migration. Blueprint object tags and query filters support targeted discovery and operational reporting. The directly relevant unsafe shortcut is “Identify tenant networks solely from informal naming conventions and ignore their actual graph relationships”.

Question 874

A development VN is accidentally assigned to the wrong routing zone during a project migration. Which initial check would most directly distinguish the likely cause?

  1. Inspect virtual-network membership and routing-zone assignments for the application segments.
  2. Inspect the VN's routing-zone binding, SVI and VRF route lookup on the affected leaf.
  3. Inspect VRF and routing-zone membership, tenant virtual-network bindings and imported routes.
  4. Inspect the route export/import policy and observed advertised routes for the affected VRF.

Explanation

Correct Answer

B:

This checks the relevant evidence first: inspect the VN's routing-zone binding, SVI and VRF route lookup on the affected leaf. The underlying concept is that a virtual network's routed gateway and routing-zone association determine its Layer 3 tenant boundary. After confirming the finding, a controlled remediation is to move the VN association to the authorized routing zone and commit reviewed blueprint changes.

Incorrect Answers

A:

That choice—“Inspect virtual-network membership and routing-zone assignments for the application segments”—addresses this other problem: A multirack tenant needs two segmented application subnets while sharing a common VRF routing domain. Here the scenario is: A development VN is accidentally assigned to the wrong routing zone during a project migration. The relevant inspection is: Inspect the VN's routing-zone binding, SVI and VRF route lookup on the affected leaf. The most discriminating first check is “Inspect the VN's routing-zone binding, SVI and VRF route lookup on the affected leaf”.

C:

The option “Inspect VRF and routing-zone membership, tenant virtual-network bindings and imported routes” is useful in a different setting: Two tenants require identical subnet ranges in a shared physical fabric while remaining isolated. The case being tested is: A development VN is accidentally assigned to the wrong routing zone during a project migration. The relevant inspection is: Inspect the VN's routing-zone binding, SVI and VRF route lookup on the affected leaf. The most discriminating first check is “Inspect the VN's routing-zone binding, SVI and VRF route lookup on the affected leaf”.

D:

“Inspect the route export/import policy and observed advertised routes for the affected VRF” is relevant to a different condition: An external peer receives a tenant's internal subnets that were supposed to stay private. The stated question instead concerns: A development VN is accidentally assigned to the wrong routing zone during a project migration. The relevant inspection is: Inspect the VN's routing-zone binding, SVI and VRF route lookup on the affected leaf. The most discriminating first check is “Inspect the VN's routing-zone binding, SVI and VRF route lookup on the affected leaf”.

Question 875

An analyst wants to find all uplinks belonging to a specific rack while avoiding assumptions based on interface names. Which initial check would most directly distinguish the likely cause?

  1. Inspect the actual node properties, expected connected edges and corresponding blueprint intent.
  2. Inspect the graph query's node types, filters and returned relationship paths for the intended rack.
  3. Test a query for tag attributes and related generic-system attachments in the target blueprint.
  4. Inspect probe data sources, monitored stages, thresholds and the exact interfaces being selected.

Explanation

Correct Answer

B:

This checks the relevant evidence first: inspect the graph query's node types, filters and returned relationship paths for the intended rack. The underlying concept is that graph Explorer and relationship-aware graph queries help identify modeled nodes and edges within a blueprint. After confirming the finding, a controlled remediation is to construct a scoped graph query based on blueprint entities and their physical connectivity.

Incorrect Answers

A:

“Inspect the actual node properties, expected connected edges and corresponding blueprint intent” is relevant to a different condition: An Apstra graph search reveals a workload object disconnected from its expected virtual-network relation. The stated question instead concerns: An analyst wants to find all uplinks belonging to a specific rack while avoiding assumptions based on interface names. The relevant inspection is: Inspect the graph query's node types, filters and returned relationship paths for the intended rack. The most discriminating first check is “Inspect the graph query's node types, filters and returned relationship paths for the intended rack”.

C:

“Test a query for tag attributes and related generic-system attachments in the target blueprint” is associated with a distinct issue: An operations dashboard must report which workload attachments inherit a specific project label. By contrast, the actual problem is: An analyst wants to find all uplinks belonging to a specific rack while avoiding assumptions based on interface names. The relevant inspection is: Inspect the graph query's node types, filters and returned relationship paths for the intended rack. The most discriminating first check is “Inspect the graph query's node types, filters and returned relationship paths for the intended rack”.

D:

The option “Inspect probe data sources, monitored stages, thresholds and the exact interfaces being selected” is useful in a different setting: A monitoring team wants to detect rising discards on the uplinks of one specific leaf group. The case being tested is: An analyst wants to find all uplinks belonging to a specific rack while avoiding assumptions based on interface names. The relevant inspection is: Inspect the graph query's node types, filters and returned relationship paths for the intended rack. The most discriminating first check is “Inspect the graph query's node types, filters and returned relationship paths for the intended rack”.

Question 876

A network engineer sees differences among the pristine, incremental and rendered configurations for a managed leaf. Which initial check would most directly distinguish the likely cause?

  1. Check current spine port availability, resource pools and the proposed rack type against the active blueprint.
  2. Inspect the intended leaf attachment ports, generic-system definition and relevant cable map.
  3. Compare pristine baseline, incremental changes and final rendered config against the active blueprint.
  4. Compare staged differences with active configuration and deployment status before testing production traffic.

Explanation

Correct Answer

C:

This checks the relevant evidence first: compare pristine baseline, incremental changes and final rendered config against the active blueprint. The underlying concept is that configuration views and their origins should be compared before diagnosing managed-device drift. After confirming the finding, a controlled remediation is to investigate unexpected changes using the appropriate generated-config view and approved override workflow.

Incorrect Answers

A:

The option “Check current spine port availability, resource pools and the proposed rack type against the active blueprint” is useful in a different setting: A data center needs to add another rack to a production fabric without replacing the existing blueprint. The case being tested is: A network engineer sees differences among the pristine, incremental and rendered configurations for a managed leaf. The relevant inspection is: Compare pristine baseline, incremental changes and final rendered config against the active blueprint. The most discriminating first check is “Compare pristine baseline, incremental changes and final rendered config against the active blueprint”.

B:

“Inspect the intended leaf attachment ports, generic-system definition and relevant cable map” is relevant to a different condition: A new dual-homed application server is physically connected but its logical attachment is absent from the active blueprint. The stated question instead concerns: A network engineer sees differences among the pristine, incremental and rendered configurations for a managed leaf. The relevant inspection is: Compare pristine baseline, incremental changes and final rendered config against the active blueprint. The most discriminating first check is “Compare pristine baseline, incremental changes and final rendered config against the active blueprint”.

D:

“Compare staged differences with active configuration and deployment status before testing production traffic” is associated with a distinct issue: An engineer edits a virtual network in a blueprint but cannot see the change reflected in the active switch configuration. By contrast, the actual problem is: A network engineer sees differences among the pristine, incremental and rendered configurations for a managed leaf. The relevant inspection is: Compare pristine baseline, incremental changes and final rendered config against the active blueprint. The most discriminating first check is “Compare pristine baseline, incremental changes and final rendered config against the active blueprint”.

Question 877

A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. Which shortcut would be most likely to undermine this objective?

  1. Build tenant bridge domains first and ignore missing tunnel endpoint routes.
  2. Create new tenant VNIs to mask an unresolved underlay routing failure.
  3. Treat the presence of two physical links as proof that routing automatically reconverges instantly.
  4. Add unrestricted lateral links between leaf devices without updating the design model.

Explanation

Correct Answer

A:

This is the unsafe shortcut to avoid: build tenant bridge domains first and ignore missing tunnel endpoint routes. It violates the principle that overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes. An appropriate alternative is to advertise the approved VTEP loopbacks through the fabric underlay and check next-hop reachability.

Incorrect Answers

B:

The option “Create new tenant VNIs to mask an unresolved underlay routing failure” is useful in a different setting: A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. The case being tested is: A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. Overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes. The directly relevant unsafe shortcut is “Build tenant bridge domains first and ignore missing tunnel endpoint routes”.

C:

“Treat the presence of two physical links as proof that routing automatically reconverges instantly” is relevant to a different condition: A fabric uses two equal-cost underlay next hops yet packets continue toward a failed path following a port outage. The stated question instead concerns: A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. Overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes. The directly relevant unsafe shortcut is “Build tenant bridge domains first and ignore missing tunnel endpoint routes”.

D:

That choice—“Add unrestricted lateral links between leaf devices without updating the design model”—addresses this other problem: A migration plan connects every rack leaf laterally and treats spine devices as only optional edge routers. Here the scenario is: A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. Overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes. The directly relevant unsafe shortcut is “Build tenant bridge domains first and ignore missing tunnel endpoint routes”.

Question 878

An operations team receives repeated probe-stage alerts after an optic begins incrementing errors. Which design or operational principle best explains this behavior?

  1. Graph and probe context can correlate multiple anomalies to a shared physical or logical source.
  2. Analytics anomalies can indicate measured performance deviations that do not coincide with configuration intent mismatches.
  3. A cleared threshold alarm alone is not sufficient proof of service recovery; measured data and intent must support the conclusion.
  4. An IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope.

Explanation

Correct Answer

A:

graph and probe context can correlate multiple anomalies to a shared physical or logical source. Here, an operations team receives repeated probe-stage alerts after an optic begins incrementing errors. A useful discriminating check is to group probe anomalies by affected node and stage, then inspect linked telemetry and topology edges.

Incorrect Answers

B:

“Analytics anomalies can indicate measured performance deviations that do not coincide with configuration intent mismatches” is associated with a distinct issue: An IBA probe reports intermittent latency spikes but application errors are not visible in basic device health summaries. By contrast, the actual problem is: An operations team receives repeated probe-stage alerts after an optic begins incrementing errors. Graph and probe context can correlate multiple anomalies to a shared physical or logical source. The controlling principle is “Graph and probe context can correlate multiple anomalies to a shared physical or logical source”.

C:

The option “A cleared threshold alarm alone is not sufficient proof of service recovery; measured data and intent must support the conclusion” is useful in a different setting: A data center dashboard becomes green immediately after an engineer increases alert thresholds without addressing failing application traffic. The case being tested is: An operations team receives repeated probe-stage alerts after an optic begins incrementing errors. Graph and probe context can correlate multiple anomalies to a shared physical or logical source. The controlling principle is “Graph and probe context can correlate multiple anomalies to a shared physical or logical source”.

D:

“An IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope” is relevant to a different condition: A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. The stated question instead concerns: An operations team receives repeated probe-stage alerts after an optic begins incrementing errors. Graph and probe context can correlate multiple anomalies to a shared physical or logical source. The controlling principle is “Graph and probe context can correlate multiple anomalies to a shared physical or logical source”.

Question 879

A new rack is partially configured and the change ticket lacks a clear record of who initiated its commit. Which evidence most directly verifies the intended network outcome?

  1. Produce a traceable operator or automation event associated with the observed revision and change window.
  2. Verify current samples arrive and synthetic test conditions create expected alarms.
  3. Confirm timestamped Apstra events arrive at the collector and retain source attribution.
  4. Confirm logs identify the affected blueprint revision, device and operator or automation identity.

Explanation

Correct Answer

D:

This directly tests the desired result: confirm logs identify the affected blueprint revision, device and operator or automation identity. The decisive investigation is to review the event timeline, blueprint commit notes, deployment status and actor records. The governing principle is that controller event logs and deployment records should be correlated with intent revisions and change approvals.

Incorrect Answers

A:

“Produce a traceable operator or automation event associated with the observed revision and change window” is relevant to a different condition: An operator needs to explain who committed a change after a rack lost connectivity overnight. The stated question instead concerns: A new rack is partially configured and the change ticket lacks a clear record of who initiated its commit. Controller event logs and deployment records should be correlated with intent revisions and change approvals. The direct acceptance evidence is “Confirm logs identify the affected blueprint revision, device and operator or automation identity”.

B:

That choice—“Verify current samples arrive and synthetic test conditions create expected alarms”—addresses this other problem: An Apstra operator sees no current alerts after a telemetry collector became unreachable. Here the scenario is: A new rack is partially configured and the change ticket lacks a clear record of who initiated its commit. Controller event logs and deployment records should be correlated with intent revisions and change approvals. The direct acceptance evidence is “Confirm logs identify the affected blueprint revision, device and operator or automation identity”.

C:

“Confirm timestamped Apstra events arrive at the collector and retain source attribution” is associated with a distinct issue: A data center runs a centralized SOC and requests appliance event forwarding without sharing administrator credentials. By contrast, the actual problem is: A new rack is partially configured and the change ticket lacks a clear record of who initiated its commit. Controller event logs and deployment records should be correlated with intent revisions and change approvals. The direct acceptance evidence is “Confirm logs identify the affected blueprint revision, device and operator or automation identity”.

Question 880

A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. 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. Correct prefix export/import and next-hop resolution for the routed EVPN IP prefix.
  4. Advertise and import the required host or prefix routes according to the approved ERB routing design.

Explanation

Correct Answer

D:

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:

The option “Implement an authorized distributed gateway design and ensure the overlay advertises the required endpoint or prefix routes” is useful in a different setting: A leaf gateway must route a workload's inter-subnet traffic locally rather than always hairpinning through a central aggregation switch. The case being tested is: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. 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:

“Align the authorized distributed gateway configuration across participating VTEPs” is relevant to a different condition: Two racks advertise the same distributed gateway virtual address but clients see intermittent first-hop behavior after a deployment. The stated question instead concerns: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. 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”.

C:

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: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. 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”.

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