NSE5_SSE_AD-7.6 Premium File
- 54 Questions & Answers
- Last Update: Nov 5, 2026
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.
A technical lead asks why the recommended approach works. 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 mechanism is most relevant?
Traffic purpose and prefix routing distinguish FortiSASE SIA from SD-WAN-backed SPA. This explains FortiSASE internet traffic hairpin after SPA in the given environment. The implementation decision is: Separate the approved public secure-internet path from private overlay routes and validate source security policies. Confirm it with: Public browsing exits through cloud inspection while approved private prefixes traverse the datacenter overlay.
SD-WAN overlay routing distributes reachable network prefixes and must honor scope policy. That concept concerns Wrong private prefix import from hub, not the mechanism needed for FortiSASE internet traffic hairpin after SPA. The relevant principle is: Traffic purpose and prefix routing distinguish FortiSASE SIA from SD-WAN-backed SPA.
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 FortiSASE internet traffic hairpin after SPA. The relevant principle is: Traffic purpose and prefix routing distinguish FortiSASE SIA from SD-WAN-backed SPA.
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 FortiSASE internet traffic hairpin after SPA. The relevant principle is: Traffic purpose and prefix routing distinguish FortiSASE SIA from SD-WAN-backed SPA.
Before changing production settings, an engineer reviews the symptoms. 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 evidence is most useful?
Inspect destination routes, PoP egress, hub tunnel usage and traffic logs. This inspection targets FortiSASE internet traffic hairpin after SPA rather than a different configuration issue. The corrective action is: Separate the approved public secure-internet path from private overlay routes and validate source security policies. Expected evidence: Public browsing exits through cloud inspection while approved private prefixes traverse the datacenter overlay.
Inspect advertised and received BGP prefixes, route filters, user traffic and tunnel counters. This is useful when diagnosing Wrong private prefix import from hub. Instead, inspect destination routes, pop egress, hub tunnel usage and 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 destination routes, pop egress, hub tunnel usage and traffic logs.
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 destination routes, pop egress, hub tunnel usage and traffic logs.
A deployment review finds this gap. 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. What is the most targeted next configuration step?
Inspect and repair the supported VXLAN-over-IPsec LAN extension parameters and associated gateway/interface configuration. FortiGate secure-edge LAN extension transports site traffic using a supported layer-2 VXLAN-over-IPsec construct. Expected evidence: Wired pilot users' internet sessions reach the cloud service under the correct tenant security rules. Key limit: Do not assume all IPsec connections inherently behave as a LAN extension.
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 FortiGate secure-edge VXLAN overlay health, the directly relevant action is: Inspect and repair the supported VXLAN-over-IPsec LAN extension parameters and associated gateway/interface configuration.
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 FortiGate secure-edge VXLAN overlay health, the directly relevant action is: Inspect and repair the supported VXLAN-over-IPsec LAN extension parameters and associated gateway/interface configuration.
Document and permit the actual authorized FortiSASE remote-user source ranges and appropriate private access policy at the hub. This could apply to the separate issue FortiSASE-to-SD-WAN hub tunnel source identity: A FortiSASE PoP establishes a private overlay but a datacenter ACL rejects remote users because the source IP range was assumed to match a normal branch subnet. For FortiGate secure-edge VXLAN overlay health, the directly relevant action is: Inspect and repair the supported VXLAN-over-IPsec LAN extension parameters and associated gateway/interface configuration.
The recommended change has been applied. 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. Which observation best verifies the intended outcome?
Wired pilot users' internet sessions reach the cloud service under the correct tenant security rules. This is the directly relevant check for FortiGate secure-edge VXLAN overlay health. It confirms the required step: Inspect and repair the supported VXLAN-over-IPsec LAN extension parameters and associated gateway/interface configuration. The operating principle is: FortiGate secure-edge LAN extension transports site traffic using a supported layer-2 VXLAN-over-IPsec construct.
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 FortiGate secure-edge VXLAN overlay health.
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 FortiGate secure-edge VXLAN overlay health.
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 FortiGate secure-edge VXLAN overlay health.
An architect reviews the platform behavior behind this incident. 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. Which explanation applies?
FortiGate secure-edge LAN extension transports site traffic using a supported layer-2 VXLAN-over-IPsec construct. This explains FortiGate secure-edge VXLAN overlay health in the given environment. The implementation decision is: Inspect and repair the supported VXLAN-over-IPsec LAN extension parameters and associated gateway/interface configuration. Confirm it with: Wired pilot users' internet sessions reach the cloud service under the correct tenant security rules.
SD-WAN overlay routing distributes reachable network prefixes and must honor scope policy. That concept concerns Wrong private prefix import from hub, not the mechanism needed for FortiGate secure-edge VXLAN overlay health. The relevant principle is: FortiGate secure-edge LAN extension transports site traffic using a supported layer-2 VXLAN-over-IPsec construct.
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 FortiGate secure-edge VXLAN overlay health. The relevant principle is: FortiGate secure-edge LAN extension transports site traffic using a supported layer-2 VXLAN-over-IPsec construct.
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 FortiGate secure-edge VXLAN overlay health. The relevant principle is: FortiGate secure-edge LAN extension transports site traffic using a supported layer-2 VXLAN-over-IPsec construct.
A support analyst is collecting data for this scenario. 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. Which diagnostic check is most targeted?
Inspect tunnel and VXLAN interfaces, layer-2 neighbor behavior and cloud ingress logs. This inspection targets FortiGate secure-edge VXLAN overlay health rather than a different configuration issue. The corrective action is: Inspect and repair the supported VXLAN-over-IPsec LAN extension parameters and associated gateway/interface configuration. Expected evidence: Wired pilot users' internet sessions reach the cloud service under the correct tenant security rules.
Inspect destination routes, PoP egress, hub tunnel usage and traffic logs. This is useful when diagnosing FortiSASE internet traffic hairpin after SPA. Instead, inspect tunnel and vxlan interfaces, layer-2 neighbor behavior and cloud ingress logs.
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 tunnel and vxlan interfaces, layer-2 neighbor behavior and cloud ingress 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 tunnel and vxlan interfaces, layer-2 neighbor behavior and cloud ingress logs.
A Fortinet administrator must address this operational problem. 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. Which response best resolves it?
Narrow route advertisement and acceptance to approved destination prefixes and verify SPA policy scope. SD-WAN overlay routing distributes reachable network prefixes and must honor scope policy. Expected evidence: Only authorized datacenter networks use the hub tunnels while unrelated corporate or internet destinations follow intended routes. Key limit: A cloud-protected connection does not justify advertising every RFC1918 subnet into the tenant.
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 Wrong private prefix import from hub, the directly relevant action is: Narrow route advertisement and acceptance to approved destination prefixes and verify SPA policy scope.
Document and permit the actual authorized FortiSASE remote-user source ranges and appropriate private access policy at the hub. This could apply to the separate issue FortiSASE-to-SD-WAN hub tunnel source identity: A FortiSASE PoP establishes a private overlay but a datacenter ACL rejects remote users because the source IP range was assumed to match a normal branch subnet. For Wrong private prefix import from hub, the directly relevant action is: Narrow route advertisement and acceptance to approved destination prefixes and verify SPA policy scope.
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 Wrong private prefix import from hub, the directly relevant action is: Narrow route advertisement and acceptance to approved destination prefixes and verify SPA policy scope.
For this situation, a reviewer needs acceptance evidence. 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. Which result most directly demonstrates success?
Only authorized datacenter networks use the hub tunnels while unrelated corporate or internet destinations follow intended routes. This is the directly relevant check for Wrong private prefix import from hub. It confirms the required step: Narrow route advertisement and acceptance to approved destination prefixes and verify SPA policy scope. The operating principle is: SD-WAN overlay routing distributes reachable network prefixes and must honor scope policy.
A representative remote user reaches the intended service while unauthorized source ranges remain blocked. This would validate a different scenario, FortiSASE-to-SD-WAN hub tunnel source identity, where A FortiSASE PoP establishes a private overlay but a datacenter ACL rejects remote users because the source IP range was assumed to match a normal branch subnet. The current case needs evidence for Wrong private prefix import from hub.
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 Wrong private prefix import from hub.
During a controlled hub outage, new permitted ERP sessions use the authorized secondary hub. This would validate a different scenario, SD-WAN private access dual hub failover, where A remote worker's FortiSASE private ERP access depends on one datacenter hub despite a healthy secondary hub and overlay connection. The current case needs evidence for Wrong private prefix import from hub.
A network administrator must explain the underlying control. 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. Which statement is correct?
SD-WAN overlay routing distributes reachable network prefixes and must honor scope policy. This explains Wrong private prefix import from hub in the given environment. The implementation decision is: Narrow route advertisement and acceptance to approved destination prefixes and verify SPA policy scope. Confirm it with: Only authorized datacenter networks use the hub tunnels while unrelated corporate or internet destinations follow intended routes.
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 Wrong private prefix import from hub. The relevant principle is: SD-WAN overlay routing distributes reachable network prefixes and must honor scope policy.
Multiple SD-WAN hubs can provide redundant private-resource paths for FortiSASE PoP spokes. That concept concerns SD-WAN private access dual hub failover, not the mechanism needed for Wrong private prefix import from hub. The relevant principle is: SD-WAN overlay routing distributes reachable network prefixes and must honor scope policy.
FortiGate secure-edge LAN extension transports site traffic using a supported layer-2 VXLAN-over-IPsec construct. That concept concerns FortiGate secure-edge VXLAN overlay health, not the mechanism needed for Wrong private prefix import from hub. The relevant principle is: SD-WAN overlay routing distributes reachable network prefixes and must honor scope policy.
An incident team needs to isolate the root cause. 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. Which investigation should be prioritized?
Inspect advertised and received BGP prefixes, route filters, user traffic and tunnel counters. This inspection targets Wrong private prefix import from hub rather than a different configuration issue. The corrective action is: Narrow route advertisement and acceptance to approved destination prefixes and verify SPA policy scope. Expected evidence: Only authorized datacenter networks use the hub tunnels while unrelated corporate or internet destinations follow intended routes.
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 advertised and received bgp prefixes, route filters, user traffic and tunnel counters.
Inspect destination routes, PoP egress, hub tunnel usage and traffic logs. This is useful when diagnosing FortiSASE internet traffic hairpin after SPA. Instead, inspect advertised and received bgp prefixes, route filters, user traffic and tunnel counters.
Inspect tunnel route source, actual session source IP, hub firewall policy and SASE group. This is useful when diagnosing FortiSASE-to-SD-WAN hub tunnel source identity. Instead, inspect advertised and received bgp prefixes, route filters, user traffic and tunnel counters.
Please check your mailbox for a message from support@examlabs.com and follow the directions.