Question 900
In the following Fortinet incident—An application steering report lists the expected rule but the path changed at a time not covered by current SLA charts—what concern should the team explicitly mitigate?
Explanation
Correct Answer
A shortcut would leave the case-specific dependency unresolved: Operational proof of selection requires time-correlated rule and member-state logs. Reduce the resulting risk by doing the following: Correlate SD-WAN rule history, SLA events and session timestamps in analytics.
Incorrect Answers
The option would apply to “A branch application is classified under a generic SD-WAN rule before a later business-critical rule can match it”. The failure exposure comes from the underlying condition: SD-WAN traffic steering depends on rule lookup order and actual match criteria. This question instead requires “Current snapshots alone cannot explain past candidate changes”.
This option serves the scenario “A campus has one trusted broadband member and a metered cellular backup, but a balancing rule uses both equally”. This is the most direct failure mode to prevent. The present scenario is distinguished by “Current snapshots alone cannot explain past candidate changes”.
This alternative addresses the separate case “A critical payment application is accidentally handled as generic web traffic because its service port is different from the rule”. The failure exposure comes from the underlying condition: Source, destination, port and application criteria collectively determine traffic matching. The deciding requirement here is “Current snapshots alone cannot explain past candidate changes”.