Question 410
In the following Fortinet incident—A remote user can resolve a private application name but TCP connections time out despite successful SASE authentication—what concern should the team explicitly mitigate?
Explanation
Correct Answer
A shortcut would leave the case-specific dependency unresolved: Name resolution and identity are not equivalent to routed private application reachability. Reduce the resulting risk by doing the following: Trace SPA connector health, application route and FortiGate policy for the TCP flow.
Incorrect Answers
This option serves the scenario “A FortiSASE administrator enables DNS filtering but an endpoint's applications keep resolving through an uninspected custom resolver”. The operational danger arises from this condition: DNS security controls only apply to queries that traverse the intended enforcement path. The present scenario is distinguished by “Fixing only DNS can leave a broken secure private route unchanged”.
This alternative addresses the separate case “An enterprise wants remote users to access a data center application through a FortiGate NGFW, but its SPA policy points to the wrong private connector”. The named risk is directly connected to the design rule: SPA connectivity is bound to an appropriate gateway and reachability path. The deciding requirement here is “Fixing only DNS can leave a broken secure private route unchanged”.
The related but distinct situation is “The engineering team is reviewing A project team enables SSL inspection for internet traffic but fails to deploy the trusted CA to managed endpoints”. A shortcut would leave the case-specific dependency unresolved: Client trust material is necessary for supported HTTPS inspection without pervasive certificate warnings. For the stated problem, “Fixing only DNS can leave a broken secure private route unchanged” addresses the central condition.