Question 690
A FortiOS 7.6 team examines: A customer asks for both link-status metrics and proof of application behavior during WAN failover. Select TWO complementary choices: the most appropriate corrective action AND the specific evidence confirming success.
Explanation
Correct Answers
For the observed situation (A customer asks for both link-status metrics and proof of application behavior during WAN failover), the most specific acceptance evidence is: The intended new sessions recover on healthy members and the test documents behavior of established flows. It validates the recommended response: Validate the FortiGate SD-WAN member health and steering decision during a controlled underlay failure with appropriate application retry expectations. This addresses the documented risk: Changing WAN path can disrupt established sessions depending on routing, NAT and remote application tolerance.
The reported FortiOS 7.6 condition is: A customer asks for both link-status metrics and proof of application behavior during WAN failover. The targeted administrative response is: Validate the FortiGate SD-WAN member health and steering decision during a controlled underlay failure with appropriate application retry expectations. The relevant failure risk is: Changing WAN path can disrupt established sessions depending on routing, NAT and remote application tolerance. Validate with: The intended new sessions recover on healthy members and the test documents behavior of established flows.
Incorrect Answers
Routing versus firewall policy separation (4.1) would demonstrate or implement: Traffic logs and route diagnostics show both the intended route and an approved first-match firewall policy. This choice can be useful for that problem, but it does not establish the Sd-wan health failover and session evidence control being assessed here.
Longest-prefix match and route lookup (4.1) would demonstrate or implement: A broad default route cannot override an installed more-specific matching prefix solely because its interface is healthy. This case instead tests Sd-wan health failover and session evidence; the choice measures or changes another part of the system.
Static route distance and priority (4.1) addresses another technical failure: Mismatched distance or priority can select a slower WAN path while the preferred next hop remains available. The required paired action and test concerns Sd-wan health failover and session evidence; a passing result for this alternative could leave that requirement unresolved.