Question 1 of 30
A network administrator for a mid-sized enterprise, utilizing FortiOS 7.0, has recently implemented a new SD-WAN rule designed to direct specific internal subnet traffic to a secondary ISP for redundancy. Post-implementation, users on certain internal subnets report intermittent connectivity to internal resources and external services when this rule is active. Tracing reveals that traffic originating from these affected subnets is sometimes being routed via the secondary ISP, leading to timeouts and packet loss, while traffic from other internal subnets remains unaffected. The existing firewall policies and routing tables appear correct for the unaffected subnets. What is the most probable underlying cause of this selective connectivity disruption?
The SD-WAN rule's traffic selectors are too broad or not precisely defined, causing it to incorrectly match and reroute traffic intended for internal services or management interfaces that should not traverse the secondary ISP.
The firmware version of the FortiGate is outdated and lacks the necessary compatibility for complex SD-WAN rule processing, leading to unpredictable traffic handling.
A hardware failure in the FortiGate's network interface card responsible for the secondary ISP connection is causing intermittent packet drops for traffic routed through that specific link.
The licensing for the SD-WAN feature has expired, resulting in a degraded performance and selective traffic management capabilities within the FortiOS environment.

Preparing for NSE4_FGT7.0 Fortinet NSE 4 FortiOS 7.0? Now land the interview.

73% of qualified candidates get rejected because of weak resumes. Build an ATS-optimized, recruiter-ready resume in under 5 minutes - free to start.

Build My Resume Free