Question 910
A FortiSASE operator faces this issue: Remote employees on agent-based SIA browse normally but private CRM connections use a separate legacy VPN that intermittently conflicts with routes. What corrective configuration or investigation is most appropriate?
Explanation
Correct Answer
The focused remedy is: Review endpoint routing and the permitted SPA integration before changing connection priorities. The underlying dependency is: Multiple endpoint tunnels and route tables can collide unless split tunneling is designed deliberately. The acceptance check is: CRM private routes and SIA public browsing coexist with predictable path selection.
Incorrect Answers
The alternative is useful for a service provider uses a regional FortiGate hub to reach private applications but fails to advertise the application prefixes back to FortiSASE, but it does not resolve the observed condition here: Multiple endpoint tunnels and route tables can collide unless split tunneling is designed deliberately. The answer is: Review endpoint routing and the permitted SPA integration before changing connection priorities.
The source problem for this choice is a FortiSASE tenant serves remote employees and branches but receives no analytics because FortiAnalyzer log forwarding was never established. The reported scenario has a different controlling condition: Multiple endpoint tunnels and route tables can collide unless split tunneling is designed deliberately.
That proposal leaves the central dependency unresolved. The correction is: Review endpoint routing and the permitted SPA integration before changing connection priorities. The expected acceptance result is: CRM private routes and SIA public browsing coexist with predictable path selection.