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?
Explanation
Correct Answer
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
“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”.
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”.
“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”.