Question 240
After a credentials rotation, the device still forwards traffic but its Apstra agent connection no longer provides the expected state updates to the server. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
This control reduces recurrence of the same class of failure: Apstra device management and telemetry depend on working agent and control connectivity in addition to ordinary data-plane reachability. Apply the recurring practice: Monitor managed agent reachability separately from leaf transit interface counters. The previous example was: After a credentials rotation, the device still forwards traffic but its Apstra agent connection no longer provides the expected state updates to the server.
Incorrect Answers
A managed fabric device must be associated with the correct physical identity and model so the controller generates and deploys the intended configuration. For the current prevention question, the evidence instead states: After a credentials rotation, the device still forwards traffic but its Apstra agent connection no longer provides the expected state updates to the server. Here, apstra device management and telemetry depend on working agent and control connectivity in addition to ordinary data-plane reachability.
Alert on telemetry staleness and controller-agent loss separately from high interface utilization. That concerns agent status versus telemetry freshness, while the issue here is apstra agent connectivity to managed device. Inspect agent health, credentials and the supported management transport, then restore the device agent connection without relaxing fabric security.
Apstra application event records and device/system syslog messages can describe different layers of activity and require correlated timestamps. For this issue, inspect agent health, credentials and the supported management transport, then restore the device agent connection without relaxing fabric security.