Question 300
A team proposes to close this Fortinet incident: An SD-WAN rule is disabled during troubleshooting but a later engineer assumes its preferred-member list remains in force. Which verification should it require?
Explanation
Correct Answer
Use this outcome as the acceptance criterion for: Inspect active rule status and the next matching rule before attributing path selection. It matters because rule enablement and precedence determine actual forwarding rather than saved values alone.
Incorrect Answers
The option would apply to “An SD-WAN policy sets one carrier as preferred but operators assume preference guarantees selection even when the member is down”. The relevant design distinction is: Preference applies among eligible routes and members and does not override link failure. This question instead requires “Live flow diagnostics identify the rule actually selecting the member”.
That answer fits the separate incident, a branch application is classified under a generic SD-WAN rule before a later business-critical rule can match it. In this environment, the appropriate proof is: Live flow diagnostics identify the rule actually selecting the member.
This alternative addresses the separate case “An application steering report lists the expected rule but the path changed at a time not covered by current SLA charts”. The technical reason is: Operational proof of selection requires time-correlated rule and member-state logs. The deciding requirement here is “Live flow diagnostics identify the rule actually selecting the member”.