Before FortiGate can steer traffic according to SD-WAN rules, certain configuration elements must be present. Fortinet SD-WAN design guidance describes the required elements: " SD-WAN is not a standalone feature and interacts with several fundamental FortiGate configurations. Specifically, you must: (1) Define the interfaces (physical, VLAN, or IPsec) that will act as SD-WAN members, (2) Create firewall policies to allow traffic to be steered by SD-WAN, and (3) Set up routing so that traffic has valid routes via SD-WAN members. Without these, SD-WAN rules will not be able to match or steer any traffic. " Security profiles and traffic shaping are not mandatory for basic SD-WAN steering but can be layered on for enhanced security and QoS once foundational elements are present.References: A deployment should preserve the distinction between the physical or logical WAN underlay, the IPsec overlay and the SD-WAN zone that groups forwarding members. These layers can have different routing and security-policy requirements. The configured architecture must also allow the required traffic paths and failover behavior rather than assuming every available interface is interchangeable.

The SD-WAN event log shows member 1 transitioning out of SLA. The member diagnostics identify member 1 as port1 and member 2 as port2. The service ' s priority list places port1 before port2, so a properly eligible port2 would be the next forwarding choice when port1 no longer meets the required threshold. This makes option B the intended answer. However, the screenshots do not independently establish port2 ' s current SLA pass state and the complete effective service selection conditions at the instant of the event. A single member ' s out-of-SLA log is insufficient to prove that port2 is healthy, reachable for the destination and selected immediately after the event. Option A is not a universal consequence of one SLA failure; option C incorrectly assumes port1 remains eligible; option D is not proven either because the configuration is not shown to be in a multi-member load-balancing state. To verify B, inspect ' diagnose sys sdwan service4 1 ' and the health-check status after the event, confirming member 2 is selected and destination-route eligible. The item is conditionally supported, not fully established by the current exhibit alone.

Verification qualification: Port2 must be shown operational and in SLA; the exhibit alone does not prove that state.

Hosting the hub at the MSSP centralizes installation, security, and ongoing management while each site (spoke) keeps local DIA. This can be done multi-tenant with a shared hub using a dedicated VDOM or with a fully dedicated hub per customer for stricter isolation and control, both meeting the requirement to delegate administration to the MSSP and support high inter-site traffic. A deployment should preserve the distinction between the physical or logical WAN underlay, the IPsec overlay and the SD-WAN zone that groups forwarding members. These layers can have different routing and security-policy requirements. The configured architecture must also allow the required traffic paths and failover behavior rather than assuming every available interface is interchangeable. Before applying a topology change, review the interface dependencies, static and dynamic routing, security policies and provisioning templates. FortiGate can support multiple transport types, but routing and tunnel compatibility still determine whether the intended member is operationally eligible.