Question 740
An Apstra analytics pipeline computes a moving aggregate from interface telemetry and compares it with policy thresholds. Which controlled change best addresses the described requirement?
Explanation
Correct Answer
This action addresses the stated defect: configure the supported aggregation and alert conditions with documented baseline behavior. The underlying constraint is that IBA stages can enrich and aggregate telemetry before evaluating conditions that constitute an anomaly. Verify rather than assume success: verify staged derived metrics match sample inputs and test threshold crossings produce accurate alarms.
Incorrect Answers
“Configure an approved probe or probe-stage threshold for the scoped leaf group and validate its data collection” is relevant to a different condition: An operator wants an early-warning signal when fabric interface errors exceed a defined threshold. The stated question instead concerns: An Apstra analytics pipeline computes a moving aggregate from interface telemetry and compares it with policy thresholds. The governing requirement is to Configure the supported aggregation and alert conditions with documented baseline behavior. The most relevant correction is “Configure the supported aggregation and alert conditions with documented baseline behavior”.
That choice—“Narrow the query and probe stages to the correct blueprint nodes and monitored metrics”—addresses this other problem: A built-in analytics probe reports a metric but cannot identify why the value changed after a rack migration. Here the scenario is: An Apstra analytics pipeline computes a moving aggregate from interface telemetry and compares it with policy thresholds. The governing requirement is to Configure the supported aggregation and alert conditions with documented baseline behavior. The most relevant correction is “Configure the supported aggregation and alert conditions with documented baseline behavior”.
“Restore justified monitoring sensitivity and remediate the measured issue instead of hiding it” is associated with a distinct issue: An operator marks IBA alarms resolved by weakening thresholds while the original interface drops continue. By contrast, the actual problem is: An Apstra analytics pipeline computes a moving aggregate from interface telemetry and compares it with policy thresholds. The governing requirement is to Configure the supported aggregation and alert conditions with documented baseline behavior. The most relevant correction is “Configure the supported aggregation and alert conditions with documented baseline behavior”.