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 7

Question 60

A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. Which controlled change best addresses the described requirement?

  1. Advertise the approved VTEP loopbacks through the fabric underlay and check next-hop reachability.
  2. Use validated spine-leaf cabling and routing relationships rather than ad hoc lateral transit links.
  3. Repair the routed underlay addressing or protocol configuration and then validate overlay sessions.
  4. Correct underlay failure detection and routing convergence within the approved topology and timer policy.

Explanation

Correct Answer

C:

This action addresses the stated defect: repair the routed underlay addressing or protocol configuration and then validate overlay sessions. The underlying constraint is that an IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly. Verify rather than assume success: observe established underlay peers and reachability of every intended VTEP loopback before testing virtual networks.

Incorrect Answers

A:

The option “Advertise the approved VTEP loopbacks through the fabric underlay and check next-hop reachability” is useful in a different setting: An engineer brings up BGP peers to the spines but omits export of the overlay endpoint loopbacks. The case being tested is: A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. Repair the routed underlay addressing or protocol configuration and then validate overlay sessions. The most relevant correction is “Repair the routed underlay addressing or protocol configuration and then validate overlay sessions”.

B:

“Use validated spine-leaf cabling and routing relationships rather than ad hoc lateral transit links” is relevant to a different condition: A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. The stated question instead concerns: A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. Repair the routed underlay addressing or protocol configuration and then validate overlay sessions. The most relevant correction is “Repair the routed underlay addressing or protocol configuration and then validate overlay sessions”.

D:

“Correct underlay failure detection and routing convergence within the approved topology and timer policy” is associated with a distinct issue: A two-spine fabric can tolerate one path failure but the application sees blackholing for several minutes after a spine uplink drops. By contrast, the actual problem is: A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. Repair the routed underlay addressing or protocol configuration and then validate overlay sessions. The most relevant correction is “Repair the routed underlay addressing or protocol configuration and then validate overlay sessions”.

Question 61

An engineer edits a virtual network in a blueprint but cannot see the change reflected in the active switch configuration. Which evidence most directly verifies the intended network outcome?

  1. Confirm device health and active configuration separately, then document any pending staged work.
  2. Observe the updated active blueprint and running device configuration reflect the approved new virtual network.
  3. Confirm the resulting active revision contains only approved changes and has a traceable description.
  4. Confirm the installed device configuration reconciles with the intended active config and authorized baseline.

Explanation

Correct Answer

B:

This directly tests the desired result: observe the updated active blueprint and running device configuration reflect the approved new virtual network. The decisive investigation is to compare staged differences with active configuration and deployment status before testing production traffic. The governing principle is that staged blueprint intent can differ from the deployed active revision until approved changes are committed.

Incorrect Answers

A:

“Confirm device health and active configuration separately, then document any pending staged work” is associated with a distinct issue: A dashboard reports that all switches are reachable while a recent staged policy change has not been deployed. By contrast, the actual problem is: An engineer edits a virtual network in a blueprint but cannot see the change reflected in the active switch configuration. Staged blueprint intent can differ from the deployed active revision until approved changes are committed. The direct acceptance evidence is “Observe the updated active blueprint and running device configuration reflect the approved new virtual network”.

C:

“Confirm the resulting active revision contains only approved changes and has a traceable description” is relevant to a different condition: Two changes are awaiting commit, and an operator wants to deploy only one without understanding the other outstanding edits. The stated question instead concerns: An engineer edits a virtual network in a blueprint but cannot see the change reflected in the active switch configuration. Staged blueprint intent can differ from the deployed active revision until approved changes are committed. The direct acceptance evidence is “Observe the updated active blueprint and running device configuration reflect the approved new virtual network”.

D:

That choice—“Confirm the installed device configuration reconciles with the intended active config and authorized baseline”—addresses this other problem: A network engineer sees differences among the pristine, incremental and rendered configurations for a managed leaf. Here the scenario is: An engineer edits a virtual network in a blueprint but cannot see the change reflected in the active switch configuration. Staged blueprint intent can differ from the deployed active revision until approved changes are committed. The direct acceptance evidence is “Observe the updated active blueprint and running device configuration reflect the approved new virtual network”.

Question 62

A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. Which evidence most directly verifies the intended network outcome?

  1. Confirm routing takes the intended local leaf path and remote tenant prefixes remain correctly reachable.
  2. Confirm both host resolution and inter-subnet routed reachability use the expected EVPN routes.
  3. Confirm local first-hop forwarding and cross-rack routing continue consistently through each attached leaf.
  4. Confirm the destination subnet appears as an imported Type 5 route and routes end-to-end in the intended VRF.

Explanation

Correct Answer

B:

This directly tests the desired result: confirm both host resolution and inter-subnet routed reachability use the expected EVPN routes. The decisive investigation is to inspect the intended traffic flow and compare Type 2 endpoint routes with Type 5 routed-prefix routes. The governing principle is that EVPN endpoint and routed-prefix reachability use different route types and their import policy must match the data path.

Incorrect Answers

A:

That choice—“Confirm routing takes the intended local leaf path and remote tenant prefixes remain correctly reachable”—addresses this other problem: A leaf gateway must route a workload's inter-subnet traffic locally rather than always hairpinning through a central aggregation switch. Here the scenario is: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. EVPN endpoint and routed-prefix reachability use different route types and their import policy must match the data path. The direct acceptance evidence is “Confirm both host resolution and inter-subnet routed reachability use the expected EVPN routes”.

C:

The option “Confirm local first-hop forwarding and cross-rack routing continue consistently through each attached leaf” is useful in a different setting: An anycast gateway design uses inconsistent SVI gateway parameters on two participating leafs. The case being tested is: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. EVPN endpoint and routed-prefix reachability use different route types and their import policy must match the data path. The direct acceptance evidence is “Confirm both host resolution and inter-subnet routed reachability use the expected EVPN routes”.

D:

“Confirm the destination subnet appears as an imported Type 5 route and routes end-to-end in the intended VRF” 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 design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. EVPN endpoint and routed-prefix reachability use different route types and their import policy must match the data path. The direct acceptance evidence is “Confirm both host resolution and inter-subnet routed reachability use the expected EVPN routes”.

Question 63

An Apstra operator wants to distinguish blueprint validation from the actual deployment to managed switches. Which shortcut would be most likely to undermine this objective?

  1. Assume every configuration view is identical and blindly paste one into the device CLI.
  2. Treat the existence of a rendered config file as proof of deployment to every switch.
  3. Mark the whole deployment complete when a single leaf reports success.
  4. Skip diff review and declare the change complete as soon as the design editor saves it.

Explanation

Correct Answer

D:

This is the unsafe shortcut to avoid: skip diff review and declare the change complete as soon as the design editor saves it. It violates the principle that controlled build and deploy phases separate design validation, reviewed staged changes and active device updates. An appropriate alternative is to review the changes, commit the authorized revision and monitor the resulting device deployments.

Incorrect Answers

A:

“Assume every configuration view is identical and blindly paste one into the device CLI” is relevant to a different condition: A new Apstra deployment includes baseline settings, platform-specific changes and generated overlay commands that an engineer wants to distinguish. The stated question instead concerns: An Apstra operator wants to distinguish blueprint validation from the actual deployment to managed switches. Controlled build and deploy phases separate design validation, reviewed staged changes and active device updates. The directly relevant unsafe shortcut is “Skip diff review and declare the change complete as soon as the design editor saves it”.

B:

That choice—“Treat the existence of a rendered config file as proof of deployment to every switch”—addresses this other problem: A design is staged and rendered correctly, but a production switch still uses the previous running configuration. Here the scenario is: An Apstra operator wants to distinguish blueprint validation from the actual deployment to managed switches. Controlled build and deploy phases separate design validation, reviewed staged changes and active device updates. The directly relevant unsafe shortcut is “Skip diff review and declare the change complete as soon as the design editor saves it”.

C:

“Mark the whole deployment complete when a single leaf reports success” is associated with a distinct issue: An operator sees devices in mixed managed states and cannot tell which switches received the new active configuration. By contrast, the actual problem is: An Apstra operator wants to distinguish blueprint validation from the actual deployment to managed switches. Controlled build and deploy phases separate design validation, reviewed staged changes and active device updates. The directly relevant unsafe shortcut is “Skip diff review and declare the change complete as soon as the design editor saves it”.

Question 64

A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. Which shortcut would be most likely to undermine this objective?

  1. Bypass reference design validation and hand-wire devices into an arbitrary topology.
  2. Assume future leaf switches can be attached even after every suitable spine port is consumed.
  3. Force a 100G logical port onto unsupported breakout lanes and rely on autonegotiation to fix the design.
  4. Select an unsuitable reference design solely because it minimizes the initial number of switches.

Explanation

Correct Answer

D:

This is the unsafe shortcut to avoid: select an unsuitable reference design solely because it minimizes the initial number of switches. It violates the principle that reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements. An appropriate alternative is to choose the reference design and blueprint template that satisfy gateway connectivity and scaling constraints.

Incorrect Answers

A:

The option “Bypass reference design validation and hand-wire devices into an arbitrary topology” is useful in a different setting: An architect wants consistent rack scale-out using a reference design rather than independently inventing each fabric topology. The case being tested is: A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. Reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements. The directly relevant unsafe shortcut is “Select an unsuitable reference design solely because it minimizes the initial number of switches”.

B:

“Assume future leaf switches can be attached even after every suitable spine port is consumed” 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: A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. Reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements. The directly relevant unsafe shortcut is “Select an unsuitable reference design solely because it minimizes the initial number of switches”.

C:

That choice—“Force a 100G logical port onto unsupported breakout lanes and rely on autonegotiation to fix the design”—addresses this other problem: A rack type requests a 100G leaf uplink but the selected switch's physical port profile only exposes that interface as four 25G breakout channels. Here the scenario is: A data center operator wants to model redundant external gateways before ordering physical rack and fabric equipment. Reference-design selection should reflect external routing, redundancy, rack scale and supported platform requirements. The directly relevant unsafe shortcut is “Select an unsuitable reference design solely because it minimizes the initial number of switches”.

Question 65

A rack template chooses a logical device with insufficient server ports for its planned generic systems. Which shortcut would be most likely to undermine this objective?

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

Explanation

Correct Answer

B:

This is the unsafe shortcut to avoid: assume the logical device automatically creates additional physical interfaces on undersized hardware. It violates the principle that logical device definitions represent required interface roles and capacities, independent of hardware SKU details. An appropriate alternative is to use a compatible logical device and device profile combination with sufficient supported host ports.

Incorrect Answers

A:

“Manually reuse an existing VTEP address to bypass resource exhaustion” is associated with a distinct issue: A new blueprint assigns every VTEP from a resource pool that is too small for the proposed rack count. By contrast, the actual problem is: A rack template chooses a logical device with insufficient server ports for its planned generic systems. Logical device definitions represent required interface roles and capacities, independent of hardware SKU details. The directly relevant unsafe shortcut is “Assume the logical device automatically creates additional physical interfaces on undersized hardware”.

C:

“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: A rack template chooses a logical device with insufficient server ports for its planned generic systems. Logical device definitions represent required interface roles and capacities, independent of hardware SKU details. The directly relevant unsafe shortcut is “Assume the logical device automatically creates additional physical interfaces on undersized hardware”.

D:

That choice—“Run changes against every switch because tags are only informational”—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: A rack template chooses a logical device with insufficient server ports for its planned generic systems. Logical device definitions represent required interface roles and capacities, independent of hardware SKU details. The directly relevant unsafe shortcut is “Assume the logical device automatically creates additional physical interfaces on undersized hardware”.

Question 66

An overlay virtual network has the correct VNI but unknown destination traffic continues to flood farther than intended. Which controlled change best addresses the described requirement?

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

Explanation

Correct Answer

C:

This action addresses the stated defect: correct replication or multicast membership and virtual-network attachment within the supported fabric design. The underlying constraint is that BUM replication behavior and EVPN learning strategy must be scoped to the intended VXLAN membership. Verify rather than assume success: measure expected BUM replication only among authorized VTEPs and improved traffic counters.

Incorrect Answers

A:

That choice—“Use the supported EVPN control plane and verify route import for the intended virtual network”—addresses this other problem: A team wants scalable MAC learning across the fabric rather than sending every remote MAC advertisement by flood. Here the scenario is: An overlay virtual network has the correct VNI but unknown destination traffic continues to flood farther than intended. Correct replication or multicast membership and virtual-network attachment within the supported fabric design. The most relevant correction is “Correct replication or multicast membership and virtual-network attachment within the supported fabric design”.

B:

“Configure sufficient supported underlay MTU along the fabric path or safely adjust payload MTU” is associated with a distinct issue: An east-west application works without tunneling but drops large payloads after VXLAN overlay migration. By contrast, the actual problem is: An overlay virtual network has the correct VNI but unknown destination traffic continues to flood farther than intended. Correct replication or multicast membership and virtual-network attachment within the supported fabric design. The most relevant correction is “Correct replication or multicast membership and virtual-network attachment within the supported fabric design”.

D:

“Restore routed reachability to the advertised VTEP and the correct tunnel forwarding state” 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: An overlay virtual network has the correct VNI but unknown destination traffic continues to flood farther than intended. Correct replication or multicast membership and virtual-network attachment within the supported fabric design. The most relevant correction is “Correct replication or multicast membership and virtual-network attachment within the supported fabric design”.

Question 67

A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. Which shortcut would be most likely to undermine this objective?

  1. Add unrestricted lateral links between leaf devices without updating the design model.
  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: add unrestricted lateral links between leaf devices without updating the design model. It violates the principle that in a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling. An appropriate alternative is to use validated spine-leaf cabling and routing relationships rather than ad hoc lateral transit links.

Incorrect Answers

B:

That choice—“Create new tenant VNIs to mask an unresolved underlay routing failure”—addresses this other problem: A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. Here the scenario is: A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. In a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling. The directly relevant unsafe shortcut is “Add unrestricted lateral links between leaf devices without updating the design model”.

C:

“Assume ECMP must divide every single packet evenly across all active links” is associated with a distinct issue: An operator finds two equal-cost fabric paths but a single large traffic flow consistently traverses only one link. By contrast, the actual problem is: A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. In a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling. The directly relevant unsafe shortcut is “Add unrestricted lateral links between leaf devices without updating the design model”.

D:

The option “Treat the presence of two physical links as proof that routing automatically reconverges instantly” is useful in a different setting: A fabric uses two equal-cost underlay next hops yet packets continue toward a failed path following a port outage. The case being tested is: A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. In a conventional Clos IP fabric, leaves connect through spines to preserve predictable equal-cost paths and scaling. The directly relevant unsafe shortcut is “Add unrestricted lateral links between leaf devices without updating the design model”.

Question 68

A server VLAN is created on two racks but remote EVPN routes cannot be imported because their route targets do not align. Which controlled change best addresses the described requirement?

  1. Assign unique route distinguishing context and appropriate route target import and export policy without leaking tenants.
  2. Correct prefix export/import and next-hop resolution for the routed EVPN IP prefix.
  3. Correct the intended route target mapping and import policies while preserving tenant isolation.
  4. Repair EVPN endpoint advertisement and import eligibility for the affected virtual network.

Explanation

Correct Answer

C:

This action addresses the stated defect: correct the intended route target mapping and import policies while preserving tenant isolation. The underlying constraint is that matching import and export policy for the intended virtual network governs whether EVPN route distribution creates usable reachability. Verify rather than assume success: observe valid imported EVPN routes and bidirectional host reachability only within the authorized virtual network.

Incorrect Answers

A:

The option “Assign unique route distinguishing context and appropriate route target import and export policy without leaking tenants” is useful in a different setting: Two tenants use overlapping private subnets and the team fears one tenant's routes will be mistaken for the other. The case being tested is: A server VLAN is created on two racks but remote EVPN routes cannot be imported because their route targets do not align. Correct the intended route target mapping and import policies while preserving tenant isolation. The most relevant correction is “Correct the intended route target mapping and import policies while preserving tenant isolation”.

B:

“Correct prefix export/import and next-hop resolution for the routed EVPN IP prefix” is relevant to a different condition: A fabric exchanges IP prefixes between tenant routing zones without requiring every remote subnet to be represented as an individual MAC. The stated question instead concerns: A server VLAN is created on two racks but remote EVPN routes cannot be imported because their route targets do not align. Correct the intended route target mapping and import policies while preserving tenant isolation. The most relevant correction is “Correct the intended route target mapping and import policies while preserving tenant isolation”.

D:

“Repair EVPN endpoint advertisement and import eligibility for the affected virtual network” is associated with a distinct issue: An EVPN network learns a host MAC address and associated IP binding from a remote VTEP. By contrast, the actual problem is: A server VLAN is created on two racks but remote EVPN routes cannot be imported because their route targets do not align. Correct the intended route target mapping and import policies while preserving tenant isolation. The most relevant correction is “Correct the intended route target mapping and import policies while preserving tenant isolation”.

Question 69

An operator sees devices in mixed managed states and cannot tell which switches received the new active configuration. Which evidence most directly verifies the intended network outcome?

  1. Confirm discovered links match the staged cable map and link-state anomalies clear.
  2. Observe matching physical and logical connectivity and no unresolved cabling anomalies.
  3. Confirm all affected devices converge on the active blueprint revision without config drift.
  4. Confirm active intent, device configuration and required network tests agree on the intended result.

Explanation

Correct Answer

C:

This directly tests the desired result: confirm all affected devices converge on the active blueprint revision without config drift. The decisive investigation is to check each device's state, failed action details and intended-versus-running configuration revision. The governing principle is that per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly.

Incorrect Answers

A:

“Confirm discovered links match the staged cable map and link-state anomalies clear” is associated with a distinct issue: A newly staged fabric reports LLDP neighbor mismatches although physical links are up. By contrast, the actual problem is: An operator sees devices in mixed managed states and cannot tell which switches received the new active configuration. Per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly. The direct acceptance evidence is “Confirm all affected devices converge on the active blueprint revision without config drift”.

B:

The option “Observe matching physical and logical connectivity and no unresolved cabling anomalies” is useful in a different setting: A staging team has different cable-map snapshots from design and observed discovery data. The case being tested is: An operator sees devices in mixed managed states and cannot tell which switches received the new active configuration. Per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly. The direct acceptance evidence is “Confirm all affected devices converge on the active blueprint revision without config drift”.

D:

That choice—“Confirm active intent, device configuration and required network tests agree on the intended result”—addresses this other problem: An Apstra operator wants to distinguish blueprint validation from the actual deployment to managed switches. Here the scenario is: An operator sees devices in mixed managed states and cannot tell which switches received the new active configuration. Per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly. The direct acceptance evidence is “Confirm all affected devices converge on the active blueprint revision without config drift”.

Question 70

A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. Which design or operational principle best explains this behavior?

  1. IBA stages can enrich and aggregate telemetry before evaluating conditions that constitute an anomaly.
  2. Apstra IBA probes process collected telemetry against conditions or expectations and can raise anomalies.
  3. Graph and probe context can correlate multiple anomalies to a shared physical or logical source.
  4. An IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope.

Explanation

Correct Answer

D:

an IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope. Here, a custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. A useful discriminating check is to inspect the probe stage's graph query, matched entities and input metrics after the migration.

Incorrect Answers

A:

That choice—“IBA stages can enrich and aggregate telemetry before evaluating conditions that constitute an anomaly”—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 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 controlling principle is “An IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope”.

B:

“Apstra IBA probes process collected telemetry against conditions or expectations and can raise anomalies” is associated with a distinct issue: An operator wants an early-warning signal when fabric interface errors exceed a defined threshold. 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. An IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope. The controlling principle is “An IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope”.

C:

The option “Graph and probe context can correlate multiple anomalies to a shared physical or logical source” is useful in a different setting: An operations team receives repeated probe-stage alerts after an optic begins incrementing errors. 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 controlling principle is “An IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope”.

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