Question 480
A site sees hundreds of anomaly events from one failing uplink and wants to distinguish one root cause from many symptoms. Which design or operational principle best explains this behavior?
Explanation
Correct Answer
graph and probe context can correlate multiple anomalies to a shared physical or logical source. Here, a site sees hundreds of anomaly events from one failing uplink and wants to distinguish one root cause from many symptoms. A useful discriminating check is to group probe anomalies by affected node and stage, then inspect linked telemetry and topology edges.
Incorrect Answers
The option “Analytics anomalies can indicate measured performance deviations that do not coincide with configuration intent mismatches” is useful in a different setting: An Apstra dashboard shows probe anomalies while fabric service topology and device reachability stay normal. The case being tested is: A site sees hundreds of anomaly events from one failing uplink and wants to distinguish one root cause from many symptoms. Graph and probe context can correlate multiple anomalies to a shared physical or logical source. The controlling principle is “Graph and probe context can correlate multiple anomalies to a shared physical or logical source”.
“A cleared threshold alarm alone is not sufficient proof of service recovery; measured data and intent must support the conclusion” is relevant to a different condition: A data center dashboard becomes green immediately after an engineer increases alert thresholds without addressing failing application traffic. The stated question instead concerns: A site sees hundreds of anomaly events from one failing uplink and wants to distinguish one root cause from many symptoms. Graph and probe context can correlate multiple anomalies to a shared physical or logical source. The controlling principle is “Graph and probe context can correlate multiple anomalies to a shared physical or logical source”.
“An IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope” is associated with a distinct issue: A built-in analytics probe reports a metric but cannot identify why the value changed after a rack migration. By contrast, the actual problem is: A site sees hundreds of anomaly events from one failing uplink and wants to distinguish one root cause from many symptoms. Graph and probe context can correlate multiple anomalies to a shared physical or logical source. The controlling principle is “Graph and probe context can correlate multiple anomalies to a shared physical or logical source”.