Question 760
During a post-incident review at a research campus, the original problem was: An engineer creates a performance SLA but does not associate the backup member with its health-check member list, leaving the backup unmonitored. Which preventive practice most directly addresses its cause?
Explanation
Correct Answer
Audit health-check member coverage during each circuit addition. This control reduces recurrence of the documented mechanism: Performance SLA eligibility depends on which member interfaces are actually monitored. It creates a repeatable check around the needed response: Include both intended members in the health-check configuration and verify probe state per link.
Incorrect Answers
Review SLA values using measured voice quality and contractual objectives. That safeguard addresses another potential failure: A voice quality rule uses a jitter maximum far above business tolerance so choppy calls continue on a variable-delay ISP. It is not the most targeted recurring control for the described cause: Performance SLA eligibility depends on which member interfaces are actually monitored.
Verify probe source IP and provider return routes during link commissioning. That safeguard addresses another potential failure: The performance SLA reports high loss on a backup line because probes use a source address not routed by its provider. It is not the most targeted recurring control for the described cause: Performance SLA eligibility depends on which member interfaces are actually monitored.
Baseline latency distributions and application tolerances before setting targets. That safeguard addresses another potential failure: A performance SLA is configured with a 5-ms latency threshold despite a normal 40-ms regional WAN path, excluding all members under healthy conditions. It is not the most targeted recurring control for the described cause: Performance SLA eligibility depends on which member interfaces are actually monitored.