Question 600
At Cobalt Retail, an infrastructure review by the branch WAN platform team is evaluating payment-site availability across a 64-store retail WAN during a regional modernization (FT-C-03-02). The review finds that a SaaS application requires sanctioned usage policy but is placed only behind an internal datacenter gateway. Any correction must respect this operating requirement: PCI-segmented traffic remains on approved paths. Which corrective approach best resolves the observed issue while meeting the operating constraint?
Explanation
Correct Answer
The observed problem is that a SaaS application requires sanctioned usage policy but is placed only behind an internal datacenter gateway. Apply a FortiSASE Secure SaaS Access design with suitable SaaS visibility and policy as part of Cobalt Retail's payment-site availability update (FT-C-03-02), while enforcing the constraint that PCI-segmented traffic remains on approved paths. A successful implementation must be checked rather than assumed: In a controlled a 64-store retail WAN acceptance test, A permitted SaaS session is governed under the approved cloud service policy; the outcome is recorded under Cobalt Retail's rollout (FT-C-03-02). The technical reason is that SSA focuses on SaaS access controls within the broader SASE offering.
Incorrect Answers
The source case reports that a SaaS application requires sanctioned usage policy but is placed only behind an internal datacenter gateway. This option would change the control governed by: Evaluate supported agentless web access rather than assuming a managed endpoint is mandatory; confirm the dependent routing state. That does not resolve the present failure, where sSA focuses on SaaS access controls within the broader SASE offering. The applicable response is “Apply a FortiSASE Secure SaaS Access design with suitable SaaS visibility and policy; confirm the dependent routing state”.
The source case reports that a SaaS application requires sanctioned usage policy but is placed only behind an internal datacenter gateway. The offered alternative is useful for: Cloud security service location can influence compliance and operational design. In this case the decisive mechanism is: SSA focuses on SaaS access controls within the broader SASE offering. The specific action is “Apply a FortiSASE Secure SaaS Access design with suitable SaaS visibility and policy; confirm the dependent routing state”.
The source case reports that a SaaS application requires sanctioned usage policy but is placed only behind an internal datacenter gateway. This option would change the control governed by: Reachable IPsec paths do not grant private application authorization by themselves. That does not resolve the present failure, where sSA focuses on SaaS access controls within the broader SASE offering. The applicable response is “Apply a FortiSASE Secure SaaS Access design with suitable SaaS visibility and policy; confirm the dependent routing state”.