MSSP-hosted hubs are generally appropriate where remote management and shared infrastructure are primary requirements. A customer-premises hub becomes valuable when corporate data center applications account for most branch traffic or when centralized internet security and egress are required at the customer site. Heavy interbranch traffic alone does not mandate a local hub because ADVPN shortcuts can bypass hubs. VoIP alone is likewise not decisive. Fortinet distinguishes secure internet access (SIA) from remote internet access (RIA); the phrase “SIA with centralized breakout” must be interpreted carefully. Remote breakout through the customer’s site corresponds to an RIA-type design, while SIA is a broader FortiSASE security service. In checking this outcome, an administrator should distinguish what the displayed exhibit proves from configuration prerequisites not visible in the screenshot. Routing eligibility, device role, rule matching, and software-version details should be verified before using the selected answer in a production decision. The referenced Fortinet documentation identifies the underlying feature and its supported configuration context.

Verification qualification: Option A conflates FortiSASE Secure Internet Access (SIA) with SD-WAN remote internet access (RIA).

FortiGate SD-WAN can distribute traffic over multiple WAN links while applying performance-based eligibility checks. These checks measure network conditions such as latency, jitter, and packet loss against defined service-level agreement thresholds.

Option A is correct because FortiGate can load balance sessions across available SD-WAN members that satisfy the configured SLA target. An interface that fails the required performance criteria is excluded from the eligible load-balancing set under normal SLA-compliant operation.

Option B is correct because current FortiOS versions support load balancing within the Lowest Cost (SLA) strategy. The configuration uses set mode sla together with set load-balance enable under the relevant SD-WAN service rule. Importantly, the load-balancing algorithm does not use interface cost to select individual links once SLA-based load balancing is enabled.

Option C is incorrect because Best Quality is a separate strategy that selects preferred members based on measured link-quality metrics. It is not the supported SLA-based multi-link load-balancing configuration described in the question.

Option D is incorrect because the legacy session, spillover, and volume terminology does not describe supported Best Quality load-balancing algorithms in this context.

FortiOS 7.4.1 and later integrated the former Maximize Bandwidth strategy into the current load-balancing configuration model.

The exhibit combines static-route priority changes with interface-specific session-route preservation.

Initially, port2 provides the preferred default route with priority 1, while port1 has priority 10. Increasing port2 ' s route priority to 20 makes port1 the preferred path for new route selections.

Option C is correct because newly created sessions use the current routing table. Since port1 now has the better route priority, traffic matching the default route is forwarded through port1.

Option E is correct because the port2 interface has preserve-session-route enable configured. This setting preserves the original egress routing information associated with existing sessions, allowing them to continue through port2 while the previously selected route remains valid.

The global setting snat-route-change enable enables reevaluation of SNAT session routing when applicable routing changes occur. However, the configured session-route preservation requires special consideration and prevents the simplistic assumption that all established sessions must immediately migrate.

Option A incorrectly assumes that every SNAT session is necessarily moved to port1. Option B introduces an IP-pool dependency that does not determine the stated behavior. Option D incorrectly assumes all sessions are marked dirty and rerouted regardless of session preservation.

The key architectural distinction is between forwarding new sessions according to the revised route priority and preserving eligible established sessions on their original egress path.

FortiSASE Secure Private Access can integrate with existing FortiGate SD-WAN infrastructure to provide cloud-delivered security enforcement and connectivity to privately hosted enterprise applications.

Option C is correct because FortiSASE acts as a security enforcement point for traffic entering its cloud infrastructure. Administrators can apply security profiles and traffic policies before permitted sessions are forwarded toward private resources through the established SD-WAN connectivity.

Option D is correct because SD-WAN-integrated SPA provides network-layer connectivity to private applications, supporting both TCP-based and UDP-based protocols. This is valuable for enterprise applications that cannot operate through HTTP-only access proxies.

Option A is incorrect because the SD-WAN integration model does not require FortiClient to establish a direct ZTNA access-proxy tunnel to the on-premises FortiGate. Instead, FortiSASE security points of presence connect to the FortiGate SD-WAN hub through IPsec overlays.

Option B describes an endpoint-posture access-control capability, but posture evaluation is not inherently performed by the SD-WAN hub in this deployment method. FortiSASE and FortiClient can assess endpoint security conditions, while the SD-WAN hub primarily provides network connectivity and local security enforcement.

The principal advantages are protocol-flexible private application connectivity and centralized cloud security inspection, integrated with the existing SD-WAN architecture.

The matching router policy uses set action deny, which is not equivalent to a firewall security-policy deny. Within config router policy, the deny action stops policy-route processing and returns the packet to normal forwarding-information-base route evaluation. Both source 10.0.1.130 and destination 128.66.0.125 match the configured policy-route ranges. FortiGate therefore uses the FIB to select forwarding, subject to a valid route and an accepting firewall policy. The candidate answer key incorrectly claims SD-WAN load balancing, and its explanation incorrectly claims the traffic is dropped. Both contradict FortiOS policy-route semantics. Reference: FortiOS 7.6 CLI Reference — config router policy, action deny; Fortinet Technical Tip — Stop Policy Route. An operational review should distinguish the rule that matches the traffic from the interface that is ultimately selected. Valid forwarding also depends on destination route eligibility, current member state and the applicable SLA or quality-selection algorithm. A diagnostic showing configured members alone is not conclusive evidence that all those members will carry a particular flow.

In FortiOS 7.6, when SD-WAN is enabled, physical and logical WAN interfaces are added as SD-WAN members and are abstracted behind the SD-WAN interface (virtual-wan-link or SD-WAN zone). Traffic forwarding decisions are then made by SD-WAN rules instead of individual interfaces. Under the FortiOS 7.6 architecture and Fortinet SD-WAN architecture guides, firewall policies must reference the SD-WAN interface or SD-WAN zone, not the individual WAN interfaces that are members of SD-WAN. Therefore, during the configuration update process, existing firewall policies that reference physical WAN interfaces must be updated to reference the SD-WAN interface. Option A is incorrect because routing configuration does not require replacing interface references when SD-WAN is enabled. Static and dynamic routes typically point to the SD-WAN interface automatically, and SD-WAN rules handle path selection. Option B is incorrect because SD-WAN is a built-in FortiOS feature. It does not require a separate license and does not require a reboot when enabled. Option D is incorrect because interfaces must remain enabled to function as SD-WAN members. Disabling an interface would prevent SD-WAN from using it for traffic forwarding. Therefore, the required action during the SD-WAN configuration update process is to replace references to interfaces used as SD-WAN members in the firewall policies, which corresponds to option C.

The SD-WAN rule (config service edit 1) is configured with set mode priority. This means the rule selects the best interface based on a defined performance metric, as opposed to a simple static priority or SLA. The event log (image_41cfb5.png) shows Metric latency and Message Service prioritized by performance metric will be redirected in sequence order. This indicates that the rule is using latency to determine the preferred member. Given that the log message is about a change, and the most logical reason for a change in a priority mode is that a different member is now the best performer, it implies that the latency on port2 has become lower than that on port1. The log message Service prioritized by performance metric will be redirected in sequence order confirms that FortiGate is changing the member being used for this service. Because the mode is priority, FortiGate dynamically selects the member that currently meets the best performance criteria, which in this case is latency. The log implies a new member has been selected as the most optimal, and with the default configuration, the members are sorted based on their performance, so the outgoing interface list is effectively updated to prefer the new best-performing member (port2).

FortiSASE geofencing provides geographical access control by permitting or denying connections to FortiSASE security points of presence (POPs) according to the originating country or region of the connecting user or edge device.

Option D is correct because FortiSASE identifies the source country using the connection ' s public IP address and evaluates it against configured regional access restrictions.

Administrators configure this functionality under Network > Geofencing > Regional access to FortiSASE.

FortiSASE supports three geographical access modes:

Allow all: Permits connections from all countries and regions. This is the default configuration.

Allow specified: Permits connections only from explicitly authorized countries or regions.

Deny specified: Blocks connections originating from selected countries or regions while permitting other locations.

Option A is incorrect because geofencing does not primarily enforce time-based application access restrictions.

Option B is incorrect because content inspection and web filtering are separate security functions.

Option C is incorrect because endpoint data encryption is unrelated to geographical connection restrictions.

Additionally, FortiSASE supports regional compliance rules that prioritize permitted POPs or on-premises gateways for users originating from specified regions. These routing preferences are distinct from geofencing ' s connection admission controls.

The exhibit demonstrates the SD-WAN cascade interface functionality, which propagates a failure detected on monitored WAN links to a designated physical interface.

The configuration includes:

config system sdwan

set fail-detect enable

set fail-alert-interfaces " port5 "

Both configured performance SLAs also enable update-cascade-interface , allowing the SD-WAN health-monitoring subsystem to control the state of the designated alert interface.

Option B is correct because FortiGate restores port5 when at least one monitored SD-WAN member is alive. When all monitored members fail, FortiGate administratively brings port5 down. Once an eligible member recovers, FortiGate brings the interface back up.

This behavior allows downstream network equipment to detect a loss of WAN connectivity even when the local Ethernet link would otherwise remain operational.

Option A is incorrect because the configuration does not specify sending notification messages through port5 whenever an individual member fails.

Option C reverses the expected behavior. Port5 is brought down, not up, when all monitored SD-WAN members fail.

Option D is incorrect because fail-alert-interfaces controls interface state rather than functioning as a dedicated notification transport.

The cascade interface mechanism is particularly useful when an alternative network device must assume traffic forwarding following a complete SD-WAN connectivity failure.

BGP on loopback separates routing adjacency establishment from individual IPsec tunnel interface addresses. Combined with Dynamic BGP, it enables scalable SD-WAN overlays and dynamic spoke-to-spoke routing relationships.

Option A is correct for the intended reference design because enabling net-device on a spoke supports dedicated tunnel-interface handling for IPsec connections and dynamically created ADVPN shortcuts. This configuration appears in Fortinet ' s overlay provisioning examples.

Option C is correct because the spoke ' s localid supplies an identifiable IKE identity that the hub can use when authenticating and matching IPsec peers. It is particularly useful where multiple spokes share a hub ' s dial-up IPsec configuration or the hub requires specific peer identities.

Option B is incorrect because the hub normally acts as the dynamic IPsec dial-up responder, rather than being configured as a static tunnel endpoint for every spoke.

Option D is not a fundamental requirement of BGP-on-loopback routing. IKE mode configuration can distribute tunnel addresses, but loopback-based BGP does not inherently require IP addresses on each IPsec overlay.

An important implementation distinction is that net-device behavior can vary by FortiOS release and reference topology. Therefore, the actual production configuration should follow the selected FortiOS 7.6 deployment template rather than treating this combination as universal.