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 80

Question 790

A greenfield project needs to decide whether the fabric template supports intended border connectivity and routing roles. Which evidence most directly verifies the intended network outcome?

  1. Confirm topology validation succeeds and the planned rack connections fit the chosen design.
  2. Show the design can add the forecast leaf ports without violating supported interface maps or capacity assumptions.
  3. Prove design-stage topology and resource validation before committing to hardware procurement.
  4. Confirm the modeled external links and routing connectivity satisfy the acceptance topology.

Explanation

Correct Answer

C:

This directly tests the desired result: prove design-stage topology and resource validation before committing to hardware procurement. The decisive investigation is to review intended external service connectivity and supported blueprint reference-design capabilities. The governing principle is that reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements.

Incorrect Answers

A:

That choice—“Confirm topology validation succeeds and the planned rack connections fit the chosen design”—addresses this other problem: A new pod requires a repeatable three-stage Clos layout but its design draft mixes unsupported spine counts and random cabling. Here the scenario is: A greenfield project needs to decide whether the fabric template supports intended border connectivity and routing roles. Reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements. The direct acceptance evidence is “Prove design-stage topology and resource validation before committing to hardware procurement”.

B:

“Show the design can add the forecast leaf ports without violating supported interface maps or capacity assumptions” is associated with a distinct issue: A planned Apstra fabric includes future rack growth but the initial design leaves no capacity for additional spine downlinks. By contrast, the actual problem is: A greenfield project needs to decide whether the fabric template supports intended border connectivity and routing roles. Reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements. The direct acceptance evidence is “Prove design-stage topology and resource validation before committing to hardware procurement”.

D:

“Confirm the modeled external links and routing connectivity satisfy the acceptance topology” is relevant to a different condition: A proposed rack blueprint includes all needed devices but its graph does not represent an external border connection required by applications. The stated question instead concerns: A greenfield project needs to decide whether the fabric template supports intended border connectivity and routing roles. Reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements. The direct acceptance evidence is “Prove design-stage topology and resource validation before committing to hardware procurement”.

Question 791

An expansion accidentally reuses a virtual network identifier assigned to another isolated overlay segment. Which evidence most directly verifies the intended network outcome?

  1. Verify all new logical devices receive unique assigned addresses and route reachability remains correct.
  2. Confirm a dry-run targets exactly the desired rack and leaf set and excludes other sites.
  3. Confirm each active virtual network has the intended unique or explicitly shared VNI mapping.
  4. Validate logical port counts and generated rack connections before building the blueprint.

Explanation

Correct Answer

C:

This directly tests the desired result: confirm each active virtual network has the intended unique or explicitly shared VNI mapping. The decisive investigation is to check the VNI resource pool, existing reservations and intended tenant-to-VN mappings. The governing principle is that managed VNI and other logical resource pools reduce collision risk when correctly partitioned and allocated.

Incorrect Answers

A:

“Verify all new logical devices receive unique assigned addresses and route reachability remains correct” is relevant to a different condition: An Apstra design runs out of loopback addresses when adding an additional leaf group. The stated question instead concerns: An expansion accidentally reuses a virtual network identifier assigned to another isolated overlay segment. Managed VNI and other logical resource pools reduce collision risk when correctly partitioned and allocated. The direct acceptance evidence is “Confirm each active virtual network has the intended unique or explicitly shared VNI mapping”.

B:

That choice—“Confirm a dry-run targets exactly the desired rack and leaf set and excludes other sites”—addresses this other problem: An automation wants to select switches tagged with a particular site and deployment tier. Here the scenario is: An expansion accidentally reuses a virtual network identifier assigned to another isolated overlay segment. Managed VNI and other logical resource pools reduce collision risk when correctly partitioned and allocated. The direct acceptance evidence is “Confirm each active virtual network has the intended unique or explicitly shared VNI mapping”.

D:

The option “Validate logical port counts and generated rack connections before building the blueprint” 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: An expansion accidentally reuses a virtual network identifier assigned to another isolated overlay segment. Managed VNI and other logical resource pools reduce collision risk when correctly partitioned and allocated. The direct acceptance evidence is “Confirm each active virtual network has the intended unique or explicitly shared VNI mapping”.

Question 792

A team wants scalable MAC learning across the fabric rather than sending every remote MAC advertisement by flood. Which design or operational principle best explains this behavior?

  1. BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership.
  2. A VTEP provides VXLAN encapsulation and decapsulation and its IP reachability must exist independently of bridge membership.
  3. VXLAN adds encapsulation overhead and requires adequate path MTU or effective payload sizing.
  4. EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data.

Explanation

Correct Answer

D:

EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data. Here, a team wants scalable MAC learning across the fabric rather than sending every remote MAC advertisement by flood. A useful discriminating check is to inspect EVPN route exchange and the selected VTEP's learned endpoint state instead of inferring learning from floods.

Incorrect Answers

A:

The option “BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership” is useful in a different setting: An overlay virtual network has the correct VNI but unknown destination traffic continues to flood farther than intended. The case being tested is: A team wants scalable MAC learning across the fabric rather than sending every remote MAC advertisement by flood. EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data. The controlling principle is “EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data”.

B:

“A VTEP provides VXLAN encapsulation and decapsulation and its IP reachability must exist independently of bridge membership” is relevant to a different condition: An endpoint's remote leaf cannot deliver traffic even though the local access VLAN is assigned correctly because the tunnel endpoint is unreachable. The stated question instead concerns: A team wants scalable MAC learning across the fabric rather than sending every remote MAC advertisement by flood. EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data. The controlling principle is “EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data”.

C:

That choice—“VXLAN adds encapsulation overhead and requires adequate path MTU or effective payload sizing”—addresses this other problem: A VXLAN packet encapsulation crosses a routed fabric but is discarded along the path due to frame size. Here the scenario is: A team wants scalable MAC learning across the fabric rather than sending every remote MAC advertisement by flood. EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data. The controlling principle is “EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data”.

Question 793

A new blueprint shows red validation errors before any managed device has received configuration. Which initial check would most directly distinguish the likely cause?

  1. Inspect selected template, interface map, device profile and advertised NOS capabilities.
  2. Compare the referenced template version and current active blueprint state before propagating design changes.
  3. Compare required external routing connections with the template topology and leaf roles.
  4. Review the blueprint build validation details for missing pools, interface assignments and logical links.

Explanation

Correct Answer

D:

This checks the relevant evidence first: review the blueprint build validation details for missing pools, interface assignments and logical links. The underlying concept is that design-phase resource and topology validation must succeed before a controlled deployment can be trusted. After confirming the finding, a controlled remediation is to resolve the specific design and resource conflicts and regenerate intended configuration.

Incorrect Answers

A:

“Inspect selected template, interface map, device profile and advertised NOS capabilities” is associated with a distinct issue: A blueprint uses a template intended for a different network OS and generated configuration contains unsupported syntax. By contrast, the actual problem is: A new blueprint shows red validation errors before any managed device has received configuration. The relevant inspection is: Review the blueprint build validation details for missing pools, interface assignments and logical links. The most discriminating first check is “Review the blueprint build validation details for missing pools, interface assignments and logical links”.

B:

The option “Compare the referenced template version and current active blueprint state before propagating design changes” is useful in a different setting: A reference template changes its interface model after three production blueprints have already deployed. The case being tested is: A new blueprint shows red validation errors before any managed device has received configuration. The relevant inspection is: Review the blueprint build validation details for missing pools, interface assignments and logical links. The most discriminating first check is “Review the blueprint build validation details for missing pools, interface assignments and logical links”.

C:

“Compare required external routing connections with the template topology and leaf roles” is relevant to a different condition: An engineer finishes a fabric template without any modeled north-south peering attachment points. The stated question instead concerns: A new blueprint shows red validation errors before any managed device has received configuration. The relevant inspection is: Review the blueprint build validation details for missing pools, interface assignments and logical links. The most discriminating first check is “Review the blueprint build validation details for missing pools, interface assignments and logical links”.

Question 794

A blueprint uses a template intended for a different network OS and generated configuration contains unsupported syntax. Which evidence most directly verifies the intended network outcome?

  1. Confirm the blueprint build validation clears and expected rendered configurations are available for review.
  2. Confirm the modeled external links and routing connectivity satisfy the acceptance topology.
  3. Confirm each targeted blueprint reflects the expected revision and existing production services remain healthy.
  4. Verify syntax validation and successful controlled deployment to representative supported devices.

Explanation

Correct Answer

D:

This directly tests the desired result: verify syntax validation and successful controlled deployment to representative supported devices. The decisive investigation is to inspect selected template, interface map, device profile and advertised NOS capabilities. The governing principle is that blueprint templates, device profiles and NOS-specific rendering must align to the supported combination.

Incorrect Answers

A:

That choice—“Confirm the blueprint build validation clears and expected rendered configurations are available for review”—addresses this other problem: A new blueprint shows red validation errors before any managed device has received configuration. Here the scenario is: A blueprint uses a template intended for a different network OS and generated configuration contains unsupported syntax. Blueprint templates, device profiles and NOS-specific rendering must align to the supported combination. The direct acceptance evidence is “Verify syntax validation and successful controlled deployment to representative supported devices”.

B:

“Confirm the modeled external links and routing connectivity satisfy the acceptance topology” is associated with a distinct issue: An engineer finishes a fabric template without any modeled north-south peering attachment points. By contrast, the actual problem is: A blueprint uses a template intended for a different network OS and generated configuration contains unsupported syntax. Blueprint templates, device profiles and NOS-specific rendering must align to the supported combination. The direct acceptance evidence is “Verify syntax validation and successful controlled deployment to representative supported devices”.

C:

The option “Confirm each targeted blueprint reflects the expected revision and existing production services remain healthy” is useful in a different setting: A design template was edited after the first rack was built and an engineer assumes existing active blueprints are retroactively rewritten. The case being tested is: A blueprint uses a template intended for a different network OS and generated configuration contains unsupported syntax. Blueprint templates, device profiles and NOS-specific rendering must align to the supported combination. The direct acceptance evidence is “Verify syntax validation and successful controlled deployment to representative supported devices”.

Question 795

A team assigns a device image and platform combination not supported by the chosen Apstra reference design. Which controlled change best addresses the described requirement?

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

Explanation

Correct Answer

D:

This action addresses the stated defect: choose an officially supported template and platform combination and regenerate the blueprint configuration. The underlying constraint is that blueprint templates, device profiles and NOS-specific rendering must align to the supported combination. Verify rather than assume success: verify syntax validation and successful controlled deployment to representative supported devices.

Incorrect Answers

A:

“Resolve the specific design and resource conflicts and regenerate intended configuration” is relevant to a different condition: A new blueprint shows red validation errors before any managed device has received configuration. The stated question instead concerns: A team assigns a device image and platform combination not supported by the chosen Apstra reference design. Choose an officially supported template and platform combination and regenerate the blueprint configuration. The most relevant correction is “Choose an officially supported template and platform combination and regenerate the blueprint configuration”.

B:

That choice—“Stage and review each intended blueprint update through an approved migration or change process”—addresses this other problem: A design template was edited after the first rack was built and an engineer assumes existing active blueprints are retroactively rewritten. Here the scenario is: A team assigns a device image and platform combination not supported by the chosen Apstra reference design. Choose an officially supported template and platform combination and regenerate the blueprint configuration. The most relevant correction is “Choose an officially supported template and platform combination and regenerate the blueprint configuration”.

C:

“Extend the approved blueprint design to include appropriate border connectivity and associated resources” is associated with a distinct issue: An engineer finishes a fabric template without any modeled north-south peering attachment points. By contrast, the actual problem is: A team assigns a device image and platform combination not supported by the chosen Apstra reference design. Choose an officially supported template and platform combination and regenerate the blueprint configuration. The most relevant correction is “Choose an officially supported template and platform combination and regenerate the blueprint configuration”.

Question 796

A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. Which initial check would most directly distinguish the likely cause?

  1. Inspect underlay routing adjacency, interface addressing and reachability to the spine or leaf loopback endpoints.
  2. Inspect installed ECMP next hops and compare per-link counters across multiple distinct flows.
  3. Check interface state, routing convergence and forwarding entries following the simulated spine-link loss.
  4. Compare the proposed physical topology with the selected reference design and expected leaf-spine connectivity.

Explanation

Correct Answer

D:

This checks the relevant evidence first: compare the proposed physical topology with the selected reference design and expected leaf-spine connectivity. The underlying concept is that in a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling. After confirming the finding, a controlled remediation is to use validated spine-leaf cabling and routing relationships rather than ad hoc lateral transit links.

Incorrect Answers

A:

The option “Inspect underlay routing adjacency, interface addressing and reachability to the spine or leaf loopback endpoints” is useful in a different setting: An additional rack joins a Clos fabric with healthy physical interfaces but fails to form underlay neighbor sessions. 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. The relevant inspection is: Compare the proposed physical topology with the selected reference design and expected leaf-spine connectivity. The most discriminating first check is “Compare the proposed physical topology with the selected reference design and expected leaf-spine connectivity”.

B:

“Inspect installed ECMP next hops and compare per-link counters across multiple distinct flows” is relevant to a different condition: An operator finds two equal-cost fabric paths but a single large traffic flow consistently traverses only one link. The stated question instead concerns: A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. The relevant inspection is: Compare the proposed physical topology with the selected reference design and expected leaf-spine connectivity. The most discriminating first check is “Compare the proposed physical topology with the selected reference design and expected leaf-spine connectivity”.

C:

That choice—“Check interface state, routing convergence and forwarding entries following the simulated spine-link loss”—addresses this other problem: A two-spine fabric can tolerate one path failure but the application sees blackholing for several minutes after a spine uplink drops. 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. The relevant inspection is: Compare the proposed physical topology with the selected reference design and expected leaf-spine connectivity. The most discriminating first check is “Compare the proposed physical topology with the selected reference design and expected leaf-spine connectivity”.

Question 797

A dual leaf rack is expected to provide application diversity but both uplinks terminate on the same physical spine. Which evidence most directly verifies the intended network outcome?

  1. Demonstrate both host attachments map to intended leafs and a single leaf loss meets recovery objectives.
  2. Validate intended path diversity against the generated cable map and a controlled spine failure test.
  3. Confirm each instantiated rack matches its logical leaf/uplink topology and allocated resources.
  4. Prove free compatible spine ports remain after allocating every forecast uplink.

Explanation

Correct Answer

B:

This directly tests the desired result: validate intended path diversity against the generated cable map and a controlled spine failure test. The decisive investigation is to inspect the rack type's expected spine attachment graph and actual cable endpoints. The governing principle is that physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required.

Incorrect Answers

A:

“Demonstrate both host attachments map to intended leafs and a single leaf loss meets recovery objectives” is associated with a distinct issue: A storage workload requires dual-homed servers but a proposed rack type provides only one access leaf. By contrast, the actual problem is: A dual leaf rack is expected to provide application diversity but both uplinks terminate on the same physical spine. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. The direct acceptance evidence is “Validate intended path diversity against the generated cable map and a controlled spine failure test”.

C:

“Confirm each instantiated rack matches its logical leaf/uplink topology and allocated resources” is relevant to a different condition: An Apstra design must deploy 12 racks with uniform leaf roles and uplink constraints. The stated question instead concerns: A dual leaf rack is expected to provide application diversity but both uplinks terminate on the same physical spine. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. The direct acceptance evidence is “Validate intended path diversity against the generated cable map and a controlled spine failure test”.

D:

That choice—“Prove free compatible spine ports remain after allocating every forecast uplink”—addresses this other problem: A new tenant floor requests six leaf uplinks but fabric spines are fully committed to existing racks. Here the scenario is: A dual leaf rack is expected to provide application diversity but both uplinks terminate on the same physical spine. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. The direct acceptance evidence is “Validate intended path diversity against the generated cable map and a controlled spine failure test”.

Question 798

A customer asks why adding a second spine path does not necessarily double the rate of one elephant-flow TCP session. 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. In a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling.
  4. Overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes.

Explanation

Correct Answer

A:

equal-cost multipath commonly hashes individual flows to a path while distributing many flows across available next hops. Here, a customer asks why adding a second spine path does not necessarily double the rate of one elephant-flow TCP session. A useful discriminating check is to inspect installed ECMP next hops and compare per-link counters across multiple distinct flows.

Incorrect Answers

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 customer asks why adding a second spine path does not necessarily double the rate of one elephant-flow TCP session. Equal-cost multipath commonly hashes individual flows to a path while distributing many flows across available next hops. The controlling principle is “Equal-cost multipath commonly hashes individual flows to a path while distributing many flows across available next hops”.

C:

The option “In a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling” is useful in a different setting: A migration plan connects every rack leaf laterally and treats spine devices as only optional edge routers. The case being tested is: A customer asks why adding a second spine path does not necessarily double the rate of one elephant-flow TCP session. Equal-cost multipath commonly hashes individual flows to a path while distributing many flows across available next hops. The controlling principle is “Equal-cost multipath commonly hashes individual flows to a path while distributing many flows across available next hops”.

D:

“Overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes” is relevant to a different condition: An engineer brings up BGP peers to the spines but omits export of the overlay endpoint loopbacks. The stated question instead concerns: A customer asks why adding a second spine path does not necessarily double the rate of one elephant-flow TCP session. Equal-cost multipath commonly hashes individual flows to a path while distributing many flows across available next hops. The controlling principle is “Equal-cost multipath commonly hashes individual flows to a path while distributing many flows across available next hops”.

Question 799

A dashboard reports that all switches are reachable while a recent staged policy change has not been deployed. 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. Correct the mismatched service intent or deployed configuration while preserving authorized tenant isolation.
  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 relevant to a different condition: Two changes are awaiting commit, and an operator wants to deploy only one without understanding the other outstanding edits. The stated question instead concerns: A dashboard reports that all switches are reachable while a recent staged policy change has not been deployed. 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:

That choice—“Complete review and commit of the authorized staged change, then monitor device convergence”—addresses this other problem: A service owner tests a new VRF assignment while the proposed change appears only in the Staged view. Here the scenario is: A dashboard reports that all switches are reachable while a recent staged policy change has not been deployed. 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:

“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 dashboard reports that all switches are reachable while a recent staged policy change has not been deployed. 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 800

An external peer receives a tenant's internal subnets that were supposed to stay private. Which evidence most directly verifies the intended network outcome?

  1. Verify the intended external session and imported/exported prefixes appear only in the proper tenant routing context.
  2. Confirm the host receives exactly the intended VLANs and no unrelated tenant traffic.
  3. Confirm only approved routes are exchanged and unauthorized prefixes no longer leave the fabric.
  4. Confirm migrated VMs communicate over the intended tenant VN while unauthorized networks remain unreachable.

Explanation

Correct Answer

C:

This directly tests the desired result: confirm only approved routes are exchanged and unauthorized prefixes no longer leave the fabric. The decisive investigation is to inspect the route export/import policy and observed advertised routes for the affected VRF. The governing principle is that routing policy and connectivity-template scope determine which tenant prefixes cross external boundaries.

Incorrect Answers

A:

The option “Verify the intended external session and imported/exported prefixes appear only in the proper tenant routing context” is useful in a different setting: A routed external firewall must exchange routes with a border leaf for only one tenant VRF. The case being tested is: An external peer receives a tenant's internal subnets that were supposed to stay private. Routing policy and connectivity-template scope determine which tenant prefixes cross external boundaries. The direct acceptance evidence is “Confirm only approved routes are exchanged and unauthorized prefixes no longer leave the fabric”.

B:

“Confirm the host receives exactly the intended VLANs and no unrelated tenant traffic” is relevant to a different condition: A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. The stated question instead concerns: An external peer receives a tenant's internal subnets that were supposed to stay private. Routing policy and connectivity-template scope determine which tenant prefixes cross external boundaries. The direct acceptance evidence is “Confirm only approved routes are exchanged and unauthorized prefixes no longer leave the fabric”.

D:

“Confirm migrated VMs communicate over the intended tenant VN while unauthorized networks remain unreachable” is associated with a distinct issue: A virtualized server moves to another rack and vCenter shows the correct network label while the fabric lacks the required VN attachment. By contrast, the actual problem is: An external peer receives a tenant's internal subnets that were supposed to stay private. Routing policy and connectivity-template scope determine which tenant prefixes cross external boundaries. The direct acceptance evidence is “Confirm only approved routes are exchanged and unauthorized prefixes no longer leave the fabric”.

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