Question 590
At Trillium Education, an infrastructure review by the school network group is evaluating branch administration connectivity across a district-wide learning network after an audit of cloud access (FT-C-07-01). The review finds that a branch needs cloud security inspection but engineers configure only local WAN load balancing. Any correction must respect this operating requirement: student devices remain separate from administrator systems. Which architectural or operational principle best explains the appropriate correction?
Explanation
Correct Answer
The relevant design principle is: Branch SD-WAN steering and SASE cloud enforcement are complementary components. In this branch administration connectivity decision, the control is assessed using observable network or policy state, not the engineer's assumption. The failure is that a branch needs cloud security inspection but engineers configure only local WAN load balancing; the intended approach is to plan a supported SD-WAN on-ramp connecting the branch edge with FortiSASE inspection. The distinguishing confirmation is that A branch-originated internet flow traverses approved FortiSASE security controls.
Incorrect Answers
The source case reports that a branch needs cloud security inspection but engineers configure only local WAN load balancing. The alternative states a real but different technical principle: FortiSASE PoPs may participate in a governed overlay topology; verify the dependent conditions independently. The facts in this question are explained by: Branch SD-WAN steering and SASE cloud enforcement are complementary components.
The source case reports that a branch needs cloud security inspection but engineers configure only local WAN load balancing. The proposed explanation concerns: Edge access models differ by required local platform and management capability. The reported symptom instead follows: Branch SD-WAN steering and SASE cloud enforcement are complementary components.
The source case reports that a branch needs cloud security inspection but engineers configure only local WAN load balancing. The alternative states a real but different technical principle: Agent-based and agentless remote use cases have different deployment requirements; do not infer authorization solely from connectivity. The facts in this question are explained by: Branch SD-WAN steering and SASE cloud enforcement are complementary components.