Question 70
At Cobalt Retail, an infrastructure review by the branch WAN platform team is evaluating payment-site availability across a 64-store retail WAN after a tenant onboarding change (FT-C-08-02). The review finds that a hub design assumes FortiSASE PoPs are only internet exits and excludes them from overlay routing. Any correction must respect this operating requirement: PCI-segmented traffic remains on approved paths. Which ongoing control most directly reduces the chance of this issue returning?
Explanation
Correct Answer
This preventive control directly targets recurrence: Review hub route scope after adding new regional PoPs; make it a repeatable part of Cobalt Retail's change assurance (FT-C-08-02). It sustains the corrective action, model supported FortiSASE spoke connectivity and hub route advertisements, and must preserve the requirement that PCI-segmented traffic remains on approved paths.
Incorrect Answers
The source case reports that a hub design assumes FortiSASE PoPs are only internet exits and excludes them from overlay routing. The alternative is a useful recurring check for: Audit SPA route reachability alongside user entitlement changes; include explicit primary and alternate path tests. The present failure instead depends on: Review hub route scope after adding new regional PoPs; document the result for the next audit cycle. The targeted safeguard is “Review hub route scope after adding new regional PoPs; document the result for the next audit cycle”.
The source case reports that a hub design assumes FortiSASE PoPs are only internet exits and excludes them from overlay routing. “Exercise log-delivery failure and recovery for the central collector; use a measured acceptance threshold where relevant” maintains another technical control: Exercise log-delivery failure and recovery for the central collector; use a measured acceptance threshold where relevant. It does not directly prevent this case’s specific recurrence, for which “Review hub route scope after adding new regional PoPs; document the result for the next audit cycle” addresses: Review hub route scope after adding new regional PoPs; document the result for the next audit cycle.
The source case reports that a hub design assumes FortiSASE PoPs are only internet exits and excludes them from overlay routing. That ongoing review concerns: Require hub policy signoff when publishing new SPA applications; confirm this in the next branch rollout checklist. The governing risk here is: Review hub route scope after adding new regional PoPs; document the result for the next audit cycle. Maintain “Review hub route scope after adding new regional PoPs; document the result for the next audit cycle” as the case-specific check.