(Refer to the exhibit. You noticed that one SD-WAN member went down and you immediately collected the session output shown in the exhibit. What can you conclude from this output? Choose one answer.)

Exhibit.

Which action will FortiGate take if it detects SD-WAN members as dead?
Which statement describes FortiGate behavior when you reference a zone in a static route?
When referencing a zone in a static route, FortiGate's behavior is described as: 'Referencing a zone in a static route causes FortiGate to install a static route for each member interface of the zone. This enables ECMP (Equal-Cost Multi-Path) and load balancing where supported and ensures that traffic can be steered over any valid zone member according to SD-WAN rules or standard routing.' This mechanism is fundamental to Fortinet's implementation of SD-WAN and simplifies large, multi-interface deployments. Reference:
[FCSS_SDW_AR-7.4 1-0.docx Q21]
FortiOS 7.4 Routing Guide, ''Zone-based Routing and ECMP Behavior''
Refer to the exhibits, which show the configuration of an SD-WAN rule and the corresponding rule status and routing table.


The administrator wants to understand the expected behavior for traffic matching the SD-WAN rule.
Based on the exhibits, what can the administrator expect for traffic matching the SD-WAN rule?
The rule is in SLA mode with two SLAs. From the status, HUB1-VPN2 and HUB1-VPN3 meet the SLA (sla(0x2) and sla(0x3)), while HUB1-VPN1 does not (sla(0x0)). Among members that meet SLA, FortiGate uses the configured order (priority-members 4 5 6) to pick the first eligible one---HUB1-VPN2---so traffic is routed over HUB1-VPN2.
(You want to configure two static routes: one that references an SD-WAN zone and a second one that references an SD-WAN member that belongs to that zone.
Which statement about this scenario is true? Choose one answer.)
In FortiOS 7.6, static routes can reference either:
an SD-WAN zone (for example, virtual-wan-link or a user-defined SD-WAN zone), or
a specific SD-WAN member interface that belongs to that zone.
However, FortiOS enforces a routing constraint to avoid ambiguity during route resolution. Two static routes cannot have the same destination prefix if one points to an SD-WAN zone and the other points to an SD-WAN member within that zone. This would create an overlapping and conflicting forwarding decision.
Therefore, if you configure:
one static route that references an SD-WAN zone, and
another static route that references an SD-WAN member belonging to that same zone,
the destination subnets of the two static routes must be different.
Why the other options are incorrect:
Option A is incorrect because FortiOS does allow static routes that reference individual SD-WAN members.
Option B is incorrect because static routes can reference SD-WAN zones.
Option D is incorrect because static routing decisions in FortiOS are based on destination prefixes, not source prefixes.
Thus, the correct answer is C.
Clement
12 hours agoLou
9 days agoAndra
16 days agoShawna
23 days agoBrett
30 days agoCary
1 month agoVinnie
1 month agoWade
2 months agoStefania
2 months agoGerman
2 months ago