Question 60
In a managed firewall deployment, the team observes: FortiGate local-out traffic to FortiGuard uses WAN2 even though administrators expected all traffic to use client SD-WAN rules. Investigation has shown: Compare system-generated traffic routing, local-out settings, source interfaces, and installed routes. Which corrective action best addresses that evidence?
Explanation
Correct Answer
The appropriate response is to apply appropriate local-out path settings instead of broadly modifying user transit policies. The case begins with fortiGate local-out traffic to FortiGuard uses WAN2 even though administrators expected all traffic to use client SD-WAN rules. The diagnostic basis is to compare system-generated traffic routing, local-out settings, source interfaces, and installed routes. This action addresses the mechanism revealed by that check rather than changing a different security feature or expanding access. A convincing post-change check would show that security-service updates use the intended source path without changing normal client application steering.
Incorrect Answers
Replace conflicting per-member routes with validated supported zone routing where appropriate. The alternative concerns replacing conflicting per-member routes with validated supported zone routing where appropriate, not applying appropriate local-out path settings instead of broadly modifying user transit policies.
Enable the approved outbound source NAT where required for public internet access. This assesses the approved outbound source NAT where required for public internet access; 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.
Refine or remove the conflicting policy route according to the approved traffic steering design. The case-specific requirement is applying appropriate local-out path settings instead of broadly modifying user transit policies, which that option does not establish.