Question 650
A FortiOS 7.6 team examines: An operator wants to use packet-loss and jitter evidence rather than relying only on interface bandwidth counters. Select TWO complementary choices: the most appropriate corrective action AND the specific evidence confirming success.
Explanation
Correct Answers
The reported FortiOS 7.6 condition is: An operator wants to use packet-loss and jitter evidence rather than relying only on interface bandwidth counters. The targeted administrative response is: Use supported SD-WAN performance SLAs to monitor appropriate destinations and thresholds for latency, jitter and packet loss. The relevant failure risk is: An unreachable or unsuitable probe target can make a healthy WAN look failed or fail to detect real application degradation. Validate with: Measured link health and an application test agree on which WAN members satisfy the required quality thresholds.
For the observed situation (An operator wants to use packet-loss and jitter evidence rather than relying only on interface bandwidth counters), the most specific acceptance evidence is: Measured link health and an application test agree on which WAN members satisfy the required quality thresholds. It validates the recommended response: Use supported SD-WAN performance SLAs to monitor appropriate destinations and thresholds for latency, jitter and packet loss. This addresses the documented risk: An unreachable or unsuitable probe target can make a healthy WAN look failed or fail to detect real application degradation.
Incorrect Answers
Routing versus firewall policy separation (4.1) addresses another technical failure: A successful route lookup does not itself authorize a packet, and an allow rule does not create a missing return route. The case states: An operator wants to use packet-loss and jitter evidence rather than relying only on interface bandwidth counters. The most direct paired action and test is: Use supported SD-WAN performance SLAs to monitor appropriate destinations and thresholds for latency, jitter and packet loss.
Longest-prefix match and route lookup (4.1) would demonstrate or implement: A test destination uses the expected longest-prefix route and packet output agrees with the selected next hop. This choice can be useful for that problem, but it does not establish the Sd-wan performance sla probes control being assessed here.
Equal-cost route redundancy and path verification (4.1) would demonstrate or implement: Assuming equal-cost paths provide perfect balancing or fast failover without link monitoring can cause session disruption. This case instead tests Sd-wan performance sla probes; the choice measures or changes another part of the system.