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 27

Question 260

A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. Which shortcut would be most likely to undermine this objective?

  1. Disable interface telemetry to suppress alerts caused by rising packet errors.
  2. Trigger incidents from a single unvalidated stale sample while discarding the source telemetry.
  3. Match every interface whose label includes the rack number without checking topology relationships.
  4. Raise the anomaly threshold to infinity because the probe currently selects unrelated devices.

Explanation

Correct Answer

D:

This is the unsafe shortcut to avoid: raise the anomaly threshold to infinity because the probe currently selects unrelated devices. It violates the principle that an IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope. An appropriate alternative is to narrow the query and probe stages to the correct blueprint nodes and monitored metrics.

Incorrect Answers

A:

The option “Disable interface telemetry to suppress alerts caused by rising packet errors” is useful in a different setting: An operator wants an early-warning signal when fabric interface errors exceed a defined threshold. 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. An IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope. The directly relevant unsafe shortcut is “Raise the anomaly threshold to infinity because the probe currently selects unrelated devices”.

B:

“Trigger incidents from a single unvalidated stale sample while discarding the source telemetry” is relevant to a different condition: An Apstra analytics pipeline computes a moving aggregate from interface telemetry and compares it with policy thresholds. The stated question instead concerns: A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. An IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope. The directly relevant unsafe shortcut is “Raise the anomaly threshold to infinity because the probe currently selects unrelated devices”.

C:

That choice—“Match every interface whose label includes the rack number without checking topology relationships”—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. An IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope. The directly relevant unsafe shortcut is “Raise the anomaly threshold to infinity because the probe currently selects unrelated devices”.

Question 261

An expansion accidentally reuses a virtual network identifier assigned to another isolated overlay segment. Which design or operational principle best explains this behavior?

  1. Managed VNI and other logical resource pools reduce collision risk when correctly partitioned and allocated.
  2. Resource pools need sufficient unique allocations for loopback, fabric subnet and other network identifiers.
  3. Logical device definitions represent required interface roles and capacities, independent of hardware SKU details.
  4. Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity.

Explanation

Correct Answer

A:

managed VNI and other logical resource pools reduce collision risk when correctly partitioned and allocated. Here, an expansion accidentally reuses a virtual network identifier assigned to another isolated overlay segment. A useful discriminating check is to check the VNI resource pool, existing reservations and intended tenant-to-VN mappings.

Incorrect Answers

B:

The option “Resource pools need sufficient unique allocations for loopback, fabric subnet and other network identifiers” is useful in a different setting: An Apstra design runs out of loopback addresses when adding an additional leaf group. The case being tested is: An expansion accidentally reuses a virtual network identifier assigned to another isolated overlay segment. Managed VNI and other logical resource pools reduce collision risk when correctly partitioned and allocated. The controlling principle is “Managed VNI and other logical resource pools reduce collision risk when correctly partitioned and allocated”.

C:

“Logical device definitions represent required interface roles and capacities, independent of hardware SKU details” is relevant to a different condition: A site models 48 server attachments using a logical device profile that exposes only 32 suitable host interfaces. The stated question instead concerns: An expansion accidentally reuses a virtual network identifier assigned to another isolated overlay segment. Managed VNI and other logical resource pools reduce collision risk when correctly partitioned and allocated. The controlling principle is “Managed VNI and other logical resource pools reduce collision risk when correctly partitioned and allocated”.

D:

That choice—“Apstra tags can identify logical objects for consistent inventory selection and operations without changing topology identity”—addresses this other problem: A team needs to group rack devices for maintenance based on operational ownership without renaming every node. Here the scenario is: An expansion accidentally reuses a virtual network identifier assigned to another isolated overlay segment. Managed VNI and other logical resource pools reduce collision risk when correctly partitioned and allocated. The controlling principle is “Managed VNI and other logical resource pools reduce collision risk when correctly partitioned and allocated”.

Question 262

An engineer discovers that a supplemental configuration template was bound to an overly broad tag. Which design or operational principle best explains this behavior?

  1. Configlet applicability must be scoped precisely to affected devices and interfaces.
  2. Configlets can extend generated device configuration through controlled, scoped supplemental configuration.
  3. Apstra property sets can centralize reusable named parameters referenced by supported configuration templates.
  4. Staged blueprint intent can differ from the deployed active revision until approved changes are committed.

Explanation

Correct Answer

A:

configlet applicability must be scoped precisely to affected devices and interfaces. Here, an engineer discovers that a supplemental configuration template was bound to an overly broad tag. A useful discriminating check is to inspect configlet attachment criteria and generated configuration diffs for all matching targets.

Incorrect Answers

B:

“Configlets can extend generated device configuration through controlled, scoped supplemental configuration” is associated with a distinct issue: A proprietary monitoring agent needs device-level CLI configuration not generated by standard Apstra intents. By contrast, the actual problem is: An engineer discovers that a supplemental configuration template was bound to an overly broad tag. Configlet applicability must be scoped precisely to affected devices and interfaces. The controlling principle is “Configlet applicability must be scoped precisely to affected devices and interfaces”.

C:

The option “Apstra property sets can centralize reusable named parameters referenced by supported configuration templates” is useful in a different setting: A blueprint operator maintains repeated data center operational variables that should have a single validated definition. The case being tested is: An engineer discovers that a supplemental configuration template was bound to an overly broad tag. Configlet applicability must be scoped precisely to affected devices and interfaces. The controlling principle is “Configlet applicability must be scoped precisely to affected devices and interfaces”.

D:

“Staged blueprint intent can differ from the deployed active revision until approved changes are committed” is relevant to a different condition: An engineer edits a virtual network in a blueprint but cannot see the change reflected in the active switch configuration. The stated question instead concerns: An engineer discovers that a supplemental configuration template was bound to an overly broad tag. Configlet applicability must be scoped precisely to affected devices and interfaces. The controlling principle is “Configlet applicability must be scoped precisely to affected devices and interfaces”.

Question 263

Two tenants require identical subnet ranges in a shared physical fabric while remaining isolated. Which design or operational principle best explains this behavior?

  1. A virtual network's routed gateway and routing-zone association determine its Layer 3 tenant boundary.
  2. A routing zone can contain multiple virtual networks that share the intended tenant Layer 3 routing context.
  3. DCI design must coordinate intended virtual-network IDs, routing zones and controlled route distribution between sites.
  4. Apstra routing zones and VRFs separate tenant Layer 3 routing contexts, allowing overlapping IP ranges by design.

Explanation

Correct Answer

D:

Apstra routing zones and VRFs separate tenant Layer 3 routing contexts, allowing overlapping IP ranges by design. Here, two tenants require identical subnet ranges in a shared physical fabric while remaining isolated. A useful discriminating check is to inspect VRF and routing-zone membership, tenant virtual-network bindings and imported routes.

Incorrect Answers

A:

“A virtual network's routed gateway and routing-zone association determine its Layer 3 tenant boundary” is relevant to a different condition: A development VN is accidentally assigned to the wrong routing zone during a project migration. 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 controlling principle is “Apstra routing zones and VRFs separate tenant Layer 3 routing contexts, allowing overlapping IP ranges by design”.

B:

That choice—“A routing zone can contain multiple virtual networks that share the intended tenant Layer 3 routing context”—addresses this other problem: A multirack tenant needs two segmented application subnets while sharing a common VRF routing domain. Here the scenario 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 controlling principle is “Apstra routing zones and VRFs separate tenant Layer 3 routing contexts, allowing overlapping IP ranges by design”.

C:

“DCI design must coordinate intended virtual-network IDs, routing zones and controlled route distribution between sites” is associated with a distinct issue: A data-center interconnect extends selected tenant segments between two sites but one site imports unrelated virtual networks. 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 controlling principle is “Apstra routing zones and VRFs separate tenant Layer 3 routing contexts, allowing overlapping IP ranges by design”.

Question 264

A site models 48 server attachments using a logical device profile that exposes only 32 suitable host interfaces. Which controlled change best addresses the described requirement?

  1. Use a compatible logical device and device profile combination with sufficient supported host ports.
  2. Apply consistent approved tags and verify the automation selector matches only the intended objects.
  3. Expand or assign a correctly scoped resource pool without overlapping existing allocations.
  4. Use validated unique VNI allocations or partition resource pools according to approved boundaries.

Explanation

Correct Answer

A:

This action addresses the stated defect: use a compatible logical device and device profile combination with sufficient supported host ports. The underlying constraint is that logical device definitions represent required interface roles and capacities, independent of hardware SKU details. Verify rather than assume success: validate logical port counts and generated rack connections before building the blueprint.

Incorrect Answers

B:

“Apply consistent approved tags and verify the automation selector matches only the intended objects” is relevant to a different condition: An automation wants to select switches tagged with a particular site and deployment tier. The stated question instead concerns: A site models 48 server attachments using a logical device profile that exposes only 32 suitable host interfaces. The governing requirement is to use a compatible logical device and device profile combination with sufficient supported host ports. The most relevant correction is “Use a compatible logical device and device profile combination with sufficient supported host ports”.

C:

That choice—“Expand or assign a correctly scoped resource pool without overlapping existing allocations”—addresses this other problem: An Apstra design runs out of loopback addresses when adding an additional leaf group. Here the scenario is: A site models 48 server attachments using a logical device profile that exposes only 32 suitable host interfaces. The governing requirement is to use a compatible logical device and device profile combination with sufficient supported host ports. The most relevant correction is “Use a compatible logical device and device profile combination with sufficient supported host ports”.

D:

“Use validated unique VNI allocations or partition resource pools according to approved boundaries” is associated with a distinct issue: A data center creates two tenants with conflicting VNI allocations despite using a shared Apstra resource service. By contrast, the actual problem is: A site models 48 server attachments using a logical device profile that exposes only 32 suitable host interfaces. The governing requirement is to use a compatible logical device and device profile combination with sufficient supported host ports. The most relevant correction is “Use a compatible logical device and device profile combination with sufficient supported host ports”.

Question 265

A new dual-homed application server is physically connected but its logical attachment is absent from the active blueprint. Which initial check would most directly distinguish the likely cause?

  1. Compare pristine baseline, incremental changes and final rendered config against the active blueprint.
  2. Check current spine port availability, resource pools and the proposed rack type against the active blueprint.
  3. Inspect property-set values, consumers and intended scope before updating a shared parameter.
  4. Inspect the intended leaf attachment ports, generic-system definition and relevant cable map.

Explanation

Correct Answer

D:

This checks the relevant evidence first: inspect the intended leaf attachment ports, generic-system definition and relevant cable map. The underlying concept is that generic systems represent attached external workloads and can be modeled with their interfaces and supported connectivity patterns. After confirming the finding, a controlled remediation is to create or update the authorized generic system and its connectivity template within the staged blueprint.

Incorrect Answers

A:

“Compare pristine baseline, incremental changes and final rendered config against the active blueprint” is associated with a distinct issue: An audit asks why some device commands come from the baseline while others appear from intended virtual-network configuration. By contrast, the actual problem is: A new dual-homed application server is physically connected but its logical attachment is absent from the active blueprint. The relevant inspection is: Inspect the intended leaf attachment ports, generic-system definition and relevant cable map. The most discriminating first check is “Inspect the intended leaf attachment ports, generic-system definition and relevant cable map”.

B:

The option “Check current spine port availability, resource pools and the proposed rack type against the active blueprint” 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: A new dual-homed application server is physically connected but its logical attachment is absent from the active blueprint. The relevant inspection is: Inspect the intended leaf attachment ports, generic-system definition and relevant cable map. The most discriminating first check is “Inspect the intended leaf attachment ports, generic-system definition and relevant cable map”.

C:

“Inspect property-set values, consumers and intended scope before updating a shared parameter” is relevant to a different condition: A blueprint operator maintains repeated data center operational variables that should have a single validated definition. The stated question instead concerns: A new dual-homed application server is physically connected but its logical attachment is absent from the active blueprint. The relevant inspection is: Inspect the intended leaf attachment ports, generic-system definition and relevant cable map. The most discriminating first check is “Inspect the intended leaf attachment ports, generic-system definition and relevant cable map”.

Question 266

A monitoring team wants to detect rising discards on the uplinks of one specific leaf group. 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 the probe stage's graph query, matched entities and input metrics after the migration.
  3. Inspect the graph query's node types, filters and returned relationship paths for the intended rack.
  4. Inspect probe data sources, monitored stages, thresholds and the exact interfaces being selected.

Explanation

Correct Answer

D:

This checks the relevant evidence first: inspect probe data sources, monitored stages, thresholds and the exact interfaces being selected. The underlying concept is that Apstra IBA probes process collected telemetry against conditions or expectations and can raise anomalies. After confirming the finding, a controlled remediation is to configure an approved probe or probe-stage threshold for the scoped leaf group and validate its data collection.

Incorrect Answers

A:

That choice—“Inspect collector timestamps, aggregation window and stage criteria for the derived utilization metric”—addresses this other problem: A team wants an analytics alert if interface utilization deviates from baseline while still retaining raw evidence. Here the scenario is: A monitoring team wants to detect rising discards on the uplinks of one specific leaf group. The relevant inspection is: Inspect probe data sources, monitored stages, thresholds and the exact interfaces being selected. The most discriminating first check is “Inspect probe data sources, monitored stages, thresholds and the exact interfaces being selected”.

B:

“Inspect the probe stage's graph query, matched entities and input metrics after the migration” is associated with a distinct issue: A built-in analytics probe reports a metric but cannot identify why the value changed after a rack migration. By contrast, the actual problem is: A monitoring team wants to detect rising discards on the uplinks of one specific leaf group. The relevant inspection is: Inspect probe data sources, monitored stages, thresholds and the exact interfaces being selected. The most discriminating first check is “Inspect probe data sources, monitored stages, thresholds and the exact interfaces being selected”.

C:

The option “Inspect the graph query's node types, filters and returned relationship paths for the intended rack” is useful in a different setting: An analyst wants to find all uplinks belonging to a specific rack while avoiding assumptions based on interface names. The case being tested is: A monitoring team wants to detect rising discards on the uplinks of one specific leaf group. The relevant inspection is: Inspect probe data sources, monitored stages, thresholds and the exact interfaces being selected. The most discriminating first check is “Inspect probe data sources, monitored stages, thresholds and the exact interfaces being selected”.

Question 267

A template identifies uplink ports by logical role but a new hardware SKU has different port naming. Which design or operational principle best explains this behavior?

  1. Logical device interfaces must be mapped to actual supported physical device ports through the correct interface map.
  2. Interface maps and device profiles define which supported physical ports and speeds satisfy logical device connectivity.
  3. A physical interface cannot simultaneously satisfy conflicting logical interface assignments in a validated blueprint.
  4. Capacity planning for reference designs must include projected rack count, spine ports, oversubscription and physical interfaces.

Explanation

Correct Answer

A:

logical device interfaces must be mapped to actual supported physical device ports through the correct interface map. Here, a template identifies uplink ports by logical role but a new hardware SKU has different port naming. A useful discriminating check is to review logical-to-physical interface mappings and device profile nomenclature for the new platform.

Incorrect Answers

B:

That choice—“Interface maps and device profiles define which supported physical ports and speeds satisfy logical device connectivity”—addresses this other problem: An Apstra design refuses a proposed uplink because its interface map does not match hardware port mode. Here the scenario is: A template identifies uplink ports by logical role but a new hardware SKU has different port naming. Logical device interfaces must be mapped to actual supported physical device ports through the correct interface map. The controlling principle is “Logical device interfaces must be mapped to actual supported physical device ports through the correct interface map”.

C:

“A physical interface cannot simultaneously satisfy conflicting logical interface assignments in a validated blueprint” is associated with a distinct issue: A fabric build fails because one interface was assigned to both an uplink and a server-facing logical port. By contrast, the actual problem is: A template identifies uplink ports by logical role but a new hardware SKU has different port naming. Logical device interfaces must be mapped to actual supported physical device ports through the correct interface map. The controlling principle is “Logical device interfaces must be mapped to actual supported physical device ports through the correct interface map”.

D:

The option “Capacity planning for reference designs must include projected rack count, spine ports, oversubscription and physical interfaces” is useful in a different setting: A site plans to double leaf count next year while reserving no interface or port-speed headroom. The case being tested is: A template identifies uplink ports by logical role but a new hardware SKU has different port naming. Logical device interfaces must be mapped to actual supported physical device ports through the correct interface map. The controlling principle is “Logical device interfaces must be mapped to actual supported physical device ports through the correct interface map”.

Question 268

A team needs to identify whether a failed deployment arose from system automation or an approved human change. Which controlled change best addresses the described requirement?

  1. Preserve audit records and review the specific committed change before a controlled correction.
  2. Document the causal change and correct the failed deployment through an auditable workflow.
  3. Configure a supported protected syslog destination with the required log categories and retention policy.
  4. Restore data collection and mark stale measurements as unknown rather than healthy.

Explanation

Correct Answer

B:

This action addresses the stated defect: document the causal change and correct the failed deployment through an auditable workflow. The underlying constraint is that controller event logs and deployment records should be correlated with intent revisions and change approvals. Verify rather than assume success: confirm logs identify the affected blueprint revision, device and operator or automation identity.

Incorrect Answers

A:

The option “Preserve audit records and review the specific committed change before a controlled correction” is useful in a different setting: A team investigates whether a blueprint revision was created by automation or by an administrator. The case being tested is: A team needs to identify whether a failed deployment arose from system automation or an approved human change. Document the causal change and correct the failed deployment through an auditable workflow. The most relevant correction is “Document the causal change and correct the failed deployment through an auditable workflow”.

C:

That choice—“Configure a supported protected syslog destination with the required log categories and retention policy”—addresses this other problem: A security team needs Apstra events delivered to its central log monitoring platform for long-term investigation. Here the scenario is: A team needs to identify whether a failed deployment arose from system automation or an approved human change. Document the causal change and correct the failed deployment through an auditable workflow. The most relevant correction is “Document the causal change and correct the failed deployment through an auditable workflow”.

D:

“Restore data collection and mark stale measurements as unknown rather than healthy” is associated with a distinct issue: A monitoring dashboard shows a device as green but telemetry timestamps stopped updating 20 minutes earlier. By contrast, the actual problem is: A team needs to identify whether a failed deployment arose from system automation or an approved human change. Document the causal change and correct the failed deployment through an auditable workflow. The most relevant correction is “Document the causal change and correct the failed deployment through an auditable workflow”.

Question 269

A VXLAN packet encapsulation crosses a routed fabric but is discarded along the path due to frame size. 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. Measure expected BUM replication only among authorized VTEPs and improved traffic counters.
  3. Observe valid endpoint advertisements with less dependence on unknown-destination flooding for known endpoints.
  4. Confirm representative maximum-size payloads traverse the VXLAN overlay without fragmentation-related drops.

Explanation

Correct Answer

D:

This directly tests the desired result: confirm representative maximum-size payloads traverse the VXLAN overlay without fragmentation-related drops. The decisive investigation is to trace effective underlay MTU and path fragmentation or drop counters between the participating VTEPs. The governing principle is that VXLAN adds encapsulation overhead and requires adequate path MTU or effective payload sizing.

Incorrect Answers

A:

“Confirm encapsulated packets reach the intended VTEP and are decapsulated to the authorized bridge domain” is associated with a distinct issue: A virtualization cluster is moved to another rack and its EVPN routes exist but the remote VXLAN encapsulation next hop fails. By contrast, the actual problem is: A VXLAN packet encapsulation crosses a routed fabric but is discarded along the path due to frame size. VXLAN adds encapsulation overhead and requires adequate path MTU or effective payload sizing. The direct acceptance evidence is “Confirm representative maximum-size payloads traverse the VXLAN overlay without fragmentation-related drops”.

B:

The option “Measure expected BUM replication only among authorized VTEPs and improved traffic counters” is useful in a different setting: An overlay virtual network has the correct VNI but unknown destination traffic continues to flood farther than intended. The case being tested is: A VXLAN packet encapsulation crosses a routed fabric but is discarded along the path due to frame size. VXLAN adds encapsulation overhead and requires adequate path MTU or effective payload sizing. The direct acceptance evidence is “Confirm representative maximum-size payloads traverse the VXLAN overlay without fragmentation-related drops”.

C:

“Observe valid endpoint advertisements with less dependence on unknown-destination flooding for known endpoints” is relevant to a different condition: An architect compares an EVPN control plane with reliance on data-plane flood-and-learn for VXLAN workloads. The stated question instead concerns: A VXLAN packet encapsulation crosses a routed fabric but is discarded along the path due to frame size. VXLAN adds encapsulation overhead and requires adequate path MTU or effective payload sizing. The direct acceptance evidence is “Confirm representative maximum-size payloads traverse the VXLAN overlay without fragmentation-related drops”.

Question 270

A dual-attached server must avoid duplicate forwarding when its two participating leaf devices share an Ethernet segment. Which design or operational principle best explains this behavior?

  1. Matching import and export policy for the intended virtual network governs whether EVPN route distribution creates usable reachability.
  2. EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability.
  3. EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning.
  4. EVPN Type 5 IP prefix routes represent routed IP reachability, complementing Type 2 endpoint advertisements.

Explanation

Correct Answer

B:

EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability. Here, a dual-attached server must avoid duplicate forwarding when its two participating leaf devices share an Ethernet segment. A useful discriminating check is to inspect Ethernet segment identifiers, multihoming state and designated-forwarder election on the relevant leafs.

Incorrect Answers

A:

That choice—“Matching import and export policy for the intended virtual network governs whether EVPN route distribution creates usable reachability”—addresses this other problem: A server VLAN is created on two racks but remote EVPN routes cannot be imported because their route targets do not align. Here the scenario is: A dual-attached server must avoid duplicate forwarding when its two participating leaf devices share an Ethernet segment. EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability. The controlling principle is “EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability”.

C:

The option “EVPN Type 2 routes distribute MAC and potentially IP reachability for endpoint learning” is useful in a different setting: An EVPN network learns a host MAC address and associated IP binding from a remote VTEP. The case being tested is: A dual-attached server must avoid duplicate forwarding when its two participating leaf devices share an Ethernet segment. EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability. The controlling principle is “EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability”.

D:

“EVPN Type 5 IP prefix routes represent routed IP reachability, complementing Type 2 endpoint advertisements” is relevant to a different condition: An operator advertises an external IPv4 subnet into an EVPN routing domain for routed reachability. The stated question instead concerns: A dual-attached server must avoid duplicate forwarding when its two participating leaf devices share an Ethernet segment. EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability. The controlling principle is “EVPN Ethernet segment identification and designated-forwarder behavior coordinate multihomed Ethernet reachability”.

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