SD-WAN interacts with many other FortiGate features. Some of them are required to allow SD-WAN to steer the traffic. Which three configuration…

For FortiGate SD-WAN to successfully steer traffic, three core components must be configured. First, physical or virtual Interfaces must be configured and added as members to the SD-WAN zone. Second, Routing, typically static routes such as default routes, must be in place for each member interface to provide reachability to the next-hop gateways. Finally, Firewall policies are required to permit the traffic, with the outgoing interface set to the SD-WAN virtual interface. These policies are what actually direct the traffic to the SD-WAN engine for path selection based on the configured SD-WAN rules. Without these three elements, traffic cannot be processed or steered by the SD-WAN feature.

C. Security profiles: These are applied to firewall policies for traffic inspection. While crucial for security, they are not a prerequisite for the SD-WAN steering mechanism itself to function.

D. Traffic shaping: This feature manages bandwidth and prioritizes traffic. It is complementary to SD-WAN and can be applied via firewall policies, but it is not required for path selection.

1. Fortinet FortiOS 7.6.0 SD-WAN Administration Guide, Page 13, "Basic configuration". The guide explicitly lists the required steps: "1. Configure the SD-WAN interface and members. 2. Configure SD-WAN rules. 3. Configure a static route. 4. Configure a firewall policy." This directly confirms the necessity of Interfaces (members), Routing (static route), and Firewall policies.

2. Fortinet FortiOS 7.6.0 Administration Guide, Page 710, "Policies". This section details firewall policy configuration, showing that the source, destination, and outgoing interface (which would be the SD-WAN interface) are mandatory fields, while security profiles are optional additions.

3. Fortinet FortiOS 7.6.0 Networking Guide, Page 10, "Static routing". This document explains the fundamental role of static routes in directing traffic to a next-hop router. For SD-WAN, a route is required for each member interface to establish reachability, which is a prerequisite for the SD-WAN logic to select it as a valid path.