Question 650
A custom IBA stage uses a graph query that accidentally includes all data-center leafs instead of the affected tenant rack. Which controlled change best addresses the described requirement?
Explanation
Correct Answer
This action addresses the stated defect: narrow the query and probe stages to the correct blueprint nodes and monitored metrics. The underlying constraint is that an IBA probe's context and graph selector are essential to interpreting its measurements and anomaly scope. Verify rather than assume success: confirm only the intended rack or tenant objects generate results and anomalies on repeat tests.
Incorrect Answers
That choice—“Configure an approved probe or probe-stage threshold for the scoped leaf group and validate its data collection”—addresses this other problem: A monitoring team wants to detect rising discards on the uplinks of one specific leaf group. 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. Narrow the query and probe stages to the correct blueprint nodes and monitored metrics. The most relevant correction is “Narrow the query and probe stages to the correct blueprint nodes and monitored metrics”.
The option “Configure the supported aggregation and alert conditions with documented baseline behavior” is useful in a different setting: A team wants an analytics alert if interface utilization deviates from baseline while still retaining raw evidence. 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. Narrow the query and probe stages to the correct blueprint nodes and monitored metrics. The most relevant correction is “Narrow the query and probe stages to the correct blueprint nodes and monitored metrics”.
“Construct a scoped graph query based on blueprint entities and their physical connectivity” is relevant to a different condition: A large fabric includes many repeated physical device names and an operator needs the exact topology relationship for one rack. 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. Narrow the query and probe stages to the correct blueprint nodes and monitored metrics. The most relevant correction is “Narrow the query and probe stages to the correct blueprint nodes and monitored metrics”.