Question 120
During a post-incident review at a logistics office, the original problem was: A branch's rule switches from best-quality to fallback during one hour, but the report includes only successful sessions and omits SLA state changes. Which preventive practice most directly addresses its cause?
Explanation
Correct Answer
Collect and retain both traffic and health events for failover analysis. This control reduces recurrence of the documented mechanism: Session allow logs and SLA transition events document different parts of path selection. It creates a repeatable check around the needed response: Correlate SD-WAN event logs with session traffic and health-check state transitions for that window.
Incorrect Answers
Use session IDs or supported correlation keys when measuring failover connection counts. That safeguard addresses another potential failure: A site sees duplicate-looking flow logs for retransmissions during an SD-WAN failover, and analysts count them as distinct user sessions. It is not the most targeted recurring control for the described cause: Session allow logs and SLA transition events document different parts of path selection.
Retain performance SLA history alongside application experience incidents. That safeguard addresses another potential failure: Voice complaints occur after WAN jitter spikes but the incident review relies on total traffic-byte reports without any performance SLA history. It is not the most targeted recurring control for the described cause: Session allow logs and SLA transition events document different parts of path selection.
Label and report implicit rule traffic separately from named application steering. That safeguard addresses another potential failure: An analyst confuses implicit SD-WAN rule hits with explicit application-specific rule selection during a monthly performance review. It is not the most targeted recurring control for the described cause: Session allow logs and SLA transition events document different parts of path selection.