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 82

Question 810

A data-center dashboard shows only intent-based analytics alerts for a rising interface discard metric. Which controlled change best addresses the described requirement?

  1. Correct the mismatched service intent or deployed configuration while preserving authorized tenant isolation.
  2. Route the issue to the correct service, telemetry or device workflow based on the observed anomaly evidence.
  3. Use each blueprint tab for its intended lifecycle step and deploy changes only after authorized review.
  4. Investigate the measured condition and adjust the approved monitored system or justified probe threshold.

Explanation

Correct Answer

D:

This action addresses the stated defect: investigate the measured condition and adjust the approved monitored system or justified probe threshold. The underlying constraint is that probe anomalies can reflect telemetry thresholds or conditions independently of blueprint service configuration anomalies. Verify rather than assume success: confirm live telemetry returns inside accepted bounds and the probe alert clears with supporting samples.

Incorrect Answers

A:

That choice—“Correct the mismatched service intent or deployed configuration while preserving authorized tenant isolation”—addresses this other problem: An operator sees a tenant-service warning while physical switch availability indicators remain green. Here the scenario is: A data-center dashboard shows only intent-based analytics alerts for a rising interface discard metric. Investigate the measured condition and adjust the approved monitored system or justified probe threshold. The most relevant correction is “Investigate the measured condition and adjust the approved monitored system or justified probe threshold”.

B:

“Route the issue to the correct service, telemetry or device workflow based on the observed anomaly evidence” is associated with a distinct issue: A support engineer assumes every anomaly is a device-down alarm even when the affected rule is a tenant connectivity expectation. By contrast, the actual problem is: A data-center dashboard shows only intent-based analytics alerts for a rising interface discard metric. Investigate the measured condition and adjust the approved monitored system or justified probe threshold. The most relevant correction is “Investigate the measured condition and adjust the approved monitored system or justified probe threshold”.

C:

The option “Use each blueprint tab for its intended lifecycle step and deploy changes only after authorized review” is useful in a different setting: A dashboard reports that all switches are reachable while a recent staged policy change has not been deployed. The case being tested is: A data-center dashboard shows only intent-based analytics alerts for a rising interface discard metric. Investigate the measured condition and adjust the approved monitored system or justified probe threshold. The most relevant correction is “Investigate the measured condition and adjust the approved monitored system or justified probe threshold”.

Question 811

A fabric engineer successfully logs into Apstra but cannot view the blueprint configuration tools needed for a scheduled change. Which initial check would most directly distinguish the likely cause?

  1. Review pending changes, user audit trail and the blueprint's staged or uncommitted state before new edits.
  2. Inspect device-agent health, controller connectivity, authentication and management-path reachability.
  3. Check supported platform and NOS versions alongside device profile and agent compatibility before assigning the switch.
  4. Inspect the user's role assignments and denied operation in the Apstra access and audit records.

Explanation

Correct Answer

D:

This checks the relevant evidence first: inspect the user's role assignments and denied operation in the Apstra access and audit records. The underlying concept is that Apstra role-based access control separates read visibility from permissions to change managed fabric objects. After confirming the finding, a controlled remediation is to grant the minimum documented blueprint role permissions through the approved access-review process.

Incorrect Answers

A:

“Review pending changes, user audit trail and the blueprint's staged or uncommitted state before new edits” is relevant to a different condition: A site adds a second blueprint operator but needs to ensure simultaneous edits do not bypass change ownership. The stated question instead concerns: A fabric engineer successfully logs into Apstra but cannot view the blueprint configuration tools needed for a scheduled change. The relevant inspection is: Inspect the user's role assignments and denied operation in the Apstra access and audit records. The most discriminating first check is “Inspect the user's role assignments and denied operation in the Apstra access and audit records”.

B:

That choice—“Inspect device-agent health, controller connectivity, authentication and management-path reachability”—addresses this other problem: A control-plane service is healthy yet one switch disappears from the Apstra device inventory after a management-network change. Here the scenario is: A fabric engineer successfully logs into Apstra but cannot view the blueprint configuration tools needed for a scheduled change. The relevant inspection is: Inspect the user's role assignments and denied operation in the Apstra access and audit records. The most discriminating first check is “Inspect the user's role assignments and denied operation in the Apstra access and audit records”.

C:

“Check supported platform and NOS versions alongside device profile and agent compatibility before assigning the switch” is associated with a distinct issue: A fabric engineer asks whether a managed switch can simply be added to any blueprint without first validating its NOS and device profile. By contrast, the actual problem is: A fabric engineer successfully logs into Apstra but cannot view the blueprint configuration tools needed for a scheduled change. The relevant inspection is: Inspect the user's role assignments and denied operation in the Apstra access and audit records. The most discriminating first check is “Inspect the user's role assignments and denied operation in the Apstra access and audit records”.

Question 812

An external peer receives a tenant's internal subnets that were supposed to stay private. Which controlled change best addresses the described requirement?

  1. Constrain the external peering policy to explicitly permitted prefixes and verify intended attachment.
  2. Create or correct a scoped connectivity template and routing policy for the authorized VRF.
  3. Bind only authorized tagged and untagged VN attachments to the selected generic-system port.
  4. Create a controlled service insertion or external routing policy permitting only approved shared-service prefixes.

Explanation

Correct Answer

A:

This action addresses the stated defect: constrain the external peering policy to explicitly permitted prefixes and verify intended attachment. The underlying constraint is that routing policy and connectivity-template scope determine which tenant prefixes cross external boundaries. Verify rather than assume success: confirm only approved routes are exchanged and unauthorized prefixes no longer leave the fabric.

Incorrect Answers

B:

“Create or correct a scoped connectivity template and routing policy for the authorized VRF” is relevant to a different condition: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. The stated question instead concerns: An external peer receives a tenant's internal subnets that were supposed to stay private. Constrain the external peering policy to explicitly permitted prefixes and verify intended attachment. The most relevant correction is “Constrain the external peering policy to explicitly permitted prefixes and verify intended attachment”.

C:

That choice—“Bind only authorized tagged and untagged VN attachments to the selected generic-system port”—addresses this other problem: A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. Here the scenario is: An external peer receives a tenant's internal subnets that were supposed to stay private. Constrain the external peering policy to explicitly permitted prefixes and verify intended attachment. The most relevant correction is “Constrain the external peering policy to explicitly permitted prefixes and verify intended attachment”.

D:

“Create a controlled service insertion or external routing policy permitting only approved shared-service prefixes” 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: An external peer receives a tenant's internal subnets that were supposed to stay private. Constrain the external peering policy to explicitly permitted prefixes and verify intended attachment. The most relevant correction is “Constrain the external peering policy to explicitly permitted prefixes and verify intended attachment”.

Question 813

A network engineer sees differences among the pristine, incremental and rendered configurations for a managed leaf. Which shortcut would be most likely to undermine this objective?

  1. Create the new rack outside the blueprint so its configurations cannot be tracked centrally.
  2. Treat unmanaged server ports as invisible and configure arbitrary switch interfaces by hand.
  3. Treat every difference between a pristine config and final rendered config as an unauthorized attack.
  4. Reboot every leaf because all anomaly types allegedly mean the same physical fault.

Explanation

Correct Answer

C:

This is the unsafe shortcut to avoid: treat every difference between a pristine config and final rendered config as an unauthorized attack. It violates the principle that configuration views and their origins should be compared before diagnosing managed-device drift. An appropriate alternative is to investigate unexpected changes using the appropriate generated-config view and approved override workflow.

Incorrect Answers

A:

“Create the new rack outside the blueprint so its configurations cannot be tracked centrally” is associated with a distinct issue: A data center needs to add another rack to a production fabric without replacing the existing blueprint. 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 directly relevant unsafe shortcut is “Treat every difference between a pristine config and final rendered config as an unauthorized attack”.

B:

The option “Treat unmanaged server ports as invisible and configure arbitrary switch interfaces by hand” is useful in a different setting: A new dual-homed application server is physically connected but its logical attachment is absent from the active 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 directly relevant unsafe shortcut is “Treat every difference between a pristine config and final rendered config as an unauthorized attack”.

D:

That choice—“Reboot every leaf because all anomaly types allegedly mean the same physical fault”—addresses this other problem: A support engineer assumes every anomaly is a device-down alarm even when the affected rule is a tenant connectivity expectation. 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 directly relevant unsafe shortcut is “Treat every difference between a pristine config and final rendered config as an unauthorized attack”.

Question 814

A team assigns a device image and platform combination not supported by the chosen Apstra reference design. Which shortcut would be most likely to undermine this objective?

  1. Ignore design validation failures and push partial configurations directly to switches.
  2. Assume every active fabric instantly adopts an edited global template without a staged change.
  3. Force generated configuration onto an unsupported NOS and disable syntax checking.
  4. Depend on later untracked switch CLI changes to supply all missing external links.

Explanation

Correct Answer

C:

This is the unsafe shortcut to avoid: force generated configuration onto an unsupported NOS and disable syntax checking. It violates the principle that blueprint templates, device profiles and NOS-specific rendering must align to the supported combination. An appropriate alternative is to choose an officially supported template and platform combination and regenerate the blueprint configuration.

Incorrect Answers

A:

That choice—“Ignore design validation failures and push partial configurations directly to switches”—addresses this other problem: A new blueprint shows red validation errors before any managed device has received configuration. Here the scenario is: A team assigns a device image and platform combination not supported by the chosen Apstra reference design. Blueprint templates, device profiles and NOS-specific rendering must align to the supported combination. The directly relevant unsafe shortcut is “Force generated configuration onto an unsupported NOS and disable syntax checking”.

B:

“Assume every active fabric instantly adopts an edited global template without a staged change” is associated with a distinct issue: A design template was edited after the first rack was built and an engineer assumes existing active blueprints are retroactively rewritten. By contrast, the actual problem is: A team assigns a device image and platform combination not supported by the chosen Apstra reference design. Blueprint templates, device profiles and NOS-specific rendering must align to the supported combination. The directly relevant unsafe shortcut is “Force generated configuration onto an unsupported NOS and disable syntax checking”.

D:

“Depend on later untracked switch CLI changes to supply all missing external links” 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 team assigns a device image and platform combination not supported by the chosen Apstra reference design. Blueprint templates, device profiles and NOS-specific rendering must align to the supported combination. The directly relevant unsafe shortcut is “Force generated configuration onto an unsupported NOS and disable syntax checking”.

Question 815

An Apstra design runs out of loopback addresses when adding an additional leaf group. Which shortcut would be most likely to undermine this objective?

  1. Assign VNIs by copying a number from an unrelated tenant's design sheet.
  2. Assume the logical device automatically creates additional physical interfaces on undersized hardware.
  3. Manually reuse an existing VTEP address to bypass resource exhaustion.
  4. Run changes against every switch because tags are only informational.

Explanation

Correct Answer

C:

This is the unsafe shortcut to avoid: manually reuse an existing VTEP address to bypass resource exhaustion. It violates the principle that resource pools need sufficient unique allocations for loopback, fabric subnet and other network identifiers. An appropriate alternative is to expand or assign a correctly scoped resource pool without overlapping existing allocations.

Incorrect Answers

A:

“Assign VNIs by copying a number from an unrelated tenant's design sheet” is relevant to a different condition: A data center creates two tenants with conflicting VNI allocations despite using a shared Apstra resource service. The stated question instead concerns: An Apstra design runs out of loopback addresses when adding an additional leaf group. Resource pools need sufficient unique allocations for loopback, fabric subnet and other network identifiers. The directly relevant unsafe shortcut is “Manually reuse an existing VTEP address to bypass resource exhaustion”.

B:

That choice—“Assume the logical device automatically creates additional physical interfaces on undersized hardware”—addresses this other problem: A rack template chooses a logical device with insufficient server ports for its planned generic systems. Here the scenario is: An Apstra design runs out of loopback addresses when adding an additional leaf group. Resource pools need sufficient unique allocations for loopback, fabric subnet and other network identifiers. The directly relevant unsafe shortcut is “Manually reuse an existing VTEP address to bypass resource exhaustion”.

D:

The option “Run changes against every switch because tags are only informational” is useful in a different setting: A team needs to group rack devices for maintenance based on operational ownership without renaming every node. The case being tested is: An Apstra design runs out of loopback addresses when adding an additional leaf group. Resource pools need sufficient unique allocations for loopback, fabric subnet and other network identifiers. The directly relevant unsafe shortcut is “Manually reuse an existing VTEP address to bypass resource exhaustion”.

Question 816

Two changes are awaiting commit, and an operator wants to deploy only one without understanding the other outstanding edits. Which shortcut would be most likely to undermine this objective?

  1. Assume that viewing a change under Staged applies it instantly across the entire fabric.
  2. Interpret a green dashboard as proof that every staged change has already been committed.
  3. Use a historical revision rollback for every minor uncommitted typo without inspecting scope.
  4. Commit blindly and assume every outstanding uncommitted change belongs to the current ticket.

Explanation

Correct Answer

D:

This is the unsafe shortcut to avoid: commit blindly and assume every outstanding uncommitted change belongs to the current ticket. It violates the principle that the set of uncommitted changes must be reviewed as a whole before deployment because committing may include multiple intended modifications. An appropriate alternative is to separate, revert or review unrelated staged edits before an authorized commit according to process.

Incorrect Answers

A:

The option “Assume that viewing a change under Staged applies it instantly across the entire fabric” is useful in a different setting: An engineer edits a virtual network in a blueprint but cannot see the change reflected in the active switch configuration. The case being tested is: Two changes are awaiting commit, and an operator wants to deploy only one without understanding the other outstanding edits. The set of uncommitted changes must be reviewed as a whole before deployment because committing may include multiple intended modifications. The directly relevant unsafe shortcut is “Commit blindly and assume every outstanding uncommitted change belongs to the current ticket”.

B:

“Interpret a green dashboard as proof that every staged change has already been committed” is relevant to a different condition: A network team needs to distinguish observed operational health from whether the desired blueprint configuration is active. The stated question instead concerns: Two changes are awaiting commit, and an operator wants to deploy only one without understanding the other outstanding edits. The set of uncommitted changes must be reviewed as a whole before deployment because committing may include multiple intended modifications. The directly relevant unsafe shortcut is “Commit blindly and assume every outstanding uncommitted change belongs to the current ticket”.

C:

That choice—“Use a historical revision rollback for every minor uncommitted typo without inspecting scope”—addresses this other problem: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. Here the scenario is: Two changes are awaiting commit, and an operator wants to deploy only one without understanding the other outstanding edits. The set of uncommitted changes must be reviewed as a whole before deployment because committing may include multiple intended modifications. The directly relevant unsafe shortcut is “Commit blindly and assume every outstanding uncommitted change belongs to the current ticket”.

Question 817

A designer notices an accidental rack parameter change before any blueprint commit has occurred. Which shortcut would be most likely to undermine this objective?

  1. Assume a Time Voyager selection automatically and safely restores every external system without review.
  2. Jump to an old revision without checking uncommitted changes or notifying their owners.
  3. Treat all past revisions as guaranteed deployable regardless of later hardware and resource changes.
  4. Use a historical revision rollback for every minor uncommitted typo without inspecting scope.

Explanation

Correct Answer

D:

This is the unsafe shortcut to avoid: use a historical revision rollback for every minor uncommitted typo without inspecting scope. It violates the principle that reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision. An appropriate alternative is to revert the specific uncommitted edit rather than rolling back an unrelated committed revision.

Incorrect Answers

A:

“Assume a Time Voyager selection automatically and safely restores every external system without review” is associated with a distinct issue: A new fabric commit causes service degradation and the team wants to return to a known earlier revision with minimal manual reconstruction. By contrast, the actual problem is: A designer notices an accidental rack parameter change before any blueprint commit has occurred. Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision. The directly relevant unsafe shortcut is “Use a historical revision rollback for every minor uncommitted typo without inspecting scope”.

B:

The option “Jump to an old revision without checking uncommitted changes or notifying their owners” is useful in a different setting: A scheduled rollback would occur while an unrelated approved feature configuration remains uncommitted. The case being tested is: A designer notices an accidental rack parameter change before any blueprint commit has occurred. Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision. The directly relevant unsafe shortcut is “Use a historical revision rollback for every minor uncommitted typo without inspecting scope”.

C:

“Treat all past revisions as guaranteed deployable regardless of later hardware and resource changes” is relevant to a different condition: A historical revision would restore a system ID that has been reassigned to another device since it was first recorded. The stated question instead concerns: A designer notices an accidental rack parameter change before any blueprint commit has occurred. Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision. The directly relevant unsafe shortcut is “Use a historical revision rollback for every minor uncommitted typo without inspecting scope”.

Question 818

An anycast gateway design uses inconsistent SVI gateway parameters on two participating leafs. Which design or operational principle best explains this behavior?

  1. A distributed anycast gateway needs consistent gateway identity and virtual network association across participating leaf devices.
  2. Edge-routed bridging places distributed gateway routing close to attached workloads while preserving EVPN reachability.
  3. EVPN endpoint and routed-prefix reachability use different route types and their import policy must match the data path.
  4. EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data.

Explanation

Correct Answer

A:

a distributed anycast gateway needs consistent gateway identity and virtual network association across participating leaf devices. Here, an anycast gateway design uses inconsistent SVI gateway parameters on two participating leafs. A useful discriminating check is to compare gateway addresses, virtual MAC policy and SVI-to-VNI intent across the affected leafs.

Incorrect Answers

B:

“Edge-routed bridging places distributed gateway routing close to attached workloads while preserving EVPN reachability” is associated with a distinct issue: An architect wants gateway functions distributed across tenant leafs in an EVPN-VXLAN fabric. By contrast, the actual problem is: An anycast gateway design uses inconsistent SVI gateway parameters on two participating leafs. A distributed anycast gateway needs consistent gateway identity and virtual network association across participating leaf devices. The controlling principle is “A distributed anycast gateway needs consistent gateway identity and virtual network association across participating leaf devices”.

C:

The option “EVPN endpoint and routed-prefix reachability use different route types and their import policy must match the data path” is useful in a different setting: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. The case being tested is: An anycast gateway design uses inconsistent SVI gateway parameters on two participating leafs. A distributed anycast gateway needs consistent gateway identity and virtual network association across participating leaf devices. The controlling principle is “A distributed anycast gateway needs consistent gateway identity and virtual network association across participating leaf devices”.

D:

“EVPN uses a control-plane route exchange to distribute endpoint reachability while VXLAN carries encapsulated data” is relevant to a different condition: A team wants scalable MAC learning across the fabric rather than sending every remote MAC advertisement by flood. The stated question instead concerns: An anycast gateway design uses inconsistent SVI gateway parameters on two participating leafs. A distributed anycast gateway needs consistent gateway identity and virtual network association across participating leaf devices. The controlling principle is “A distributed anycast gateway needs consistent gateway identity and virtual network association across participating leaf devices”.

Question 819

A data center dashboard becomes green immediately after an engineer increases alert thresholds without addressing failing application traffic. Which controlled change best addresses the described requirement?

  1. Restore justified monitoring sensitivity and remediate the measured issue instead of hiding it.
  2. Repair the verified common uplink fault and retain alert history for root-cause analysis.
  3. Correlate the observed metrics with topology and tune or remediate the validated underlying condition.
  4. Configure the supported aggregation and alert conditions with documented baseline behavior.

Explanation

Correct Answer

A:

This action addresses the stated defect: restore justified monitoring sensitivity and remediate the measured issue instead of hiding it. The underlying constraint is that a cleared threshold alarm alone is not sufficient proof of service recovery; measured data and intent must support the conclusion. Verify rather than assume success: verify objective service and interface measurements improve and a valid probe no longer detects an anomaly.

Incorrect Answers

B:

That choice—“Repair the verified common uplink fault and retain alert history for root-cause analysis”—addresses this other problem: A site sees hundreds of anomaly events from one failing uplink and wants to distinguish one root cause from many symptoms. Here the scenario is: A data center dashboard becomes green immediately after an engineer increases alert thresholds without addressing failing application traffic. Restore justified monitoring sensitivity and remediate the measured issue instead of hiding it. The most relevant correction is “Restore justified monitoring sensitivity and remediate the measured issue instead of hiding it”.

C:

“Correlate the observed metrics with topology and tune or remediate the validated underlying condition” is associated with a distinct issue: An IBA probe reports intermittent latency spikes but application errors are not visible in basic device health summaries. By contrast, the actual problem is: A data center dashboard becomes green immediately after an engineer increases alert thresholds without addressing failing application traffic. Restore justified monitoring sensitivity and remediate the measured issue instead of hiding it. The most relevant correction is “Restore justified monitoring sensitivity and remediate the measured issue instead of hiding it”.

D:

The option “Configure the supported aggregation and alert conditions with documented baseline behavior” is useful in a different setting: An Apstra analytics pipeline computes a moving aggregate from interface telemetry and compares it with policy thresholds. The case being tested is: A data center dashboard becomes green immediately after an engineer increases alert thresholds without addressing failing application traffic. Restore justified monitoring sensitivity and remediate the measured issue instead of hiding it. The most relevant correction is “Restore justified monitoring sensitivity and remediate the measured issue instead of hiding it”.

Question 820

A dual-attached server must avoid duplicate forwarding when its two participating leaf devices share an Ethernet segment. Which controlled change best addresses the described requirement?

  1. Correct the intended route target mapping and import policies while preserving tenant isolation.
  2. Repair EVPN endpoint advertisement and import eligibility for the affected virtual network.
  3. Align approved Ethernet segment and multihoming configuration on the participating leaf devices.
  4. Assign unique route distinguishing context and appropriate route target import and export policy without leaking tenants.

Explanation

Correct Answer

C:

This action addresses the stated defect: align approved Ethernet segment and multihoming configuration on the participating leaf devices. The underlying constraint is that EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability. Verify rather than assume success: confirm stable multihoming advertisements and appropriate forwarding when each server attachment is tested.

Incorrect Answers

A:

The option “Correct the intended route target mapping and import policies while preserving tenant isolation” is useful in a different setting: A server VLAN is created on two racks but remote EVPN routes cannot be imported because their route targets do not align. The case being tested is: A dual-attached server must avoid duplicate forwarding when its two participating leaf devices share an Ethernet segment. Align approved Ethernet segment and multihoming configuration on the participating leaf devices. The most relevant correction is “Align approved Ethernet segment and multihoming configuration on the participating leaf devices”.

B:

“Repair EVPN endpoint advertisement and import eligibility for the affected virtual network” is relevant to a different condition: An EVPN network learns a host MAC address and associated IP binding from a remote VTEP. The stated question instead concerns: A dual-attached server must avoid duplicate forwarding when its two participating leaf devices share an Ethernet segment. Align approved Ethernet segment and multihoming configuration on the participating leaf devices. The most relevant correction is “Align approved Ethernet segment and multihoming configuration on the participating leaf devices”.

D:

“Assign unique route distinguishing context and appropriate route target import and export policy without leaking tenants” is associated with a distinct issue: Two tenants use overlapping private subnets and the team fears one tenant's routes will be mistaken for the other. By contrast, the actual problem is: A dual-attached server must avoid duplicate forwarding when its two participating leaf devices share an Ethernet segment. Align approved Ethernet segment and multihoming configuration on the participating leaf devices. The most relevant correction is “Align approved Ethernet segment and multihoming configuration on the participating leaf devices”.

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