Performance SLA (Service Level Agreement) in FortiGate SD-WAN is used to monitor the performance of member interfaces based on defined targets for latency, jitter, and packet loss.

An SD-WAN rule configured with the Best Quality strategy must reference a Performance SLA. This strategy relies on the SLA targets to compare the quality of available links and select the one that best meets the criteria. Therefore, SLA targets are a mandatory component for this specific rule strategy.

Furthermore, while Performance SLAs actively measure link quality once configured, these measurements only influence traffic routing decisions when an SD-WAN rule explicitly references that SLA. Without being linked to a rule, the SLA performs its measurements, but no traffic steering action is taken based on the results.

A. You can configure multiple SLA targets (latency, jitter, packet loss) within a single Performance SLA, and you can create many Performance SLAs. There is no limit of two.

B. This statement is too general. While you can configure SD-WAN without using Performance SLAs (e.g., with a manual strategy), they are mandatory for certain strategies like Best Quality.

1. Fortinet FortiOS 7.0 SD-WAN Administration Guide

Page 23

"SD-WAN rules":

"The Best Quality strategy selects a link based on the link quality

which is measured by a performance SLA. You must select a performance SLA in the Interface preference field." This directly supports option C.

2. Fortinet FortiOS 7.0 SD-WAN Administration Guide

Page 18

"Performance SLA":

"Performance SLAs

also known as health checks

are used to monitor the health and performance of SD-WAN members that are used to route traffic. SD-WAN rules use the results from performance SLAs to route traffic to the best link to maintain performance for business-critical applications." This supports option D

as the use of the SLA results for routing is tied to the SD-WAN rules.

3. Fortinet FortiOS 7.0 SD-WAN Administration Guide

Page 20

"Configuring the performance SLA":

The configuration steps show that within one Performance SLA

you can set thresholds for Latency

Jitter

and Packet Loss. This refutes the arbitrary limit of two targets mentioned in option A.