Question 50
The deployment team is preparing a sign-off for: A FortiGate SD-WAN rule points internet traffic toward a healthy member but the routing table lacks a default route through the SD-WAN zone. Which limitation or risk should it explicitly consider before approval?
Explanation
Correct Answer
The most relevant caution is that sD-WAN rules do not remove the need for a usable destination route. The case concerns a FortiGate SD-WAN rule points internet traffic toward a healthy member but the routing table lacks a default route through the SD-WAN zone. The safer path is to inspect route-table lookup, active static routes, and the required SD-WAN zone next-hop design and then, after verification, to add or repair a valid default route for the applicable SD-WAN zone and verify the policy path. This is the closest caution because it addresses the failure mechanism instead of a generic issue from another security workflow.
Incorrect Answers
Manually pinning a static route to one physical link can undermine SD-WAN steering design. The check concerns manually pinning a static route to one physical link can undermine SD-WAN steering design, not confirming that sD-WAN rules do not remove the need for a usable destination route.
A default SD-WAN route should not be expected to override a valid longer prefix. This assesses a default SD-WAN route should not be expected to override a valid longer prefix; it does not determine the reported condition—a FortiGate SD-WAN rule points internet traffic toward a healthy member but the routing table lacks a default route through the SD-WAN zone.
Policy-route precedence can make debugging only the SD-WAN rule misleading. The case-specific requirement is confirming that sD-WAN rules do not remove the need for a usable destination route, which that option does not establish.