Question 330
A Fortinet SD-WAN/FortiSASE operations team encounters the following situation: An SD-WAN branch should use FortiSASE for public SaaS while keeping private ERP over datacenter overlays, yet one catch-all route sends both destinations to SASE. After the correction is implemented, which observable result most specifically proves this incident was resolved?
Explanation
Correct Answer
This result directly tests whether the observed failure has cleared: An SD-WAN branch should use FortiSASE for public SaaS while keeping private ERP over datacenter overlays, yet one catch-all route sends both destinations to SASE. It confirms the targeted change, Split SIA and SPA or private overlay destinations with explicit steering and route criteria, rather than a healthy but unrelated component. The technical cause under test is: One broad route conflates internet-security egress with internal application transport.
Incorrect Answers
That observation verifies a different Integrate SD-WAN and FortiSASE workflows condition, namely: 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 could be true even if the current failure persists. In this case the decisive evidence is tied to: One broad route conflates internet-security egress with internal application transport.
That observation verifies a different Integrate SD-WAN and FortiSASE workflows condition, namely: A branch team sees user SaaS slowness and adds more bandwidth before checking whether a new on-ramp policy moved traffic across a distant PoP. It could be true even if the current failure persists. In this case the decisive evidence is tied to: One broad route conflates internet-security egress with internal application transport.
That observation verifies a different Integrate SD-WAN and FortiSASE workflows condition, namely: A regional branch accesses the same SaaS hostname through local DIA and through SASE, and asymmetric return packets break long-lived sessions. It could be true even if the current failure persists. In this case the decisive evidence is tied to: One broad route conflates internet-security egress with internal application transport.