100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 530
Select THREE correct elements of a safe remedy-and-evidence plan for the Site on-ramp for nonagent branch users case. Following a production change affecting Northbank Logistics in its metro branch group, a network team receives repeatable user-impact reports. Its fault evidence is: A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support. Unrelated services are still operating, so the immediate response must isolate the failing control for the cloud PoP and private hub path without disabling unrelated protections.
- Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
- Agentless branch terminals inherit approved cloud enforcement through the edge.
- Connect a supported branch edge or LAN-extension device into the FortiSASE SIA path under site-based policy.
- A second authorized hub sustains private-app connectivity during a single-hub fault.
- Validate FortiSASE PoP and data-residency capabilities against the contractual geography before user rollout.
- Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge.
Explanation
Correct Answers
B:Agentless branch terminals inherit approved cloud enforcement through the edge. This confirms the case-specific path or security boundary.
C:Correct remediation element: Connect a supported branch edge or LAN-extension device into the FortiSASE SIA path under site-based policy. It addresses A per-user agent tunnel cannot be assumed on unmanaged factory endpoints. [Case R161-C106; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0530.]
F:Correct verification element: Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge. This independently measures whether the intended change works. [Case R161-C106; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0530.]
Incorrect Answers
A:That intervention addresses SD-WAN and SASE split security ownership: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. The relevant verification here is: Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge.
D:That intervention addresses Single-hub versus dual-hub SPA design: An enterprise wants high availability but its FortiSASE integration still uses a single hub endpoint. The case-specific requirement is: Agentless branch terminals inherit approved cloud enforcement through the edge. Verify it with: Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge.
E:That intervention addresses Sovereign access-point selection: A tenant's security architecture requires traffic inspection to remain within approved geographic PoPs. The case-specific requirement is: Connect a supported branch edge or LAN-extension device into the FortiSASE SIA path under site-based policy. Verify it with: Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge.
Question 531
Which corrective action MOST DIRECTLY addresses the observed FortiSASE PoP reachability to hub private routes problem within the approved change scope? During a scoped central region deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- Select an SPA architecture using SD-WAN/IPsec overlays that supports private TCP and UDP workloads.
- Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix.
- Deploy the supported agentless explicit-proxy/SWG method with user authentication and scoped browser policies.
- Use a FortiGate SD-WAN or supported thin-edge LAN-extension path to FortiSASE for site-based SIA.
Explanation
Correct Answer
B:Correct: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. The targeted remedy is Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix. This addresses cloud-user authentication alone does not create private sd-wan reachability. Confirm it by: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. [Case R161-C107; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0531.]
Incorrect Answers
A:That intervention addresses Private TCP and UDP application access: Remote workers need access to a private UDP-dependent application hosted behind an SD-WAN hub. The case-specific requirement is: Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix. Verify it with: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
C:Incorrect for this case: Deploy the supported agentless explicit-proxy/SWG method with user authentication and scoped browser policies. concerns the separate issue of Agentless browser-only internet access (A contractor uses a device on which the enterprise cannot install FortiClient but must secure browser traffic.). It does not directly establish Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix. The case-specific evidence is Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. [Case R161-C107; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0531.]
D:That intervention addresses Site-based SIA for edge branches: A remote branch has many IoT devices that cannot run individual endpoint agents but need inspected internet access. The case-specific requirement is: Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix. Verify it with: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
Question 532
Which independent diagnostic check best validates that the FortiSASE PoP reachability to hub private routes repair works? During a scoped central region deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
- Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
- Configure a test browser to use the FortiSASE proxy and inspect authentication and web-policy logs.
- Send traffic from an agentless branch host and check the edge-to-PoP transport and applied SIA security policy.
Explanation
Correct Answer
A:Correct: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. This directly tests the failure mechanism and the required acceptance evidence: The intended private subnet has a viable overlay route from the user's PoP. [Case R161-C107; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0532.]
Incorrect Answers
B:That intervention addresses SPA route propagation through dual hubs: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. The relevant verification here is: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
C:Incorrect for this case: Configure a test browser to use the FortiSASE proxy and inspect authentication and web-policy logs. concerns the separate issue of Agentless browser-only internet access (A contractor uses a device on which the enterprise cannot install FortiClient but must secure browser traffic.). It does not directly establish Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. The case-specific evidence is Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. [Case R161-C107; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0532.]
D:That intervention addresses Site-based SIA for edge branches: A remote branch has many IoT devices that cannot run individual endpoint agents but need inspected internet access. The relevant verification here is: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
Question 533
What observable result would show that the intended FortiSASE PoP reachability to hub private routes behavior has been restored? During a scoped central region deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- Internet and private workloads follow their intended separate security paths.
- The managed endpoint's internet traffic receives the intended cloud security inspection.
- Security inspection is routed using the allowed geographic scope with documented exceptions.
- The intended private subnet has a viable overlay route from the user's PoP.
Explanation
Correct Answer
D:Correct: The intended private subnet has a viable overlay route from the user's PoP. That result demonstrates the requested controlled repair and avoids the failure mode: Cloud-user authentication alone does not create private SD-WAN reachability. [Case R161-C107; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0533.]
Incorrect Answers
A:That intervention addresses Selective private versus internet access: Remote users must send general web traffic to cloud inspection but private application traffic over approved SPA. The case-specific requirement is: The intended private subnet has a viable overlay route from the user's PoP. Verify it with: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
B:Incorrect for this case: The managed endpoint's internet traffic receives the intended cloud security inspection. concerns the separate issue of Agent-based remote-user secure internet access (Managed laptops require full-tunnel policy enforcement when users browse from unmanaged networks.). It does not directly establish The intended private subnet has a viable overlay route from the user's PoP. The case-specific evidence is Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. [Case R161-C107; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0533.]
C:Incorrect for this case: Security inspection is routed using the allowed geographic scope with documented exceptions. concerns the separate issue of Sovereign access-point selection (A tenant's security architecture requires traffic inspection to remain within approved geographic PoPs.). It does not directly establish The intended private subnet has a viable overlay route from the user's PoP. The case-specific evidence is Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. [Case R161-C107; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0533.]
Question 534
Which failure mechanism BEST explains the FortiSASE PoP reachability to hub private routes observation before a repair is attempted? During a scoped central region deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- An agentless web-only proxy is mismatched to the application's private UDP transport.
- Cloud-user authentication alone does not create private SD-WAN reachability.
- Endpoint installation requirements make agent-based access infeasible for this user population.
- Cloud SPA routes were configured only for the primary hub.
Explanation
Correct Answer
B:Correct: Cloud-user authentication alone does not create private SD-WAN reachability. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. [Case R161-C107; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0534.]
Incorrect Answers
A:Incorrect diagnosis: this describes a different operational mechanism (Agentless SPA requirement classification), not the documented observation (Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN.). The supported case diagnosis is Cloud-user authentication alone does not create private SD-WAN reachability. [Case R161-C107; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0534.]
C:The Agentless browser-only internet access diagnosis does not explain the observed case: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. The supported diagnosis is: Cloud-user authentication alone does not create private SD-WAN reachability.
D:The SPA route propagation through dual hubs diagnosis does not explain the observed case: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. The supported diagnosis is: Cloud-user authentication alone does not create private SD-WAN reachability.
Question 535
Select TWO correct elements of a safe remedy-and-evidence plan for the FortiSASE PoP reachability to hub private routes case. During a scoped central region deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
- The managed endpoint's internet traffic receives the intended cloud security inspection.
- Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix.
- Fail the primary hub and observe PoP-to-secondary route selection and application continuity.
- Use the vendor-supported tenant and service provisioning workflow with customer-specific administrator scope.
Explanation
Correct Answers
A:Correct verification element: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. This independently measures whether the intended change works. [Case R161-C107; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0535.]
C:Correct remediation element: Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix. It addresses Cloud-user authentication alone does not create private SD-WAN reachability. [Case R161-C107; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0535.]
Incorrect Answers
B:Incorrect for this case: The managed endpoint's internet traffic receives the intended cloud security inspection. concerns the separate issue of Agent-based remote-user secure internet access (Managed laptops require full-tunnel policy enforcement when users browse from unmanaged networks.). It does not directly establish The intended private subnet has a viable overlay route from the user's PoP. The case-specific evidence is Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. [Case R161-C107; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0535.]
D:That intervention addresses Single-hub versus dual-hub SPA design: An enterprise wants high availability but its FortiSASE integration still uses a single hub endpoint. The relevant verification here is: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
E:That intervention addresses MSSP customer provisioning separation: An MSSP operator is onboarding two customers with different licenses, policies and delegated admins. The case-specific requirement is: Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix. Verify it with: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
Question 536
Which corrective action MOST DIRECTLY addresses the observed FortiSASE PoP reachability to hub private routes problem within the approved change scope? Following a production change affecting Mistral Education in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Separate SIA and SPA use cases with explicit destination classifications and the appropriate FortiSASE and hub controls.
- Validate FortiSASE PoP and data-residency capabilities against the contractual geography before user rollout.
- Deploy the supported agentless explicit-proxy/SWG method with user authentication and scoped browser policies.
- Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix.
Explanation
Correct Answer
D:Correct: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. The targeted remedy is Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix. This addresses cloud-user authentication alone does not create private sd-wan reachability. Confirm it by: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. [Case R161-C108; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0536.]
Incorrect Answers
A:That intervention addresses Selective private versus internet access: Remote users must send general web traffic to cloud inspection but private application traffic over approved SPA. The case-specific requirement is: Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix. Verify it with: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
B:That intervention addresses Sovereign access-point selection: A tenant's security architecture requires traffic inspection to remain within approved geographic PoPs. The case-specific requirement is: Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix. Verify it with: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
C:Incorrect for this case: Deploy the supported agentless explicit-proxy/SWG method with user authentication and scoped browser policies. concerns the separate issue of Agentless browser-only internet access (A contractor uses a device on which the enterprise cannot install FortiClient but must secure browser traffic.). It does not directly establish Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix. The case-specific evidence is Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. [Case R161-C108; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0536.]
Question 537
Which independent diagnostic check best validates that the FortiSASE PoP reachability to hub private routes repair works? Following a production change affecting Mistral Education in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Audit who can see each tenant's policies and verify licensed services and PoP assignments separately.
- Configure a test browser to use the FortiSASE proxy and inspect authentication and web-policy logs.
- Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
- Read the observed public source IP from a SaaS request in each intended user region.
Explanation
Correct Answer
C:Correct: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. This directly tests the failure mechanism and the required acceptance evidence: The intended private subnet has a viable overlay route from the user's PoP. [Case R161-C108; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0537.]
Incorrect Answers
A:That intervention addresses MSSP customer provisioning separation: An MSSP operator is onboarding two customers with different licenses, policies and delegated admins. The relevant verification here is: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
B:Incorrect for this case: Configure a test browser to use the FortiSASE proxy and inspect authentication and web-policy logs. concerns the separate issue of Agentless browser-only internet access (A contractor uses a device on which the enterprise cannot install FortiClient but must secure browser traffic.). It does not directly establish Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. The case-specific evidence is Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. [Case R161-C108; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0537.]
D:That intervention addresses Dedicated public egress IP requirement: A SaaS vendor permits traffic only from a preapproved public address but users traverse changing cloud egress. The relevant verification here is: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
Question 538
What observable result would show that the intended FortiSASE PoP reachability to hub private routes behavior has been restored? Following a production change affecting Mistral Education in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Authorized users reach spoke-hosted services through the hub's protected WAN routing.
- The intended private subnet has a viable overlay route from the user's PoP.
- A second authorized hub sustains private-app connectivity during a single-hub fault.
- Security inspection is routed using the allowed geographic scope with documented exceptions.
Explanation
Correct Answer
B:Correct: The intended private subnet has a viable overlay route from the user's PoP. That result demonstrates the requested controlled repair and avoids the failure mode: Cloud-user authentication alone does not create private SD-WAN reachability. [Case R161-C108; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0538.]
Incorrect Answers
A:That intervention addresses SD-WAN hub as private-access exchange: Cloud-authenticated remote users can reach the corporate hub but not a spoke-hosted file service. The case-specific requirement is: The intended private subnet has a viable overlay route from the user's PoP. Verify it with: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
C:That intervention addresses Single-hub versus dual-hub SPA design: An enterprise wants high availability but its FortiSASE integration still uses a single hub endpoint. The case-specific requirement is: The intended private subnet has a viable overlay route from the user's PoP. Verify it with: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
D:Incorrect for this case: Security inspection is routed using the allowed geographic scope with documented exceptions. concerns the separate issue of Sovereign access-point selection (A tenant's security architecture requires traffic inspection to remain within approved geographic PoPs.). It does not directly establish The intended private subnet has a viable overlay route from the user's PoP. The case-specific evidence is Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. [Case R161-C108; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0538.]
Question 539
Which failure mechanism BEST explains the FortiSASE PoP reachability to hub private routes observation before a repair is attempted? Following a production change affecting Mistral Education in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- An agentless web-only proxy is mismatched to the application's private UDP transport.
- Cloud-user authentication alone does not create private SD-WAN reachability.
- Dynamic shared egress addresses can break vendor IP allowlisting.
- A browser-only proxy is not equivalent to the requested managed full-tunnel mode.
Explanation
Correct Answer
B:Correct: Cloud-user authentication alone does not create private SD-WAN reachability. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. [Case R161-C108; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0539.]
Incorrect Answers
A:Incorrect diagnosis: this describes a different operational mechanism (Agentless SPA requirement classification), not the documented observation (Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN.). The supported case diagnosis is Cloud-user authentication alone does not create private SD-WAN reachability. [Case R161-C108; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0539.]
C:The Dedicated public egress IP requirement diagnosis does not explain the observed case: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. The supported diagnosis is: Cloud-user authentication alone does not create private SD-WAN reachability.
D:The Agent-based remote-user secure internet access diagnosis does not explain the observed case: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. The supported diagnosis is: Cloud-user authentication alone does not create private SD-WAN reachability.
Question 540
Select THREE correct elements of a safe remedy-and-evidence plan for the FortiSASE PoP reachability to hub private routes case. Following a production change affecting Mistral Education in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix.
- The intended private subnet has a viable overlay route from the user's PoP.
- Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
- Use a supported dedicated public IP egress capability with validated policy and licensing assumptions.
- Test a public website and a private address, recording PoP, return path and matching policy for both.
- Protected browser sessions pass through the cloud proxy without requiring an endpoint agent.
Explanation
Correct Answers
A:Correct remediation element: Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix. It addresses Cloud-user authentication alone does not create private SD-WAN reachability. [Case R161-C108; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0540.]
B:The intended private subnet has a viable overlay route from the user's PoP. This confirms the case-specific path or security boundary.
C:Correct verification element: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test. This independently measures whether the intended change works. [Case R161-C108; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0540.]
Incorrect Answers
D:That intervention addresses Dedicated public egress IP requirement: A SaaS vendor permits traffic only from a preapproved public address but users traverse changing cloud egress. The case-specific requirement is: Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix. Verify it with: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
E:That intervention addresses Selective private versus internet access: Remote users must send general web traffic to cloud inspection but private application traffic over approved SPA. The relevant verification here is: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
F:That intervention addresses Agentless browser-only internet access: A contractor uses a device on which the enterprise cannot install FortiClient but must secure browser traffic. The case-specific requirement is: The intended private subnet has a viable overlay route from the user's PoP. Verify it with: Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests