FortiGate first establishes destination reachability and then evaluates the eligible members of the matching SD-WAN service. The exhibit reports that traffic for the corporate network is reaching HUB1-VPN3 even though HUB1-VPN1 appears earlier in member preference. Option C is supported if HUB1-VPN1 has no valid route for the exact destination prefix. An SD-WAN service cannot force traffic through an overlay member that does not provide reachability. The candidate ' s second answer, D, is less precise: the exhibit presents SD-WAN member preference or priority values, whereas the wording says ' route priority ' . FortiOS distinguishes route priority in the FIB from the preference order defined in an SD-WAN service. A smaller numerical member preference can influence forwarding, but it should not be described as proof of a more-preferred static route. Option A reverses the ranking, and option B invents an overriding conventional policy route not established by the diagnostic output. As presented, C is secure but the complete C,D pair depends on interpreting D as member priority rather than routing-table priority. Validate the actual route entries, their administrative distance and priority, and ' diagnose sys sdwan service4 ' before treating D as conclusive.

Verification qualification: The choice concerning route priority is imprecisely worded; displayed member priority is not necessarily static-route priority.