Question 750
At Summit Hospitality, an infrastructure review by the guest connectivity group is evaluating hotel staff service applications across a regional resort branch fabric after the last approved policy installation (FT-C-18-02). The review finds that a new SPA path is routed but a FortiGate hub lacks the relevant application authorization policy. Any correction must respect this operating requirement: guest and staff traffic must use separate security boundaries. Which architectural or operational principle best explains the appropriate correction?
Explanation
Correct Answer
The relevant design principle is: Reachable IPsec paths do not grant private application authorization by themselves. In this hotel staff service applications decision, the control is assessed using observable network or policy state, not the engineer's assumption. The failure is that a new SPA path is routed but a FortiGate hub lacks the relevant application authorization policy; the intended approach is to align FortiSASE SPA connectivity with the hub-side policy and private application mapping. The distinguishing confirmation is that An entitled remote session succeeds while a nonentitled test remains denied.
Incorrect Answers
The source case reports that a new SPA path is routed but a FortiGate hub lacks the relevant application authorization policy. That principle controls the offered alternative: Different onboarding methods can produce different effective access and routing policy; avoid assuming a healthy session proves all services work. It is not the causal distinction established here: Reachable IPsec paths do not grant private application authorization by themselves.
The source case reports that a new SPA path is routed but a FortiGate hub lacks the relevant application authorization policy. The proposed explanation concerns: SPA high availability spans tunnels routes and application firewall permissions; avoid assuming a healthy session proves all services work. The reported symptom instead follows: Reachable IPsec paths do not grant private application authorization by themselves.
The source case reports that a new SPA path is routed but a FortiGate hub lacks the relevant application authorization policy. The alternative states a real but different technical principle: SPA extends governed connectivity to private resources rather than generic web browsing; do not infer authorization solely from connectivity. The facts in this question are explained by: Reachable IPsec paths do not grant private application authorization by themselves.