Question 360
A Fortinet SD-WAN/FortiSASE operations team encounters the following situation: A dual-hub SASE deployment routes private application requests through hub B after failure but sends their responses through hub A's stale summary route. Which sustained control would best prevent this same failure from recurring?
Explanation
Correct Answer
This guard addresses the recurring failure mode demonstrated by the case: Failover policy was validated in only the outbound direction. It guards the same affected workflow, rather than merely checking that some other service works. A successful controlled outcome would be: Stateful application traffic survives or reconnects through the surviving hub with valid bidirectional paths.
Incorrect Answers
This control is relevant to another scenario in the stated requirement, specifically: A manufacturing campus has two datacenter hubs, but the FortiSASE SPA design relies solely on the first hub for resource access. It would not prevent the present mechanism: Failover policy was validated in only the outbound direction. Prevention must be linked to that actual failure mode rather than a generic adjacent control.
This control is relevant to another scenario in the stated requirement, specifically: A regional branch accesses the same SaaS hostname through local DIA and through SASE, and asymmetric return packets break long-lived sessions. It would not prevent the present mechanism: Failover policy was validated in only the outbound direction. Prevention must be linked to that actual failure mode rather than a generic adjacent control.
This control is relevant to another scenario in the stated requirement, specifically: An IT team assumes that connecting the SASE tenant to the hub automatically gives every branch access to private applications without user or site authorization. It would not prevent the present mechanism: Failover policy was validated in only the outbound direction. Prevention must be linked to that actual failure mode rather than a generic adjacent control.