Question 170
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 architectural or operational principle best explains the appropriate correction?
Explanation
Correct Answer
The relevant design principle is: Private routing changes can invalidate access even when user authentication succeeds. In this parts and diagnostics services decision, the control is assessed using observable network or policy state, not the engineer's assumption. The failure is that users authenticate to FortiSASE but a private application times out when its subnet is moved behind another hub; the intended approach is to compare FortiSASE and FortiGate private route advertisements after the subnet move. The distinguishing confirmation is that The new application prefix is reachable over the intended SPA path while the old prefix is withdrawn.
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. That principle controls the offered alternative: Endpoint evidence helps isolate device-specific failures from cloud or hub outages; distinguish desired policy from effective enforcement. It is not the causal distinction established here: Private routing changes can invalidate access even when user authentication succeeds; separate observed path selection from configuration intent.
The source case reports that users authenticate to FortiSASE but a private application times out when its subnet is moved behind another hub. The proposed explanation concerns: IPsec failures can occur before routing or application policy is relevant; do not infer authorization solely from connectivity. The reported symptom instead follows: Private routing changes can invalidate access even when user authentication succeeds; separate observed path selection from configuration intent.
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 states a real but different technical principle: Template consistency supports scale when local differences are deliberate and reviewable; separate observed path selection from configuration intent. The facts in this question are explained by: Private routing changes can invalidate access even when user authentication succeeds; separate observed path selection from configuration intent.