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 39

Question 380

A replacement leaf has a new serial number, but the blueprint still associates the old unavailable hardware with its logical role. Which controlled change best addresses the described requirement?

  1. Correct the duplicate device registration and assign each real device its own validated identity.
  2. Install or repair the supported agent and associate the correct device identity through approved onboarding.
  3. Assign the replacement supported system to the correct logical role using the documented controlled process.
  4. Review and commit the approved staged change using the documented deployment process.

Explanation

Correct Answer

C:

This action addresses the stated defect: assign the replacement supported system to the correct logical role using the documented controlled process. The underlying constraint is that device replacement requires reconciling the blueprint's intended logical device with the actual managed system identity. Verify rather than assume success: verify logical port mappings, rendered configuration and fabric services recover on the new physical device.

Incorrect Answers

A:

The option “Correct the duplicate device registration and assign each real device its own validated identity” is useful in a different setting: Two appliances appear as one managed system after inventory import because their identifiers were copied from a template. The case being tested is: A replacement leaf has a new serial number, but the blueprint still associates the old unavailable hardware with its logical role. Assign the replacement supported system to the correct logical role using the documented controlled process. The most relevant correction is “Assign the replacement supported system to the correct logical role using the documented controlled process”.

B:

“Install or repair the supported agent and associate the correct device identity through approved onboarding” is relevant to a different condition: A switch is reachable over SSH but Apstra cannot assign it to a blueprint because the device agent is not installed correctly. The stated question instead concerns: A replacement leaf has a new serial number, but the blueprint still associates the old unavailable hardware with its logical role. Assign the replacement supported system to the correct logical role using the documented controlled process. The most relevant correction is “Assign the replacement supported system to the correct logical role using the documented controlled process”.

D:

“Review and commit the approved staged change using the documented deployment process” is associated with a distinct issue: A design is staged and rendered correctly, but a production switch still uses the previous running configuration. By contrast, the actual problem is: A replacement leaf has a new serial number, but the blueprint still associates the old unavailable hardware with its logical role. Assign the replacement supported system to the correct logical role using the documented controlled process. The most relevant correction is “Assign the replacement supported system to the correct logical role using the documented controlled process”.

Question 381

A blueprint uses a template intended for a different network OS and generated configuration contains unsupported syntax. Which initial check would most directly distinguish the likely cause?

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

Explanation

Correct Answer

A:

This checks the relevant evidence first: inspect selected template, interface map, device profile and advertised NOS capabilities. The underlying concept is that blueprint templates, device profiles and NOS-specific rendering must align to the supported combination. After confirming the finding, a controlled remediation is to choose an officially supported template and platform combination and regenerate the blueprint configuration.

Incorrect Answers

B:

The option “Review the blueprint build validation details for missing pools, interface assignments and logical links” is useful in a different setting: A new blueprint shows red validation errors before any managed device has received configuration. The case being tested is: A blueprint uses a template intended for a different network OS and generated configuration contains unsupported syntax. The relevant inspection is: Inspect selected template, interface map, device profile and advertised NOS capabilities. The most discriminating first check is “Inspect selected template, interface map, device profile and advertised NOS capabilities”.

C:

“Compare the referenced template version and current active blueprint state before propagating design changes” is relevant to a different condition: A reference template changes its interface model after three production blueprints have already deployed. The stated question instead concerns: A blueprint uses a template intended for a different network OS and generated configuration contains unsupported syntax. The relevant inspection is: Inspect selected template, interface map, device profile and advertised NOS capabilities. The most discriminating first check is “Inspect selected template, interface map, device profile and advertised NOS capabilities”.

D:

That choice—“Compare required external routing connections with the template topology and leaf roles”—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 blueprint uses a template intended for a different network OS and generated configuration contains unsupported syntax. The relevant inspection is: Inspect selected template, interface map, device profile and advertised NOS capabilities. The most discriminating first check is “Inspect selected template, interface map, device profile and advertised NOS capabilities”.

Question 382

A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. Which shortcut would be most likely to undermine this objective?

  1. Build tenant bridge domains first and ignore missing tunnel endpoint routes.
  2. Treat the presence of two physical links as proof that routing automatically reconverges instantly.
  3. Add unrestricted lateral links between leaf devices without updating the design model.
  4. Create new tenant VNIs to mask an unresolved underlay routing failure.

Explanation

Correct Answer

D:

This is the unsafe shortcut to avoid: create new tenant VNIs to mask an unresolved underlay routing failure. It violates the principle that an IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly. An appropriate alternative is to repair the routed underlay addressing or protocol configuration and then validate overlay sessions.

Incorrect Answers

A:

That choice—“Build tenant bridge domains first and ignore missing tunnel endpoint routes”—addresses this other problem: A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. Here the scenario is: A data center team adds a leaf switch but the new node cannot reach any spine loopback addresses although local links are up. An IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly. The directly relevant unsafe shortcut is “Create new tenant VNIs to mask an unresolved underlay routing failure”.

B:

“Treat the presence of two physical links as proof that routing automatically reconverges instantly” 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. An IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly. The directly relevant unsafe shortcut is “Create new tenant VNIs to mask an unresolved underlay routing failure”.

C:

The option “Add unrestricted lateral links between leaf devices without updating the design model” is useful in a different setting: A team designs a three-stage leaf-spine fabric but wants to connect leaf switches to one another for ordinary transit. 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. An IP fabric requires valid routed underlay adjacency and reachability before an EVPN-VXLAN overlay can operate correctly. The directly relevant unsafe shortcut is “Create new tenant VNIs to mask an unresolved underlay routing failure”.

Question 383

An operations team receives repeated probe-stage alerts after an optic begins incrementing errors. Which controlled change best addresses the described requirement?

  1. Correlate the observed metrics with topology and tune or remediate the validated underlying condition.
  2. Repair the verified common uplink fault and retain alert history for root-cause analysis.
  3. Restore justified monitoring sensitivity and remediate the measured issue instead of hiding it.
  4. Configure an approved probe or probe-stage threshold for the scoped leaf group and validate its data collection.

Explanation

Correct Answer

B:

This action addresses the stated defect: repair the verified common uplink fault and retain alert history for root-cause analysis. The underlying constraint is that graph and probe context can correlate multiple anomalies to a shared physical or logical source. Verify rather than assume success: confirm the root metric stabilizes and correlated anomalies across dependent probes clear.

Incorrect Answers

A:

“Correlate the observed metrics with topology and tune or remediate the validated underlying condition” is relevant to a different condition: An IBA probe reports intermittent latency spikes but application errors are not visible in basic device health summaries. The stated question instead concerns: An operations team receives repeated probe-stage alerts after an optic begins incrementing errors. Repair the verified common uplink fault and retain alert history for root-cause analysis. The most relevant correction is “Repair the verified common uplink fault and retain alert history for root-cause analysis”.

C:

“Restore justified monitoring sensitivity and remediate the measured issue instead of hiding it” is associated with a distinct issue: A data center dashboard becomes green immediately after an engineer increases alert thresholds without addressing failing application traffic. By contrast, the actual problem is: An operations team receives repeated probe-stage alerts after an optic begins incrementing errors. Repair the verified common uplink fault and retain alert history for root-cause analysis. The most relevant correction is “Repair the verified common uplink fault and retain alert history for root-cause analysis”.

D:

The option “Configure an approved probe or probe-stage threshold for the scoped leaf group and validate its data collection” 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: An operations team receives repeated probe-stage alerts after an optic begins incrementing errors. Repair the verified common uplink fault and retain alert history for root-cause analysis. The most relevant correction is “Repair the verified common uplink fault and retain alert history for root-cause analysis”.

Question 384

A routed external firewall must exchange routes with a border leaf for only one tenant VRF. Which shortcut would be most likely to undermine this objective?

  1. Enable unrestricted route redistribution for every tenant to make a single external peering session work.
  2. Announce every local routing-zone prefix to all external peers instead of reviewing policy.
  3. Configure every virtual network as a tagged VLAN on the server trunk for convenience.
  4. Leak all tenant routes into one global routing table because only one shared DNS server is needed.

Explanation

Correct Answer

A:

This is the unsafe shortcut to avoid: enable unrestricted route redistribution for every tenant to make a single external peering session work. It violates the principle that connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. An appropriate alternative is to create or correct a scoped connectivity template and routing policy for the authorized VRF.

Incorrect Answers

B:

“Announce every local routing-zone prefix to all external peers instead of reviewing policy” is relevant to a different condition: A route export template applied to a border device advertises all tenant prefixes beyond the data center. The stated question instead concerns: A routed external firewall must exchange routes with a border leaf for only one tenant VRF. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. The directly relevant unsafe shortcut is “Enable unrestricted route redistribution for every tenant to make a single external peering session work”.

C:

That choice—“Configure every virtual network as a tagged VLAN on the server trunk for convenience”—addresses this other problem: A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. Here the scenario is: A routed external firewall must exchange routes with a border leaf for only one tenant VRF. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. The directly relevant unsafe shortcut is “Enable unrestricted route redistribution for every tenant to make a single external peering session work”.

D:

“Leak all tenant routes into one global routing table because only one shared DNS server is needed” is associated with a distinct issue: Two tenants require a controlled shared service, and a proposal suggests importing every route into each tenant VRF. By contrast, the actual problem is: A routed external firewall must exchange routes with a border leaf for only one tenant VRF. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. The directly relevant unsafe shortcut is “Enable unrestricted route redistribution for every tenant to make a single external peering session work”.

Question 385

A virtualized server moves to another rack and vCenter shows the correct network label while the fabric lacks the required VN attachment. Which initial check would most directly distinguish the likely cause?

  1. Inspect DCI route targets, participating VN or VRF memberships and cross-site advertisements.
  2. Inspect the proposed external or shared-services routing path, import policy and required security controls.
  3. Compare the host attachment, hypervisor port-group mapping and Apstra VN or connectivity-template assignment.
  4. Inspect the generic-system interface and assigned VN tagging primitives in the relevant connectivity template.

Explanation

Correct Answer

C:

This checks the relevant evidence first: compare the host attachment, hypervisor port-group mapping and Apstra VN or connectivity-template assignment. The underlying concept is that hypervisor network labels and Apstra fabric virtual-network connectivity must both represent the intended tenant service. After confirming the finding, a controlled remediation is to correct the approved virtual-network attachment and associated host-facing VLAN primitives.

Incorrect Answers

A:

“Inspect DCI route targets, participating VN or VRF memberships and cross-site advertisements” is associated with a distinct issue: A multiregion deployment needs to preserve tenant boundaries while propagating specific data center routes across a DCI. By contrast, the actual problem is: A virtualized server moves to another rack and vCenter shows the correct network label while the fabric lacks the required VN attachment. The relevant inspection is: Compare the host attachment, hypervisor port-group mapping and Apstra VN or connectivity-template assignment. The most discriminating first check is “Compare the host attachment, hypervisor port-group mapping and Apstra VN or connectivity-template assignment”.

B:

The option “Inspect the proposed external or shared-services routing path, import policy and required security controls” is useful in a different setting: Two tenants require a controlled shared service, and a proposal suggests importing every route into each tenant VRF. The case being tested is: A virtualized server moves to another rack and vCenter shows the correct network label while the fabric lacks the required VN attachment. The relevant inspection is: Compare the host attachment, hypervisor port-group mapping and Apstra VN or connectivity-template assignment. The most discriminating first check is “Compare the host attachment, hypervisor port-group mapping and Apstra VN or connectivity-template assignment”.

D:

That choice—“Inspect the generic-system interface and assigned VN tagging primitives in the relevant connectivity template”—addresses this other problem: A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. Here the scenario is: A virtualized server moves to another rack and vCenter shows the correct network label while the fabric lacks the required VN attachment. The relevant inspection is: Compare the host attachment, hypervisor port-group mapping and Apstra VN or connectivity-template assignment. The most discriminating first check is “Compare the host attachment, hypervisor port-group mapping and Apstra VN or connectivity-template assignment”.

Question 386

A new blueprint shows red validation errors before any managed device has received configuration. Which design or operational principle best explains this behavior?

  1. Blueprint design intent must model necessary fabric roles and external connectivity before deployment.
  2. Design-phase resource and topology validation must succeed before a controlled deployment can be trusted.
  3. Blueprint templates, device profiles and NOS-specific rendering must align to the supported combination.
  4. Blueprint design inheritance and change management must be validated; editing a design object does not prove all deployed fabrics changed.

Explanation

Correct Answer

B:

design-phase resource and topology validation must succeed before a controlled deployment can be trusted. Here, a new blueprint shows red validation errors before any managed device has received configuration. A useful discriminating check is to review the blueprint build validation details for missing pools, interface assignments and logical links.

Incorrect Answers

A:

That choice—“Blueprint design intent must model necessary fabric roles and external connectivity before deployment”—addresses this other problem: An engineer finishes a fabric template without any modeled north-south peering attachment points. 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 controlling principle is “Design-phase resource and topology validation must succeed before a controlled deployment can be trusted”.

C:

The option “Blueprint templates, device profiles and NOS-specific rendering must align to the supported combination” is useful in a different setting: A team assigns a device image and platform combination not supported by the chosen Apstra reference design. The case being tested 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 controlling principle is “Design-phase resource and topology validation must succeed before a controlled deployment can be trusted”.

D:

“Blueprint design inheritance and change management must be validated; editing a design object does not prove all deployed fabrics changed” is relevant to a different condition: A reference template changes its interface model after three production blueprints have already deployed. 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 controlling principle is “Design-phase resource and topology validation must succeed before a controlled deployment can be trusted”.

Question 387

A site adds a second blueprint operator but needs to ensure simultaneous edits do not bypass change ownership. Which shortcut would be most likely to undermine this objective?

  1. Assume an old green device status proves the agent is still collecting current data.
  2. Share a full-administrator account with all engineers to avoid configuring granular roles.
  3. Assume restoring an older controller database automatically rolls back all switches to the same moment.
  4. Make device CLI changes outside Apstra because overlapping blueprint edits are inconvenient.

Explanation

Correct Answer

D:

This is the unsafe shortcut to avoid: make device CLI changes outside Apstra because overlapping blueprint edits are inconvenient. It violates the principle that centralized intent and change management should distinguish staged edits, reviewed changes and active deployment ownership. An appropriate alternative is to coordinate change ownership and apply role or process controls to prevent conflicting unreviewed commits.

Incorrect Answers

A:

“Assume an old green device status proves the agent is still collecting current data” is relevant to a different condition: A control-plane service is healthy yet one switch disappears from the Apstra device inventory after a management-network change. The stated question instead concerns: A site adds a second blueprint operator but needs to ensure simultaneous edits do not bypass change ownership. Centralized intent and change management should distinguish staged edits, reviewed changes and active deployment ownership. The directly relevant unsafe shortcut is “Make device CLI changes outside Apstra because overlapping blueprint edits are inconvenient”.

B:

That choice—“Share a full-administrator account with all engineers to avoid configuring granular roles”—addresses this other problem: A fabric engineer successfully logs into Apstra but cannot view the blueprint configuration tools needed for a scheduled change. Here the scenario is: A site adds a second blueprint operator but needs to ensure simultaneous edits do not bypass change ownership. Centralized intent and change management should distinguish staged edits, reviewed changes and active deployment ownership. The directly relevant unsafe shortcut is “Make device CLI changes outside Apstra because overlapping blueprint edits are inconvenient”.

C:

“Assume restoring an older controller database automatically rolls back all switches to the same moment” is associated with a distinct issue: An operations team recovers a backup of the controller taken before the most recent fabric changes. By contrast, the actual problem is: A site adds a second blueprint operator but needs to ensure simultaneous edits do not bypass change ownership. Centralized intent and change management should distinguish staged edits, reviewed changes and active deployment ownership. The directly relevant unsafe shortcut is “Make device CLI changes outside Apstra because overlapping blueprint edits are inconvenient”.

Question 388

A visualization shows an unexpected isolated node and an engineer wants to know whether it reflects a genuine modeling error. Which evidence most directly verifies the intended network outcome?

  1. Confirm the graph shows the intended node relationships and end-to-end attachment tests pass.
  2. Confirm the result contains all intended rack uplinks and excludes unrelated interface objects.
  3. Compare query results with a known inventory sample and correct false-positive attachments.
  4. Confirm only the intended rack or tenant objects generate results and anomalies on repeat tests.

Explanation

Correct Answer

A:

This directly tests the desired result: confirm the graph shows the intended node relationships and end-to-end attachment tests pass. The decisive investigation is to inspect the actual node properties, expected connected edges and corresponding blueprint intent. The governing principle is that graph query results reflect the modeled topology and may reveal missing or misassigned relationships that need validation.

Incorrect Answers

B:

“Confirm the result contains all intended rack uplinks and excludes unrelated interface objects” is relevant to a different condition: An analyst wants to find all uplinks belonging to a specific rack while avoiding assumptions based on interface names. The stated question instead concerns: A visualization shows an unexpected isolated node and an engineer wants to know whether it reflects a genuine modeling error. Graph query results reflect the modeled topology and may reveal missing or misassigned relationships that need validation. The direct acceptance evidence is “Confirm the graph shows the intended node relationships and end-to-end attachment tests pass”.

C:

That choice—“Compare query results with a known inventory sample and correct false-positive attachments”—addresses this other problem: An operations dashboard must report which workload attachments inherit a specific project label. Here the scenario is: A visualization shows an unexpected isolated node and an engineer wants to know whether it reflects a genuine modeling error. Graph query results reflect the modeled topology and may reveal missing or misassigned relationships that need validation. The direct acceptance evidence is “Confirm the graph shows the intended node relationships and end-to-end attachment tests pass”.

D:

“Confirm only the intended rack or tenant objects generate results and anomalies on repeat tests” is associated with a distinct issue: A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. By contrast, the actual problem is: A visualization shows an unexpected isolated node and an engineer wants to know whether it reflects a genuine modeling error. Graph query results reflect the modeled topology and may reveal missing or misassigned relationships that need validation. The direct acceptance evidence is “Confirm the graph shows the intended node relationships and end-to-end attachment tests pass”.

Question 389

A data center creates two tenants with conflicting VNI allocations despite using a shared Apstra resource service. Which initial check would most directly distinguish the likely cause?

  1. Check the VNI resource pool, existing reservations and intended tenant-to-VN mappings.
  2. Inspect pool size, consumed allocations and required identifiers for all logical devices.
  3. Inspect object tags and query results before selecting the intended device set.
  4. Compare the selected logical device's interface count, speeds and connection roles with rack requirements.

Explanation

Correct Answer

A:

This checks the relevant evidence first: check the VNI resource pool, existing reservations and intended tenant-to-VN mappings. The underlying concept is that managed VNI and other logical resource pools reduce collision risk when correctly partitioned and allocated. After confirming the finding, a controlled remediation is to use validated unique VNI allocations or partition resource pools according to approved boundaries.

Incorrect Answers

B:

The option “Inspect pool size, consumed allocations and required identifiers for all logical devices” is useful in a different setting: A new blueprint assigns every VTEP from a resource pool that is too small for the proposed rack count. The case being tested is: A data center creates two tenants with conflicting VNI allocations despite using a shared Apstra resource service. The relevant inspection is: Check the VNI resource pool, existing reservations and intended tenant-to-VN mappings. The most discriminating first check is “Check the VNI resource pool, existing reservations and intended tenant-to-VN mappings”.

C:

“Inspect object tags and query results before selecting the intended device set” 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 data center creates two tenants with conflicting VNI allocations despite using a shared Apstra resource service. The relevant inspection is: Check the VNI resource pool, existing reservations and intended tenant-to-VN mappings. The most discriminating first check is “Check the VNI resource pool, existing reservations and intended tenant-to-VN mappings”.

D:

That choice—“Compare the selected logical device's interface count, speeds and connection roles with rack requirements”—addresses this other problem: A rack template chooses a logical device with insufficient server ports for its planned generic systems. Here the scenario is: A data center creates two tenants with conflicting VNI allocations despite using a shared Apstra resource service. The relevant inspection is: Check the VNI resource pool, existing reservations and intended tenant-to-VN mappings. The most discriminating first check is “Check the VNI resource pool, existing reservations and intended tenant-to-VN mappings”.

Question 390

A control-plane service is healthy yet one switch disappears from the Apstra device inventory after a management-network change. Which initial check would most directly distinguish the likely cause?

  1. Inspect device-agent health, controller connectivity, authentication and management-path reachability.
  2. Check supported platform and NOS versions alongside device profile and agent compatibility before assigning the switch.
  3. Inspect the user's role assignments and denied operation in the Apstra access and audit records.
  4. Compare the restored controller state against live device configuration and the latest known approved revision.

Explanation

Correct Answer

A:

This checks the relevant evidence first: inspect device-agent health, controller connectivity, authentication and management-path reachability. The underlying concept is that the Apstra server relies on managed device agent connectivity and state collection to maintain an accurate operational model. After confirming the finding, a controlled remediation is to restore the supported device-agent connection and management credentials without bypassing security checks.

Incorrect Answers

B:

“Check supported platform and NOS versions alongside device profile and agent compatibility before assigning the switch” is associated with a distinct issue: A new leaf model arrives with an unsupported operating-system image while the Apstra server still shows available inventory capacity. By contrast, the actual problem is: A control-plane service is healthy yet one switch disappears from the Apstra device inventory after a management-network change. The relevant inspection is: Inspect device-agent health, controller connectivity, authentication and management-path reachability. The most discriminating first check is “Inspect device-agent health, controller connectivity, authentication and management-path reachability”.

C:

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

D:

“Compare the restored controller state against live device configuration and the latest known approved revision” is relevant to a different condition: An operations team recovers a backup of the controller taken before the most recent fabric changes. The stated question instead concerns: A control-plane service is healthy yet one switch disappears from the Apstra device inventory after a management-network change. The relevant inspection is: Inspect device-agent health, controller connectivity, authentication and management-path reachability. The most discriminating first check is “Inspect device-agent health, controller connectivity, authentication and management-path reachability”.

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