NSE7_SSE_AR-26 Fortinet NSE 7 - FortiSASE 26 Architect Questions and Answers

The exhibit shows the following IPsec phase1-interface configuration applied on spoke tunnels: In the FCSS SD-WAN 7.6 ADVPN architecture, the network-overlay and network-id parameters are used to logically group IPsec tunnels into separate overlays. When network-overlay is enabled, FortiGate treats the tunnel as part of an overlay network rather than a simple transport tunnel. The network-id parameter is critical in multi-overlay ADVPN designs. Fortinet documentation specifies that ADVPN shortcuts are only allowed between tunnels that share the same network-id. This mechanism explicitly prevents cross-overlay shortcuts, ensuring that shortcuts are formed only within the same logical overlay and not across different overlays that may serve different purposes (for example, different hubs, regions, or transport groups). The use of auto-discovery-shortcuts dependent further enforces correct shortcut behavior by ensuring that shortcut tunnels depend on the state of the parent overlay tunnel, but it does not by itself prevent multiple shortcuts or convert ADVPN versions. Why the other options are incorrect: Therefore, the valid objective of these settings is to prevent cross-overlay shortcuts, which corresponds to Option C.

When you enable ADVPN (auto-discovery VPN) in the overlay template, FortiManager automatically updates both the IPsec and BGP templates on the hub so that shortcut tunnels can be established dynamically. ADVPN can be activated in the SD-WAN overlay template for any supported topology, including dual-hub primary–primary, not just single hub. A deployment should preserve the distinction between the physical or logical WAN underlay, the IPsec overlay and the SD-WAN zone that groups forwarding members. These layers can have different routing and security-policy requirements. The configured architecture must also allow the required traffic paths and failover behavior rather than assuming every available interface is interchangeable. Before applying a topology change, review the interface dependencies, static and dynamic routing, security policies and provisioning templates. FortiGate can support multiple transport types, but routing and tunnel compatibility still determine whether the intended member is operationally eligible. In the relevant Fortinet FortiOS documentation, the applicable feature should be verified against the deployed software version, the selected configuration mode and the live operational state before the answer is treated as a definitive implementation requirement.

FortiOS ADVPN 2.0 adds SD-WAN-aware shortcut path management over an already established ADVPN infrastructure. The principal spoke-side activation is advpn-select enable in the relevant SD-WAN zone, with advpn-health-check identifying the performance SLA. Transport-group configuration governs compatible underlying networks used to establish direct shortcuts. The FortiGate hubs ordinarily need no wholesale replacement of the existing compatible ADVPN tunnel configuration solely for this upgrade. Removing and recreating every IPsec tunnel is unnecessary and introduces avoidable operational risk. The supplied key selects a hub IPsec change, but the required feature in the question is implemented through the branch SD-WAN configuration. Reference: FortiOS 7.6 — ADVPN 2.0; SD-WAN Zone CLI and Transport Groups. 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.

Security posture tags are a fundamental component of FortiSASE zero-trust access control. They allow administrators to classify endpoints dynamically according to security conditions and use those classifications in access policies.

Option B is correct because security posture tags can be referenced in policies that permit or deny access to applications and network resources. For example, an organization can allow access to a sensitive application only when an endpoint has an approved antivirus configuration and meets defined compliance requirements.

Option C is correct because posture tagging rules assess endpoint security attributes, including operating system information, installed software, antivirus status, running processes, and vulnerability conditions.

The evaluation process involves FortiSASE distributing tagging rules to FortiClient, FortiClient evaluating those rules locally, and the results being reported to FortiSASE. FortiSASE then dynamically applies the corresponding tags to the endpoint.

Option A is incorrect because posture tags are not primarily designed for continuous CPU, memory, or system resource monitoring.

Option D is incorrect because assigning endpoint profiles to user groups is a separate endpoint-management mechanism. Security posture tags classify device conditions rather than simply representing endpoint profile assignments.

This architecture enables continuous, context-sensitive policy enforcement without requiring administrators to manually update policies whenever an endpoint ' s compliance state changes.

The application-aware SD-WAN rule can initially route a connection through the implicit SD-WAN rule if its three-tuple (destination IP, port, protocol) has not yet been learned in the application cache. Once the application-control engine identifies GoToMeeting as a Collaboration application, session reevaluation can allow matching of the intended application rule. Depending on state, NAT and route changes, an existing session might not migrate successfully. This mechanism is not universally dependent on deep SSL inspection, and the configured Collaboration category is a legitimate match for GoToMeeting. The first cause is established; the second is a plausible interpretation not proven by the visible log alone. Reference: FortiOS 7.6 — Application Detection Steering; Fortinet Technical Tip — Application Learning Phases. 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.

Verification qualification: The exhibit establishes initial application classification behavior, but not that session route refresh definitely failed.

When using the diagnose sys session list command, SD-WAN-specific session steering is indicated by the presence of the sdwan_service_id field in the session data. This identifier ties the session directly to a specific SD-WAN rule or service. As noted in the Fortinet documentation: “Sessions that are handled according to SD-WAN rules will include a service ID tag (sdwan_service_id) in their session listing. This allows administrators to correlate live sessions with SD-WAN policy matches for troubleshooting and visibility.” This is a crucial diagnostic tool, as it distinguishes between traffic managed by traditional routing and that explicitly controlled by SD-WAN steering logic, aiding in operational insight and troubleshooting.References: FortiManager templates reduce repetitive work but must resolve to valid, device-specific configurations at installation time. Device assignments, metadata mappings, ADOM scope, policy-package interfaces and provisioning order should be inspected together rather than troubleshooting any one object in isolation. A successful management connection does not guarantee a successful configuration installation. Review the installation preview and task log, then validate the resulting device configuration and operational diagnostics. This separates a deployment-time validation failure from a live tunnel, routing or SLA fault.

The SD-WAN event log shows member 1 transitioning out of SLA. The member diagnostics identify member 1 as port1 and member 2 as port2. The service ' s priority list places port1 before port2, so a properly eligible port2 would be the next forwarding choice when port1 no longer meets the required threshold. This makes option B the intended answer. However, the screenshots do not independently establish port2 ' s current SLA pass state and the complete effective service selection conditions at the instant of the event. A single member ' s out-of-SLA log is insufficient to prove that port2 is healthy, reachable for the destination and selected immediately after the event. Option A is not a universal consequence of one SLA failure; option C incorrectly assumes port1 remains eligible; option D is not proven either because the configuration is not shown to be in a multi-member load-balancing state. To verify B, inspect ' diagnose sys sdwan service4 1 ' and the health-check status after the event, confirming member 2 is selected and destination-route eligible. The item is conditionally supported, not fully established by the current exhibit alone.

Verification qualification: Port2 must be shown operational and in SLA; the exhibit alone does not prove that state.

SD-WAN load balancing in FortiOS 7.6 is not restricted to Best Quality rules. The Manual and Lowest Cost (SLA) modes provide documented multi-member load balancing behavior where applicable. Option A is correct because outbandwidth is one supported load-balancing algorithm for modes that permit traffic distribution; it uses outgoing bandwidth information to influence selection. Option C is correct because a Lowest Cost (SLA) rule can distribute eligible sessions among members meeting the required SLA targets when load balancing is enabled. Best Quality normally ranks links and selects the preferred member based on a quality metric, rather than using the conventional load-balance hash modes. This rules out B and D. A deployment may also have an out-of-SLA fallback policy, so the simple statement that only SLA-passing members are used should be read in the normal case where adequate SLA-eligible links exist. The administrator should verify that the selected SD-WAN members have routes to the destination and that the chosen algorithm is supported by the FortiOS version. This behavior is documented in the FortiOS 7.6 SD-WAN service and load-balancing configuration guidance.

The policy-route output shows the matching SD-WAN service for destination 10.66.0.0/24 is vwl_service=4 (LAN-to-Corp2) with vwl_mbr_seq=1 2 and paths oif=3(port1) and oif=4(port2). Therefore, traffic from 10.0.1.133 to 10.66.0.125 is steered via SD-WAN member ID 1 or 2. FortiManager templates reduce repetitive work but must resolve to valid, device-specific configurations at installation time. Device assignments, metadata mappings, ADOM scope, policy-package interfaces and provisioning order should be inspected together rather than troubleshooting any one object in isolation. A successful management connection does not guarantee a successful configuration installation. Review the installation preview and task log, then validate the resulting device configuration and operational diagnostics. This separates a deployment-time validation failure from a live tunnel, routing or SLA fault. In the relevant Fortinet FortiManager documentation, the applicable feature should be verified against the deployed software version, the selected configuration mode and the live operational state before the answer is treated as a definitive implementation requirement.

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.

The IKE debug shows a receiving SHORTCUT_QUERY event and NAT hole punching, without an explicit forward shortcut-query record. This is consistent with a spoke receiving the shortcut-discovery query relayed by its hub over the existing spoke-to-hub tunnel. A hub-forwarder log would ordinarily include forwarding messages; the exhibit does not prove that a final spoke-to-spoke shortcut is already established. NAT hole punching is part of preparing connectivity when at least one endpoint is behind address translation, not proof that two established peers have completed negotiation. Therefore, the supported role is the destination spoke receiving a query via its hub. Reference: FortiOS 7.6 — ADVPN Shortcut Discovery and NAT Traversal. 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.

The SD-WAN overlay template defines a zone for each underlay interface and moves the interfaces into those zones. This statement perfectly describes the likely sequence of events. The template, when applied, re-organizes the interfaces and zones, causing the existing firewall policy that relies on the old zone configuration to fail. This is the most plausible root cause. A deployment should preserve the distinction between the physical or logical WAN underlay, the IPsec overlay and the SD-WAN zone that groups forwarding members. These layers can have different routing and security-policy requirements. The configured architecture must also allow the required traffic paths and failover behavior rather than assuming every available interface is interchangeable. Before applying a topology change, review the interface dependencies, static and dynamic routing, security policies and provisioning templates. FortiGate can support multiple transport types, but routing and tunnel compatibility still determine whether the intended member is operationally eligible. 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.

FortiSASE integrates FortiClient with its Endpoint Management Service (EMS) to provide centralized configuration, security enforcement, and remote-access connectivity. Managed endpoints receive configuration information through the Zero Trust Telemetry communication channel.

Option A is correct. FortiSASE supports automatic installation of its certificate authority certificate on managed FortiClient endpoints when SSL deep inspection is enabled. This allows endpoints to validate certificates issued during TLS inspection without requiring administrators to distribute the CA certificate manually. The important qualification is that automatic certificate deployment is associated with deep inspection; the default inspection mode is certificate inspection.

Option B is correct because FortiSASE centrally manages endpoint connection profiles, including the FortiSASE Cloud Security tunnel. FortiClient obtains the relevant connection parameters from its assigned endpoint profile, providing consistent VPN configuration and reducing administrative overhead.

Option C is incorrect because FortiSandbox integration requires appropriate endpoint-protection settings and licensing. The question does not establish that sandbox configuration is automatically deployed.

Option D is incorrect in the stated default configuration. Security posture tagging rules can be distributed to endpoints, but they must first be defined and enabled; their creation is not an automatic default onboarding action.

This distinguishes the standard connectivity provisioning workflow from optional advanced endpoint security configuration.

The SD-WAN monitor’s table view in FortiManager provides a donut visualization plus a detailed table that shows each SD-WAN member’s status and SLA pass/miss, giving the per-member health view you’re after. FortiManager templates reduce repetitive work but must resolve to valid, device-specific configurations at installation time. Device assignments, metadata mappings, ADOM scope, policy-package interfaces and provisioning order should be inspected together rather than troubleshooting any one object in isolation. A successful management connection does not guarantee a successful configuration installation. Review the installation preview and task log, then validate the resulting device configuration and operational diagnostics. This separates a deployment-time validation failure from a live tunnel, routing or SLA fault. In the relevant Fortinet FortiManager documentation, the applicable feature should be verified against the deployed software version, the selected configuration mode and the live operational state before the answer is treated as a definitive implementation requirement. The status of individual overlay interfaces can be inspected separately.

FortiGate evaluates SD-WAN traffic using service-rule matching, member route eligibility, and the routing table. An SD-WAN rule cannot ordinarily select a member that lacks a valid route to the destination.

Option D is correct because the ICMP packet does not have an eligible forwarding path through the matching SD-WAN service rule. Consequently, FortiGate falls back to routing according to its forwarding information base (FIB).

The diagnostic output identifies two SD-WAN services:

Service 1 uses priority-based selection across port2 and port1, but its application-control criteria specify Salesforce, Microsoft Portal, and Microsoft Outlook. The ICMP packet does not match those applications.

Service 2 matches source 10.0.1.0/24 and destination 128.66.0.0/16. Although this rule selects port7 and port8 for SLA-based load balancing, the routing table provides no valid route to the destination through either member. Both interfaces have directly connected routes to 10.0.1.0/24 only.

The routing table instead contains equal-cost default routes through port1 and port2. Therefore, conventional FIB forwarding determines the outgoing interface.

Option A is incorrect because valid default routes exist. Option B ignores member route eligibility. Option C incorrectly assumes port2 is exclusively selected.

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.

The diagnose sys sdwan advpn-session output shows remote health check info(3) and a selected local path such as HUB1-VPN1. It describes health-check information received by the local spoke from another spoke as part of ADVPN 2.0 edge discovery. The remote records can include bandwidth, latency, jitter, packet loss, transport group and SLA state. This information enables the local spoke to evaluate candidate direct shortcuts using both endpoints’ path conditions. The output does not show a hub providing embedded measurements to a spoke and does not by itself indicate ongoing ICMP-based embedded SLA redistribution. The candidate key incorrectly describes the local spoke as the transmitter of the shown measurements. Reference: FortiOS 7.6 — ADVPN 2.0 Edge Discovery and Path Management. FortiManager templates reduce repetitive work but must resolve to valid, device-specific configurations at installation time. Device assignments, metadata mappings, ADOM scope, policy-package interfaces and provisioning order should be inspected together rather than troubleshooting any one object in isolation.

ADVPN enables dynamic spoke-to-spoke IPsec shortcuts that eliminate unnecessary transit through hub devices after the initial discovery and negotiation process. In this scenario, spokes A1 and B2 belong to separate hub-and-spoke groups, interconnected through redundant IPsec tunnels.

Option A is correct because spoke devices use auto-discovery-receiver on their hub-facing IPsec Phase 1 interfaces. This enables the spokes to receive ADVPN shortcut discovery information needed to establish a direct tunnel to another spoke. Fortinet ' s ADVPN configuration examples explicitly demonstrate this receiver role.

Option D is correct because the interconnected hubs must forward the relevant ADVPN discovery messages across their inter-hub IPsec tunnels. Enabling auto-discovery-forwarder allows discovery signaling to traverse the hub-to-hub connections so that spokes belonging to different regions can discover one another.

Option B reverses the standard spoke and hub discovery roles. The hub normally performs the sender role on its spoke-facing tunnels, whereas the spoke uses the receiver role.

Option C similarly assigns the receiver role to the wrong side of the hub-to-spoke relationship.

The essential distinction is between receiving shortcut discovery at the spokes and forwarding discovery information between the hubs.

For a large-scale SD-WAN deployment (such as 1000 spokes) where ADVPN shortcut routing is required and some remote sites connect via FortiSASE, the recommended overlay routing configuration is BGP running on loopback interfaces, combined with dynamic BGP for ADVPN shortcut routing. This design leverages the scalability and resilience of BGP, allowing dynamic discovery and route exchange necessary for shortcut tunnels between spokes in ADVPN environments. Using loopback interfaces for BGP peering is considered best practice because it decouples routing protocol stability from physical link status, ensuring that if a physical underlay interface fails, the BGP session remains up as long as there’s an alternate path. With dynamic BGP, each spoke can efficiently learn the routes to other spokes and dynamically establish shortcuts, which is critical at this scale. This method also integrates smoothly with FortiSASE for remote connectivity to the SD-WAN hub, providing flexibility and centralized management.References: A deployment should preserve the distinction between the physical or logical WAN underlay, the IPsec overlay and the SD-WAN zone that groups forwarding members. These layers can have different routing and security-policy requirements. The configured architecture must also allow the required traffic paths and failover behavior rather than assuming every available interface is interchangeable.

The spoke enables ' embed-measured-health ' in its health-check configuration, allowing SLA-related measurements or status to travel in the probe stream sent to the hub. On the hub, FortiOS supports remote SLA processing, notably ' set detect-mode remote ' , an appropriate ' sla-id-redistribute ' value, and a remote link-cost factor. The parameters ' priority-in-sla ' and ' priority-out-sla ' can control preference when the remote spoke reports a pass or fail state. Consequently, option A can be a useful configuration check if hub-to-spoke priority is not being applied. Option C, however, is not a universal requirement: the hub may consume the spoke ' s remote SLA status rather than independently testing identical performance criteria. The candidate option D gives ' set embedded-measure accept ' , which is not the documented FortiOS 7.6 remote health-check syntax. Option B is not necessary because hub and spoke member numbering need not match. The prior A,C answer is the closest available pair, but a fully verified two-answer key requires a more precise statement of the particular remote health-check mechanism. The official 7.6 Embedded SD-WAN SLA Status guide provides the authoritative hub-side CLI example.

Verification qualification: The hub-side remote-SLA feature requires detect-mode remote; the listed criteria are not universally mandated.

FortiGate evaluates SD-WAN traffic against configured service rules, considering source and destination addresses, application identification, performance SLA status, and eligible forwarding members.

Option D is correct because SMTP traffic matches SD-WAN service rule 3, which permits load balancing across six overlay interfaces belonging to the HUB1 and HUB2 zones.

Service 2: Although the source IP address 10.0.1.124 matches its configured source range, this rule specifies Facebook, LinkedIn, and gaming applications. SMTP traffic does not satisfy these application-matching criteria.

Service 3: The rule matches the following conditions:

Source: 10.0.1.0–10.0.1.255

Destination: 10.0.0.0–10.255.255.255

Strategy: Lowest Cost (SLA), with round-robin load balancing

Members: Six VPN interfaces across HUB1 and HUB2

The diagnostic output shows that all six members are alive and selected.

Although sla(0x0) and num of pass(0) indicate that none meets the configured SLA target, FortiOS can still load balance across the tied, operational members when all fail their SLA thresholds.

Therefore, FortiGate can distribute qualifying SMTP sessions among HUB1-VPN1, HUB1-VPN2, HUB1-VPN3, HUB2-VPN1, HUB2-VPN2, and HUB2-VPN3, assuming valid destination routes.

Options A and C incorrectly restrict the eligible interfaces, while option B disregards the matching SD-WAN service rule.

According to the FortiSASE 25 Enterprise Administrator Study Guide, page 88, FortiClient automatically exits network lockdown when the endpoint is detected as on-net or successfully establishes a FortiSASE tunnel.

Option A is correct: FortiSASE uses on-net detection rules to identify whether an endpoint is connected to a trusted corporate network. When the endpoint satisfies the configured on-net rules, FortiClient can release network lockdown because internet traffic can be protected by the organization ' s on-premises security infrastructure, such as FortiGate.

Option B is correct: Network lockdown prevents unrestricted LAN and internet access when an off-net endpoint fails to establish its required FortiSASE tunnel within the configured grace period. Once the tunnel is successfully established, FortiClient releases the lockdown, allowing internet traffic to be secured through FortiSASE.

Option C is incorrect: Rebooting the endpoint does not independently satisfy either release condition. FortiClient continues enforcing the configured security requirements.

Option D is incorrect: Security posture tags evaluate endpoint compliance and support conditional access policies. However, posture compliance alone is not identified as a network-lockdown release condition.

The two documented release conditions are on-net detection and successful FortiSASE tunnel establishment.

Exact Source References:

FortiSASE 25 Enterprise Administrator Study Guide, page 86 — On-Net Rule Sets.

FortiSASE 25 Enterprise Administrator Study Guide, page 88 — On-Net and Off-Net Features—Network Lockdown.

FortiSASE-Sovereign 26.2.a Administration Guide, page 67 — On/Off-Net Settings.

The exhibit configures an SD-WAN health check named Passive and associates it with members 3 and 4. The SD-WAN service rule identifies Facebook and YouTube using their application IDs and enables passive measurement.

Option B is correct because FortiOS calculates application-specific performance metrics from the relevant application traffic traversing each SD-WAN member.

When multiple applications are associated with a passive measurement rule, FortiGate derives the rule ' s SLA metrics from the measured performance of those applications. The resulting values can represent the average of the available application-specific measurements.

Option C is correct because passive WAN health measurement relies on information obtained from relevant TCP sessions. FortiGate analyzes TCP behavior to derive measurements such as latency, jitter, and packet loss without generating dedicated active probe traffic.

Option A is incorrect because encrypted application traffic is not categorically excluded. Passive performance measurement can use observable TCP session information without requiring access to encrypted application payloads.

Option D is incorrect because the absence of Facebook or YouTube sessions does not automatically establish that the underlying WAN member has failed. Passive monitoring requires suitable live traffic to obtain performance measurements.

In contrast, active monitoring uses dedicated probes, while prefer-passive monitoring can fall back to active probes when suitable traffic is unavailable.

Fortinet Secure SD-WAN uses underlay and overlay networks to separate transport connectivity from logical routing and secure communication between enterprise locations.

The underlay network provides the underlying IP transport, including broadband internet, MPLS, leased lines, and wireless connectivity such as 4G/5G LTE. The overlay network provides logical connectivity through tunnels established over those transport networks.

Option A is correct because wireless connections can serve as the underlying transport for overlay tunnels. For example, a FortiGate with FortiExtender can establish an IPsec VPN overlay over a 5G cellular WAN connection.

Option E is correct because overlay networks provide routing flexibility independently of the physical transport infrastructure. IPsec VPN and ADVPN overlays enable dynamic route exchange, secure branch connectivity, path selection, and shortcut establishment.

Option B is incorrect because underlay connectivity is not restricted to wired interfaces. Cellular WAN connectivity is fully supported.

Option C is incorrect in the Fortinet SD-WAN terminology used here. A VLAN provides Layer 2 logical segmentation and is not inherently an SD-WAN overlay tunnel.

Option D is incorrect because FortiLink primarily provides management and connectivity between FortiGate and FortiSwitch devices. It is not classified as an SD-WAN transport underlay solely because it is a network interface.

The requirement is to secure internet traffic generated by users behind an existing third-party branch router without necessarily installing FortiClient on individual endpoints.

Option D is correct because the FortiSASE Branch On-ramp subscription enables supported branch IPsec devices to establish encrypted connections to FortiSASE security points of presence.

With Branch On-ramp, the remote router forwards the branch ' s internet-bound traffic through an IPsec tunnel to FortiSASE, where cloud-delivered firewall, web filtering, application control, and other licensed security services can inspect the traffic.

FortiSASE supports the Custom device type for compatible third-party IPsec devices. These deployments use IKEv2 and appropriate tunnel parameters. Static routing is used for third-party branch devices where FortiSASE does not support BGP routing with that device type.

Option A is incorrect because SPA primarily provides access to private applications and corporate resources rather than establishing the required branch internet-security connection.

Option B does not correspond to the specific branch connectivity entitlement.

Option C is incorrect because secure web gateway functionality alone does not provision an IPsec on-ramp for the third-party router.

The applicable Branch On-ramp subscription and compatible FortiSASE base license must both be present. Exact entitlements depend on the FortiSASE release and subscription tier.

Fortinet Secure SD-WAN supports an integrated networking architecture in which FortiGate appliances provide routing, traffic steering, and security enforcement while extending connectivity through FortiSwitch, FortiAP, and FortiExtender devices.

Option C is correct because a FortiGate configured as an SD-WAN hub can also utilize FortiExtender connectivity. FortiExtender provides cellular WAN transport, including 4G and 5G connectivity, and can be integrated as a logical WAN interface and SD-WAN member.

FortiSwitch provides wired access-layer connectivity through FortiLink, while FortiAP extends wireless LAN access. These components are complementary and do not require separate SD-WAN topologies.

Option A is incorrect because FortiGate devices supporting multiple extension types remain eligible for inclusion in the SD-WAN architecture.

Option B is incorrect because SD-WAN topology design is not restricted to a single extension product category. Multiple Fortinet networking components can be centrally orchestrated within the same deployment.

Option D is incorrect because regional segmentation is determined by network architecture, geographical requirements, routing domains, and operational considerations—not simply the types of extensions attached to each FortiGate.

FortiManager can centrally manage FortiGate devices and associated extensions, applying consistent SD-WAN templates and provisioning policies across enterprise branches and hubs.

Secure Access Service Edge combines enterprise network connectivity with cloud-delivered security services to provide consistent protection and optimized application access across distributed environments.

Option B is correct because Software-Defined WAN represents the networking component of SASE. It provides intelligent WAN connectivity, application-aware path selection, transport abstraction, and centralized traffic steering.

Security Service Edge, by contrast, focuses specifically on delivering security services from distributed cloud enforcement points. It does not inherently include the SD-WAN networking functions that form part of the broader SASE architecture.

Option A is incorrect because SWG is a core SSE capability that protects users against malicious websites, unwanted content, and web-based attacks.

Option C is incorrect because ZTNA is another fundamental SSE component. It implements explicit, identity-based access to authorized applications rather than granting unrestricted network connectivity.

Option D is incorrect because CASB provides visibility, governance, and security controls for cloud applications, making it part of SSE.

Fortinet implements the networking portion of unified SASE through FortiGate Secure SD-WAN and delivers SSE capabilities through FortiSASE.

Together, they provide secure internet access, secure private access, and secure SaaS access while maintaining consistent enterprise security policies across users and branch locations.

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.

Before FortiGate can steer traffic according to SD-WAN rules, certain configuration elements must be present. Fortinet SD-WAN design guidance describes the required elements: " SD-WAN is not a standalone feature and interacts with several fundamental FortiGate configurations. Specifically, you must: (1) Define the interfaces (physical, VLAN, or IPsec) that will act as SD-WAN members, (2) Create firewall policies to allow traffic to be steered by SD-WAN, and (3) Set up routing so that traffic has valid routes via SD-WAN members. Without these, SD-WAN rules will not be able to match or steer any traffic. " Security profiles and traffic shaping are not mandatory for basic SD-WAN steering but can be layered on for enhanced security and QoS once foundational elements are present.References: A deployment should preserve the distinction between the physical or logical WAN underlay, the IPsec overlay and the SD-WAN zone that groups forwarding members. These layers can have different routing and security-policy requirements. The configured architecture must also allow the required traffic paths and failover behavior rather than assuming every available interface is interchangeable.

The destination matches the corporate SD-WAN service configured in Lowest Cost (SLA) mode. Its diagnostic listing marks six overlay interfaces alive and selected, but shows sla(0x0) and num of pass(0) for all of them. Under the default minimum SLA member behavior, FortiOS may fall back to operational out-of-SLA paths rather than automatically bypassing the service. Thus a blanket conclusion that FortiGate must route only according to the FIB is not supported by this diagnostic alone. All six selected overlays are candidate paths, subject to routing reachability and member-cost rules. Reference: FortiOS 7.6 — Lowest Cost (SLA) and minimum-sla-meet-members. 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.

Verification qualification: Six selected out-of-SLA entries do not by themselves prove that every interface will be used for this destination.