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 34

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”.

Question 331

Two tenants use overlapping private subnets and the team fears one tenant's routes will be mistaken for the other. Which shortcut would be most likely to undermine this objective?

  1. Disable tenant-specific route import controls globally as a quick way to make MAC routes appear.
  2. Assume Type 2 MAC advertisements alone always provide every external routed subnet.
  3. Treat the two legs of a multihomed Ethernet segment as unrelated unmanaged single-homed endpoints.
  4. Configure the same unrestricted import policy for every tenant just because route distinguishers differ.

Explanation

Correct Answer

D:

This is the unsafe shortcut to avoid: configure the same unrestricted import policy for every tenant just because route distinguishers differ. It violates the principle that EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution. An appropriate alternative is to assign unique route distinguishing context and appropriate route target import and export policy without leaking tenants.

Incorrect Answers

A:

“Disable tenant-specific route import controls globally as a quick way to make MAC routes appear” is relevant to a different condition: Two leaves advertise the same virtual network yet one leaf rejects the other's EVPN MAC routes. The stated question instead concerns: Two tenants use overlapping private subnets and the team fears one tenant's routes will be mistaken for the other. EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution. The directly relevant unsafe shortcut is “Configure the same unrestricted import policy for every tenant just because route distinguishers differ”.

B:

That choice—“Assume Type 2 MAC advertisements alone always provide every external routed subnet”—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. EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution. The directly relevant unsafe shortcut is “Configure the same unrestricted import policy for every tenant just because route distinguishers differ”.

C:

“Treat the two legs of a multihomed Ethernet segment as unrelated unmanaged single-homed endpoints” 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: Two tenants use overlapping private subnets and the team fears one tenant's routes will be mistaken for the other. EVPN route distinguishers distinguish otherwise identical route identifiers while route targets govern intended import and export distribution. The directly relevant unsafe shortcut is “Configure the same unrestricted import policy for every tenant just because route distinguishers differ”.

Question 332

A new switch reports Ready while its peers remain in a deployment-failed state after committing fabric intent. Which evidence most directly verifies the intended network outcome?

  1. Confirm discovered links match the staged cable map and link-state anomalies clear.
  2. Observe matching physical and logical connectivity and no unresolved cabling anomalies.
  3. Confirm all affected devices converge on the active blueprint revision without config drift.
  4. Confirm active intent, device configuration and required network tests agree on the intended result.

Explanation

Correct Answer

C:

This directly tests the desired result: confirm all affected devices converge on the active blueprint revision without config drift. The decisive investigation is to check each device's state, failed action details and intended-versus-running configuration revision. The governing principle is that per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly.

Incorrect Answers

A:

The option “Confirm discovered links match the staged cable map and link-state anomalies clear” is useful in a different setting: A newly staged fabric reports LLDP neighbor mismatches although physical links are up. The case being tested is: A new switch reports Ready while its peers remain in a deployment-failed state after committing fabric intent. Per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly. The direct acceptance evidence is “Confirm all affected devices converge on the active blueprint revision without config drift”.

B:

“Observe matching physical and logical connectivity and no unresolved cabling anomalies” is relevant to a different condition: A staging team has different cable-map snapshots from design and observed discovery data. The stated question instead concerns: A new switch reports Ready while its peers remain in a deployment-failed state after committing fabric intent. Per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly. The direct acceptance evidence is “Confirm all affected devices converge on the active blueprint revision without config drift”.

D:

“Confirm active intent, device configuration and required network tests agree on the intended result” 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 new switch reports Ready while its peers remain in a deployment-failed state after committing fabric intent. Per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly. The direct acceptance evidence is “Confirm all affected devices converge on the active blueprint revision without config drift”.

Question 333

A network team needs to distinguish observed operational health from whether the desired blueprint configuration is active. Which controlled change best addresses the described requirement?

  1. Separate, revert or review unrelated staged edits before an authorized commit according to process.
  2. Complete review and commit of the authorized staged change, then monitor device convergence.
  3. Investigate unexpected changes using the appropriate generated-config view and approved override workflow.
  4. Use each blueprint tab for its intended lifecycle step and deploy changes only after authorized review.

Explanation

Correct Answer

D:

This action addresses the stated defect: use each blueprint tab for its intended lifecycle step and deploy changes only after authorized review. The underlying constraint is that device health, intended active blueprint state and pending staged edits describe different dimensions of operations. Verify rather than assume success: confirm device health and active configuration separately, then document any pending staged work.

Incorrect Answers

A:

“Separate, revert or review unrelated staged edits before an authorized commit according to process” is associated with a distinct issue: Two changes are awaiting commit, and an operator wants to deploy only one without understanding the other outstanding edits. By contrast, the actual problem is: A network team needs to distinguish observed operational health from whether the desired blueprint configuration is active. The governing requirement is to use each blueprint tab for its intended lifecycle step and deploy changes only after authorized review. The most relevant correction is “Use each blueprint tab for its intended lifecycle step and deploy changes only after authorized review”.

B:

The option “Complete review and commit of the authorized staged change, then monitor device convergence” is useful in a different setting: An engineer edits a virtual network in a blueprint but cannot see the change reflected in the active switch configuration. The case being tested is: A network team needs to distinguish observed operational health from whether the desired blueprint configuration is active. The governing requirement is to use each blueprint tab for its intended lifecycle step and deploy changes only after authorized review. The most relevant correction is “Use each blueprint tab for its intended lifecycle step and deploy changes only after authorized review”.

C:

“Investigate unexpected changes using the appropriate generated-config view and approved override workflow” is relevant to a different condition: An audit asks why some device commands come from the baseline while others appear from intended virtual-network configuration. The stated question instead concerns: A network team needs to distinguish observed operational health from whether the desired blueprint configuration is active. The governing requirement is to use each blueprint tab for its intended lifecycle step and deploy changes only after authorized review. The most relevant correction is “Use each blueprint tab for its intended lifecycle step and deploy changes only after authorized review”.

Question 334

A monitoring team wants to detect rising discards on the uplinks of one specific leaf group. Which evidence most directly verifies the intended network outcome?

  1. Generate a controlled test condition and confirm the probe reports the expected anomaly with accurate context.
  2. Confirm only the intended rack or tenant objects generate results and anomalies on repeat tests.
  3. Verify staged derived metrics match sample inputs and test threshold crossings produce accurate alarms.
  4. Confirm the result contains all intended rack uplinks and excludes unrelated interface objects.

Explanation

Correct Answer

A:

This directly tests the desired result: generate a controlled test condition and confirm the probe reports the expected anomaly with accurate context. The decisive investigation is to inspect probe data sources, monitored stages, thresholds and the exact interfaces being selected. The governing principle is that Apstra IBA probes process collected telemetry against conditions or expectations and can raise anomalies.

Incorrect Answers

B:

“Confirm only the intended rack or tenant objects generate results and anomalies on repeat tests” is associated with a distinct issue: A built-in analytics probe reports a metric but cannot identify why the value changed after a rack migration. By contrast, the actual problem is: A monitoring team wants to detect rising discards on the uplinks of one specific leaf group. Apstra IBA probes process collected telemetry against conditions or expectations and can raise anomalies. The direct acceptance evidence is “Generate a controlled test condition and confirm the probe reports the expected anomaly with accurate context”.

C:

The option “Verify staged derived metrics match sample inputs and test threshold crossings produce accurate alarms” is useful in a different setting: A team wants an analytics alert if interface utilization deviates from baseline while still retaining raw evidence. The case being tested is: A monitoring team wants to detect rising discards on the uplinks of one specific leaf group. Apstra IBA probes process collected telemetry against conditions or expectations and can raise anomalies. The direct acceptance evidence is “Generate a controlled test condition and confirm the probe reports the expected anomaly with accurate context”.

D:

“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: A monitoring team wants to detect rising discards on the uplinks of one specific leaf group. Apstra IBA probes process collected telemetry against conditions or expectations and can raise anomalies. The direct acceptance evidence is “Generate a controlled test condition and confirm the probe reports the expected anomaly with accurate context”.

Question 335

A new leaf rack should use a repeatable single-leaf topology but its manually modeled connections differ from existing identical racks. Which shortcut would be most likely to undermine this objective?

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

Explanation

Correct Answer

C:

This is the unsafe shortcut to avoid: create a new ad hoc rack type for every identical rack without checking design drift. It violates the principle that rack types are reusable logical patterns for leaf topology and attached systems within a blueprint. An appropriate alternative is to create or select the approved reusable rack type and instantiate the rack consistently.

Incorrect Answers

A:

“Ignore port and oversubscription limits because Apstra can generate logical connections automatically” is relevant to a different condition: A new tenant floor requests six leaf uplinks but fabric spines are fully committed to existing racks. The stated question instead concerns: A new leaf rack should use a repeatable single-leaf topology but its manually modeled connections differ from existing identical racks. Rack types are reusable logical patterns for leaf topology and attached systems within a blueprint. The directly relevant unsafe shortcut is “Create a new ad hoc rack type for every identical rack without checking design drift”.

B:

That choice—“Label a single-leaf rack as redundant merely because it has two host-facing ports”—addresses this other problem: A storage workload requires dual-homed servers but a proposed rack type provides only one access leaf. Here the scenario is: A new leaf rack should use a repeatable single-leaf topology but its manually modeled connections differ from existing identical racks. Rack types are reusable logical patterns for leaf topology and attached systems within a blueprint. The directly relevant unsafe shortcut is “Create a new ad hoc rack type for every identical rack without checking design drift”.

D:

The option “Count two cables as independent redundancy even when both share the same single upstream switch” is useful in a different setting: A data center cabling plan repeats one spine endpoint for all redundant paths from a critical rack. The case being tested is: A new leaf rack should use a repeatable single-leaf topology but its manually modeled connections differ from existing identical racks. Rack types are reusable logical patterns for leaf topology and attached systems within a blueprint. The directly relevant unsafe shortcut is “Create a new ad hoc rack type for every identical rack without checking design drift”.

Question 336

A blueprint operator maintains repeated data center operational variables that should have a single validated definition. Which design or operational principle best explains this behavior?

  1. Configlets can extend generated device configuration through controlled, scoped supplemental configuration.
  2. Apstra property sets can centralize reusable named parameters referenced by supported configuration templates.
  3. Configlet applicability must be scoped precisely to affected devices and interfaces.
  4. Device health, intended active blueprint state and pending staged edits describe different dimensions of operations.

Explanation

Correct Answer

B:

Apstra property sets can centralize reusable named parameters referenced by supported configuration templates. Here, a blueprint operator maintains repeated data center operational variables that should have a single validated definition. A useful discriminating check is to inspect property-set values, consumers and intended scope before updating a shared parameter.

Incorrect Answers

A:

The option “Configlets can extend generated device configuration through controlled, scoped supplemental configuration” is useful in a different setting: An application requires a supported vendor-specific setting absent from the blueprint's default rendered commands. The case being tested is: A blueprint operator maintains repeated data center operational variables that should have a single validated definition. Apstra property sets can centralize reusable named parameters referenced by supported configuration templates. The controlling principle is “Apstra property sets can centralize reusable named parameters referenced by supported configuration templates”.

C:

That choice—“Configlet applicability must be scoped precisely to affected devices and interfaces”—addresses this other problem: An engineer discovers that a supplemental configuration template was bound to an overly broad tag. Here the scenario is: A blueprint operator maintains repeated data center operational variables that should have a single validated definition. Apstra property sets can centralize reusable named parameters referenced by supported configuration templates. The controlling principle is “Apstra property sets can centralize reusable named parameters referenced by supported configuration templates”.

D:

“Device health, intended active blueprint state and pending staged edits describe different dimensions of operations” is associated with a distinct issue: A network team needs to distinguish observed operational health from whether the desired blueprint configuration is active. By contrast, the actual problem is: A blueprint operator maintains repeated data center operational variables that should have a single validated definition. Apstra property sets can centralize reusable named parameters referenced by supported configuration templates. The controlling principle is “Apstra property sets can centralize reusable named parameters referenced by supported configuration templates”.

Question 337

Two tenants require a controlled shared service, and a proposal suggests importing every route into each tenant VRF. Which design or operational principle best explains this behavior?

  1. Shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation.
  2. DCI design must coordinate intended virtual-network IDs, routing zones and controlled route distribution between sites.
  3. Hypervisor network labels and Apstra fabric virtual-network connectivity must both represent the intended tenant service.
  4. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone.

Explanation

Correct Answer

A:

shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation. Here, two tenants require a controlled shared service, and a proposal suggests importing every route into each tenant VRF. A useful discriminating check is to inspect the proposed external or shared-services routing path, import policy and required security controls.

Incorrect Answers

B:

The option “DCI design must coordinate intended virtual-network IDs, routing zones and controlled route distribution between sites” is useful in a different setting: A data-center interconnect extends selected tenant segments between two sites but one site imports unrelated virtual networks. The case being tested is: Two tenants require a controlled shared service, and a proposal suggests importing every route into each tenant VRF. Shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation. The controlling principle is “Shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation”.

C:

“Hypervisor network labels and Apstra fabric virtual-network connectivity must both represent the intended tenant service” is relevant to a different condition: A virtualized server moves to another rack and vCenter shows the correct network label while the fabric lacks the required VN attachment. The stated question instead concerns: Two tenants require a controlled shared service, and a proposal suggests importing every route into each tenant VRF. Shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation. The controlling principle is “Shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation”.

D:

That choice—“Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone”—addresses this other problem: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Here the scenario is: Two tenants require a controlled shared service, and a proposal suggests importing every route into each tenant VRF. Shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation. The controlling principle is “Shared-service connectivity must be explicitly routed and filtered without collapsing tenant VRF isolation”.

Question 338

A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. Which design or operational principle best explains this behavior?

  1. Equal-cost multipath commonly hashes individual flows to a path while distributing many flows across available next hops.
  2. Path redundancy only improves availability when failed underlay next hops are withdrawn or detected promptly.
  3. An IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly.
  4. In a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling.

Explanation

Correct Answer

D:

in a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling. Here, a team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. A useful discriminating check is to compare the proposed physical topology with the selected reference design and expected leaf-spine connectivity.

Incorrect Answers

A:

That choice—“Equal-cost multipath commonly hashes individual flows to a path while distributing many flows across available next hops”—addresses this other problem: An operator finds two equal-cost fabric paths but a single large traffic flow consistently traverses only one link. Here the scenario is: A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. In a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling. The controlling principle is “In a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling”.

B:

“Path redundancy only improves availability when failed underlay next hops are withdrawn or detected promptly” is associated with a distinct issue: A fabric uses two equal-cost underlay next hops yet packets continue toward a failed path following a port outage. By contrast, the actual problem is: A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. In a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling. The controlling principle is “In a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling”.

C:

The option “An IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly” 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 team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. In a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling. The controlling principle is “In a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling”.

Question 339

A new Apstra deployment includes baseline settings, platform-specific changes and generated overlay commands that an engineer wants to distinguish. Which design or operational principle best explains this behavior?

  1. Controlled build and deploy phases separate design validation, reviewed staged changes and active device updates.
  2. Configuration views represent different aspects of the managed device configuration and should be interpreted in their proper context.
  3. Staging and rendering intended configuration are distinct from committing and deploying the active blueprint.
  4. Per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly.

Explanation

Correct Answer

B:

configuration views represent different aspects of the managed device configuration and should be interpreted in their proper context. Here, a new Apstra deployment includes baseline settings, platform-specific changes and generated overlay commands that an engineer wants to distinguish. A useful discriminating check is to compare pristine, incremental and rendered configuration artifacts for the targeted device and intended change.

Incorrect Answers

A:

“Controlled build and deploy phases separate design validation, reviewed staged changes and active device updates” 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. Configuration views represent different aspects of the managed device configuration and should be interpreted in their proper context. The controlling principle is “Configuration views represent different aspects of the managed device configuration and should be interpreted in their proper context”.

C:

“Staging and rendering intended configuration are distinct from committing and deploying the active blueprint” 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 controlling principle is “Configuration views represent different aspects of the managed device configuration and should be interpreted in their proper context”.

D:

The option “Per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly” is useful in a different setting: An operator sees devices in mixed managed states and cannot tell which switches received the new active configuration. 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 controlling principle is “Configuration views represent different aspects of the managed device configuration and should be interpreted in their proper context”.

Question 340

A fabric sees unexpectedly broad BUM traffic after a new VXLAN virtual network is provisioned. Which design or operational principle best explains this behavior?

  1. A VTEP provides VXLAN encapsulation and decapsulation and its IP reachability must exist independently of bridge membership.
  2. BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership.
  3. EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data.
  4. The VNI associates overlay VXLAN traffic with the intended virtual network, so inconsistent VLAN-to-VNI mapping breaks isolation or connectivity.

Explanation

Correct Answer

B:

BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership. Here, a fabric sees unexpectedly broad BUM traffic after a new VXLAN virtual network is provisioned. A useful discriminating check is to inspect broadcast, unknown-unicast and multicast handling and participating VTEPs for the affected VNI.

Incorrect Answers

A:

The option “A VTEP provides VXLAN encapsulation and decapsulation and its IP reachability must exist independently of bridge membership” is useful in a different setting: A virtualization cluster is moved to another rack and its EVPN routes exist but the remote VXLAN encapsulation next hop fails. The case being tested is: A fabric sees unexpectedly broad BUM traffic after a new VXLAN virtual network is provisioned. BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership. The controlling principle is “BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership”.

C:

That choice—“EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data”—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: A fabric sees unexpectedly broad BUM traffic after a new VXLAN virtual network is provisioned. BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership. The controlling principle is “BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership”.

D:

“The VNI associates overlay VXLAN traffic with the intended virtual network, so inconsistent VLAN-to-VNI mapping breaks isolation or connectivity” 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: A fabric sees unexpectedly broad BUM traffic after a new VXLAN virtual network is provisioned. BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership. The controlling principle is “BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership”.

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