NSE5_SSE_AD-7.6 Premium File
- 54 Questions & Answers
- Last Update: Nov 5, 2026
A support analyst is collecting data for this scenario. An onboarding email with a live FortiSASE invitation link was forwarded to an unauthorized external address. Which diagnostic check is most targeted?
Inspect invitation lifecycle, claimed devices, identity logs and revocation evidence. This inspection targets Enrollment invitation compromised rather than a different configuration issue. The corrective action is: Revoke or rotate the affected invitation and verify authenticated named-user constraints before issuing a new approved invitation. Expected evidence: An unauthorized test cannot enroll using the old invitation, while the legitimate recipient succeeds with the new process.
Inspect invite history, code entry, account scope and client enrollment error. This is useful when diagnosing Manual enrollment code invalid. Instead, inspect invitation lifecycle, claimed devices, identity logs and revocation evidence.
Inspect SWG proxy URL, browser configuration, credentials and web logs. This is useful when diagnosing SWG agentless browser-only onboarding. Instead, inspect invitation lifecycle, claimed devices, identity logs and revocation evidence.
Inspect IdP group claims, FortiSASE group mapping and authenticated session policy. This is useful when diagnosing SAML identity group-based onboarding. Instead, inspect invitation lifecycle, claimed devices, identity logs and revocation evidence.
A Fortinet administrator must address this operational problem. Remote engineers reach public SaaS through FortiSASE but cannot access on-premises ERP that sits behind the enterprise's FortiGate SD-WAN hubs. Which response best resolves it?
Configure the supported FortiSASE-to-SD-WAN private access integration with appropriate overlay routing and security policies. FortiSASE PoPs can participate as spokes in a FortiGate SD-WAN private-access topology using supported IPsec and routing. Expected evidence: An authorized test user reaches the private ERP prefix through a healthy hub path without exposing it to the public internet. Key limit: Secure internet access and secure private access are distinct services and require their own access design.
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 FortiSASE secure private access through SD-WAN hubs, the directly relevant action is: Configure the supported FortiSASE-to-SD-WAN private access integration with appropriate overlay routing and security policies.
Configure supported multi-hub private access and validate route prioritization and redundancy under hub failure. This could apply to the separate issue SD-WAN private access dual hub failover: A remote worker's FortiSASE private ERP access depends on one datacenter hub despite a healthy secondary hub and overlay connection. For FortiSASE secure private access through SD-WAN hubs, the directly relevant action is: Configure the supported FortiSASE-to-SD-WAN private access integration with appropriate overlay routing and 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 secure private access through SD-WAN hubs, the directly relevant action is: Configure the supported FortiSASE-to-SD-WAN private access integration with appropriate overlay routing and security policies.
For this situation, a reviewer needs acceptance evidence. Remote engineers reach public SaaS through FortiSASE but cannot access on-premises ERP that sits behind the enterprise's FortiGate SD-WAN hubs. Which result most directly demonstrates success?
An authorized test user reaches the private ERP prefix through a healthy hub path without exposing it to the public internet. This is the directly relevant check for FortiSASE secure private access through SD-WAN hubs. It confirms the required step: Configure the supported FortiSASE-to-SD-WAN private access integration with appropriate overlay routing and security policies. The operating principle is: FortiSASE PoPs can participate as spokes in a FortiGate SD-WAN private-access topology using supported IPsec and routing.
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 FortiSASE secure private access through SD-WAN hubs.
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 FortiSASE secure private access through SD-WAN hubs.
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 FortiSASE secure private access through SD-WAN hubs.
A network administrator must explain the underlying control. Remote engineers reach public SaaS through FortiSASE but cannot access on-premises ERP that sits behind the enterprise's FortiGate SD-WAN hubs. Which statement is correct?
FortiSASE PoPs can participate as spokes in a FortiGate SD-WAN private-access topology using supported IPsec and routing. This explains FortiSASE secure private access through SD-WAN hubs in the given environment. The implementation decision is: Configure the supported FortiSASE-to-SD-WAN private access integration with appropriate overlay routing and security policies. Confirm it with: An authorized test user reaches the private ERP prefix through a healthy hub path without exposing it to the public internet.
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 FortiSASE secure private access through SD-WAN hubs. The relevant principle is: FortiSASE PoPs can participate as spokes in a FortiGate SD-WAN private-access topology using supported IPsec and routing.
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 FortiSASE secure private access through SD-WAN hubs. The relevant principle is: FortiSASE PoPs can participate as spokes in a FortiGate SD-WAN private-access topology using supported IPsec and routing.
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 FortiSASE secure private access through SD-WAN hubs. The relevant principle is: FortiSASE PoPs can participate as spokes in a FortiGate SD-WAN private-access topology using supported IPsec and routing.
An incident team needs to isolate the root cause. Remote engineers reach public SaaS through FortiSASE but cannot access on-premises ERP that sits behind the enterprise's FortiGate SD-WAN hubs. Which investigation should be prioritized?
Inspect private-access topology, tunnel state, BGP prefixes and user policy. This inspection targets FortiSASE secure private access through SD-WAN hubs rather than a different configuration issue. The corrective action is: Configure the supported FortiSASE-to-SD-WAN private access integration with appropriate overlay routing and security policies. Expected evidence: An authorized test user reaches the private ERP prefix through a healthy hub path without exposing it to the public internet.
Inspect destination routes, PoP egress, hub tunnel usage and traffic logs. This is useful when diagnosing FortiSASE internet traffic hairpin after SPA. Instead, inspect private-access topology, tunnel state, bgp prefixes and user policy.
Inspect device series, FortiOS version, secure-edge subscription and FortiSASE device inventory. This is useful when diagnosing Site-based FortiGate license missing. Instead, inspect private-access topology, tunnel state, bgp prefixes and user policy.
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 private-access topology, tunnel state, bgp prefixes and user policy.
A network engineer faces the following FortiSASE or SD-WAN condition. A FortiSASE private access tunnel comes up to an SD-WAN hub, but new campus prefixes remain unreachable for remote users. What should the engineer do?
Verify that the supported overlay routing advertises and accepts the intended private prefixes between the PoP spoke and SD-WAN hub. A working IPsec tunnel alone does not advertise every destination; routing exchanges supply private network reachability. Expected evidence: A remote pilot receives routes for approved prefixes and connects to the intended internal host. Key limit: Seeing an IKE tunnel status as up does not prove the required destination prefixes exist.
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 SASE PoP as overlay spoke BGP route, the directly relevant action is: Verify that the supported overlay routing advertises and accepts the intended private prefixes between the PoP spoke and SD-WAN hub.
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 SASE PoP as overlay spoke BGP route, the directly relevant action is: Verify that the supported overlay routing advertises and accepts the intended private prefixes between the PoP spoke and SD-WAN hub.
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 SASE PoP as overlay spoke BGP route, the directly relevant action is: Verify that the supported overlay routing advertises and accepts the intended private prefixes between the PoP spoke and SD-WAN hub.
A pilot is validating the implementation. A FortiSASE private access tunnel comes up to an SD-WAN hub, but new campus prefixes remain unreachable for remote users. Which finding proves that the intended fix works?
A remote pilot receives routes for approved prefixes and connects to the intended internal host. This is the directly relevant check for SASE PoP as overlay spoke BGP route. It confirms the required step: Verify that the supported overlay routing advertises and accepts the intended private prefixes between the PoP spoke and SD-WAN hub. The operating principle is: A working IPsec tunnel alone does not advertise every destination; routing exchanges supply private network reachability.
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 SASE PoP as overlay spoke BGP route.
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 SASE PoP as overlay spoke BGP route.
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 SASE PoP as overlay spoke BGP route.
A technical lead asks why the recommended approach works. A FortiSASE private access tunnel comes up to an SD-WAN hub, but new campus prefixes remain unreachable for remote users. Which mechanism is most relevant?
A working IPsec tunnel alone does not advertise every destination; routing exchanges supply private network reachability. This explains SASE PoP as overlay spoke BGP route in the given environment. The implementation decision is: Verify that the supported overlay routing advertises and accepts the intended private prefixes between the PoP spoke and SD-WAN hub. Confirm it with: A remote pilot receives routes for approved prefixes and connects to the intended internal host.
PoP-sourced private access can use configured remote-access address space distinct from physical branch subnets. That concept concerns FortiSASE-to-SD-WAN hub tunnel source identity, not the mechanism needed for SASE PoP as overlay spoke BGP route. The relevant principle is: A working IPsec tunnel alone does not advertise every destination; routing exchanges supply private network reachability.
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 SASE PoP as overlay spoke BGP route. The relevant principle is: A working IPsec tunnel alone does not advertise every destination; routing exchanges supply private network reachability.
Overlay reachability and datacenter firewall access control are separate enforcement requirements. That concept concerns FortiSASE user policy and hub firewall allow, not the mechanism needed for SASE PoP as overlay spoke BGP route. The relevant principle is: A working IPsec tunnel alone does not advertise every destination; routing exchanges supply private network reachability.
Before changing production settings, an engineer reviews the symptoms. A FortiSASE private access tunnel comes up to an SD-WAN hub, but new campus prefixes remain unreachable for remote users. Which evidence is most useful?
Inspect BGP neighbor state, advertised routes, route filters and firewall permission. This inspection targets SASE PoP as overlay spoke BGP route rather than a different configuration issue. The corrective action is: Verify that the supported overlay routing advertises and accepts the intended private prefixes between the PoP spoke and SD-WAN hub. Expected evidence: A remote pilot receives routes for approved prefixes and connects to the intended internal host.
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 bgp neighbor state, advertised routes, route filters and firewall permission.
Inspect rule assignment, security profile settings, trial traffic logs and push/publication status. This is useful when diagnosing Cloud security baseline before enabling users. Instead, inspect bgp neighbor state, advertised routes, route filters and firewall permission.
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 bgp neighbor state, advertised routes, route filters and firewall permission.
A deployment review finds this gap. An office wants all user internet sessions to receive FortiSASE cloud inspection without installing FortiClient on every wired desktop. What is the most targeted next configuration step?
Use a supported licensed FortiGate secure-edge LAN extension design with the approved tunnel and site connectivity configuration. A FortiGate LAN extension can transport site user traffic into FortiSASE over a supported overlay while clients keep the FortiGate as gateway. Expected evidence: A sample wired workstation uses the branch gateway and its internet browsing appears under FortiSASE security policy. Key limit: This feature has device/version/subscription prerequisites and is not universally available on every 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 FortiGate LAN extension to FortiSASE, the directly relevant action is: Use a supported licensed FortiGate secure-edge LAN extension design with the approved tunnel and site connectivity configuration.
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 FortiGate LAN extension to FortiSASE, the directly relevant action is: Use a supported licensed FortiGate secure-edge LAN extension design with the approved tunnel and site connectivity configuration.
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 FortiGate LAN extension to FortiSASE, the directly relevant action is: Use a supported licensed FortiGate secure-edge LAN extension design with the approved tunnel and site connectivity configuration.
The recommended change has been applied. An office wants all user internet sessions to receive FortiSASE cloud inspection without installing FortiClient on every wired desktop. Which observation best verifies the intended outcome?
A sample wired workstation uses the branch gateway and its internet browsing appears under FortiSASE security policy. This is the directly relevant check for FortiGate LAN extension to FortiSASE. It confirms the required step: Use a supported licensed FortiGate secure-edge LAN extension design with the approved tunnel and site connectivity configuration. The operating principle is: A FortiGate LAN extension can transport site user traffic into FortiSASE over a supported overlay while clients keep the FortiGate as gateway.
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 FortiGate LAN extension to FortiSASE.
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 LAN extension to FortiSASE.
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 FortiGate LAN extension to FortiSASE.
Please check your mailbox for a message from support@examlabs.com and follow the directions.