Question 650
One interface telemetry probe reports an anomaly while application traffic remains available, and the team labels the whole tenant service down without corroboration. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
The preventive practice is aligned with the diagnosed mechanism, not an unrelated protection. Maintain service-to-probe correlation steps in operations runbooks and alert routing. A probe signal can inform service investigation without being interchangeable with an end-to-end service verdict.
Incorrect Answers
Version shared property values and review all consumers before modifying common settings. That concerns property sets used by repeated configuration intent, while the issue here is service anomaly versus probe anomaly. Identify the affected service and probe objects, inspect their dependencies and compare counters and paths before remediation.
Supported Apstra fabric expansion stages a rack instance using design objects and validates required connectivity and resources before deployment. However, the present prevention decision is grounded in: One interface telemetry probe reports an anomaly while application traffic remains available, and the team labels the whole tenant service down without corroboration. For this issue, identify the affected service and probe objects, inspect their dependencies and compare counters and paths before remediation.
Label staged experiments clearly and use controlled revert procedures before escalating to time-travel recovery. Here, service health evaluations and intent-based analytics probe results can represent different scopes and should be correlated before identifying an outage.