Question 160
At Orchard Biotech, an infrastructure review by the laboratory network group is evaluating remote researcher access across a laboratory hybrid network during a scheduled resiliency exercise (FT-C-18-01). 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: sensitive lab assets remain inaccessible to untrusted endpoints. Which corrective approach best resolves the observed issue while meeting the operating constraint?
Explanation
Correct Answer
The observed problem is that a new SPA path is routed but a FortiGate hub lacks the relevant application authorization policy. Align FortiSASE SPA connectivity with the hub-side policy and private application mapping as part of Orchard Biotech's remote researcher access update (FT-C-18-01), while enforcing the constraint that sensitive lab assets remain inaccessible to untrusted endpoints. A successful implementation must be checked rather than assumed: In a controlled a laboratory hybrid network acceptance test, An entitled remote session succeeds while a nonentitled test remains denied; the outcome is recorded under Orchard Biotech's rollout (FT-C-18-01). The technical reason is that Reachable IPsec paths do not grant private application authorization by themselves.
Incorrect Answers
The source case reports that a new SPA path is routed but a FortiGate hub lacks the relevant application authorization policy. The offered alternative is useful for: SPA high availability spans tunnels routes and application firewall permissions. In this case the decisive mechanism is: Reachable IPsec paths do not grant private application authorization by themselves. The specific action is “Align FortiSASE SPA connectivity with the hub-side policy and private application mapping; keep the affected tenant scope documented”.
The source case reports that a new SPA path is routed but a FortiGate hub lacks the relevant application authorization policy. This option would change the control governed by: Path failover should not silently bypass a mandatory inspection service. That does not resolve the present failure, where reachable IPsec paths do not grant private application authorization by themselves. The applicable response is “Align FortiSASE SPA connectivity with the hub-side policy and private application mapping; keep the affected tenant scope documented”.
The source case reports that a new SPA path is routed but a FortiGate hub lacks the relevant application authorization policy. The offered alternative is useful for: SIA applies cloud-delivered security to internet-bound traffic. In this case the decisive mechanism is: Reachable IPsec paths do not grant private application authorization by themselves. The specific action is “Align FortiSASE SPA connectivity with the hub-side policy and private application mapping; keep the affected tenant scope documented”.