Question 1
During a security audit at a financial services branch, analysts observe: A two-ISP FortiGate has working physical WAN interfaces but no SD-WAN configuration, so a branch cannot steer applications by link health. Which Fortinet configuration or investigation action BEST corrects the identified issue?
Explanation
Correct Answer
Enable SD-WAN, add both WAN interfaces as members in an intended zone, and create the necessary route and firewall policy. This is the most direct response to the stated incident: A two-ISP FortiGate has working physical WAN interfaces but no SD-WAN configuration, so a branch cannot steer applications by link health. The technical mechanism is: Separate usable WAN links do not provide SD-WAN steering until zone, members, routes, and policy are configured together. Confirmation requires: A test client accesses the Internet through the zone and steering follows the enabled member selection.
Incorrect Answers
Reconcile route distance, priority, and zone route design so the approved SD-WAN route wins. That could address a different issue in the same blueprint area: Two WAN links share a configured zone, but a second default route via a physical member is preferred and bypasses the planned SD-WAN gateway abstraction. It does not directly correct the given incident, whose decisive mechanism is: Separate usable WAN links do not provide SD-WAN steering until zone, members, routes, and policy are configured together.
Inspect the selected SD-WAN strategy and choose a supported load-balance strategy only where the business requires distribution. That could address a different issue in the same blueprint area: A support engineer assumes the presence of an SD-WAN health-check means all employee traffic is being load-balanced, yet the policy uses a manual priority path. It does not directly correct the given incident, whose decisive mechanism is: Separate usable WAN links do not provide SD-WAN steering until zone, members, routes, and policy are configured together.
Test and configure the relevant local-out routing or source-interface settings for FortiGate services as supported. That could address a different issue in the same blueprint area: A FortiGate uses an SD-WAN zone for office traffic while FortiGate-originated DNS probes follow an unrelated management path, so user and device tests disagree. It does not directly correct the given incident, whose decisive mechanism is: Separate usable WAN links do not provide SD-WAN steering until zone, members, routes, and policy are configured together.