100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 630
Select THREE correct elements of a safe remedy-and-evidence plan for the Agentless SPA requirement classification case. Following a production change affecting Cascade Commerce in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: A customer proposes an agentless web proxy for a private UDP application that must not be public. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge.
- Test the actual application's UDP flow and verify which permitted SPA architecture carries it.
- Verify the PoP-as-spoke IPsec/BGP route exchange to the hub and advertise the authorized private prefix.
- Security inspection is routed using the allowed geographic scope with documented exceptions.
- Choose the documented SPA method that supports the transport and client capabilities, rather than assuming SWG proxy handles UDP private services.
- The private application is accessed using a supported secure transport path.
Explanation
Correct Answers
B:Correct verification element: Test the actual application's UDP flow and verify which permitted SPA architecture carries it. This independently measures whether the intended change works. [Case R161-C126; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0630.]
E:Correct remediation element: Choose the documented SPA method that supports the transport and client capabilities, rather than assuming SWG proxy handles UDP private services. It addresses An agentless web-only proxy is mismatched to the application's private UDP transport. [Case R161-C126; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0630.]
F:The private application is accessed using a supported secure transport path. This confirms the case-specific path or security boundary.
Incorrect Answers
A:Incorrect for this case: Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge. concerns the separate issue of Site on-ramp for nonagent branch users (A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support.). It does not directly establish Test the actual application's UDP flow and verify which permitted SPA architecture carries it. The case-specific evidence is Test the actual application's UDP flow and verify which permitted SPA architecture carries it. [Case R161-C126; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0630.]
C:That intervention addresses FortiSASE PoP reachability to hub private routes: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. The case-specific requirement is: Choose the documented SPA method that supports the transport and client capabilities, rather than assuming SWG proxy handles UDP private services. Verify it with: Test the actual application's UDP flow and verify which permitted SPA architecture carries it.
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 private application is accessed using a supported secure transport path. The case-specific evidence is Test the actual application's UDP flow and verify which permitted SPA architecture carries it. [Case R161-C126; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0630.]
Question 631
Which corrective action MOST DIRECTLY addresses the observed Asymmetric routing across SASE and SD-WAN problem within the approved change scope? During a scoped remote campus corridor deployment across a staged branch cohort, Brookfield Media must commission the planned FortiSASE/SD-WAN control. The operational finding is: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. The change ticket limits modifications to the new branch group and requires a reversible test.
- Model FortiSASE PoPs as spokes via the documented SPA IPsec/BGP integration with its FortiGate hubs.
- Create separate policy identities/scopes for site-based edge sessions and individual remote-user sessions.
- Select private log-forwarding access and validate the SPA route and trusted log receiver configuration.
- Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design.
Explanation
Correct Answer
D:Correct: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. The targeted remedy is Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design. This addresses a mismatched return path breaks stateful access despite successful forward routing. Confirm it by: Capture both request and response paths and verify a stable stateful session after routing correction. [Case R161-C127; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0631.]
Incorrect Answers
A:Incorrect for this case: Model FortiSASE PoPs as spokes via the documented SPA IPsec/BGP integration with its FortiGate hubs. concerns the separate issue of FortiSASE as SD-WAN spoke (An enterprise wants SASE PoPs to participate in its existing hub-and-spoke routing rather than build unrelated public paths.). It does not directly establish Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design. The case-specific evidence is Capture both request and response paths and verify a stable stateful session after routing correction. [Case R161-C127; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0631.]
B:That intervention addresses Mixed edge and remote-user segmentation: Branch LAN-extension traffic and individual remote-user traffic share FortiSASE but need different access restrictions. The case-specific requirement is: Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design. Verify it with: Capture both request and response paths and verify a stable stateful session after routing correction.
C:Incorrect for this case: Select private log-forwarding access and validate the SPA route and trusted log receiver configuration. concerns the separate issue of Private FortiAnalyzer behind SPA (The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub.). It does not directly establish Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design. The case-specific evidence is Capture both request and response paths and verify a stable stateful session after routing correction. [Case R161-C127; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0631.]
Question 632
Which independent diagnostic check best validates that the Asymmetric routing across SASE and SD-WAN repair works? During a scoped remote campus corridor deployment across a staged branch cohort, Brookfield Media must commission the planned FortiSASE/SD-WAN control. The operational finding is: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. The change ticket limits modifications to the new branch group and requires a reversible test.
- Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
- Disable the primary hub and inspect PoP tunnel state, route preference and private-app reachability.
- Capture both request and response paths and verify a stable stateful session after routing correction.
- Send traffic from an agentless branch host and check the edge-to-PoP transport and applied SIA security policy.
Explanation
Correct Answer
C:Correct: Capture both request and response paths and verify a stable stateful session after routing correction. This directly tests the failure mechanism and the required acceptance evidence: Both directions traverse compatible secure paths and private sessions complete. [Case R161-C127; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0632.]
Incorrect Answers
A:That intervention addresses Private FortiAnalyzer behind SPA: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. The relevant verification here is: Capture both request and response paths and verify a stable stateful session after routing correction.
B:That intervention addresses Dual-hub SPA resilience: A remote-user SPA design has two datacenters but only the primary hub is associated with the SASE integration. The relevant verification here is: Capture both request and response paths and verify a stable stateful session after routing correction.
D:Incorrect for this case: Send traffic from an agentless branch host and check the edge-to-PoP transport and applied SIA security policy. concerns the separate issue of Site-based SIA for edge branches (A remote branch has many IoT devices that cannot run individual endpoint agents but need inspected internet access.). It does not directly establish Capture both request and response paths and verify a stable stateful session after routing correction. The case-specific evidence is Capture both request and response paths and verify a stable stateful session after routing correction. [Case R161-C127; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0632.]
Question 633
What observable result would show that the intended Asymmetric routing across SASE and SD-WAN behavior has been restored? During a scoped remote campus corridor deployment across a staged branch cohort, Brookfield Media must commission the planned FortiSASE/SD-WAN control. The operational finding is: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. The change ticket limits modifications to the new branch group and requires a reversible test.
- Each customer receives only its subscribed capabilities and delegated administrative boundary.
- Both directions traverse compatible secure paths and private sessions complete.
- The intended private subnet has a viable overlay route from the user's PoP.
- Internet and private workloads follow their intended separate security paths.
Explanation
Correct Answer
B:Correct: Both directions traverse compatible secure paths and private sessions complete. That result demonstrates the requested controlled repair and avoids the failure mode: A mismatched return path breaks stateful access despite successful forward routing. [Case R161-C127; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0633.]
Incorrect Answers
A:Incorrect for this case: Each customer receives only its subscribed capabilities and delegated administrative boundary. concerns the separate issue of MSSP customer provisioning separation (An MSSP operator is onboarding two customers with different licenses, policies and delegated admins.). It does not directly establish Both directions traverse compatible secure paths and private sessions complete. The case-specific evidence is Capture both request and response paths and verify a stable stateful session after routing correction. [Case R161-C127; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0633.]
C:That intervention addresses FortiSASE PoP reachability to hub private routes: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. The case-specific requirement is: Both directions traverse compatible secure paths and private sessions complete. Verify it with: Capture both request and response paths and verify a stable stateful session after routing correction.
D: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: Both directions traverse compatible secure paths and private sessions complete. Verify it with: Capture both request and response paths and verify a stable stateful session after routing correction.
Question 634
Which failure mechanism BEST explains the Asymmetric routing across SASE and SD-WAN observation before a repair is attempted? During a scoped remote campus corridor deployment across a staged branch cohort, Brookfield Media must commission the planned FortiSASE/SD-WAN control. The operational finding is: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. The change ticket limits modifications to the new branch group and requires a reversible test.
- A mismatched return path breaks stateful access despite successful forward routing.
- A per-user agent tunnel cannot be assumed on unmanaged factory endpoints.
- 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
A:Correct: A mismatched return path breaks stateful access despite successful forward routing. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Capture both request and response paths and verify a stable stateful session after routing correction. [Case R161-C127; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0634.]
Incorrect Answers
B:The Site on-ramp for nonagent branch users diagnosis does not explain the observed case: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. The supported diagnosis is: A mismatched return path breaks stateful access despite successful forward routing.
C:The Dedicated public egress IP requirement diagnosis does not explain the observed case: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. The supported diagnosis is: A mismatched return path breaks stateful access despite successful forward routing.
D:The Agent-based remote-user secure internet access diagnosis does not explain the observed case: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. The supported diagnosis is: A mismatched return path breaks stateful access despite successful forward routing.
Question 635
Select TWO correct elements of a safe remedy-and-evidence plan for the Asymmetric routing across SASE and SD-WAN case. During a scoped remote campus corridor deployment across a staged branch cohort, Brookfield Media must commission the planned FortiSASE/SD-WAN control. The operational finding is: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. The change ticket limits modifications to the new branch group and requires a reversible test.
- Each customer receives only its subscribed capabilities and delegated administrative boundary.
- Capture both request and response paths and verify a stable stateful session after routing correction.
- Connect a supported branch edge or LAN-extension device into the FortiSASE SIA path under site-based policy.
- Inspect PoP-side and hub-side learned routes and an end-to-end private-app test.
- Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design.
Explanation
Correct Answers
B:Correct verification element: Capture both request and response paths and verify a stable stateful session after routing correction. This independently measures whether the intended change works. [Case R161-C127; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0635.]
E:Correct remediation element: Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design. It addresses A mismatched return path breaks stateful access despite successful forward routing. [Case R161-C127; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0635.]
Incorrect Answers
A:Incorrect for this case: Each customer receives only its subscribed capabilities and delegated administrative boundary. concerns the separate issue of MSSP customer provisioning separation (An MSSP operator is onboarding two customers with different licenses, policies and delegated admins.). It does not directly establish Both directions traverse compatible secure paths and private sessions complete. The case-specific evidence is Capture both request and response paths and verify a stable stateful session after routing correction. [Case R161-C127; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0635.]
C:Incorrect for this case: Connect a supported branch edge or LAN-extension device into the FortiSASE SIA path under site-based policy. concerns the separate issue of Site on-ramp for nonagent branch users (A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support.). It does not directly establish Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design. The case-specific evidence is Capture both request and response paths and verify a stable stateful session after routing correction. [Case R161-C127; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0635.]
D:That intervention addresses FortiSASE PoP reachability to hub private routes: Remote users authenticate successfully but cannot reach an internal subnet through SPA over SD-WAN. The relevant verification here is: Capture both request and response paths and verify a stable stateful session after routing correction.
Question 636
Which corrective action MOST DIRECTLY addresses the observed Asymmetric routing across SASE and SD-WAN problem within the approved change scope? Following a production change affecting Stonebridge Markets in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- Connect a supported branch edge or LAN-extension device into the FortiSASE SIA path under site-based policy.
- Deploy the supported agentless explicit-proxy/SWG method with user authentication and scoped browser policies.
- Select private log-forwarding access and validate the SPA route and trusted log receiver configuration.
- Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design.
Explanation
Correct Answer
D:Correct: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. The targeted remedy is Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design. This addresses a mismatched return path breaks stateful access despite successful forward routing. Confirm it by: Capture both request and response paths and verify a stable stateful session after routing correction. [Case R161-C128; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0636.]
Incorrect Answers
A:Incorrect for this case: Connect a supported branch edge or LAN-extension device into the FortiSASE SIA path under site-based policy. concerns the separate issue of Site on-ramp for nonagent branch users (A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support.). It does not directly establish Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design. The case-specific evidence is Capture both request and response paths and verify a stable stateful session after routing correction. [Case R161-C128; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0636.]
B: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: Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design. Verify it with: Capture both request and response paths and verify a stable stateful session after routing correction.
C:Incorrect for this case: Select private log-forwarding access and validate the SPA route and trusted log receiver configuration. concerns the separate issue of Private FortiAnalyzer behind SPA (The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub.). It does not directly establish Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design. The case-specific evidence is Capture both request and response paths and verify a stable stateful session after routing correction. [Case R161-C128; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0636.]
Question 637
Which independent diagnostic check best validates that the Asymmetric routing across SASE and SD-WAN repair works? Following a production change affecting Stonebridge Markets in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge.
- Configure a test browser to use the FortiSASE proxy and inspect authentication and web-policy logs.
- Validate return-path routing and test both TCP and UDP private-app sessions through a qualified PoP.
- Capture both request and response paths and verify a stable stateful session after routing correction.
Explanation
Correct Answer
D:Correct: Capture both request and response paths and verify a stable stateful session after routing correction. This directly tests the failure mechanism and the required acceptance evidence: Both directions traverse compatible secure paths and private sessions complete. [Case R161-C128; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0637.]
Incorrect Answers
A:That intervention addresses Site on-ramp for nonagent branch users: A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support. The relevant verification here is: Capture both request and response paths and verify a stable stateful session after routing correction.
B: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 relevant verification here is: Capture both request and response paths and verify a stable stateful session after routing correction.
C: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 relevant verification here is: Capture both request and response paths and verify a stable stateful session after routing correction.
Question 638
What observable result would show that the intended Asymmetric routing across SASE and SD-WAN behavior has been restored? Following a production change affecting Stonebridge Markets in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- Both directions traverse compatible secure paths and private sessions complete.
- The allowed users originate from the authorized egress identity without arbitrary source changes.
- Cloud events arrive securely at the internal collector without public exposure.
- The cloud edge participates in authorized private routing while the hub policy remains in control.
Explanation
Correct Answer
A:Correct: Both directions traverse compatible secure paths and private sessions complete. That result demonstrates the requested controlled repair and avoids the failure mode: A mismatched return path breaks stateful access despite successful forward routing. [Case R161-C128; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0638.]
Incorrect Answers
B: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: Both directions traverse compatible secure paths and private sessions complete. Verify it with: Capture both request and response paths and verify a stable stateful session after routing correction.
C:That intervention addresses Private FortiAnalyzer behind SPA: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. The case-specific requirement is: Both directions traverse compatible secure paths and private sessions complete. Verify it with: Capture both request and response paths and verify a stable stateful session after routing correction.
D:That intervention addresses FortiSASE as SD-WAN spoke: An enterprise wants SASE PoPs to participate in its existing hub-and-spoke routing rather than build unrelated public paths. The case-specific requirement is: Both directions traverse compatible secure paths and private sessions complete. Verify it with: Capture both request and response paths and verify a stable stateful session after routing correction.
Question 639
Which failure mechanism BEST explains the Asymmetric routing across SASE and SD-WAN observation before a repair is attempted? Following a production change affecting Stonebridge Markets in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- Treating the access point as an arbitrary full-featured FortiGate substitutes unsupported edge assumptions.
- Treating all traffic as public web browsing masks private-app routing requirements.
- Unscoped shared administration exposes unrelated customer settings.
- A mismatched return path breaks stateful access despite successful forward routing.
Explanation
Correct Answer
D:Correct: A mismatched return path breaks stateful access despite successful forward routing. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Capture both request and response paths and verify a stable stateful session after routing correction. [Case R161-C128; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0639.]
Incorrect Answers
A:The Branch FortiAP as SASE edge diagnosis does not explain the observed case: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. The supported diagnosis is: A mismatched return path breaks stateful access despite successful forward routing.
B:The Selective private versus internet access diagnosis does not explain the observed case: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. The supported diagnosis is: A mismatched return path breaks stateful access despite successful forward routing.
C:The MSSP customer provisioning separation diagnosis does not explain the observed case: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. The supported diagnosis is: A mismatched return path breaks stateful access despite successful forward routing.
Question 640
Select THREE correct elements of a safe remedy-and-evidence plan for the Asymmetric routing across SASE and SD-WAN case. Following a production change affecting Stonebridge Markets in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- Capture both request and response paths and verify a stable stateful session after routing correction.
- Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design.
- Remote users retain secure private access through the approved secondary hub.
- Model FortiSASE PoPs as spokes via the documented SPA IPsec/BGP integration with its FortiGate hubs.
- Send traffic from an agentless branch host and check the edge-to-PoP transport and applied SIA security policy.
- Both directions traverse compatible secure paths and private sessions complete.
Explanation
Correct Answers
A:Correct verification element: Capture both request and response paths and verify a stable stateful session after routing correction. This independently measures whether the intended change works. [Case R161-C128; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0640.]
B:Correct remediation element: Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design. It addresses A mismatched return path breaks stateful access despite successful forward routing. [Case R161-C128; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0640.]
F:Both directions traverse compatible secure paths and private sessions complete. This confirms the case-specific path or security boundary.
Incorrect Answers
C:That intervention addresses Dual-hub SPA resilience: A remote-user SPA design has two datacenters but only the primary hub is associated with the SASE integration. The case-specific requirement is: Both directions traverse compatible secure paths and private sessions complete. Verify it with: Capture both request and response paths and verify a stable stateful session after routing correction.
D:Incorrect for this case: Model FortiSASE PoPs as spokes via the documented SPA IPsec/BGP integration with its FortiGate hubs. concerns the separate issue of FortiSASE as SD-WAN spoke (An enterprise wants SASE PoPs to participate in its existing hub-and-spoke routing rather than build unrelated public paths.). It does not directly establish Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design. The case-specific evidence is Capture both request and response paths and verify a stable stateful session after routing correction. [Case R161-C128; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0640.]
E:Incorrect for this case: Send traffic from an agentless branch host and check the edge-to-PoP transport and applied SIA security policy. concerns the separate issue of Site-based SIA for edge branches (A remote branch has many IoT devices that cannot run individual endpoint agents but need inspected internet access.). It does not directly establish Capture both request and response paths and verify a stable stateful session after routing correction. The case-specific evidence is Capture both request and response paths and verify a stable stateful session after routing correction. [Case R161-C128; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0640.]
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests