Question 430
A built-in analytics probe reports a metric but cannot identify why the value changed after a rack migration. Which shortcut would be most likely to undermine this objective?
Explanation
Correct Answer
This is the unsafe shortcut to avoid: raise the anomaly threshold to infinity because the probe currently selects unrelated devices. It violates the principle that an IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope. An appropriate alternative is to narrow the query and probe stages to the correct blueprint nodes and monitored metrics.
Incorrect Answers
“Trigger incidents from a single unvalidated stale sample while discarding the source telemetry” is associated with a distinct issue: A team wants an analytics alert if interface utilization deviates from baseline while still retaining raw evidence. By contrast, the actual problem is: A built-in analytics probe reports a metric but cannot identify why the value changed after a rack migration. An IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope. The directly relevant unsafe shortcut is “Raise the anomaly threshold to infinity because the probe currently selects unrelated devices”.
The option “Disable interface telemetry to suppress alerts caused by rising packet errors” is useful in a different setting: An operator wants an early-warning signal when fabric interface errors exceed a defined threshold. The case being tested is: A built-in analytics probe reports a metric but cannot identify why the value changed after a rack migration. An IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope. The directly relevant unsafe shortcut is “Raise the anomaly threshold to infinity because the probe currently selects unrelated devices”.
“Treat absence of a service configuration anomaly as proof that every application performance metric is normal” is relevant to a different condition: An IBA probe reports intermittent latency spikes but application errors are not visible in basic device health summaries. The stated question instead concerns: A built-in analytics probe reports a metric but cannot identify why the value changed after a rack migration. An IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope. The directly relevant unsafe shortcut is “Raise the anomaly threshold to infinity because the probe currently selects unrelated devices”.