Question 40
During a post-incident review at a research campus, the original problem was: Voice complaints occur after WAN jitter spikes but the incident review relies on total traffic-byte reports without any performance SLA history. Which preventive practice most directly addresses its cause?
Explanation
Correct Answer
Retain performance SLA history alongside application experience incidents. This control reduces recurrence of the documented mechanism: Traffic volume statistics cannot establish link-quality violations for real-time services. It creates a repeatable check around the needed response: Inspect historical SLA jitter metrics and correlate them with affected voice session timestamps.
Incorrect Answers
Monitor NTP drift and preserve timezone metadata in security log analysis. That safeguard addresses another potential failure: A security operations team compares FortiGate SD-WAN log times with FortiSASE events and misorders an incident because the branch clock is unsynchronized. It is not the most targeted recurring control for the described cause: Traffic volume statistics cannot establish link-quality violations for real-time services.
Record data freshness and reporting time boundaries on WAN health dashboards. That safeguard addresses another potential failure: A service report claims a WAN path is healthy based on an old dashboard snapshot even though the SLA failed later in the review interval. It is not the most targeted recurring control for the described cause: Traffic volume statistics cannot establish link-quality violations for real-time services.
Maintain per-member utilization dashboards with cost thresholds. That safeguard addresses another potential failure: An operations dashboard shows an unexpected surge on cellular backup but a report aggregates all WAN members, obscuring the affected interface. It is not the most targeted recurring control for the described cause: Traffic volume statistics cannot establish link-quality violations for real-time services.