A FortiGate has two static default routes out of two different ISP links. Both routes have the same administrative distance and the same priority. What is the effect on traffic that uses the default route?
- ABoth routes are installed in the forwarding table and traffic is load balanced across both links using equal-cost multi-path routing Correct
- BOnly the route whose gateway has the lower IP address is installed, and all default traffic uses that single link
- CNeither route is installed because FortiGate rejects duplicate default routes and logs a configuration conflict
- DBoth routes are installed but only the most recently configured one forwards traffic until it fails over to the other
Why A is correct: When two routes share the same distance and priority, FortiGate treats them as equal-cost and installs both, performing ECMP load balancing across the two links according to the configured load-balancing method.
Why B is wrong: FortiGate does not select between equal routes by comparing gateway IP addresses. This sounds like a deterministic tie-breaker but no such rule exists, so it is incorrect.
Why C is wrong: FortiGate accepts multiple default routes; it does not reject them as duplicates. The idea of a conflict rejection is plausible to a newcomer but does not reflect FortiOS behaviour.
Why D is wrong: Equal routes do not behave as an active and passive pair when distance and priority match. This describes failover, which requires differing priority or distance, so it is a tempting but wrong assumption.