The 7.6 study guide explains the route selection order:
"Route Selection Process
Most specific route
Lowest distance
Lowest metric (dynamic routes)
Lowest priority (static routes)
ECMP (static, BGP, and OSPF routes)"**
It then states:
"If there are multiple routes with the same netmask, distance, metric, and priority, FortiGate shares the traffic among all of them. This is called equal-cost multi-path (ECMP)." The FortiOS administration guide confirms the ECMP prerequisite:
"Routes must have the same destination and costs. In the case of static routes costs include distance and priority." In the exhibit, the kernel/FIB output shows the two default routes as:
gwy=100.64.1.254 dev=3 (port1) prio=0
gwy=100.64.2.254 dev=6 (port2) prio=10
So although both are default routes, their priorities are different. Since FortiGate uses the FIB/kernel for forwarding traffic, ECMP will not happen until the static-route priorities are the same. The study guide also notes that the FIB is the table used to perform standard routing Therefore, to make the two default routes eligible for ECMP, the administrator must make the priorities equal.
Since port2 is already 10, the needed change is to set the port1 default route priority to 10.
Why the other options are wrong:
A is wrong because snat-route-change affects how existing SNAT sessions react to routing changes, not whether static routes qualify for ECMP B is wrong because changing port2 to priority 1 still would not match port1 at 0, so the routes still would not have equal cost for ECMP C is wrong because preserve-session-route affects existing-session route persistence after routing changes, not ECMP qualification

The ADVPN shortcut negotiation begins after traffic from Spoke 1 to Spoke 2 initially travels through the hub. When the hub detects that both spokes can establish a more direct connection, the hub-not Spoke 1- sends the first control message: a shortcut offer to Spoke 1.
The SD-WAN 7.6 Enterprise Administrator Study Guide then states: "Spoke 1 acknowledges the shortcut offer by sending a shortcut query to the hub." Therefore, the first message that Spoke 1 sends in response is the shortcut query , making option A correct.
The hub subsequently forwards that query to Spoke 2. Spoke 2 responds with a shortcut reply , which the hub forwards back to Spoke 1. After Spoke 1 receives the reply containing the necessary peer information, Spoke 1 and Spoke 2 begin IKE negotiation and establish the dynamic spoke-to-spoke shortcut tunnel.
Consequently, the shortcut reply occurs later and originates from Spoke 2, while the offer originates from the hub. "Shortcut forward" describes the hub's forwarding action rather than Spoke 1's first response. This behavior is part of Fortinet's ADVPN shortcut architecture .

To establish a functional Security Fabric, specific network and configuration prerequisites must be met to ensure nodes can communicate, authorize, and share telemetry data:
A). You must ensure that TCP port 8013 is not blocked along the way:
TCP port 8013 is the dedicated port for FortiTelemetry (Fabric) communication. If firewalls (intermediate or local) block this port, the Fabric connection between the root and downstream FortiGates will fail.
D). You must authorize the downstream FortiGate on the root FortiGate:
Security Fabric relies on a trust relationship. When a downstream device attempts to join, it appears in the Root FortiGate ' s dashboard. The administrator must manually authorize this device (unless pre-authorized via serial number) to allow it to join the Fabric topology.
E). You must enable FortiTelemetry on the receiving interface of the upstream FortiGate:
The interface on the Root (upstream) FortiGate that faces the downstream devices must have the " Security Fabric Connection " (formerly CAPWAP/FortiTelemetry) administrative access setting enabled. Without this, the interface will not listen for or accept Fabric connection requests.
Why other options are incorrect:
B: Neighbor Discovery uses standard multicast/broadcast or static settings; changing the port is not a standard requirement.
C: FortiGates can participate in the Security Fabric in either NAT or Transparent mode; Transparent mode is not a mandatory requirement for the Fabric itself.
Reference:
FortiGate Security 7.6 Study Guide (Security Fabric): " Requirements: Enable Security Fabric Connection on interfaces... Authorize downstream devices... Ensure TCP 8013 is allowed. "

To determine the type of policy route, we must interpret the specific flags and fields visible in the diagnose firewall proute list (or similar kernel table) output provided in the exhibit Identify Key Indicators:
The most critical field in the output is vwl_service=1(test123).
It also lists vwl_mbr_seq=1 5.
Decode the Terminology:
vwl: This stands for Virtual WAN Link. In FortiOS, " Virtual WAN Link " is the legacy internal name for the SD-WAN feature. Even in newer firmware versions (7.x), the kernel and CLI debugs often still refer to SD- WAN objects as vwl.
vwl_service: This specifically refers to an SD-WAN Rule (also known as an SD-WAN Service). The name (test123) is the name given to that specific SD-WAN rule by the administrator.
Evaluate the Options:
A & D (Regular Policy Route): Standard policy routes (configured under config router policy) do not carry the vwl_service tag. They are typically identified by simple gateway or interface instructions without the SD- WAN service abstraction.
B (ISDB Route): While SD-WAN rules can use the Internet Service Database (ISDB) as a destination, the structure of the route entry shown here-specifically defined by a vwl_service ID-classifies it fundamentally as an SD-WAN rule, regardless of the destination object.
C (An SD-WAN rule): The presence of vwl_service and vwl_mbr_seq (SD-WAN member sequence) definitively identifies this entry as a rule generated by the SD-WAN subsystem.
Conclusion: The output shows a route controlled by the SD-WAN engine (vwl), confirming it is an SD-WAN rule.
Reference:
FortiGate Security 7.6 Study Guide (SD-WAN): " In the kernel routing table and debugs, SD-WAN rules are often referenced as vwl (Virtual WAN Link) services. The vwl_service field indicates the specific SD-WAN rule ID and name. "

The configured rule operates in Lowest Cost (SLA) mode and references both HUB1_HC and HUB1_HTTP.
Although the configured interface-preference sequence is members 4, 5, and 6, that order is not sufficient by itself to determine the active path after SLA evaluation.
The runtime diagnose sys sdwan service4 3 output shows member 6, HUB1-VPN3, first in the evaluated member list. It is alive and displays sla(0x3), indicating that it satisfies the SLA conditions being evaluated. In SLA mode, FortiGate first considers SLA eligibility and cost; configuration order acts as a later tiebreaker.
Fortinet documents this Lowest Cost selection behavior .
Because load balancing is not enabled, traffic is not distributed over all three members. The currently preferred usable member is therefore HUB1-VPN3, making D correct.