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 89

Question 880

A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. Which controlled change best addresses the described requirement?

  1. Implement an authorized distributed gateway design and ensure the overlay advertises the required endpoint or prefix routes.
  2. Align the authorized distributed gateway configuration across participating VTEPs.
  3. Correct prefix export/import and next-hop resolution for the routed EVPN IP prefix.
  4. Advertise and import the required host or prefix routes according to the approved ERB routing design.

Explanation

Correct Answer

D:

This action addresses the stated defect: advertise and import the required host or prefix routes according to the approved ERB routing design. The underlying constraint is that EVPN endpoint and routed-prefix reachability use different route types and their import policy must match the data path. Verify rather than assume success: confirm both host resolution and inter-subnet routed reachability use the expected EVPN routes.

Incorrect Answers

A:

The option “Implement an authorized distributed gateway design and ensure the overlay advertises the required endpoint or prefix routes” is useful in a different setting: A leaf gateway must route a workload's inter-subnet traffic locally rather than always hairpinning through a central aggregation switch. The case being tested is: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. Advertise and import the required host or prefix routes according to the approved ERB routing design. The most relevant correction is “Advertise and import the required host or prefix routes according to the approved ERB routing design”.

B:

“Align the authorized distributed gateway configuration across participating VTEPs” is relevant to a different condition: Two racks advertise the same distributed gateway virtual address but clients see intermittent first-hop behavior after a deployment. The stated question instead concerns: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. Advertise and import the required host or prefix routes according to the approved ERB routing design. The most relevant correction is “Advertise and import the required host or prefix routes according to the approved ERB routing design”.

C:

That choice—“Correct prefix export/import and next-hop resolution for the routed EVPN IP prefix”—addresses this other problem: A fabric exchanges IP prefixes between tenant routing zones without requiring every remote subnet to be represented as an individual MAC. Here the scenario is: A design review confuses Type 2 MAC-IP advertisements with Type 5 IP prefix advertisements in an ERB fabric. Advertise and import the required host or prefix routes according to the approved ERB routing design. The most relevant correction is “Advertise and import the required host or prefix routes according to the approved ERB routing design”.

Question 881

A migration plan connects every rack leaf laterally and treats spine devices as only optional edge routers. Which shortcut would be most likely to undermine this objective?

  1. Add unrestricted lateral links between leaf devices without updating the design model.
  2. Assume ECMP must divide every single packet evenly across all active links.
  3. Create new tenant VNIs to mask an unresolved underlay routing failure.
  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:

The option “Assume ECMP must divide every single packet evenly across all active links” is useful in a different setting: An operator finds two equal-cost fabric paths but a single large traffic flow consistently traverses only one link. The case being tested is: A migration plan connects every rack leaf laterally and treats spine devices as only optional edge routers. 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:

“Create new tenant VNIs to mask an unresolved underlay routing failure” is relevant to a different condition: A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. The stated question instead concerns: A migration plan connects every rack leaf laterally and treats spine devices as only optional edge routers. 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:

That choice—“Treat the presence of two physical links as proof that routing automatically reconverges instantly”—addresses this other problem: A two-spine fabric can tolerate one path failure but the application sees blackholing for several minutes after a spine uplink drops. Here the scenario is: A migration plan connects every rack leaf laterally and treats spine devices as only optional edge routers. 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 882

An engineer edits a virtual network in a blueprint but cannot see the change reflected in the active switch configuration. Which shortcut would be most likely to undermine this objective?

  1. Interpret a green dashboard as proof that every staged change has already been committed.
  2. Commit blindly and assume every outstanding uncommitted change belongs to the current ticket.
  3. Apply supplemental configlets globally to avoid tracking which devices need them.
  4. Assume that viewing a change under Staged applies it instantly across the entire fabric.

Explanation

Correct Answer

D:

This is the unsafe shortcut to avoid: assume that viewing a change under Staged applies it instantly across the entire fabric. It violates the principle that staged blueprint intent can differ from the deployed active revision until approved changes are committed. An appropriate alternative is to complete review and commit of the authorized staged change, then monitor device convergence.

Incorrect Answers

A:

That choice—“Interpret a green dashboard as proof that every staged change has already been committed”—addresses this other problem: A network team needs to distinguish observed operational health from whether the desired blueprint configuration is active. 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 directly relevant unsafe shortcut is “Assume that viewing a change under Staged applies it instantly across the entire fabric”.

B:

“Commit blindly and assume every outstanding uncommitted change belongs to the current ticket” is associated with a distinct issue: Two changes are awaiting commit, and an operator wants to deploy only one without understanding the other outstanding edits. 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 directly relevant unsafe shortcut is “Assume that viewing a change under Staged applies it instantly across the entire fabric”.

C:

The option “Apply supplemental configlets globally to avoid tracking which devices need them” is useful in a different setting: An engineer discovers that a supplemental configuration template was bound to an overly broad tag. The case being tested 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 directly relevant unsafe shortcut is “Assume that viewing a change under Staged applies it instantly across the entire fabric”.

Question 883

A proposed rack blueprint includes all needed devices but its graph does not represent an external border connection required by applications. Which initial check would most directly distinguish the likely cause?

  1. Compare the referenced template version and current active blueprint state before propagating design changes.
  2. Inspect selected template, interface map, device profile and advertised NOS capabilities.
  3. Compare required external routing connections with the template topology and leaf roles.
  4. Review the blueprint build validation details for missing pools, interface assignments and logical links.

Explanation

Correct Answer

C:

This checks the relevant evidence first: compare required external routing connections with the template topology and leaf roles. The underlying concept is that blueprint design intent must model necessary fabric roles and external connectivity before deployment. After confirming the finding, a controlled remediation is to extend the approved blueprint design to include appropriate border connectivity and associated resources.

Incorrect Answers

A:

“Compare the referenced template version and current active blueprint state before propagating design changes” is relevant to a different condition: A design template was edited after the first rack was built and an engineer assumes existing active blueprints are retroactively rewritten. The stated question instead concerns: A proposed rack blueprint includes all needed devices but its graph does not represent an external border connection required by applications. The relevant inspection is: Compare required external routing connections with the template topology and leaf roles. The most discriminating first check is “Compare required external routing connections with the template topology and leaf roles”.

B:

That choice—“Inspect selected template, interface map, device profile and advertised NOS capabilities”—addresses this other problem: A blueprint uses a template intended for a different network OS and generated configuration contains unsupported syntax. Here the scenario is: A proposed rack blueprint includes all needed devices but its graph does not represent an external border connection required by applications. The relevant inspection is: Compare required external routing connections with the template topology and leaf roles. The most discriminating first check is “Compare required external routing connections with the template topology and leaf roles”.

D:

The option “Review the blueprint build validation details for missing pools, interface assignments and logical links” is useful in a different setting: An Apstra designer tries to deploy a rack without allocating required underlay interface and IP pools. The case being tested is: A proposed rack blueprint includes all needed devices but its graph does not represent an external border connection required by applications. The relevant inspection is: Compare required external routing connections with the template topology and leaf roles. The most discriminating first check is “Compare required external routing connections with the template topology and leaf roles”.

Question 884

A live rack cable is connected to the wrong spine port compared with the blueprint's intended cable map. Which design or operational principle best explains this behavior?

  1. Cable-map discrepancies should be reconciled before traffic flows through an unvalidated physical fabric.
  2. Per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly.
  3. Cabling validation compares observed neighbor links against intended device/interface relationships.
  4. Controlled build and deploy phases separate design validation, reviewed staged changes and active device updates.

Explanation

Correct Answer

C:

cabling validation compares observed neighbor links against intended device/interface relationships. Here, a live rack cable is connected to the wrong spine port compared with the blueprint's intended cable map. A useful discriminating check is to compare LLDP-discovered endpoints and physical interface identifiers against the generated cable map.

Incorrect Answers

A:

The option “Cable-map discrepancies should be reconciled before traffic flows through an unvalidated physical fabric” 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: A live rack cable is connected to the wrong spine port compared with the blueprint's intended cable map. Cabling validation compares observed neighbor links against intended device/interface relationships. The controlling principle is “Cabling validation compares observed neighbor links against intended device/interface relationships”.

B:

“Per-device deployment and configuration status must be inspected rather than assuming a blueprint commit succeeded uniformly” is relevant to a different condition: A new switch reports Ready while its peers remain in a deployment-failed state after committing fabric intent. The stated question instead concerns: A live rack cable is connected to the wrong spine port compared with the blueprint's intended cable map. Cabling validation compares observed neighbor links against intended device/interface relationships. The controlling principle is “Cabling validation compares observed neighbor links against intended device/interface relationships”.

D:

“Controlled build and deploy phases separate design validation, reviewed staged changes and active device updates” is associated with a distinct issue: A team needs to roll out a fabric change safely but its change record mixes staging a modification with committing the active state. By contrast, the actual problem is: A live rack cable is connected to the wrong spine port compared with the blueprint's intended cable map. Cabling validation compares observed neighbor links against intended device/interface relationships. The controlling principle is “Cabling validation compares observed neighbor links against intended device/interface relationships”.

Question 885

A data center dashboard becomes green immediately after an engineer increases alert thresholds without addressing failing application traffic. Which evidence most directly verifies the intended network outcome?

  1. Confirm latency measurements and anomaly state return within accepted bounds under representative traffic.
  2. Confirm the root metric stabilizes and correlated anomalies across dependent probes clear.
  3. Verify objective service and interface measurements improve and a valid probe no longer detects an anomaly.
  4. Verify staged derived metrics match sample inputs and test threshold crossings produce accurate alarms.

Explanation

Correct Answer

C:

This directly tests the desired result: verify objective service and interface measurements improve and a valid probe no longer detects an anomaly. The decisive investigation is to compare live raw telemetry, probe thresholds and application SLOs before and after the change. The governing principle is that a cleared threshold alarm alone is not sufficient proof of service recovery; measured data and intent must support the conclusion.

Incorrect Answers

A:

“Confirm latency measurements and anomaly state return within accepted bounds under representative traffic” 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. A cleared threshold alarm alone is not sufficient proof of service recovery; measured data and intent must support the conclusion. The direct acceptance evidence is “Verify objective service and interface measurements improve and a valid probe no longer detects an anomaly”.

B:

The option “Confirm the root metric stabilizes and correlated anomalies across dependent probes clear” is useful in a different setting: A site sees hundreds of anomaly events from one failing uplink and wants to distinguish one root cause from many symptoms. The case being tested is: A data center dashboard becomes green immediately after an engineer increases alert thresholds without addressing failing application traffic. A cleared threshold alarm alone is not sufficient proof of service recovery; measured data and intent must support the conclusion. The direct acceptance evidence is “Verify objective service and interface measurements improve and a valid probe no longer detects an anomaly”.

D:

That choice—“Verify staged derived metrics match sample inputs and test threshold crossings produce accurate alarms”—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 data center dashboard becomes green immediately after an engineer increases alert thresholds without addressing failing application traffic. A cleared threshold alarm alone is not sufficient proof of service recovery; measured data and intent must support the conclusion. The direct acceptance evidence is “Verify objective service and interface measurements improve and a valid probe no longer detects an anomaly”.

Question 886

An administrator discovers a bad blueprint deployment and needs to restore a prior retained intent state. 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. Use a historical revision rollback for every minor uncommitted typo without inspecting scope.
  3. Jump to an old revision without checking uncommitted changes or notifying their owners.
  4. Treat all past revisions as guaranteed deployable regardless of later hardware and resource changes.

Explanation

Correct Answer

A:

This is the unsafe shortcut to avoid: assume a Time Voyager selection automatically and safely restores every external system without review. It violates the principle that Apstra Time Voyager supports controlled movement to retained blueprint revisions, subject to compatibility and staged-change constraints. An appropriate alternative is to select the approved prior revision, review resulting uncommitted differences and commit the rollback following change control.

Incorrect Answers

B:

“Use a historical revision rollback for every minor uncommitted typo without inspecting scope” is associated with a distinct issue: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. By contrast, the actual problem is: An administrator discovers a bad blueprint deployment and needs to restore a prior retained intent state. Apstra Time Voyager supports controlled movement to retained blueprint revisions, subject to compatibility and staged-change constraints. The directly relevant unsafe shortcut is “Assume a Time Voyager selection automatically and safely restores every external system without review”.

C:

The option “Jump to an old revision without checking uncommitted changes or notifying their owners” is useful in a different setting: An operator has valuable staged changes when another administrator proposes jumping to an older blueprint revision. The case being tested is: An administrator discovers a bad blueprint deployment and needs to restore a prior retained intent state. Apstra Time Voyager supports controlled movement to retained blueprint revisions, subject to compatibility and staged-change constraints. The directly relevant unsafe shortcut is “Assume a Time Voyager selection automatically and safely restores every external system without review”.

D:

“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: An administrator discovers a bad blueprint deployment and needs to restore a prior retained intent state. Apstra Time Voyager supports controlled movement to retained blueprint revisions, subject to compatibility and staged-change constraints. The directly relevant unsafe shortcut is “Assume a Time Voyager selection automatically and safely restores every external system without review”.

Question 887

A fabric engineer asks whether a managed switch can simply be added to any blueprint without first validating its NOS and device profile. Which controlled change best addresses the described requirement?

  1. Restore the supported device-agent connection and management credentials without bypassing security checks.
  2. Select a supported device and image combination and complete controlled onboarding checks.
  3. Grant the minimum documented blueprint role permissions through the approved access-review process.
  4. Coordinate change ownership and apply role or process controls to prevent conflicting unreviewed commits.

Explanation

Correct Answer

B:

This action addresses the stated defect: select a supported device and image combination and complete controlled onboarding checks. The underlying constraint is that supported device integration requires compatible platform profiles, agents and operating-system capabilities for intended automation. Verify rather than assume success: prove the switch joins managed inventory and supports required rendered configuration under the selected blueprint.

Incorrect Answers

A:

“Restore the supported device-agent connection and management credentials without bypassing security checks” is relevant to a different condition: A managed leaf is physically reachable but its Apstra device agent no longer reports state to the controller. The stated question instead concerns: A fabric engineer asks whether a managed switch can simply be added to any blueprint without first validating its NOS and device profile. The governing requirement is to Select a supported device and image combination and complete controlled onboarding checks. The most relevant correction is “Select a supported device and image combination and complete controlled onboarding checks”.

C:

“Grant the minimum documented blueprint role permissions through the approved access-review process” is associated with a distinct issue: A fabric engineer successfully logs into Apstra but cannot view the blueprint configuration tools needed for a scheduled change. By contrast, the actual problem is: A fabric engineer asks whether a managed switch can simply be added to any blueprint without first validating its NOS and device profile. The governing requirement is to Select a supported device and image combination and complete controlled onboarding checks. The most relevant correction is “Select a supported device and image combination and complete controlled onboarding checks”.

D:

The option “Coordinate change ownership and apply role or process controls to prevent conflicting unreviewed commits” is useful in a different setting: Two on-call staff attempt to stage modifications for the same fabric without a documented approval process. The case being tested is: A fabric engineer asks whether a managed switch can simply be added to any blueprint without first validating its NOS and device profile. The governing requirement is to Select a supported device and image combination and complete controlled onboarding checks. The most relevant correction is “Select a supported device and image combination and complete controlled onboarding checks”.

Question 888

A network team needs to distinguish observed operational health from whether the desired blueprint configuration is active. Which initial check would most directly distinguish the likely cause?

  1. Compare dashboard health with active revision and pending staged configuration diffs.
  2. Compare staged differences with active configuration and deployment status before testing production traffic.
  3. Inspect the Uncommitted diff and attribution for every pending blueprint change.
  4. Determine whether the unwanted modification exists only in Staged or in the Active revision.

Explanation

Correct Answer

A:

This checks the relevant evidence first: compare dashboard health with active revision and pending staged configuration diffs. The underlying concept is that device health, intended active blueprint state and pending staged edits describe different dimensions of operations. After confirming the finding, a controlled remediation is to use each blueprint tab for its intended lifecycle step and deploy changes only after authorized review.

Incorrect Answers

B:

“Compare staged differences with active configuration and deployment status before testing production traffic” is relevant to a different condition: A service owner tests a new VRF assignment while the proposed change appears only in the Staged view. The stated question instead concerns: A network team needs to distinguish observed operational health from whether the desired blueprint configuration is active. The relevant inspection is: Compare dashboard health with active revision and pending staged configuration diffs. The most discriminating first check is “Compare dashboard health with active revision and pending staged configuration diffs”.

C:

That choice—“Inspect the Uncommitted diff and attribution for every pending blueprint change”—addresses this other problem: A blueprint has accumulated unrelated uncommitted routing and rack modifications from different change windows. Here the scenario is: A network team needs to distinguish observed operational health from whether the desired blueprint configuration is active. The relevant inspection is: Compare dashboard health with active revision and pending staged configuration diffs. The most discriminating first check is “Compare dashboard health with active revision and pending staged configuration diffs”.

D:

“Determine whether the unwanted modification exists only in Staged or in the Active revision” is associated with a distinct issue: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. By contrast, the actual problem is: A network team needs to distinguish observed operational health from whether the desired blueprint configuration is active. The relevant inspection is: Compare dashboard health with active revision and pending staged configuration diffs. The most discriminating first check is “Compare dashboard health with active revision and pending staged configuration diffs”.

Question 889

A new blueprint shows red validation errors before any managed device has received configuration. Which evidence most directly verifies the intended network outcome?

  1. Confirm each targeted blueprint reflects the expected revision and existing production services remain healthy.
  2. Confirm the blueprint build validation clears and expected rendered configurations are available for review.
  3. Verify syntax validation and successful controlled deployment to representative supported devices.
  4. Confirm the modeled external links and routing connectivity satisfy the acceptance topology.

Explanation

Correct Answer

B:

This directly tests the desired result: confirm the blueprint build validation clears and expected rendered configurations are available for review. The decisive investigation is to review the blueprint build validation details for missing pools, interface assignments and logical links. The governing principle is that design-phase resource and topology validation must succeed before a controlled deployment can be trusted.

Incorrect Answers

A:

“Confirm each targeted blueprint reflects the expected revision and existing production services remain healthy” is associated with a distinct issue: A reference template changes its interface model after three production blueprints have already deployed. By contrast, the actual problem is: A new blueprint shows red validation errors before any managed device has received configuration. Design-phase resource and topology validation must succeed before a controlled deployment can be trusted. The direct acceptance evidence is “Confirm the blueprint build validation clears and expected rendered configurations are available for review”.

C:

“Verify syntax validation and successful controlled deployment to representative supported devices” is relevant to a different condition: A blueprint uses a template intended for a different network OS and generated configuration contains unsupported syntax. The stated question instead concerns: A new blueprint shows red validation errors before any managed device has received configuration. Design-phase resource and topology validation must succeed before a controlled deployment can be trusted. The direct acceptance evidence is “Confirm the blueprint build validation clears and expected rendered configurations are available for review”.

D:

That choice—“Confirm the modeled external links and routing connectivity satisfy the acceptance topology”—addresses this other problem: A proposed rack blueprint includes all needed devices but its graph does not represent an external border connection required by applications. Here the scenario is: A new blueprint shows red validation errors before any managed device has received configuration. Design-phase resource and topology validation must succeed before a controlled deployment can be trusted. The direct acceptance evidence is “Confirm the blueprint build validation clears and expected rendered configurations are available for review”.

Question 890

A managed leaf is physically reachable but its Apstra device agent no longer reports state to the controller. Which design or operational principle best explains this behavior?

  1. The Apstra server relies on managed device agent connectivity and state collection to maintain an accurate operational model.
  2. The controller's intended blueprint state and deployed device configurations must be reconciled after an out-of-band restore.
  3. Supported device integration requires compatible platform profiles, agents and operating-system capabilities for intended automation.
  4. Apstra role-based access control separates read visibility from permissions to change managed fabric objects.

Explanation

Correct Answer

A:

the Apstra server relies on managed device agent connectivity and state collection to maintain an accurate operational model. Here, a managed leaf is physically reachable but its Apstra device agent no longer reports state to the controller. A useful discriminating check is to inspect device-agent health, controller connectivity, authentication and management-path reachability.

Incorrect Answers

B:

“The controller's intended blueprint state and deployed device configurations must be reconciled after an out-of-band restore” is associated with a distinct issue: A Juniper Apstra controller is restored following a failure and some device configurations no longer match its database. By contrast, the actual problem is: A managed leaf is physically reachable but its Apstra device agent no longer reports state to the controller. The Apstra server relies on managed device agent connectivity and state collection to maintain an accurate operational model. The controlling principle is “The Apstra server relies on managed device agent connectivity and state collection to maintain an accurate operational model”.

C:

The option “Supported device integration requires compatible platform profiles, agents and operating-system capabilities for intended automation” is useful in a different setting: A new leaf model arrives with an unsupported operating-system image while the Apstra server still shows available inventory capacity. The case being tested is: A managed leaf is physically reachable but its Apstra device agent no longer reports state to the controller. The Apstra server relies on managed device agent connectivity and state collection to maintain an accurate operational model. The controlling principle is “The Apstra server relies on managed device agent connectivity and state collection to maintain an accurate operational model”.

D:

“Apstra role-based access control separates read visibility from permissions to change managed fabric objects” is relevant to a different condition: A new operations account can open the Apstra UI yet receives authorization errors when trying to manage device blueprints. The stated question instead concerns: A managed leaf is physically reachable but its Apstra device agent no longer reports state to the controller. The Apstra server relies on managed device agent connectivity and state collection to maintain an accurate operational model. The controlling principle is “The Apstra server relies on managed device agent connectivity and state collection to maintain an accurate operational model”.

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