Question 880
A team proposes to close this Fortinet incident: A FortiSASE-as-a-spoke design reaches a hub but never learns a specific branch subnet needed for SPA. Which verification should it require?
Explanation
Correct Answer
The observed result gives evidence of the repaired dependency rather than unrelated service health. The targeted fix is: Review advertised private network prefixes and the hub's return-route scope. The principle is: FortiSASE used as a spoke still requires controlled routing to private overlay destinations.
Incorrect Answers
The option would apply to “A regional hub forwards SASE traffic to data center apps but return packets bypass its stateful inspection firewall”. This is the specific acceptance result for the remediation: Correct routing and stateful inspection placement on both request and return paths. This question instead requires “Authorized users can reach the intended branch subnet with symmetric routed return traffic”.
The related but distinct situation is “An enterprise uses a single FortiGate hub for SASE private access despite a contractual requirement to survive hub loss”. The check verifies the actual business or network path after the step: Design a supported dual-hub SPA topology and test hub failure and route convergence. For the stated problem, “Authorized users can reach the intended branch subnet with symmetric routed return traffic” addresses the central condition.
This alternative addresses the separate case “A FortiGate branch must use SD-WAN on-ramp for public SIA but direct WAN overlay for finance servers”. The check verifies the actual business or network path after the step: Define public internet on-ramp selection and finance-specific secure private overlay steering. The deciding requirement here is “Authorized users can reach the intended branch subnet with symmetric routed return traffic”.