Question 470
The deployment team is preparing a sign-off for: FortiGate local-out traffic to FortiGuard uses WAN2 even though administrators expected all traffic to use client SD-WAN rules. Which limitation or risk should it explicitly consider before approval?
Explanation
Correct Answer
The most relevant caution is that local management traffic and forwarded user sessions need not share identical policy evaluation. The case concerns fortiGate local-out traffic to FortiGuard uses WAN2 even though administrators expected all traffic to use client SD-WAN rules. The safer path is to compare system-generated traffic routing, local-out settings, source interfaces, and installed routes and then, after verification, to apply appropriate local-out path settings instead of broadly modifying user transit policies. This is the closest caution because it addresses the failure mechanism instead of a generic issue from another security workflow.
Incorrect Answers
Policy-route precedence can make debugging only the SD-WAN rule misleading. The check concerns policy-route precedence can make debugging only the SD-WAN rule misleading, not confirming that local management traffic and forwarded user sessions need not share identical policy evaluation.
Selecting a healthy outbound WAN alone does not prove the return path is symmetric. This assesses selecting a healthy outbound WAN alone does not prove the return path is symmetric; it does not determine the reported condition—fortiGate local-out traffic to FortiGuard uses WAN2 even though administrators expected all traffic to use client SD-WAN rules.
Manually pinning a static route to one physical link can undermine SD-WAN steering design. The case-specific requirement is confirming that local management traffic and forwarded user sessions need not share identical policy evaluation, which that option does not establish.