Question 830
A Fortinet architect receives this requirement: A dual-ISP branch on-ramp sends cloud traffic to FortiSASE only over the primary carrier and ignores the second. Which change should the team implement first?
Explanation
Correct Answer
Apply this remedy rather than changing unrelated policies: Configure permitted failover for the FortiSASE on-ramp across healthy underlay members. This follows from the fact that hybrid edge resilience must include alternative transport selection for the SASE attachment. The expected result is: Selected browsing recovers through backup WAN while maintaining cloud security policy.
Incorrect Answers
This shortcut is attractive but misses the underlying condition: Hybrid edge resilience must include alternative transport selection for the SASE attachment. The case requires the targeted remedy: Configure permitted failover for the FortiSASE on-ramp across healthy underlay members.
The option would apply to “A provider changes a branch public IP after ISP migration and the SASE on-ramp tunnel no longer authenticates”. The change needed here is: Revalidate the on-ramp peer identity, reachable endpoint and approved IPsec settings. This question instead requires “Configure permitted failover for the FortiSASE on-ramp across healthy underlay members”.
The related but distinct situation is “A customer wants to connect thousands of internet-of-things devices to SASE but assumes each must have personal SAML credentials”. The change needed here is: Use an approved branch or FortiExtender attachment to carry device traffic under policy. For the stated problem, “Configure permitted failover for the FortiSASE on-ramp across healthy underlay members” addresses the central condition.