The SD-WAN rule is configured to use the Best Quality strategy, with SLAJitter as the measured criterion. This strategy operates in two steps: first, it identifies all member interfaces that meet the configured SLA target; second, from that filtered list, it selects the single best interface based on the quality metric (lowest jitter).

According to Exhibit B, only the TINET10 interface meets the SLA requirements (SLA Met: Yes). The other two interfaces, TINET00 and TMPLS0, do not meet the SLA (SLA Met: No). Therefore, they are not considered eligible paths. As TINET10 is the only member that satisfies the SLA, FortiGate will route all traffic matching this rule through it.

A: The Best Quality strategy selects a single optimal path based on the defined metric; it does not perform load balancing across multiple overlays.

B: TINET00 is not selected because it fails to meet the SLA target, making it an ineligible path for this rule.

C: TMPLS0 is not selected because it fails to meet the SLA target, making it an ineligible path for this rule.

1. Fortinet NSE 7 SD-WAN 7.2 Study Guide, Chapter: "SD-WAN Rules", Section: "Rule Steering Behavior". The guide explains that for the Best Quality strategy, "FortiGate first checks which members meet the SLA target, and then chooses the best one among them based on the link cost." This confirms that members failing the SLA are not considered for selection.

2. FortiOS 7.2 Administration Guide, Section: "SD-WAN > SD-WAN Rules". The documentation states for the Best Quality strategy: "FortiGate sends all traffic to the link with the best quality... If the best link goes down or does not meet the health-check SLA, FortiGate sends traffic to the next best link." This implies that meeting the SLA is a prerequisite for being considered the "best link".