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 11

Question 100

Two tenants require identical subnet ranges in a shared physical fabric while remaining isolated. Which evidence most directly verifies the intended network outcome?

  1. Confirm the application subnet uses the expected tenant VRF and other tenants remain isolated.
  2. Confirm both VN endpoints are isolated at Layer 2 but routed according to tenant policy within the VRF.
  3. Confirm each tenant uses its own routing table and no unapproved inter-tenant connectivity occurs.
  4. Verify permitted shared-service traffic works and all other inter-tenant paths remain blocked.

Explanation

Correct Answer

C:

This directly tests the desired result: confirm each tenant uses its own routing table and no unapproved inter-tenant connectivity occurs. The decisive investigation is to inspect VRF and routing-zone membership, tenant virtual-network bindings and imported routes. The governing principle is that Apstra routing zones and VRFs separate tenant Layer 3 routing contexts, allowing overlapping IP ranges by design.

Incorrect Answers

A:

The option “Confirm the application subnet uses the expected tenant VRF and other tenants remain isolated” is useful in a different setting: A newly created virtual network must be attached to a tenant VRF, but application packets route through the default routing instance. The case being tested is: Two tenants require identical subnet ranges in a shared physical fabric while remaining isolated. Apstra routing zones and VRFs separate tenant Layer 3 routing contexts, allowing overlapping IP ranges by design. The direct acceptance evidence is “Confirm each tenant uses its own routing table and no unapproved inter-tenant connectivity occurs”.

B:

“Confirm both VN endpoints are isolated at Layer 2 but routed according to tenant policy within the VRF” is relevant to a different condition: A multirack tenant needs two segmented application subnets while sharing a common VRF routing domain. The stated question instead concerns: Two tenants require identical subnet ranges in a shared physical fabric while remaining isolated. Apstra routing zones and VRFs separate tenant Layer 3 routing contexts, allowing overlapping IP ranges by design. The direct acceptance evidence is “Confirm each tenant uses its own routing table and no unapproved inter-tenant connectivity occurs”.

D:

“Verify permitted shared-service traffic works and all other inter-tenant paths remain blocked” is associated with a distinct issue: Two tenants require a controlled shared service, and a proposal suggests importing every route into each tenant VRF. By contrast, the actual problem is: Two tenants require identical subnet ranges in a shared physical fabric while remaining isolated. Apstra routing zones and VRFs separate tenant Layer 3 routing contexts, allowing overlapping IP ranges by design. The direct acceptance evidence is “Confirm each tenant uses its own routing table and no unapproved inter-tenant connectivity occurs”.

Question 101

A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. Which initial check would most directly distinguish the likely cause?

  1. Inspect and preserve or commit required pending modifications before initiating a revision jump.
  2. Inspect available retained revisions, current uncommitted changes and the revision's applicability to present devices.
  3. Determine whether the unwanted modification exists only in Staged or in the Active revision.
  4. Inspect historical identifiers, resource assignments, device availability and supported rollback constraints.

Explanation

Correct Answer

C:

This checks the relevant evidence first: determine whether the unwanted modification exists only in Staged or in the Active revision. The underlying concept is that reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision. After confirming the finding, a controlled remediation is to revert the specific uncommitted edit rather than rolling back an unrelated committed revision.

Incorrect Answers

A:

“Inspect and preserve or commit required pending modifications before initiating a revision jump” is associated with a distinct issue: An operator has valuable staged changes when another administrator proposes jumping to an older blueprint revision. By contrast, the actual problem is: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. Determine whether the unwanted modification exists only in Staged or in the Active revision. The most discriminating first check is “Determine whether the unwanted modification exists only in Staged or in the Active revision”.

B:

The option “Inspect available retained revisions, current uncommitted changes and the revision's applicability to present devices” is useful in a different setting: A new fabric commit causes service degradation and the team wants to return to a known earlier revision with minimal manual reconstruction. The case being tested is: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. Determine whether the unwanted modification exists only in Staged or in the Active revision. The most discriminating first check is “Determine whether the unwanted modification exists only in Staged or in the Active revision”.

D:

That choice—“Inspect historical identifiers, resource assignments, device availability and supported rollback constraints”—addresses this other problem: An engineer wants to return to a blueprint commit created before several resource pool and hardware changes. Here the scenario is: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. Determine whether the unwanted modification exists only in Staged or in the Active revision. The most discriminating first check is “Determine whether the unwanted modification exists only in Staged or in the Active revision”.

Question 102

An engineer brings up BGP peers to the spines but omits export of the overlay endpoint loopbacks. Which shortcut would be most likely to undermine this objective?

  1. Build tenant bridge domains first and ignore missing tunnel endpoint routes.
  2. Create new tenant VNIs to mask an unresolved underlay routing failure.
  3. Assume ECMP must divide every single packet evenly across all active links.
  4. Treat the presence of two physical links as proof that routing automatically reconverges instantly.

Explanation

Correct Answer

A:

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

Incorrect Answers

B:

“Create new tenant VNIs to mask an unresolved underlay routing failure” 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: An engineer brings up BGP peers to the spines but omits export of the overlay endpoint loopbacks. Overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes. The directly relevant unsafe shortcut is “Build tenant bridge domains first and ignore missing tunnel endpoint routes”.

C:

The option “Assume ECMP must divide every single packet evenly across all active links” is useful in a different setting: An operator finds two equal-cost fabric paths but a single large traffic flow consistently traverses only one link. The case being tested is: An engineer brings up BGP peers to the spines but omits export of the overlay endpoint loopbacks. Overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes. The directly relevant unsafe shortcut is “Build tenant bridge domains first and ignore missing tunnel endpoint routes”.

D:

“Treat the presence of two physical links as proof that routing automatically reconverges instantly” is relevant to a different condition: A fabric uses two equal-cost underlay next hops yet packets continue toward a failed path following a port outage. The stated question instead concerns: An engineer brings up BGP peers to the spines but omits export of the overlay endpoint loopbacks. Overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes. The directly relevant unsafe shortcut is “Build tenant bridge domains first and ignore missing tunnel endpoint routes”.

Question 103

A rack migration assigns the correct switch access VLAN but places the VTEP into another tenant's virtual network identifier. Which evidence most directly verifies the intended network outcome?

  1. Confirm encapsulated packets reach the intended VTEP and are decapsulated to the authorized bridge domain.
  2. Confirm representative maximum-size payloads traverse the VXLAN overlay without fragmentation-related drops.
  3. Verify same-tenant endpoints communicate and traffic is not delivered to the unrelated tenant VNI.
  4. Observe valid endpoint advertisements with less dependence on unknown-destination flooding for known endpoints.

Explanation

Correct Answer

C:

This directly tests the desired result: verify same-tenant endpoints communicate and traffic is not delivered to the unrelated tenant VNI. The decisive investigation is to inspect the VLAN-to-VNI bindings on both local and remote VTEPs and compare the blueprint virtual-network intent. The governing principle is that the VNI associates overlay VXLAN traffic with the intended virtual network, so inconsistent VLAN-to-VNI mapping breaks isolation or connectivity.

Incorrect Answers

A:

“Confirm encapsulated packets reach the intended VTEP and are decapsulated to the authorized bridge domain” is relevant to a different condition: A virtualization cluster is moved to another rack and its EVPN routes exist but the remote VXLAN encapsulation next hop fails. The stated question instead concerns: A rack migration assigns the correct switch access VLAN but places the VTEP into another tenant's virtual network identifier. The VNI associates overlay VXLAN traffic with the intended virtual network, so inconsistent VLAN-to-VNI mapping breaks isolation or connectivity. The direct acceptance evidence is “Verify same-tenant endpoints communicate and traffic is not delivered to the unrelated tenant VNI”.

B:

That choice—“Confirm representative maximum-size payloads traverse the VXLAN overlay without fragmentation-related drops”—addresses this other problem: An east-west application works without tunneling but drops large payloads after VXLAN overlay migration. Here the scenario is: A rack migration assigns the correct switch access VLAN but places the VTEP into another tenant's virtual network identifier. The VNI associates overlay VXLAN traffic with the intended virtual network, so inconsistent VLAN-to-VNI mapping breaks isolation or connectivity. The direct acceptance evidence is “Verify same-tenant endpoints communicate and traffic is not delivered to the unrelated tenant VNI”.

D:

The option “Observe valid endpoint advertisements with less dependence on unknown-destination flooding for known endpoints” is useful in a different setting: A team wants scalable MAC learning across the fabric rather than sending every remote MAC advertisement by flood. The case being tested is: A rack migration assigns the correct switch access VLAN but places the VTEP into another tenant's virtual network identifier. The VNI associates overlay VXLAN traffic with the intended virtual network, so inconsistent VLAN-to-VNI mapping breaks isolation or connectivity. The direct acceptance evidence is “Verify same-tenant endpoints communicate and traffic is not delivered to the unrelated tenant VNI”.

Question 104

A data center cabling plan repeats one spine endpoint for all redundant paths from a critical rack. Which shortcut would be most likely to undermine this objective?

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

Explanation

Correct Answer

D:

This is the unsafe shortcut to avoid: count two cables as independent redundancy even when both share the same single upstream switch. It violates the principle that physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. An appropriate alternative is to correct the cable plan to use approved physically independent spine paths.

Incorrect Answers

A:

The option “Label a single-leaf rack as redundant merely because it has two host-facing ports” is useful in a different setting: A rack designer wants a redundant host attachment pattern for critical appliances. The case being tested is: A data center cabling plan repeats one spine endpoint for all redundant paths from a critical rack. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. The directly relevant unsafe shortcut is “Count two cables as independent redundancy even when both share the same single upstream switch”.

B:

“Create a new ad hoc rack type for every identical rack without checking design drift” 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 data center cabling plan repeats one spine endpoint for all redundant paths from a critical rack. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. The directly relevant unsafe shortcut is “Count two cables as independent redundancy even when both share the same single upstream switch”.

C:

That choice—“Ignore port and oversubscription limits because Apstra can generate logical connections automatically”—addresses this other problem: A planned rack addition fails because the spine layer has no compatible free ports at the required link speed. Here the scenario is: A data center cabling plan repeats one spine endpoint for all redundant paths from a critical rack. Physical topology diversity is necessary to avoid a common point of failure when rack redundancy is required. The directly relevant unsafe shortcut is “Count two cables as independent redundancy even when both share the same single upstream switch”.

Question 105

An audit asks why some device commands come from the baseline while others appear from intended virtual-network configuration. Which design or operational principle best explains this behavior?

  1. Configuration views and their origins should be compared before diagnosing managed-device drift.
  2. Apstra supports controlled blueprint day-two rack additions using supported rack types, resources and spine capacity.
  3. Generic systems represent attached external workloads and can be modeled with their interfaces and supported connectivity patterns.
  4. Configlets can extend generated device configuration through controlled, scoped supplemental configuration.

Explanation

Correct Answer

A:

configuration views and their origins should be compared before diagnosing managed-device drift. Here, an audit asks why some device commands come from the baseline while others appear from intended virtual-network configuration. A useful discriminating check is to compare pristine baseline, incremental changes and final rendered config against the active blueprint.

Incorrect Answers

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: An organization expands a Clos topology and wants newly created racks to inherit validated patterns and allocations. The case being tested is: An audit asks why some device commands come from the baseline while others appear from intended virtual-network configuration. 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”.

C:

“Generic systems represent attached external workloads and can be modeled with their interfaces and supported connectivity patterns” is relevant to a different condition: An operations team adds a hypervisor pair whose access ports are not modeled in Apstra generic-system inventory. The stated question instead concerns: An audit asks why some device commands come from the baseline while others appear from intended virtual-network configuration. 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—“Configlets can extend generated device configuration through controlled, scoped supplemental configuration”—addresses this other problem: An application requires a supported vendor-specific setting absent from the blueprint's default rendered commands. Here the scenario is: An audit asks why some device commands come from the baseline while others appear from intended virtual-network configuration. 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 106

A user asks whether a single tenant routing zone can include multiple Layer 2 VNs attached to different racks. Which controlled change best addresses the described requirement?

  1. Assign each customer to the intended isolated routing zone and VRF with appropriate virtual-network mappings.
  2. Move the VN association to the authorized routing zone and commit reviewed blueprint changes.
  3. Assign each intended VN to the correct routing zone while preserving appropriate bridging and routing boundaries.
  4. Create a controlled service insertion or external routing policy permitting only approved shared-service prefixes.

Explanation

Correct Answer

C:

This action addresses the stated defect: assign each intended VN to the correct routing zone while preserving appropriate bridging and routing boundaries. The underlying constraint is that a routing zone can contain multiple virtual networks that share the intended tenant Layer 3 routing context. Verify rather than assume success: confirm both VN endpoints are isolated at Layer 2 but routed according to tenant policy within the VRF.

Incorrect Answers

A:

That choice—“Assign each customer to the intended isolated routing zone and VRF with appropriate virtual-network mappings”—addresses this other problem: Two tenants require identical subnet ranges in a shared physical fabric while remaining isolated. Here the scenario is: A user asks whether a single tenant routing zone can include multiple Layer 2 VNs attached to different racks. Assign each intended VN to the correct routing zone while preserving appropriate bridging and routing boundaries. The most relevant correction is “Assign each intended VN to the correct routing zone while preserving appropriate bridging and routing boundaries”.

B:

“Move the VN association to the authorized routing zone and commit reviewed blueprint changes” is associated with a distinct issue: A newly created virtual network must be attached to a tenant VRF, but application packets route through the default routing instance. By contrast, the actual problem is: A user asks whether a single tenant routing zone can include multiple Layer 2 VNs attached to different racks. Assign each intended VN to the correct routing zone while preserving appropriate bridging and routing boundaries. The most relevant correction is “Assign each intended VN to the correct routing zone while preserving appropriate bridging and routing boundaries”.

D:

“Create a controlled service insertion or external routing policy permitting only approved shared-service prefixes” is relevant to a different condition: Two tenants require a controlled shared service, and a proposal suggests importing every route into each tenant VRF. The stated question instead concerns: A user asks whether a single tenant routing zone can include multiple Layer 2 VNs attached to different racks. Assign each intended VN to the correct routing zone while preserving appropriate bridging and routing boundaries. The most relevant correction is “Assign each intended VN to the correct routing zone while preserving appropriate bridging and routing boundaries”.

Question 107

A new leaf rack should use a repeatable single-leaf topology but its manually modeled connections differ from existing identical racks. Which controlled change best addresses the described requirement?

  1. Expand spine capacity or rescope rack additions under a supported topology design.
  2. Select a supported redundant leaf rack type and document host LAG or independent paths as appropriate.
  3. Correct the cable plan to use approved physically independent spine paths.
  4. Create or select the approved reusable rack type and instantiate the rack consistently.

Explanation

Correct Answer

D:

This action addresses the stated defect: create or select the approved reusable rack type and instantiate the rack consistently. The underlying constraint is that rack types are reusable logical patterns for leaf topology and attached systems within a blueprint. Verify rather than assume success: confirm each instantiated rack matches its logical leaf/uplink topology and allocated resources.

Incorrect Answers

A:

“Expand spine capacity or rescope rack additions under a supported topology design” 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. Create or select the approved reusable rack type and instantiate the rack consistently. The most relevant correction is “Create or select the approved reusable rack type and instantiate the rack consistently”.

B:

That choice—“Select a supported redundant leaf rack type and document host LAG or independent paths as appropriate”—addresses this other problem: A rack designer wants a redundant host attachment pattern for critical appliances. 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. Create or select the approved reusable rack type and instantiate the rack consistently. The most relevant correction is “Create or select the approved reusable rack type and instantiate the rack consistently”.

C:

“Correct the cable plan to use approved physically independent spine paths” is associated with a distinct issue: A dual leaf rack is expected to provide application diversity but both uplinks terminate on the same physical spine. By contrast, the actual problem is: A new leaf rack should use a repeatable single-leaf topology but its manually modeled connections differ from existing identical racks. Create or select the approved reusable rack type and instantiate the rack consistently. The most relevant correction is “Create or select the approved reusable rack type and instantiate the rack consistently”.

Question 108

An architect wants consistent rack scale-out using a reference design rather than independently inventing each fabric topology. Which controlled change best addresses the described requirement?

  1. Choose the reference design and blueprint template that satisfy gateway connectivity and scaling constraints.
  2. Reserve supported spine and rack capacity for the forecast growth while tracking oversubscription targets.
  3. Expand spine capacity or rescope rack additions under a supported topology design.
  4. Select a compatible reference design and align planned spine, leaf and rack relationships before deployment.

Explanation

Correct Answer

D:

This action addresses the stated defect: select a compatible reference design and align planned spine, leaf and rack relationships before deployment. The underlying constraint is that Apstra reference designs provide supported fabric topology constraints that guide reproducible rack and spine planning. Verify rather than assume success: confirm topology validation succeeds and the planned rack connections fit the chosen design.

Incorrect Answers

A:

The option “Choose the reference design and blueprint template that satisfy gateway connectivity and scaling constraints” is useful in a different setting: A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. The case being tested is: An architect wants consistent rack scale-out using a reference design rather than independently inventing each fabric topology. The governing requirement is to Select a compatible reference design and align planned spine, leaf and rack relationships before deployment. The most relevant correction is “Select a compatible reference design and align planned spine, leaf and rack relationships before deployment”.

B:

“Reserve supported spine and rack capacity for the forecast growth while tracking oversubscription targets” is relevant to a different condition: A planned Apstra fabric includes future rack growth but the initial design leaves no capacity for additional spine downlinks. The stated question instead concerns: An architect wants consistent rack scale-out using a reference design rather than independently inventing each fabric topology. The governing requirement is to Select a compatible reference design and align planned spine, leaf and rack relationships before deployment. The most relevant correction is “Select a compatible reference design and align planned spine, leaf and rack relationships before deployment”.

C:

That choice—“Expand spine capacity or rescope rack additions under a supported topology design”—addresses this other problem: A planned rack addition fails because the spine layer has no compatible free ports at the required link speed. Here the scenario is: An architect wants consistent rack scale-out using a reference design rather than independently inventing each fabric topology. The governing requirement is to Select a compatible reference design and align planned spine, leaf and rack relationships before deployment. The most relevant correction is “Select a compatible reference design and align planned spine, leaf and rack relationships before deployment”.

Question 109

A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. Which initial check would most directly distinguish the likely cause?

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

Explanation

Correct Answer

C:

This checks the relevant evidence first: inspect the probe stage's graph query, matched entities and input metrics after the migration. The underlying concept is that an IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope. After confirming the finding, a controlled remediation is to narrow the query and probe stages to the correct blueprint nodes and monitored metrics.

Incorrect Answers

A:

“Inspect collector timestamps, aggregation window and stage criteria for the derived utilization metric” is associated with a distinct issue: An Apstra analytics pipeline computes a moving aggregate from interface telemetry and compares it with policy thresholds. By contrast, the actual problem is: A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. The relevant inspection is: Inspect the probe stage's graph query, matched entities and input metrics after the migration. The most discriminating first check is “Inspect the probe stage's graph query, matched entities and input metrics after the migration”.

B:

The option “Inspect probe data sources, monitored stages, thresholds and the exact interfaces being selected” is useful in a different setting: A monitoring team wants to detect rising discards on the uplinks of one specific leaf group. The case being tested is: A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. The relevant inspection is: Inspect the probe stage's graph query, matched entities and input metrics after the migration. The most discriminating first check is “Inspect the probe stage's graph query, matched entities and input metrics after the migration”.

D:

That choice—“Inspect the graph query's node types, filters and returned relationship paths for the intended rack”—addresses this other problem: A large fabric includes many repeated physical device names and an operator needs the exact topology relationship for one rack. Here the scenario is: A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. The relevant inspection is: Inspect the probe stage's graph query, matched entities and input metrics after the migration. The most discriminating first check is “Inspect the probe stage's graph query, matched entities and input metrics after the migration”.

Question 110

A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. Which controlled change best addresses the described requirement?

  1. Create or correct a scoped connectivity template and routing policy for the authorized VRF.
  2. Constrain the external peering policy to explicitly permitted prefixes and verify intended attachment.
  3. Bind only authorized tagged and untagged VN attachments to the selected generic-system port.
  4. Apply documented DCI policies for only authorized tenant prefixes and virtual-network reachability.

Explanation

Correct Answer

C:

This action addresses the stated defect: bind only authorized tagged and untagged VN attachments to the selected generic-system port. The underlying constraint is that connectivity templates define host-facing virtual-network endpoint membership and tagging behavior. Verify rather than assume success: confirm the host receives exactly the intended VLANs and no unrelated tenant traffic.

Incorrect Answers

A:

That choice—“Create or correct a scoped connectivity template and routing policy for the authorized VRF”—addresses this other problem: A routed external firewall must exchange routes with a border leaf for only one tenant VRF. Here the scenario is: A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. Bind only authorized tagged and untagged VN attachments to the selected generic-system port. The most relevant correction is “Bind only authorized tagged and untagged VN attachments to the selected generic-system port”.

B:

“Constrain the external peering policy to explicitly permitted prefixes and verify intended attachment” is associated with a distinct issue: A route export template applied to a border device advertises all tenant prefixes beyond the data center. By contrast, the actual problem is: A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. Bind only authorized tagged and untagged VN attachments to the selected generic-system port. The most relevant correction is “Bind only authorized tagged and untagged VN attachments to the selected generic-system port”.

D:

“Apply documented DCI policies for only authorized tenant prefixes and virtual-network reachability” is relevant to a different condition: A data-center interconnect extends selected tenant segments between two sites but one site imports unrelated virtual networks. The stated question instead concerns: A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. Bind only authorized tagged and untagged VN attachments to the selected generic-system port. The most relevant correction is “Bind only authorized tagged and untagged VN attachments to the selected generic-system port”.

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