NSE5_SSE_AD-7.6 Premium File
- 54 Questions & Answers
- Last Update: Nov 5, 2026
Before changing production settings, an engineer reviews the symptoms. A SASE user authenticates and has a private route to a branch database but the FortiGate hub denies the connection. Which evidence is most useful?
Inspect hub policy match, source pool, destination, service and corresponding traffic logs. This inspection targets FortiSASE user policy and hub firewall allow rather than a different configuration issue. The corrective action is: Keep the overlay and add an approved narrowly scoped FortiGate firewall policy for the intended user network and database service. Expected evidence: A pilot query succeeds only for the authorized user group and approved service.
Inspect BGP neighbor state, advertised routes, route filters and firewall permission. This is useful when diagnosing SASE PoP as overlay spoke BGP route. Instead, inspect hub policy match, source pool, destination, service and corresponding traffic logs.
Inspect local routes, FortiClient tunnel state, branch edge path and SASE session attribution. This is useful when diagnosing Site-based SASE and endpoint agent double steering. Instead, inspect hub policy match, source pool, destination, service and corresponding traffic logs.
Inspect both tunnels, BGP route preference, hub health and session path. This is useful when diagnosing SD-WAN private access dual hub failover. Instead, inspect hub policy match, source pool, destination, service and corresponding traffic logs.
A deployment review finds this gap. A remote branch has a supported IPsec-capable edge appliance but no FortiGate, and owners want its internet traffic inspected by FortiSASE. What is the most targeted next configuration step?
Evaluate supported FortiSASE Branch On-ramp IPsec integration and configure only approved compatible edge settings. Branch On-ramp can connect eligible site-based networks to cloud security using an IPsec capable edge. Expected evidence: The branch establishes its approved on-ramp and test internet traffic is logged under the intended cloud policy. Key limit: The compatibility and licensing of Branch On-ramp must be confirmed for the specific tenant.
Separate the approved public secure-internet path from private overlay routes and validate source security policies. This could apply to the separate issue FortiSASE internet traffic hairpin after SPA: A remote-user rollout routes both private datacenter traffic and public browsing through the corporate SD-WAN hub, although security owners intended FortiSASE PoP internet inspection. For Branch on-ramp for non-FortiGate site, the directly relevant action is: Evaluate supported FortiSASE Branch On-ramp IPsec integration and configure only approved compatible edge settings.
Inspect and repair the supported VXLAN-over-IPsec LAN extension parameters and associated gateway/interface configuration. This could apply to the separate issue FortiGate secure-edge VXLAN overlay health: A site-based FortiGate LAN extension shows an active base IPsec tunnel, yet user traffic never reaches the FortiSASE inspection PoP because the VXLAN overlay is misconfigured. For Branch on-ramp for non-FortiGate site, the directly relevant action is: Evaluate supported FortiSASE Branch On-ramp IPsec integration and configure only approved compatible edge settings.
Choose and validate the intended supported client-versus-site traffic path for that user cohort before enabling both mechanisms. This could apply to the separate issue Site-based SASE and endpoint agent double steering: A branch sends user internet traffic to FortiSASE through a secure-edge appliance, but managed laptops also install a full tunnel client and suffer routing loops. For Branch on-ramp for non-FortiGate site, the directly relevant action is: Evaluate supported FortiSASE Branch On-ramp IPsec integration and configure only approved compatible edge settings.
The recommended change has been applied. A remote branch has a supported IPsec-capable edge appliance but no FortiGate, and owners want its internet traffic inspected by FortiSASE. Which observation best verifies the intended outcome?
The branch establishes its approved on-ramp and test internet traffic is logged under the intended cloud policy. This is the directly relevant check for Branch on-ramp for non-FortiGate site. It confirms the required step: Evaluate supported FortiSASE Branch On-ramp IPsec integration and configure only approved compatible edge settings. The operating principle is: Branch On-ramp can connect eligible site-based networks to cloud security using an IPsec capable edge.
Wired pilot users' internet sessions reach the cloud service under the correct tenant security rules. This would validate a different scenario, FortiGate secure-edge VXLAN overlay health, where A site-based FortiGate LAN extension shows an active base IPsec tunnel, yet user traffic never reaches the FortiSASE inspection PoP because the VXLAN overlay is misconfigured. The current case needs evidence for Branch on-ramp for non-FortiGate site.
Public browsing exits through cloud inspection while approved private prefixes traverse the datacenter overlay. This would validate a different scenario, FortiSASE internet traffic hairpin after SPA, where A remote-user rollout routes both private datacenter traffic and public browsing through the corporate SD-WAN hub, although security owners intended FortiSASE PoP internet inspection. The current case needs evidence for Branch on-ramp for non-FortiGate site.
The device becomes eligible for approved secure-edge onboarding after required entitlement and compatibility checks. This would validate a different scenario, Site-based FortiGate license missing, where A branch FortiGate supports normal SD-WAN but the FortiSASE secure-edge/LAN-extension integration option is unavailable in tenant settings. The current case needs evidence for Branch on-ramp for non-FortiGate site.
An architect reviews the platform behavior behind this incident. A remote branch has a supported IPsec-capable edge appliance but no FortiGate, and owners want its internet traffic inspected by FortiSASE. Which explanation applies?
Branch On-ramp can connect eligible site-based networks to cloud security using an IPsec capable edge. This explains Branch on-ramp for non-FortiGate site in the given environment. The implementation decision is: Evaluate supported FortiSASE Branch On-ramp IPsec integration and configure only approved compatible edge settings. Confirm it with: The branch establishes its approved on-ramp and test internet traffic is logged under the intended cloud policy.
Traffic purpose and prefix routing distinguish FortiSASE SIA from SD-WAN-backed SPA. That concept concerns FortiSASE internet traffic hairpin after SPA, not the mechanism needed for Branch on-ramp for non-FortiGate site. The relevant principle is: Branch On-ramp can connect eligible site-based networks to cloud security using an IPsec capable edge.
Site-based LAN extension and endpoint agent connections are distinct ingress models that need coordinated routing. That concept concerns Site-based SASE and endpoint agent double steering, not the mechanism needed for Branch on-ramp for non-FortiGate site. The relevant principle is: Branch On-ramp can connect eligible site-based networks to cloud security using an IPsec capable edge.
A valid FortiGate SD-WAN configuration is not necessarily licensed for FortiSASE LAN extension. That concept concerns Site-based FortiGate license missing, not the mechanism needed for Branch on-ramp for non-FortiGate site. The relevant principle is: Branch On-ramp can connect eligible site-based networks to cloud security using an IPsec capable edge.
A support analyst is collecting data for this scenario. A remote branch has a supported IPsec-capable edge appliance but no FortiGate, and owners want its internet traffic inspected by FortiSASE. Which diagnostic check is most targeted?
Inspect edge compatibility, tunnel endpoints, routing, allowed prefixes and SASE logs. This inspection targets Branch on-ramp for non-FortiGate site rather than a different configuration issue. The corrective action is: Evaluate supported FortiSASE Branch On-ramp IPsec integration and configure only approved compatible edge settings. Expected evidence: The branch establishes its approved on-ramp and test internet traffic is logged under the intended cloud policy.
Inspect tunnel and VXLAN interfaces, layer-2 neighbor behavior and cloud ingress logs. This is useful when diagnosing FortiGate secure-edge VXLAN overlay health. Instead, inspect edge compatibility, tunnel endpoints, routing, allowed prefixes and sase logs.
Inspect device series, FortiOS version, secure-edge subscription and FortiSASE device inventory. This is useful when diagnosing Site-based FortiGate license missing. Instead, inspect edge compatibility, tunnel endpoints, routing, allowed prefixes and sase logs.
Inspect destination routes, PoP egress, hub tunnel usage and traffic logs. This is useful when diagnosing FortiSASE internet traffic hairpin after SPA. Instead, inspect edge compatibility, tunnel endpoints, routing, allowed prefixes and sase logs.
A Fortinet administrator must address this operational problem. A branch FortiGate supports normal SD-WAN but the FortiSASE secure-edge/LAN-extension integration option is unavailable in tenant settings. Which response best resolves it?
Confirm the separate supported FortiSASE secure-edge subscription and tenant feature eligibility for the specific FortiGate. A valid FortiGate SD-WAN configuration is not necessarily licensed for FortiSASE LAN extension. Expected evidence: The device becomes eligible for approved secure-edge onboarding after required entitlement and compatibility checks. Key limit: A FortiGate support subscription is not proof of a separate FortiSASE edge entitlement.
Keep the overlay and add an approved narrowly scoped FortiGate firewall policy for the intended user network and database service. This could apply to the separate issue FortiSASE user policy and hub firewall allow: A SASE user authenticates and has a private route to a branch database but the FortiGate hub denies the connection. For Site-based FortiGate license missing, the directly relevant action is: Confirm the separate supported FortiSASE secure-edge subscription and tenant feature eligibility for the specific FortiGate.
Evaluate supported FortiSASE Branch On-ramp IPsec integration and configure only approved compatible edge settings. This could apply to the separate issue Branch on-ramp for non-FortiGate site: A remote branch has a supported IPsec-capable edge appliance but no FortiGate, and owners want its internet traffic inspected by FortiSASE. For Site-based FortiGate license missing, the directly relevant action is: Confirm the separate supported FortiSASE secure-edge subscription and tenant feature eligibility for the specific FortiGate.
Choose and validate the intended supported client-versus-site traffic path for that user cohort before enabling both mechanisms. This could apply to the separate issue Site-based SASE and endpoint agent double steering: A branch sends user internet traffic to FortiSASE through a secure-edge appliance, but managed laptops also install a full tunnel client and suffer routing loops. For Site-based FortiGate license missing, the directly relevant action is: Confirm the separate supported FortiSASE secure-edge subscription and tenant feature eligibility for the specific FortiGate.
For this situation, a reviewer needs acceptance evidence. A branch FortiGate supports normal SD-WAN but the FortiSASE secure-edge/LAN-extension integration option is unavailable in tenant settings. Which result most directly demonstrates success?
The device becomes eligible for approved secure-edge onboarding after required entitlement and compatibility checks. This is the directly relevant check for Site-based FortiGate license missing. It confirms the required step: Confirm the separate supported FortiSASE secure-edge subscription and tenant feature eligibility for the specific FortiGate. The operating principle is: A valid FortiGate SD-WAN configuration is not necessarily licensed for FortiSASE LAN extension.
A pilot query succeeds only for the authorized user group and approved service. This would validate a different scenario, FortiSASE user policy and hub firewall allow, where A SASE user authenticates and has a private route to a branch database but the FortiGate hub denies the connection. The current case needs evidence for Site-based FortiGate license missing.
The branch establishes its approved on-ramp and test internet traffic is logged under the intended cloud policy. This would validate a different scenario, Branch on-ramp for non-FortiGate site, where A remote branch has a supported IPsec-capable edge appliance but no FortiGate, and owners want its internet traffic inspected by FortiSASE. The current case needs evidence for Site-based FortiGate license missing.
Pilot laptops use one approved cloud inspection path without duplicated tunnels or recursive proxy behavior. This would validate a different scenario, Site-based SASE and endpoint agent double steering, where A branch sends user internet traffic to FortiSASE through a secure-edge appliance, but managed laptops also install a full tunnel client and suffer routing loops. The current case needs evidence for Site-based FortiGate license missing.
A network administrator must explain the underlying control. A branch FortiGate supports normal SD-WAN but the FortiSASE secure-edge/LAN-extension integration option is unavailable in tenant settings. Which statement is correct?
A valid FortiGate SD-WAN configuration is not necessarily licensed for FortiSASE LAN extension. This explains Site-based FortiGate license missing in the given environment. The implementation decision is: Confirm the separate supported FortiSASE secure-edge subscription and tenant feature eligibility for the specific FortiGate. Confirm it with: The device becomes eligible for approved secure-edge onboarding after required entitlement and compatibility checks.
Branch On-ramp can connect eligible site-based networks to cloud security using an IPsec capable edge. That concept concerns Branch on-ramp for non-FortiGate site, not the mechanism needed for Site-based FortiGate license missing. The relevant principle is: A valid FortiGate SD-WAN configuration is not necessarily licensed for FortiSASE LAN extension.
Site-based LAN extension and endpoint agent connections are distinct ingress models that need coordinated routing. That concept concerns Site-based SASE and endpoint agent double steering, not the mechanism needed for Site-based FortiGate license missing. The relevant principle is: A valid FortiGate SD-WAN configuration is not necessarily licensed for FortiSASE LAN extension.
FortiSASE PoPs can participate as spokes in a FortiGate SD-WAN private-access topology using supported IPsec and routing. That concept concerns FortiSASE secure private access through SD-WAN hubs, not the mechanism needed for Site-based FortiGate license missing. The relevant principle is: A valid FortiGate SD-WAN configuration is not necessarily licensed for FortiSASE LAN extension.
An incident team needs to isolate the root cause. A branch FortiGate supports normal SD-WAN but the FortiSASE secure-edge/LAN-extension integration option is unavailable in tenant settings. Which investigation should be prioritized?
Inspect device series, FortiOS version, secure-edge subscription and FortiSASE device inventory. This inspection targets Site-based FortiGate license missing rather than a different configuration issue. The corrective action is: Confirm the separate supported FortiSASE secure-edge subscription and tenant feature eligibility for the specific FortiGate. Expected evidence: The device becomes eligible for approved secure-edge onboarding after required entitlement and compatibility checks.
Inspect edge compatibility, tunnel endpoints, routing, allowed prefixes and SASE logs. This is useful when diagnosing Branch on-ramp for non-FortiGate site. Instead, inspect device series, fortios version, secure-edge subscription and fortisase device inventory.
Inspect local routes, FortiClient tunnel state, branch edge path and SASE session attribution. This is useful when diagnosing Site-based SASE and endpoint agent double steering. Instead, inspect device series, fortios version, secure-edge subscription and fortisase device inventory.
Inspect hub policy match, source pool, destination, service and corresponding traffic logs. This is useful when diagnosing FortiSASE user policy and hub firewall allow. Instead, inspect device series, fortios version, secure-edge subscription and fortisase device inventory.
A network engineer faces the following FortiSASE or SD-WAN condition. A remote-user rollout routes both private datacenter traffic and public browsing through the corporate SD-WAN hub, although security owners intended FortiSASE PoP internet inspection. What should the engineer do?
Separate the approved public secure-internet path from private overlay routes and validate source security policies. Traffic purpose and prefix routing distinguish FortiSASE SIA from SD-WAN-backed SPA. Expected evidence: Public browsing exits through cloud inspection while approved private prefixes traverse the datacenter overlay. Key limit: Not every endpoint needs the same path for SaaS and private application traffic.
Evaluate supported FortiSASE Branch On-ramp IPsec integration and configure only approved compatible edge settings. This could apply to the separate issue Branch on-ramp for non-FortiGate site: A remote branch has a supported IPsec-capable edge appliance but no FortiGate, and owners want its internet traffic inspected by FortiSASE. For FortiSASE internet traffic hairpin after SPA, the directly relevant action is: Separate the approved public secure-internet path from private overlay routes and validate source security policies.
Narrow route advertisement and acceptance to approved destination prefixes and verify SPA policy scope. This could apply to the separate issue Wrong private prefix import from hub: A datacenter hub advertises an overly broad 10.0.0.0/8 prefix to FortiSASE, and remote-user traffic for unrelated networks is diverted over the private overlay. For FortiSASE internet traffic hairpin after SPA, the directly relevant action is: Separate the approved public secure-internet path from private overlay routes and validate source security policies.
Choose and validate the intended supported client-versus-site traffic path for that user cohort before enabling both mechanisms. This could apply to the separate issue Site-based SASE and endpoint agent double steering: A branch sends user internet traffic to FortiSASE through a secure-edge appliance, but managed laptops also install a full tunnel client and suffer routing loops. For FortiSASE internet traffic hairpin after SPA, the directly relevant action is: Separate the approved public secure-internet path from private overlay routes and validate source security policies.
A pilot is validating the implementation. A remote-user rollout routes both private datacenter traffic and public browsing through the corporate SD-WAN hub, although security owners intended FortiSASE PoP internet inspection. Which finding proves that the intended fix works?
Public browsing exits through cloud inspection while approved private prefixes traverse the datacenter overlay. This is the directly relevant check for FortiSASE internet traffic hairpin after SPA. It confirms the required step: Separate the approved public secure-internet path from private overlay routes and validate source security policies. The operating principle is: Traffic purpose and prefix routing distinguish FortiSASE SIA from SD-WAN-backed SPA.
Only authorized datacenter networks use the hub tunnels while unrelated corporate or internet destinations follow intended routes. This would validate a different scenario, Wrong private prefix import from hub, where A datacenter hub advertises an overly broad 10.0.0.0/8 prefix to FortiSASE, and remote-user traffic for unrelated networks is diverted over the private overlay. The current case needs evidence for FortiSASE internet traffic hairpin after SPA.
Pilot laptops use one approved cloud inspection path without duplicated tunnels or recursive proxy behavior. This would validate a different scenario, Site-based SASE and endpoint agent double steering, where A branch sends user internet traffic to FortiSASE through a secure-edge appliance, but managed laptops also install a full tunnel client and suffer routing loops. The current case needs evidence for FortiSASE internet traffic hairpin after SPA.
The branch establishes its approved on-ramp and test internet traffic is logged under the intended cloud policy. This would validate a different scenario, Branch on-ramp for non-FortiGate site, where A remote branch has a supported IPsec-capable edge appliance but no FortiGate, and owners want its internet traffic inspected by FortiSASE. The current case needs evidence for FortiSASE internet traffic hairpin after SPA.
Please check your mailbox for a message from support@examlabs.com and follow the directions.