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 76

Question 750

A new QFX leaf responds to management pings while the Apstra device manager reports no valid agent identity. Which controlled change best addresses the described requirement?

  1. Assign the replacement supported system to the correct logical role using the documented controlled process.
  2. Correct the duplicate device registration and assign each real device its own validated identity.
  3. Correct physical cabling or update the approved design only after confirming the intended topology.
  4. Install or repair the supported agent and associate the correct device identity through approved onboarding.

Explanation

Correct Answer

D:

This action addresses the stated defect: install or repair the supported agent and associate the correct device identity through approved onboarding. The underlying constraint is that Apstra fabric onboarding needs a compatible managed agent and correctly established system identity, not only IP connectivity. Verify rather than assume success: confirm the device appears healthy, available and uniquely identified for blueprint assignment.

Incorrect Answers

A:

That choice—“Assign the replacement supported system to the correct logical role using the documented controlled process”—addresses this other problem: A failed managed switch is swapped physically yet Apstra refuses deployment to the replacement inventory device. Here the scenario is: A new QFX leaf responds to management pings while the Apstra device manager reports no valid agent identity. Install or repair the supported agent and associate the correct device identity through approved onboarding. The most relevant correction is “Install or repair the supported agent and associate the correct device identity through approved onboarding”.

B:

“Correct the duplicate device registration and assign each real device its own validated identity” is associated with a distinct issue: A deployment team duplicates a device-system ID when registering two new leaf switches. By contrast, the actual problem is: A new QFX leaf responds to management pings while the Apstra device manager reports no valid agent identity. Install or repair the supported agent and associate the correct device identity through approved onboarding. The most relevant correction is “Install or repair the supported agent and associate the correct device identity through approved onboarding”.

C:

The option “Correct physical cabling or update the approved design only after confirming the intended topology” 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 QFX leaf responds to management pings while the Apstra device manager reports no valid agent identity. Install or repair the supported agent and associate the correct device identity through approved onboarding. The most relevant correction is “Install or repair the supported agent and associate the correct device identity through approved onboarding”.

Question 751

A change adds a server port to a device profile but accidentally reserves the same port for spine connectivity. Which evidence most directly verifies the intended network outcome?

  1. Confirm rendered port assignments match the physical cable map and supported switch interfaces.
  2. Validate that physical port assignments and supported speeds match the rack design without resource conflicts.
  3. Confirm the design validator has no duplicate port assignments and each link role maps to the intended connector.
  4. Confirm each active virtual network has the intended unique or explicitly shared VNI mapping.

Explanation

Correct Answer

C:

This directly tests the desired result: confirm the design validator has no duplicate port assignments and each link role maps to the intended connector. The decisive investigation is to inspect the interface map and assigned logical device port roles for overlapping reservations. The governing principle is that a physical interface cannot simultaneously satisfy conflicting logical interface assignments in a validated blueprint.

Incorrect Answers

A:

“Confirm rendered port assignments match the physical cable map and supported switch interfaces” is relevant to a different condition: A template identifies uplink ports by logical role but a new hardware SKU has different port naming. 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 direct acceptance evidence is “Confirm the design validator has no duplicate port assignments and each link role maps to the intended connector”.

B:

That choice—“Validate that physical port assignments and supported speeds match the rack design without resource conflicts”—addresses this other problem: 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. 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 direct acceptance evidence is “Confirm the design validator has no duplicate port assignments and each link role maps to the intended connector”.

D:

The option “Confirm each active virtual network has the intended unique or explicitly shared VNI mapping” is useful in a different setting: An expansion accidentally reuses a virtual network identifier assigned to another isolated overlay segment. 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 direct acceptance evidence is “Confirm the design validator has no duplicate port assignments and each link role maps to the intended connector”.

Question 752

A storage workload requires dual-homed servers but a proposed rack type provides only one access leaf. Which evidence most directly verifies the intended network outcome?

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

Explanation

Correct Answer

C:

This directly tests the desired result: demonstrate both host attachments map to intended leafs and a single leaf loss meets recovery objectives. The decisive investigation is to review single-versus-dual leaf rack settings and server connectivity requirements. The governing principle is that rack type and leaf selection must support the intended redundant attachment topology and host interface roles.

Incorrect Answers

A:

The option “Validate intended path diversity against the generated cable map and a controlled spine failure test” is useful in a different setting: A dual leaf rack is expected to provide application diversity but both uplinks terminate on the same physical spine. The case being tested is: A storage workload requires dual-homed servers but a proposed rack type provides only one access leaf. Rack type and leaf selection must support the intended redundant attachment topology and host interface roles. The direct acceptance evidence is “Demonstrate both host attachments map to intended leafs and a single leaf loss meets recovery objectives”.

B:

“Confirm each instantiated rack matches its logical leaf/uplink topology and allocated resources” is relevant to a different condition: A new leaf rack should use a repeatable single-leaf topology but its manually modeled connections differ from existing identical racks. The stated question instead concerns: A storage workload requires dual-homed servers but a proposed rack type provides only one access leaf. Rack type and leaf selection must support the intended redundant attachment topology and host interface roles. The direct acceptance evidence is “Demonstrate both host attachments map to intended leafs and a single leaf loss meets recovery objectives”.

D:

“Prove free compatible spine ports remain after allocating every forecast uplink” is associated with a distinct issue: A planned rack addition fails because the spine layer has no compatible free ports at the required link speed. By contrast, the actual problem is: A storage workload requires dual-homed servers but a proposed rack type provides only one access leaf. Rack type and leaf selection must support the intended redundant attachment topology and host interface roles. The direct acceptance evidence is “Demonstrate both host attachments map to intended leafs and a single leaf loss meets recovery objectives”.

Question 753

A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. Which evidence most directly verifies the intended network outcome?

  1. Observe established underlay peers and reachability of every intended VTEP loopback before testing virtual networks.
  2. Confirm remote VTEP loopbacks resolve to healthy fabric routes and VXLAN tunnel traffic succeeds.
  3. Prove traffic moves to remaining healthy ECMP next hops within the accepted convergence objective.
  4. Confirm each leaf reaches other leaves via expected spine paths and no unintended data-center transit loops exist.

Explanation

Correct Answer

B:

This directly tests the desired result: confirm remote VTEP loopbacks resolve to healthy fabric routes and VXLAN tunnel traffic succeeds. The decisive investigation is to inspect routing tables and underlay advertisements for each intended VTEP address. The governing principle is that overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes.

Incorrect Answers

A:

“Observe established underlay peers and reachability of every intended VTEP loopback before testing virtual networks” is associated with a distinct issue: An additional rack joins a Clos fabric with healthy physical interfaces but fails to form underlay neighbor sessions. By contrast, the actual problem is: A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. Overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes. The direct acceptance evidence is “Confirm remote VTEP loopbacks resolve to healthy fabric routes and VXLAN tunnel traffic succeeds”.

C:

“Prove traffic moves to remaining healthy ECMP next hops within the accepted convergence objective” is relevant to a different condition: A fabric uses two equal-cost underlay next hops yet packets continue toward a failed path following a port outage. The stated question instead concerns: A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. Overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes. The direct acceptance evidence is “Confirm remote VTEP loopbacks resolve to healthy fabric routes and VXLAN tunnel traffic succeeds”.

D:

That choice—“Confirm each leaf reaches other leaves via expected spine paths and no unintended data-center transit loops exist”—addresses this other problem: A migration plan connects every rack leaf laterally and treats spine devices as only optional edge routers. Here the scenario is: A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. Overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes. The direct acceptance evidence is “Confirm remote VTEP loopbacks resolve to healthy fabric routes and VXLAN tunnel traffic succeeds”.

Question 754

An overlay virtual network has the correct VNI but unknown destination traffic continues to flood farther than intended. Which shortcut would be most likely to undermine this objective?

  1. Disable the EVPN control plane and assume every remote endpoint is learned optimally from normal TCP traffic.
  2. Map every rack's VLAN 210 to an arbitrary shared VNI without checking tenant boundaries.
  3. Assume the underlay can carry the original maximum Ethernet frame unchanged after VXLAN headers are added.
  4. Treat all VXLAN BUM packets as harmless and expand replication to every VTEP in the data center.

Explanation

Correct Answer

D:

This is the unsafe shortcut to avoid: treat all VXLAN BUM packets as harmless and expand replication to every VTEP in the data center. It violates the principle that BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership. An appropriate alternative is to correct replication or multicast membership and virtual-network attachment within the supported fabric design.

Incorrect Answers

A:

That choice—“Disable the EVPN control plane and assume every remote endpoint is learned optimally from normal TCP traffic”—addresses this other problem: An architect compares an EVPN control plane with reliance on data-plane flood-and-learn for VXLAN workloads. Here the scenario is: An overlay virtual network has the correct VNI but unknown destination traffic continues to flood farther than intended. BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership. The directly relevant unsafe shortcut is “Treat all VXLAN BUM packets as harmless and expand replication to every VTEP in the data center”.

B:

“Map every rack's VLAN 210 to an arbitrary shared VNI without checking tenant boundaries” 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 overlay virtual network has the correct VNI but unknown destination traffic continues to flood farther than intended. BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership. The directly relevant unsafe shortcut is “Treat all VXLAN BUM packets as harmless and expand replication to every VTEP in the data center”.

C:

The option “Assume the underlay can carry the original maximum Ethernet frame unchanged after VXLAN headers are added” is useful in a different setting: An east-west application works without tunneling but drops large payloads after VXLAN overlay migration. The case being tested is: An overlay virtual network has the correct VNI but unknown destination traffic continues to flood farther than intended. BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership. The directly relevant unsafe shortcut is “Treat all VXLAN BUM packets as harmless and expand replication to every VTEP in the data center”.

Question 755

A team wants to locate every virtual network owned by a particular application during a migration. Which initial check would most directly distinguish the likely cause?

  1. Inspect object types, graph relationship properties and returned identities for the intended rack.
  2. Inspect property-set values, consumers and intended scope before updating a shared parameter.
  3. Check current spine port availability, resource pools and the proposed rack type against the active blueprint.
  4. Query the relevant virtual-network and endpoint objects with validated tag criteria.

Explanation

Correct Answer

D:

This checks the relevant evidence first: query the relevant virtual-network and endpoint objects with validated tag criteria. The underlying concept is that blueprint object tags and query filters support targeted discovery and operational reporting. After confirming the finding, a controlled remediation is to apply consistent tags and use targeted graph or blueprint searches to generate the migration inventory.

Incorrect Answers

A:

“Inspect object types, graph relationship properties and returned identities for the intended rack” is relevant to a different condition: An operator wants to identify managed nodes by rack and role in the blueprint graph. The stated question instead concerns: A team wants to locate every virtual network owned by a particular application during a migration. Query the relevant virtual-network and endpoint objects with validated tag criteria. The most discriminating first check is “Query the relevant virtual-network and endpoint objects with validated tag criteria”.

B:

That choice—“Inspect property-set values, consumers and intended scope before updating a shared parameter”—addresses this other problem: A team wants to reuse the same approved DNS and NTP settings across multiple racks without editing every switch individually. Here the scenario is: A team wants to locate every virtual network owned by a particular application during a migration. Query the relevant virtual-network and endpoint objects with validated tag criteria. The most discriminating first check is “Query the relevant virtual-network and endpoint objects with validated tag criteria”.

C:

“Check current spine port availability, resource pools and the proposed rack type against the active blueprint” is associated with a distinct issue: An organization expands a Clos topology and wants newly created racks to inherit validated patterns and allocations. By contrast, the actual problem is: A team wants to locate every virtual network owned by a particular application during a migration. Query the relevant virtual-network and endpoint objects with validated tag criteria. The most discriminating first check is “Query the relevant virtual-network and endpoint objects with validated tag criteria”.

Question 756

An east-west application works without tunneling but drops large payloads after VXLAN overlay migration. Which controlled change best addresses the described requirement?

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

Explanation

Correct Answer

D:

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:

The option “Use the supported EVPN control plane and verify route import for the intended virtual network” is useful in a different setting: An architect compares an EVPN control plane with reliance on data-plane flood-and-learn for VXLAN workloads. The case being tested is: An east-west application works without tunneling but drops large payloads after VXLAN overlay migration. 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”.

B:

“Correct replication or multicast membership and virtual-network attachment within the supported fabric design” is relevant to a different condition: A fabric sees unexpectedly broad BUM traffic after a new VXLAN virtual network is provisioned. The stated question instead concerns: An east-west application works without tunneling but drops large payloads after VXLAN overlay migration. 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:

That choice—“Restore routed reachability to the advertised VTEP and the correct tunnel forwarding state”—addresses this other problem: A virtualization cluster is moved to another rack and its EVPN routes exist but the remote VXLAN encapsulation next hop fails. Here the scenario is: An east-west application works without tunneling but drops large payloads after VXLAN overlay migration. 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 757

A network engineer sees differences among the pristine, incremental and rendered configurations for a managed leaf. Which design or operational principle best explains this behavior?

  1. Generic systems represent attached external workloads and can be modeled with their interfaces and supported connectivity patterns.
  2. Apstra supports controlled blueprint day-two rack additions using supported rack types, resources and spine capacity.
  3. Configuration views and their origins should be compared before diagnosing managed-device drift.
  4. Staged blueprint intent can differ from the deployed active revision until approved changes are committed.

Explanation

Correct Answer

C:

configuration views and their origins should be compared before diagnosing managed-device drift. Here, a network engineer sees differences among the pristine, incremental and rendered configurations for a managed leaf. A useful discriminating check is to compare pristine baseline, incremental changes and final rendered config against the active blueprint.

Incorrect Answers

A:

“Generic systems represent attached external workloads and can be modeled with their interfaces and supported connectivity patterns” is associated with a distinct issue: An operations team adds a hypervisor pair whose access ports are not modeled in Apstra generic-system inventory. By contrast, the actual problem is: A network engineer sees differences among the pristine, incremental and rendered configurations for a managed leaf. Configuration views and their origins should be compared before diagnosing managed-device drift. The controlling principle is “Configuration views and their origins should be compared before diagnosing managed-device drift”.

B:

The option “Apstra supports controlled blueprint day-two rack additions using supported rack types, resources and spine capacity” is useful in a different setting: A data center needs to add another rack to a production fabric without replacing the existing blueprint. The case being tested is: A network engineer sees differences among the pristine, incremental and rendered configurations for a managed leaf. Configuration views and their origins should be compared before diagnosing managed-device drift. The controlling principle is “Configuration views and their origins should be compared before diagnosing managed-device drift”.

D:

That choice—“Staged blueprint intent can differ from the deployed active revision until approved changes are committed”—addresses this other problem: An engineer edits a virtual network in a blueprint but cannot see the change reflected in the active switch configuration. Here the scenario is: A network engineer sees differences among the pristine, incremental and rendered configurations for a managed leaf. Configuration views and their origins should be compared before diagnosing managed-device drift. The controlling principle is “Configuration views and their origins should be compared before diagnosing managed-device drift”.

Question 758

An Apstra graph search reveals a workload object disconnected from its expected virtual-network relation. Which initial check would most directly distinguish the likely cause?

  1. Inspect the actual node properties, expected connected edges and corresponding blueprint intent.
  2. Inspect the graph query's node types, filters and returned relationship paths for the intended rack.
  3. Test a query for tag attributes and related generic-system attachments in the target blueprint.
  4. Group probe anomalies by affected node and stage, then inspect linked telemetry and topology edges.

Explanation

Correct Answer

A:

This checks the relevant evidence first: inspect the actual node properties, expected connected edges and corresponding blueprint intent. The underlying concept is that graph query results reflect the modeled topology and may reveal missing or misassigned relationships that need validation. After confirming the finding, a controlled remediation is to repair the validated missing logical relation or correct the query filter if it is misleading.

Incorrect Answers

B:

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

C:

The option “Test a query for tag attributes and related generic-system attachments in the target blueprint” is useful in a different setting: An operations dashboard must report which workload attachments inherit a specific project label. The case being tested is: An Apstra graph search reveals a workload object disconnected from its expected virtual-network relation. The relevant inspection is: Inspect the actual node properties, expected connected edges and corresponding blueprint intent. The most discriminating first check is “Inspect the actual node properties, expected connected edges and corresponding blueprint intent”.

D:

“Group probe anomalies by affected node and stage, then inspect linked telemetry and topology edges” is relevant to a different condition: A site sees hundreds of anomaly events from one failing uplink and wants to distinguish one root cause from many symptoms. The stated question instead concerns: An Apstra graph search reveals a workload object disconnected from its expected virtual-network relation. The relevant inspection is: Inspect the actual node properties, expected connected edges and corresponding blueprint intent. The most discriminating first check is “Inspect the actual node properties, expected connected edges and corresponding blueprint intent”.

Question 759

An operator needs to explain who committed a change after a rack lost connectivity overnight. Which initial check would most directly distinguish the likely cause?

  1. Review the event timeline, blueprint commit notes, deployment status and actor records.
  2. Correlate blueprint revision history, actor identity and event logs around the failure timestamp.
  3. Check collector or agent timestamps, sample rates and ingestion connectivity before trusting status.
  4. Inspect supported syslog configuration, transport reachability and receiving collector parsing.

Explanation

Correct Answer

B:

This checks the relevant evidence first: correlate blueprint revision history, actor identity and event logs around the failure timestamp. The underlying concept is that Apstra event and audit records provide change accountability distinct from raw packet telemetry. After confirming the finding, a controlled remediation is to preserve audit records and review the specific committed change before a controlled correction.

Incorrect Answers

A:

“Review the event timeline, blueprint commit notes, deployment status and actor records” is relevant to a different condition: A team needs to identify whether a failed deployment arose from system automation or an approved human change. The stated question instead concerns: An operator needs to explain who committed a change after a rack lost connectivity overnight. Correlate blueprint revision history, actor identity and event logs around the failure timestamp. The most discriminating first check is “Correlate blueprint revision history, actor identity and event logs around the failure timestamp”.

C:

“Check collector or agent timestamps, sample rates and ingestion connectivity before trusting status” is associated with a distinct issue: An Apstra operator sees no current alerts after a telemetry collector became unreachable. By contrast, the actual problem is: An operator needs to explain who committed a change after a rack lost connectivity overnight. Correlate blueprint revision history, actor identity and event logs around the failure timestamp. The most discriminating first check is “Correlate blueprint revision history, actor identity and event logs around the failure timestamp”.

D:

The option “Inspect supported syslog configuration, transport reachability and receiving collector parsing” is useful in a different setting: A security team needs Apstra events delivered to its central log monitoring platform for long-term investigation. The case being tested is: An operator needs to explain who committed a change after a rack lost connectivity overnight. Correlate blueprint revision history, actor identity and event logs around the failure timestamp. The most discriminating first check is “Correlate blueprint revision history, actor identity and event logs around the failure timestamp”.

Question 760

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

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

Explanation

Correct Answer

C:

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

Incorrect Answers

A:

The option “Announce every local routing-zone prefix to all external peers instead of reviewing policy” is useful in a different setting: A route export template applied to a border device advertises all tenant prefixes beyond the data center. The case being tested is: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. The directly relevant unsafe shortcut is “Enable unrestricted route redistribution for every tenant to make a single external peering session work”.

B:

“Configure every virtual network as a tagged VLAN on the server trunk for convenience” is relevant to a different condition: A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. The stated question instead concerns: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. The directly relevant unsafe shortcut is “Enable unrestricted route redistribution for every tenant to make a single external peering session work”.

D:

“Create an unrelated VRF for each VLAN without validating the tenant's routing requirements” is associated with a distinct issue: A multirack tenant needs two segmented application subnets while sharing a common VRF routing domain. By contrast, the actual problem is: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. The directly relevant unsafe shortcut is “Enable unrestricted route redistribution for every tenant to make a single external peering session work”.

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