Question 200
At Willow Mobility, an infrastructure review by the fleet security engineers is evaluating parts and diagnostics services across a vehicle service branch platform before an expanded branch rollout (FT-E-15-01). The review finds that users authenticate to FortiSASE but a private application times out when its subnet is moved behind another hub. Any correction must respect this operating requirement: vehicle telemetry is available only to approved maintenance roles. Which ongoing control most directly reduces the chance of this issue returning?
Explanation
Correct Answer
This preventive control directly targets recurrence: Validate private-prefix inventory after datacenter migrations; make it a repeatable part of Willow Mobility's change assurance (FT-E-15-01). It sustains the corrective action, compare FortiSASE and FortiGate private route advertisements after the subnet move, and must preserve the requirement that vehicle telemetry is available only to approved maintenance roles.
Incorrect Answers
The source case reports that users authenticate to FortiSASE but a private application times out when its subnet is moved behind another hub. The alternative is a useful recurring check for: Require policy-verdict evidence before approving capacity changes; retain the evidence under approved change control. The present failure instead depends on: Validate private-prefix inventory after datacenter migrations; use a measured acceptance threshold where relevant. The targeted safeguard is “Validate private-prefix inventory after datacenter migrations; use a measured acceptance threshold where relevant”.
The source case reports that users authenticate to FortiSASE but a private application times out when its subnet is moved behind another hub. “Keep short diagnostic capture procedures for recurring steering incidents; use a measured acceptance threshold where relevant” maintains another technical control: Keep short diagnostic capture procedures for recurring steering incidents; use a measured acceptance threshold where relevant. It does not directly prevent this case’s specific recurrence, for which “Validate private-prefix inventory after datacenter migrations; use a measured acceptance threshold where relevant” addresses: Validate private-prefix inventory after datacenter migrations; use a measured acceptance threshold where relevant.
The source case reports that users authenticate to FortiSASE but a private application times out when its subnet is moved behind another hub. That ongoing review concerns: Maintain incident triage checklists by symptom and log class; use a measured acceptance threshold where relevant. The governing risk here is: Validate private-prefix inventory after datacenter migrations; use a measured acceptance threshold where relevant. Maintain “Validate private-prefix inventory after datacenter migrations; use a measured acceptance threshold where relevant” as the case-specific check.