Question 310
A capacity dashboard remains visible after management connectivity fails, leading analysts to claim current port utilization without checking sample timestamps. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
A lasting control should detect the original error before release. Alert on telemetry staleness and controller-agent loss separately from high interface utilization. That is important in this case because previously collected telemetry may remain displayed after management collection stops and must not be mistaken for a live measurement. The scenario was: A capacity dashboard remains visible after management connectivity fails, leading analysts to claim current port utilization without checking sample timestamps.
Incorrect Answers
The Apstra server maintains the managed blueprint intent and derives coordinated device configurations from that centralized model. Here, previously collected telemetry may remain displayed after management collection stops and must not be mistaken for a live measurement.
Monitor managed agent reachability separately from leaf transit interface counters. That concerns apstra agent connectivity to managed device, while the issue here is agent status versus telemetry freshness. Check agent status and telemetry sample timestamps, restore collection, and label historical values until current data resumes. Specifically for the prevention question, the case to validate is: A capacity dashboard remains visible after management connectivity fails, leading analysts to claim current port utilization without checking sample timestamps.
Apstra abstracts desired design and renders supported device-specific configuration according to each managed platform's profiles and capabilities. For this issue, check agent status and telemetry sample timestamps, restore collection, and label historical values until current data resumes.