A FortiGate has an SD-WAN configuration with two members (wan1, wan2). The performance SLA monitors latency to 8.8.8.8. The admin notices that even when the SLA is satisfied on both members, all traffic uses wan1. The SD-WAN rule is configured with 'strategy = best quality'. What is the most likely cause?
Best quality uses a tie-breaking order; it does not load balance equally.
Why this answer
When the SD-WAN rule uses 'best quality' strategy and both members meet the performance SLA, FortiGate selects the member with the best (lowest) latency metric. By default, if both members have equal SLA satisfaction, the first member in the SD-WAN configuration (wan1) is chosen as the tie-breaker. This explains why all traffic uses wan1 even though both links are healthy.
Exam trap
The trap here is that candidates assume 'best quality' always selects the best-performing link, but they overlook the implicit tie-breaking rule that defaults to the first configured member when SLA metrics are equal.
How to eliminate wrong answers
Option A is wrong because firewall policies in FortiGate do not override SD-WAN rules; SD-WAN rules are evaluated before firewall policies, and traffic matching an SD-WAN rule is forwarded according to that rule. Option C is wrong because the performance SLA is correctly configured (monitoring 8.8.8.8) and both members satisfy it, so the issue is not misconfiguration but the tie-breaking behavior of 'best quality'. Option D is wrong because 'set match-vip disable' controls whether virtual IP (VIP) objects are matched in the SD-WAN rule, not which WAN member is selected; it has no effect on member selection.