Question 260
A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. 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
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 custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. 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”.
“Trigger incidents from a single unvalidated stale sample while discarding the source telemetry” is relevant to a different condition: An Apstra analytics pipeline computes a moving aggregate from interface telemetry and compares it with policy thresholds. The stated question instead concerns: A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. 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”.
That choice—“Match every interface whose label includes the rack number without checking topology relationships”—addresses this other problem: A large fabric includes many repeated physical device names and an operator needs the exact topology relationship for one rack. Here the scenario is: A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. 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”.