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 33

Question 320

A large fabric includes many repeated physical device names and an operator needs the exact topology relationship for one rack. Which controlled change best addresses the described requirement?

  1. Use graph explorer filters and query syntax that return only the intended workload nodes.
  2. Repair the validated missing logical relation or correct the query filter if it is misleading.
  3. Construct a scoped graph query based on blueprint entities and their physical connectivity.
  4. Narrow the query and probe stages to the correct blueprint nodes and monitored metrics.

Explanation

Correct Answer

C:

This action addresses the stated defect: construct a scoped graph query based on blueprint entities and their physical connectivity. The underlying constraint is that graph Explorer and relationship-aware graph queries help identify modeled nodes and edges within a blueprint. Verify rather than assume success: confirm the result contains all intended rack uplinks and excludes unrelated interface objects.

Incorrect Answers

A:

The option “Use graph explorer filters and query syntax that return only the intended workload nodes” is useful in a different setting: A team needs to locate generic systems attached to leafs in a single application tag group. The case being tested is: A large fabric includes many repeated physical device names and an operator needs the exact topology relationship for one rack. Construct a scoped graph query based on blueprint entities and their physical connectivity. The most relevant correction is “Construct a scoped graph query based on blueprint entities and their physical connectivity”.

B:

“Repair the validated missing logical relation or correct the query filter if it is misleading” 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: A large fabric includes many repeated physical device names and an operator needs the exact topology relationship for one rack. Construct a scoped graph query based on blueprint entities and their physical connectivity. The most relevant correction is “Construct a scoped graph query based on blueprint entities and their physical connectivity”.

D:

“Narrow the query and probe stages to the correct blueprint nodes and monitored metrics” is associated with a distinct issue: A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. By contrast, the actual problem is: A large fabric includes many repeated physical device names and an operator needs the exact topology relationship for one rack. Construct a scoped graph query based on blueprint entities and their physical connectivity. The most relevant correction is “Construct a scoped graph query based on blueprint entities and their physical connectivity”.

Question 321

A VXLAN packet encapsulation crosses a routed fabric but is discarded along the path due to frame size. Which controlled change best addresses the described requirement?

  1. Restore routed reachability to the advertised VTEP and the correct tunnel forwarding state.
  2. Configure sufficient supported underlay MTU along the fabric path or safely adjust payload MTU.
  3. Use the supported EVPN control plane and verify route import for the intended virtual network.
  4. Correct replication or multicast membership and virtual-network attachment within the supported fabric design.

Explanation

Correct Answer

B:

This action addresses the stated defect: configure sufficient supported underlay MTU along the fabric path or safely adjust payload MTU. The underlying constraint is that VXLAN adds encapsulation overhead and requires adequate path MTU or effective payload sizing. Verify rather than assume success: confirm representative maximum-size payloads traverse the VXLAN overlay without fragmentation-related drops.

Incorrect Answers

A:

“Restore routed reachability to the advertised VTEP and the correct tunnel forwarding state” is associated with a distinct issue: A virtualization cluster is moved to another rack and its EVPN routes exist but the remote VXLAN encapsulation next hop fails. By contrast, the actual problem is: A VXLAN packet encapsulation crosses a routed fabric but is discarded along the path due to frame size. The governing requirement is to Configure sufficient supported underlay MTU along the fabric path or safely adjust payload MTU. The most relevant correction is “Configure sufficient supported underlay MTU along the fabric path or safely adjust payload MTU”.

C:

“Use the supported EVPN control plane and verify route import for the intended virtual network” is relevant to a different condition: An architect compares an EVPN control plane with reliance on data-plane flood-and-learn for VXLAN workloads. The stated question instead concerns: A VXLAN packet encapsulation crosses a routed fabric but is discarded along the path due to frame size. The governing requirement is to Configure sufficient supported underlay MTU along the fabric path or safely adjust payload MTU. The most relevant correction is “Configure sufficient supported underlay MTU along the fabric path or safely adjust payload MTU”.

D:

That choice—“Correct replication or multicast membership and virtual-network attachment within the supported fabric design”—addresses this other problem: A fabric sees unexpectedly broad BUM traffic after a new VXLAN virtual network is provisioned. Here the scenario is: A VXLAN packet encapsulation crosses a routed fabric but is discarded along the path due to frame size. The governing requirement is to Configure sufficient supported underlay MTU along the fabric path or safely adjust payload MTU. The most relevant correction is “Configure sufficient supported underlay MTU along the fabric path or safely adjust payload MTU”.

Question 322

A team wants an analytics alert if interface utilization deviates from baseline while still retaining raw evidence. Which initial check would most directly distinguish the likely cause?

  1. Inspect the probe stage's graph query, matched entities and input metrics after the migration.
  2. Inspect probe data sources, monitored stages, thresholds and the exact interfaces being selected.
  3. Inspect the graph query's node types, filters and returned relationship paths for the intended rack.
  4. Inspect collector timestamps, aggregation window and stage criteria for the derived utilization metric.

Explanation

Correct Answer

D:

This checks the relevant evidence first: inspect collector timestamps, aggregation window and stage criteria for the derived utilization metric. The underlying concept is that IBA stages can enrich and aggregate telemetry before evaluating conditions that constitute an anomaly. After confirming the finding, a controlled remediation is to configure the supported aggregation and alert conditions with documented baseline behavior.

Incorrect Answers

A:

That choice—“Inspect the probe stage's graph query, matched entities and input metrics after the migration”—addresses this other problem: A built-in analytics probe reports a metric but cannot identify why the value changed after a rack migration. Here the scenario is: A team wants an analytics alert if interface utilization deviates from baseline while still retaining raw evidence. The relevant inspection is: Inspect collector timestamps, aggregation window and stage criteria for the derived utilization metric. The most discriminating first check is “Inspect collector timestamps, aggregation window and stage criteria for the derived utilization metric”.

B:

“Inspect probe data sources, monitored stages, thresholds and the exact interfaces being selected” is associated with a distinct issue: A monitoring team wants to detect rising discards on the uplinks of one specific leaf group. By contrast, the actual problem is: A team wants an analytics alert if interface utilization deviates from baseline while still retaining raw evidence. The relevant inspection is: Inspect collector timestamps, aggregation window and stage criteria for the derived utilization metric. The most discriminating first check is “Inspect collector timestamps, aggregation window and stage criteria for the derived utilization metric”.

C:

The option “Inspect the graph query's node types, filters and returned relationship paths for the intended rack” is useful in a different setting: An analyst wants to find all uplinks belonging to a specific rack while avoiding assumptions based on interface names. The case being tested is: A team wants an analytics alert if interface utilization deviates from baseline while still retaining raw evidence. The relevant inspection is: Inspect collector timestamps, aggregation window and stage criteria for the derived utilization metric. The most discriminating first check is “Inspect collector timestamps, aggregation window and stage criteria for the derived utilization metric”.

Question 323

A change adds a server port to a device profile but accidentally reserves the same port for spine connectivity. Which design or operational principle best explains this behavior?

  1. Interface maps and device profiles define which supported physical ports and speeds satisfy logical device connectivity.
  2. Logical device interfaces must be mapped to actual supported physical device ports through the correct interface map.
  3. A physical interface cannot simultaneously satisfy conflicting logical interface assignments in a validated blueprint.
  4. Logical device definitions represent required interface roles and capacities, independent of hardware SKU details.

Explanation

Correct Answer

C:

a physical interface cannot simultaneously satisfy conflicting logical interface assignments in a validated blueprint. Here, a change adds a server port to a device profile but accidentally reserves the same port for spine connectivity. A useful discriminating check is to inspect the interface map and assigned logical device port roles for overlapping reservations.

Incorrect Answers

A:

“Interface maps and device profiles define which supported physical ports and speeds satisfy logical device connectivity” is relevant to a different condition: A rack type requests a 100G leaf uplink but the selected switch's physical port profile only exposes that interface as four 25G breakout channels. The stated question instead concerns: A change adds a server port to a device profile but accidentally reserves the same port for spine connectivity. A physical interface cannot simultaneously satisfy conflicting logical interface assignments in a validated blueprint. The controlling principle is “A physical interface cannot simultaneously satisfy conflicting logical interface assignments in a validated blueprint”.

B:

That choice—“Logical device interfaces must be mapped to actual supported physical device ports through the correct interface map”—addresses this other problem: A template identifies uplink ports by logical role but a new hardware SKU has different port naming. Here the scenario is: A change adds a server port to a device profile but accidentally reserves the same port for spine connectivity. A physical interface cannot simultaneously satisfy conflicting logical interface assignments in a validated blueprint. The controlling principle is “A physical interface cannot simultaneously satisfy conflicting logical interface assignments in a validated blueprint”.

D:

The option “Logical device definitions represent required interface roles and capacities, independent of hardware SKU details” is useful in a different setting: A site models 48 server attachments using a logical device profile that exposes only 32 suitable host interfaces. The case being tested is: A change adds a server port to a device profile but accidentally reserves the same port for spine connectivity. A physical interface cannot simultaneously satisfy conflicting logical interface assignments in a validated blueprint. The controlling principle is “A physical interface cannot simultaneously satisfy conflicting logical interface assignments in a validated blueprint”.

Question 324

A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. Which design or operational principle best explains this behavior?

  1. Reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements.
  2. Apstra reference designs provide supported fabric topology constraints that guide reproducible rack and spine planning.
  3. Capacity planning for reference designs must include projected rack count, spine ports, oversubscription and physical interfaces.
  4. Rack type and leaf selection must support the intended redundant attachment topology and host interface roles.

Explanation

Correct Answer

A:

reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements. Here, a data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. A useful discriminating check is to review intended external service connectivity and supported blueprint reference-design capabilities.

Incorrect Answers

B:

“Apstra reference designs provide supported fabric topology constraints that guide reproducible rack and spine planning” is relevant to a different condition: An architect wants consistent rack scale-out using a reference design rather than independently inventing each fabric topology. The stated question instead concerns: A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. Reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements. The controlling principle is “Reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements”.

C:

That choice—“Capacity planning for reference designs must include projected rack count, spine ports, oversubscription and physical interfaces”—addresses this other problem: A planned Apstra fabric includes future rack growth but the initial design leaves no capacity for additional spine downlinks. Here the scenario is: A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. Reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements. The controlling principle is “Reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements”.

D:

“Rack type and leaf selection must support the intended redundant attachment topology and host interface roles” is associated with a distinct issue: A rack designer wants a redundant host attachment pattern for critical appliances. By contrast, the actual problem is: A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. Reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements. The controlling principle is “Reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements”.

Question 325

A support engineer assumes every anomaly is a device-down alarm even when the affected rule is a tenant connectivity expectation. Which controlled change best addresses the described requirement?

  1. Correct the mismatched service intent or deployed configuration while preserving authorized tenant isolation.
  2. Route the issue to the correct service, telemetry or device workflow based on the observed anomaly evidence.
  3. Investigate the measured condition and adjust the approved monitored system or justified probe threshold.
  4. Investigate unexpected changes using the appropriate generated-config view and approved override workflow.

Explanation

Correct Answer

B:

This action addresses the stated defect: route the issue to the correct service, telemetry or device workflow based on the observed anomaly evidence. The underlying constraint is that Apstra anomaly categories distinguish service intent violations, device issues and analytics-detected deviations. Verify rather than assume success: confirm the corrective workflow resolves the specific anomaly class without hiding unrelated alarms.

Incorrect Answers

A:

“Correct the mismatched service intent or deployed configuration while preserving authorized tenant isolation” is associated with a distinct issue: A blueprint raises a service anomaly for a virtual network even though all interfaces in its rack are administratively up. By contrast, the actual problem is: A support engineer assumes every anomaly is a device-down alarm even when the affected rule is a tenant connectivity expectation. Route the issue to the correct service, telemetry or device workflow based on the observed anomaly evidence. The most relevant correction is “Route the issue to the correct service, telemetry or device workflow based on the observed anomaly evidence”.

C:

“Investigate the measured condition and adjust the approved monitored system or justified probe threshold” is relevant to a different condition: A custom telemetry probe flags a latency anomaly but the blueprint shows no service configuration errors. The stated question instead concerns: A support engineer assumes every anomaly is a device-down alarm even when the affected rule is a tenant connectivity expectation. Route the issue to the correct service, telemetry or device workflow based on the observed anomaly evidence. The most relevant correction is “Route the issue to the correct service, telemetry or device workflow based on the observed anomaly evidence”.

D:

That choice—“Investigate unexpected changes using the appropriate generated-config view and approved override workflow”—addresses this other problem: A network engineer sees differences among the pristine, incremental and rendered configurations for a managed leaf. Here the scenario is: A support engineer assumes every anomaly is a device-down alarm even when the affected rule is a tenant connectivity expectation. Route the issue to the correct service, telemetry or device workflow based on the observed anomaly evidence. The most relevant correction is “Route the issue to the correct service, telemetry or device workflow based on the observed anomaly evidence”.

Question 326

A multirack tenant needs two segmented application subnets while sharing a common VRF routing domain. 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 border-leaf interfaces, attached connectivity template and tenant-specific routing policy.

Explanation

Correct Answer

A:

This checks the relevant evidence first: inspect virtual-network membership and routing-zone assignments for the application segments. The underlying concept is that a routing zone can contain multiple virtual networks that share the intended tenant Layer 3 routing context. After confirming the finding, a controlled remediation is to assign each intended VN to the correct routing zone while preserving appropriate bridging and routing boundaries.

Incorrect Answers

B:

“Inspect the VN's routing-zone binding, SVI and VRF route lookup on the affected leaf” is associated with a distinct issue: A newly created virtual network must be attached to a tenant VRF, but application packets route through the default routing instance. By contrast, the actual problem is: A multirack tenant needs two segmented application subnets while sharing a common VRF routing domain. The relevant inspection is: Inspect virtual-network membership and routing-zone assignments for the application segments. The most discriminating first check is “Inspect virtual-network membership and routing-zone assignments for the application segments”.

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 multirack tenant needs two segmented application subnets while sharing a common VRF routing domain. The relevant inspection is: Inspect virtual-network membership and routing-zone assignments for the application segments. The most discriminating first check is “Inspect virtual-network membership and routing-zone assignments for the application segments”.

D:

“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 multirack tenant needs two segmented application subnets while sharing a common VRF routing domain. The relevant inspection is: Inspect virtual-network membership and routing-zone assignments for the application segments. The most discriminating first check is “Inspect virtual-network membership and routing-zone assignments for the application segments”.

Question 327

A staging team has different cable-map snapshots from design and observed discovery data. Which design or operational principle best explains this behavior?

  1. Cabling validation compares observed neighbor links against intended device/interface relationships.
  2. Per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly.
  3. Controlled build and deploy phases separate design validation, reviewed staged changes and active device updates.
  4. Cable-map discrepancies should be reconciled before traffic flows through an unvalidated physical fabric.

Explanation

Correct Answer

D:

cable-map discrepancies should be reconciled before traffic flows through an unvalidated physical fabric. Here, a staging team has different cable-map snapshots from design and observed discovery data. A useful discriminating check is to review the intended cable-map endpoints, device identities and actual discovered LLDP neighbors.

Incorrect Answers

A:

“Cabling validation compares observed neighbor links against intended device/interface relationships” is relevant to a different condition: A live rack cable is connected to the wrong spine port compared with the blueprint's intended cable map. The stated question instead concerns: A staging team has different cable-map snapshots from design and observed discovery data. Cable-map discrepancies should be reconciled before traffic flows through an unvalidated physical fabric. The controlling principle is “Cable-map discrepancies should be reconciled before traffic flows through an unvalidated physical fabric”.

B:

That choice—“Per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly”—addresses this other problem: An operator sees devices in mixed managed states and cannot tell which switches received the new active configuration. Here the scenario is: A staging team has different cable-map snapshots from design and observed discovery data. Cable-map discrepancies should be reconciled before traffic flows through an unvalidated physical fabric. The controlling principle is “Cable-map discrepancies should be reconciled before traffic flows through an unvalidated physical fabric”.

C:

“Controlled build and deploy phases separate design validation, reviewed staged changes and active device updates” is associated with a distinct issue: A team needs to roll out a fabric change safely but its change record mixes staging a modification with committing the active state. By contrast, the actual problem is: A staging team has different cable-map snapshots from design and observed discovery data. Cable-map discrepancies should be reconciled before traffic flows through an unvalidated physical fabric. The controlling principle is “Cable-map discrepancies should be reconciled before traffic flows through an unvalidated physical fabric”.

Question 328

A development VN is accidentally assigned to the wrong routing zone during a project migration. Which controlled change best addresses the described requirement?

  1. Assign each customer to the intended isolated routing zone and VRF with appropriate virtual-network mappings.
  2. Assign each intended VN to the correct routing zone while preserving appropriate bridging and routing boundaries.
  3. Move the VN association to the authorized routing zone and commit reviewed blueprint changes.
  4. Create or correct a scoped connectivity template and routing policy for the authorized VRF.

Explanation

Correct Answer

C:

This action addresses the stated defect: move the VN association to the authorized routing zone and commit reviewed blueprint changes. The underlying constraint is that a virtual network's routed gateway and routing-zone association determine its Layer 3 tenant boundary. Verify rather than assume success: confirm the application subnet uses the expected tenant VRF and other tenants remain isolated.

Incorrect Answers

A:

The option “Assign each customer to the intended isolated routing zone and VRF with appropriate virtual-network mappings” 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. Move the VN association to the authorized routing zone and commit reviewed blueprint changes. The most relevant correction is “Move the VN association to the authorized routing zone and commit reviewed blueprint changes”.

B:

“Assign each intended VN to the correct routing zone while preserving appropriate bridging and routing boundaries” is relevant to a different condition: A multirack tenant needs two segmented application subnets while sharing a common VRF routing domain. The stated question instead concerns: A development VN is accidentally assigned to the wrong routing zone during a project migration. Move the VN association to the authorized routing zone and commit reviewed blueprint changes. The most relevant correction is “Move the VN association to the authorized routing zone and commit reviewed blueprint changes”.

D:

“Create or correct a scoped connectivity template and routing policy for the authorized VRF” is associated with a distinct issue: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. By contrast, the actual problem is: A development VN is accidentally assigned to the wrong routing zone during a project migration. Move the VN association to the authorized routing zone and commit reviewed blueprint changes. The most relevant correction is “Move the VN association to the authorized routing zone and commit reviewed blueprint changes”.

Question 329

An endpoint's remote leaf cannot deliver traffic even though the local access VLAN is assigned correctly because the tunnel endpoint is unreachable. Which controlled change best addresses the described requirement?

  1. Restore the authorized VLAN and VNI association and commit the correct virtual-network configuration.
  2. Configure sufficient supported underlay MTU along the fabric path or safely adjust payload MTU.
  3. Restore routed reachability to the advertised VTEP and the correct tunnel forwarding state.
  4. Use the supported EVPN control plane and verify route import for the intended virtual network.

Explanation

Correct Answer

C:

This action addresses the stated defect: restore routed reachability to the advertised VTEP and the correct tunnel forwarding state. The underlying constraint is that a VTEP provides VXLAN encapsulation and decapsulation and its IP reachability must exist independently of bridge membership. Verify rather than assume success: confirm encapsulated packets reach the intended VTEP and are decapsulated to the authorized bridge domain.

Incorrect Answers

A:

“Restore the authorized VLAN and VNI association and commit the correct virtual-network configuration” is associated with a distinct issue: A rack migration assigns the correct switch access VLAN but places the VTEP into another tenant's virtual network identifier. By contrast, the actual problem is: An endpoint's remote leaf cannot deliver traffic even though the local access VLAN is assigned correctly because the tunnel endpoint is unreachable. Restore routed reachability to the advertised VTEP and the correct tunnel forwarding state. The most relevant correction is “Restore routed reachability to the advertised VTEP and the correct tunnel forwarding state”.

B:

The option “Configure sufficient supported underlay MTU along the fabric path or safely adjust payload MTU” is useful in a different setting: A VXLAN packet encapsulation crosses a routed fabric but is discarded along the path due to frame size. The case being tested is: An endpoint's remote leaf cannot deliver traffic even though the local access VLAN is assigned correctly because the tunnel endpoint is unreachable. Restore routed reachability to the advertised VTEP and the correct tunnel forwarding state. The most relevant correction is “Restore routed reachability to the advertised VTEP and the correct tunnel forwarding state”.

D:

That choice—“Use the supported EVPN control plane and verify route import for the intended virtual network”—addresses this other problem: A team wants scalable MAC learning across the fabric rather than sending every remote MAC advertisement by flood. Here the scenario is: An endpoint's remote leaf cannot deliver traffic even though the local access VLAN is assigned correctly because the tunnel endpoint is unreachable. Restore routed reachability to the advertised VTEP and the correct tunnel forwarding state. The most relevant correction is “Restore routed reachability to the advertised VTEP and the correct tunnel forwarding state”.

Question 330

A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. Which initial check would most directly distinguish the likely cause?

  1. Inspect the tenant's SVI, gateway placement, host routes and effective Type 2 or Type 5 EVPN advertisements.
  2. Inspect the intended traffic flow and compare Type 2 endpoint routes with Type 5 routed-prefix routes.
  3. Compare gateway addresses, virtual MAC policy and SVI-to-VNI intent across the affected leafs.
  4. Inspect Type 5 prefix advertisements, route-target import and resolving next hops for the tenant VRF.

Explanation

Correct Answer

B:

This checks the relevant evidence first: inspect the intended traffic flow and compare Type 2 endpoint routes with Type 5 routed-prefix routes. The underlying concept is that EVPN endpoint and routed-prefix reachability use different route types and their import policy must match the data path. After confirming the finding, a controlled remediation is to advertise and import the required host or prefix routes according to the approved ERB routing design.

Incorrect Answers

A:

That choice—“Inspect the tenant's SVI, gateway placement, host routes and effective Type 2 or Type 5 EVPN advertisements”—addresses this other problem: A leaf gateway must route a workload's inter-subnet traffic locally rather than always hairpinning through a central aggregation switch. Here the scenario is: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. The relevant inspection is: Inspect the intended traffic flow and compare Type 2 endpoint routes with Type 5 routed-prefix routes. The most discriminating first check is “Inspect the intended traffic flow and compare Type 2 endpoint routes with Type 5 routed-prefix routes”.

C:

The option “Compare gateway addresses, virtual MAC policy and SVI-to-VNI intent across the affected leafs” is useful in a different setting: An anycast gateway design uses inconsistent SVI gateway parameters on two participating leafs. The case being tested is: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. The relevant inspection is: Inspect the intended traffic flow and compare Type 2 endpoint routes with Type 5 routed-prefix routes. The most discriminating first check is “Inspect the intended traffic flow and compare Type 2 endpoint routes with Type 5 routed-prefix routes”.

D:

“Inspect Type 5 prefix advertisements, route-target import and resolving next hops for the tenant VRF” is relevant to a different condition: An operator advertises an external IPv4 subnet into an EVPN routing domain for routed reachability. The stated question instead concerns: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. The relevant inspection is: Inspect the intended traffic flow and compare Type 2 endpoint routes with Type 5 routed-prefix routes. The most discriminating first check is “Inspect the intended traffic flow and compare Type 2 endpoint routes with Type 5 routed-prefix routes”.

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