Question 60
An operations group at a university network resolved: An engineer states SD-WAN ignored a rule because the interface was healthy, but rule diagnostics show no source-address match for the problem client. Which ongoing safeguard should become part of its change process?
Explanation
Correct Answer
Check rule hit and session keys before tuning SLA thresholds. This control reduces recurrence of the documented mechanism: A healthy member is irrelevant when traffic never matches its associated SD-WAN rule. It creates a repeatable check around the needed response: Review rule hit status, match criteria and session source before changing member health settings.
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: A healthy member is irrelevant when traffic never matches its associated SD-WAN rule.
Use per-session SD-WAN rule and egress fields during steering incident triage. That safeguard addresses another potential failure: A branch's CRM sessions use wan2 instead of preferred wan1 but an engineer looks only at interface uptime rather than the matching SD-WAN service logs. It is not the most targeted recurring control for the described cause: A healthy member is irrelevant when traffic never matches its associated SD-WAN rule.
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: A healthy member is irrelevant when traffic never matches its associated SD-WAN rule.