NSE5_SSE_AD-7.6 Premium File
- 54 Questions & Answers
- Last Update: Nov 5, 2026
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.
A network engineer faces the following FortiSASE or SD-WAN condition. 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. What should the engineer do?
Choose and validate the intended supported client-versus-site traffic path for that user cohort before enabling both mechanisms. Site-based LAN extension and endpoint agent connections are distinct ingress models that need coordinated routing. Expected evidence: Pilot laptops use one approved cloud inspection path without duplicated tunnels or recursive proxy behavior. Key limit: A client being enrolled does not mean both tunnel modes should be active concurrently.
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 Site-based SASE and endpoint agent double steering, the directly relevant action is: Choose and validate the intended supported client-versus-site traffic path for that user cohort before enabling both mechanisms.
Confirm the separate supported FortiSASE secure-edge subscription and tenant feature eligibility for the specific FortiGate. This could apply to the separate issue Site-based FortiGate license missing: A branch FortiGate supports normal SD-WAN but the FortiSASE secure-edge/LAN-extension integration option is unavailable in tenant settings. For Site-based SASE and endpoint agent double steering, the directly relevant action is: Choose and validate the intended supported client-versus-site traffic path for that user cohort before enabling both mechanisms.
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 SASE and endpoint agent double steering, the directly relevant action is: Choose and validate the intended supported client-versus-site traffic path for that user cohort before enabling both mechanisms.
A pilot is validating the implementation. 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. Which finding proves that the intended fix works?
Pilot laptops use one approved cloud inspection path without duplicated tunnels or recursive proxy behavior. This is the directly relevant check for Site-based SASE and endpoint agent double steering. It confirms the required step: Choose and validate the intended supported client-versus-site traffic path for that user cohort before enabling both mechanisms. The operating principle is: Site-based LAN extension and endpoint agent connections are distinct ingress models that need coordinated routing.
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 SASE and endpoint agent double steering.
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 Site-based SASE and endpoint agent double steering.
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 Site-based SASE and endpoint agent double steering.
A technical lead asks why the recommended approach works. 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. Which mechanism is most relevant?
Site-based LAN extension and endpoint agent connections are distinct ingress models that need coordinated routing. This explains Site-based SASE and endpoint agent double steering in the given environment. The implementation decision is: Choose and validate the intended supported client-versus-site traffic path for that user cohort before enabling both mechanisms. Confirm it with: Pilot laptops use one approved cloud inspection path without duplicated tunnels or recursive proxy behavior.
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 SASE and endpoint agent double steering. The relevant principle is: Site-based LAN extension and endpoint agent connections are distinct ingress models that need coordinated routing.
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 Site-based SASE and endpoint agent double steering. The relevant principle is: Site-based LAN extension and endpoint agent connections are distinct ingress models that need coordinated routing.
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 Site-based SASE and endpoint agent double steering. The relevant principle is: Site-based LAN extension and endpoint agent connections are distinct ingress models that need coordinated routing.
Before changing production settings, an engineer reviews the symptoms. 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. Which evidence is most useful?
Inspect local routes, FortiClient tunnel state, branch edge path and SASE session attribution. This inspection targets Site-based SASE and endpoint agent double steering rather than a different configuration issue. The corrective action is: Choose and validate the intended supported client-versus-site traffic path for that user cohort before enabling both mechanisms. Expected evidence: Pilot laptops use one approved cloud inspection path without duplicated tunnels or recursive proxy behavior.
Inspect device series, FortiOS version, secure-edge subscription and FortiSASE device inventory. This is useful when diagnosing Site-based FortiGate license missing. Instead, inspect local routes, forticlient tunnel state, branch edge path and sase session attribution.
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 local routes, forticlient tunnel state, branch edge path and sase session attribution.
Inspect destination routes, PoP egress, hub tunnel usage and traffic logs. This is useful when diagnosing FortiSASE internet traffic hairpin after SPA. Instead, inspect local routes, forticlient tunnel state, branch edge path and sase session attribution.
A deployment review finds this gap. 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. What is the most targeted next configuration step?
Document and permit the actual authorized FortiSASE remote-user source ranges and appropriate private access policy at the hub. PoP-sourced private access can use configured remote-access address space distinct from physical branch subnets. Expected evidence: A representative remote user reaches the intended service while unauthorized source ranges remain blocked. Key limit: Never replace precise source identity with any-address authorization to make a test pass.
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-to-SD-WAN hub tunnel source identity, the directly relevant action is: Document and permit the actual authorized FortiSASE remote-user source ranges and appropriate private access policy at the hub.
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-to-SD-WAN hub tunnel source identity, the directly relevant action is: Document and permit the actual authorized FortiSASE remote-user source ranges and appropriate private access policy at the hub.
Verify that the supported overlay routing advertises and accepts the intended private prefixes between the PoP spoke and SD-WAN hub. This could apply to the separate issue SASE PoP as overlay spoke BGP route: A FortiSASE private access tunnel comes up to an SD-WAN hub, but new campus prefixes remain unreachable for remote users. For FortiSASE-to-SD-WAN hub tunnel source identity, the directly relevant action is: Document and permit the actual authorized FortiSASE remote-user source ranges and appropriate private access policy at the hub.
The recommended change has been applied. 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. Which observation best verifies the intended outcome?
A representative remote user reaches the intended service while unauthorized source ranges remain blocked. This is the directly relevant check for FortiSASE-to-SD-WAN hub tunnel source identity. It confirms the required step: Document and permit the actual authorized FortiSASE remote-user source ranges and appropriate private access policy at the hub. The operating principle is: PoP-sourced private access can use configured remote-access address space distinct from physical branch subnets.
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-to-SD-WAN hub tunnel source identity.
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-to-SD-WAN hub tunnel source identity.
A remote pilot receives routes for approved prefixes and connects to the intended internal host. This would validate a different scenario, SASE PoP as overlay spoke BGP route, where A FortiSASE private access tunnel comes up to an SD-WAN hub, but new campus prefixes remain unreachable for remote users. The current case needs evidence for FortiSASE-to-SD-WAN hub tunnel source identity.
An architect reviews the platform behavior behind this incident. 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. Which explanation applies?
PoP-sourced private access can use configured remote-access address space distinct from physical branch subnets. This explains FortiSASE-to-SD-WAN hub tunnel source identity in the given environment. The implementation decision is: Document and permit the actual authorized FortiSASE remote-user source ranges and appropriate private access policy at the hub. Confirm it with: A representative remote user reaches the intended service while unauthorized source ranges remain blocked.
A working IPsec tunnel alone does not advertise every destination; routing exchanges supply private network reachability. That concept concerns SASE PoP as overlay spoke BGP route, not the mechanism needed for FortiSASE-to-SD-WAN hub tunnel source identity. The relevant principle is: PoP-sourced private access can use configured remote-access address space distinct from physical branch subnets.
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-to-SD-WAN hub tunnel source identity. The relevant principle is: PoP-sourced private access can use configured remote-access address space distinct from physical branch subnets.
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 FortiSASE-to-SD-WAN hub tunnel source identity. The relevant principle is: PoP-sourced private access can use configured remote-access address space distinct from physical branch subnets.
A support analyst is collecting data for this scenario. 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. Which diagnostic check is most targeted?
Inspect tunnel route source, actual session source IP, hub firewall policy and SASE group. This inspection targets FortiSASE-to-SD-WAN hub tunnel source identity rather than a different configuration issue. The corrective action is: Document and permit the actual authorized FortiSASE remote-user source ranges and appropriate private access policy at the hub. Expected evidence: A representative remote user reaches the intended service while unauthorized source ranges remain blocked.
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 tunnel route source, actual session source ip, hub firewall policy and sase group.
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 tunnel route source, actual session source ip, hub firewall policy and sase group.
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 tunnel route source, actual session source ip, hub firewall policy and sase group.
A Fortinet administrator must address this operational problem. Remote users download executables through an approved SaaS portal but known malicious files pass because the matching SASE policy has no antivirus control. Which response best resolves it?
Attach the appropriate supported antivirus security profile to the eligible internet/SaaS policy and choose the approved prevention actions. Cloud security profiles inspect supported content on traffic that actually matches an eligible FortiSASE policy. Expected evidence: Controlled safe test samples generate expected malware verdicts while normal allowed content still works. Key limit: Encrypted file inspection may require authorized deep inspection and appropriate service entitlement.
Enable supported malicious-domain protection in the matching DNS/web security profile and check current intelligence eligibility. This could apply to the separate issue FortiSASE DNS malicious-domain block: Remote employees visit a phishing domain via an otherwise permitted browser, but the SASE policy lacks an appropriate DNS or URL threat control. For FortiSASE antivirus inspection on permitted download, the directly relevant action is: Attach the appropriate supported antivirus security profile to the eligible internet/SaaS policy and choose the approved prevention actions.
Scope supported inline-CASB/application-control and web-filter policies to the sanctioned SaaS provider and approved user group. This could apply to the separate issue FortiSASE secure SaaS access via app and web policy: A SASE tenant permits an entire category of cloud collaboration services, though the organization authorizes only one specific vendor. For FortiSASE antivirus inspection on permitted download, the directly relevant action is: Attach the appropriate supported antivirus security profile to the eligible internet/SaaS policy and choose the approved prevention actions.
Enable a suitable FortiSASE intrusion prevention sensor/profile and targeted rule attachment for the protected traffic. This could apply to the separate issue FortiSASE IPS protection for web exploit: A customer application is reached through cloud secure access, but the security team detects known exploit attempts and no IPS action is applied. For FortiSASE antivirus inspection on permitted download, the directly relevant action is: Attach the appropriate supported antivirus security profile to the eligible internet/SaaS policy and choose the approved prevention actions.
For this situation, a reviewer needs acceptance evidence. Remote users download executables through an approved SaaS portal but known malicious files pass because the matching SASE policy has no antivirus control. Which result most directly demonstrates success?
Controlled safe test samples generate expected malware verdicts while normal allowed content still works. This is the directly relevant check for FortiSASE antivirus inspection on permitted download. It confirms the required step: Attach the appropriate supported antivirus security profile to the eligible internet/SaaS policy and choose the approved prevention actions. The operating principle is: Cloud security profiles inspect supported content on traffic that actually matches an eligible FortiSASE policy.
Only the approved portal becomes reachable and unrelated blocked sites remain restricted. This would validate a different scenario, Web-filter category exception for approved partner, where A regulated medical portal is misclassified under a broad blocked URL category and users request disabling that entire category. The current case needs evidence for FortiSASE antivirus inspection on permitted download.
A controlled known-bad test domain triggers the required block or alert with a recorded identity. This would validate a different scenario, FortiSASE DNS malicious-domain block, where Remote employees visit a phishing domain via an otherwise permitted browser, but the SASE policy lacks an appropriate DNS or URL threat control. The current case needs evidence for FortiSASE antivirus inspection on permitted download.
Authorized cloud collaboration succeeds and unsanctioned alternatives follow their intended deny policy. This would validate a different scenario, FortiSASE secure SaaS access via app and web policy, where A SASE tenant permits an entire category of cloud collaboration services, though the organization authorizes only one specific vendor. The current case needs evidence for FortiSASE antivirus inspection on permitted download.
Please check your mailbox for a message from support@examlabs.com and follow the directions.