100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 520
Select THREE correct elements of a safe remedy-and-evidence plan for the Selective private versus internet access case. Following a production change affecting Aster Research in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: Remote users must send general web traffic to cloud inspection but private application traffic over approved SPA. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- Internet and private workloads follow their intended separate security paths.
- Separate SIA and SPA use cases with explicit destination classifications and the appropriate FortiSASE and hub controls.
- Test a public website and a private address, recording PoP, return path and matching policy for both.
- Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design.
- Both normal and failover hubs advertise viable private application paths to PoPs.
- Compare IPsec SA state and BGP advertisements between a PoP and each configured hub.
Explanation
Correct Answers
A:Internet and private workloads follow their intended separate security paths. This confirms the case-specific path or security boundary.
B:Correct remediation element: Separate SIA and SPA use cases with explicit destination classifications and the appropriate FortiSASE and hub controls. It addresses Treating all traffic as public web browsing masks private-app routing requirements. [Case R161-C104; Fortinet task I1; anchors EXAM, SASE_USE, SASE_SIA.] [Question R161-Q0520.]
C:Correct verification element: Test a public website and a private address, recording PoP, return path and matching policy for both. This independently measures whether the intended change works. [Case R161-C104; Fortinet task I1; anchors EXAM, SASE_USE, SASE_SIA.] [Question R161-Q0520.]
Incorrect Answers
D:Incorrect for this case: Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design. concerns the separate issue of Asymmetric routing across SASE and SD-WAN (Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops.). It does not directly establish Separate SIA and SPA use cases with explicit destination classifications and the appropriate FortiSASE and hub controls. The case-specific evidence is Test a public website and a private address, recording PoP, return path and matching policy for both. [Case R161-C104; Fortinet task I1; anchors EXAM, SASE_USE, SASE_SIA.] [Question R161-Q0520.]
E:Incorrect for this case: Both normal and failover hubs advertise viable private application paths to PoPs. concerns the separate issue of 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.). It does not directly establish Internet and private workloads follow their intended separate security paths. The case-specific evidence is Test a public website and a private address, recording PoP, return path and matching policy for both. [Case R161-C104; Fortinet task I1; anchors EXAM, SASE_USE, SASE_SIA.] [Question R161-Q0520.]
F:Incorrect for this case: Compare IPsec SA state and BGP advertisements between a PoP and each configured hub. 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 Test a public website and a private address, recording PoP, return path and matching policy for both. The case-specific evidence is Test a public website and a private address, recording PoP, return path and matching policy for both. [Case R161-C104; Fortinet task I1; anchors EXAM, SASE_USE, SASE_SIA.] [Question R161-Q0520.]
Question 521
Which corrective action MOST DIRECTLY addresses the observed Site on-ramp for nonagent branch users problem within the approved change scope? During a scoped coastal district deployment across a staged branch cohort, Pinehaven Distribution must commission the planned FortiSASE/SD-WAN control. The operational finding is: A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support. The change ticket limits modifications to the affected production application and requires a reversible test.
- Choose the documented SPA method that supports the transport and client capabilities, rather than assuming SWG proxy handles UDP private services.
- Separate SIA and SPA use cases with explicit destination classifications and the appropriate FortiSASE and hub controls.
- Use the vendor-supported tenant and service provisioning workflow with customer-specific administrator scope.
- Connect a supported branch edge or LAN-extension device into the FortiSASE SIA path under site-based policy.
Explanation
Correct Answer
D:Correct: A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support. The targeted remedy is Connect a supported branch edge or LAN-extension device into the FortiSASE SIA path under site-based policy. This addresses a per-user agent tunnel cannot be assumed on unmanaged factory endpoints. Confirm it by: Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge. [Case R161-C105; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0521.]
Incorrect Answers
A:That intervention addresses Agentless SPA requirement classification: A customer proposes an agentless web proxy for a private UDP application that must not be public. 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.
B: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: 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.
C: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: 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 522
Which independent diagnostic check best validates that the Site on-ramp for nonagent branch users repair works? During a scoped coastal district deployment across a staged branch cohort, Pinehaven Distribution must commission the planned FortiSASE/SD-WAN control. The operational finding is: A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support. The change ticket limits modifications to the affected production application and requires a reversible test.
- Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge.
- Fail the primary hub and observe PoP-to-secondary route selection and application continuity.
- Inspect chosen PoP region and data-flow documentation for a geographically restricted test cohort.
- Configure a test browser to use the FortiSASE proxy and inspect authentication and web-policy logs.
Explanation
Correct Answer
A:Correct: Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge. This directly tests the failure mechanism and the required acceptance evidence: Agentless branch terminals inherit approved cloud enforcement through the edge. [Case R161-C105; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0522.]
Incorrect Answers
B:Incorrect for this case: Fail the primary hub and observe PoP-to-secondary route selection and application continuity. concerns the separate issue of Single-hub versus dual-hub SPA design (An enterprise wants high availability but its FortiSASE integration still uses a single hub endpoint.). It does not directly establish Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge. The case-specific evidence is Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge. [Case R161-C105; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0522.]
C:That intervention addresses Sovereign access-point selection: A tenant's security architecture requires traffic inspection to remain within approved geographic PoPs. The relevant verification here is: Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge.
D: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: Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge.
Question 523
What observable result would show that the intended Site on-ramp for nonagent branch users behavior has been restored? During a scoped coastal district deployment across a staged branch cohort, Pinehaven Distribution must commission the planned FortiSASE/SD-WAN control. The operational finding is: A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support. The change ticket limits modifications to the affected production application and requires a reversible test.
- The allowed users originate from the authorized egress identity without arbitrary source changes.
- Approved private UDP services become reachable without exposing them to the public internet.
- Agentless branch terminals inherit approved cloud enforcement through the edge.
- Branch devices receive centrally enforced cloud internet inspection without agents on every host.
Explanation
Correct Answer
C:Correct: Agentless branch terminals inherit approved cloud enforcement through the edge. That result demonstrates the requested controlled repair and avoids the failure mode: A per-user agent tunnel cannot be assumed on unmanaged factory endpoints. [Case R161-C105; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0523.]
Incorrect Answers
A: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: 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.
B:Incorrect for this case: Approved private UDP services become reachable without exposing them to the public internet. concerns the separate issue of Private TCP and UDP application access (Remote workers need access to a private UDP-dependent application hosted behind an SD-WAN hub.). It does not directly establish Agentless branch terminals inherit approved cloud enforcement through the edge. The case-specific evidence is Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge. [Case R161-C105; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0523.]
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: 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.
Question 524
Which failure mechanism BEST explains the Site on-ramp for nonagent branch users observation before a repair is attempted? During a scoped coastal district deployment across a staged branch cohort, Pinehaven Distribution must commission the planned FortiSASE/SD-WAN control. The operational finding is: A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support. The change ticket limits modifications to the affected production application and requires a reversible test.
- A mismatched return path breaks stateful access despite successful forward routing.
- Redundant branch uplinks alone do not remove a single SPA hub dependency.
- A per-user agent tunnel cannot be assumed on unmanaged factory endpoints.
- Endpoint installation requirements make agent-based access infeasible for this user population.
Explanation
Correct Answer
C:Correct: A per-user agent tunnel cannot be assumed on unmanaged factory endpoints. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge. [Case R161-C105; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0524.]
Incorrect Answers
A:The Asymmetric routing across SASE and SD-WAN diagnosis does not explain the observed case: A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support. The supported diagnosis is: A per-user agent tunnel cannot be assumed on unmanaged factory endpoints.
B:The Single-hub versus dual-hub SPA design diagnosis does not explain the observed case: A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support. The supported diagnosis is: A per-user agent tunnel cannot be assumed on unmanaged factory endpoints.
D:Incorrect diagnosis: this describes a different operational mechanism (Agentless browser-only internet access), not the documented observation (A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support.). The supported case diagnosis is A per-user agent tunnel cannot be assumed on unmanaged factory endpoints. [Case R161-C105; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0524.]
Question 525
Select TWO correct elements of a safe remedy-and-evidence plan for the Site on-ramp for nonagent branch users case. During a scoped coastal district deployment across a staged branch cohort, Pinehaven Distribution must commission the planned FortiSASE/SD-WAN control. The operational finding is: A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support. The change ticket limits modifications to the affected production application and requires a reversible test.
- Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge.
- 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.
- Approved private UDP services become reachable without exposing them to the public internet.
- Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership.
Explanation
Correct Answers
A: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-C105; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0525.]
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-C105; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0525.]
Incorrect Answers
B:That intervention addresses Asymmetric routing across SASE and SD-WAN: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. The relevant verification here is: Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge.
D:Incorrect for this case: Approved private UDP services become reachable without exposing them to the public internet. concerns the separate issue of Private TCP and UDP application access (Remote workers need access to a private UDP-dependent application hosted behind an SD-WAN hub.). It does not directly establish Agentless branch terminals inherit approved cloud enforcement through the edge. The case-specific evidence is Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge. [Case R161-C105; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0525.]
E: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 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 526
Which corrective action MOST DIRECTLY addresses the observed Site on-ramp for nonagent branch users problem within the approved change scope? 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.
- Connect a supported branch edge or LAN-extension device into the FortiSASE SIA path under site-based policy.
- Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design.
- Use the supported FortiClient agent-based SIA mode with the appropriate endpoint profile and FortiSASE security policy.
- Select an SPA architecture using SD-WAN/IPsec overlays that supports private TCP and UDP workloads.
Explanation
Correct Answer
A:Correct: A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support. The targeted remedy is Connect a supported branch edge or LAN-extension device into the FortiSASE SIA path under site-based policy. This addresses a per-user agent tunnel cannot be assumed on unmanaged factory endpoints. Confirm it by: Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge. [Case R161-C106; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0526.]
Incorrect Answers
B:That intervention addresses Asymmetric routing across SASE and SD-WAN: Private-app requests arrive through an SPA hub but replies follow public DIA, causing session drops. 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.
C:That intervention addresses Agent-based remote-user secure internet access: Managed laptops require full-tunnel policy enforcement when users browse from unmanaged networks. 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.
D: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: 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 527
Which independent diagnostic check best validates that the Site on-ramp for nonagent branch users repair works? 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.
- Test a public website and a private address, recording PoP, return path and matching policy for both.
- Inspect end-to-end PoP to hub to spoke path and a permitted file-service session.
- Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge.
- Fail the primary hub and observe PoP-to-secondary route selection and application continuity.
Explanation
Correct Answer
C:Correct: Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge. This directly tests the failure mechanism and the required acceptance evidence: Agentless branch terminals inherit approved cloud enforcement through the edge. [Case R161-C106; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0527.]
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 relevant verification here is: Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge.
B: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 relevant verification here is: Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge.
D:Incorrect for this case: Fail the primary hub and observe PoP-to-secondary route selection and application continuity. concerns the separate issue of Single-hub versus dual-hub SPA design (An enterprise wants high availability but its FortiSASE integration still uses a single hub endpoint.). It does not directly establish Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge. The case-specific evidence is Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge. [Case R161-C106; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0527.]
Question 528
What observable result would show that the intended Site on-ramp for nonagent branch users behavior has been restored? 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.
- Protected browser sessions pass through the cloud proxy without requiring an endpoint agent.
- The private application is accessed using a supported secure transport path.
- Agentless branch terminals inherit approved cloud enforcement through the edge.
- Security inspection is routed using the allowed geographic scope with documented exceptions.
Explanation
Correct Answer
C:Correct: Agentless branch terminals inherit approved cloud enforcement through the edge. That result demonstrates the requested controlled repair and avoids the failure mode: 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-Q0528.]
Incorrect Answers
A: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: 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.
B:That intervention addresses Agentless SPA requirement classification: A customer proposes an agentless web proxy for a private UDP application that must not be public. 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.
D: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: 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.
Question 529
Which failure mechanism BEST explains the Site on-ramp for nonagent branch users observation before a repair is attempted? 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.
- A global proximity-based PoP default does not by itself prove data-residency compliance.
- A per-user agent tunnel cannot be assumed on unmanaged factory endpoints.
- Endpoint installation requirements make agent-based access infeasible for this user population.
- A TCP-only ZTNA access-proxy approach does not meet the stated UDP requirement.
Explanation
Correct Answer
B:Correct: A per-user agent tunnel cannot be assumed on unmanaged factory endpoints. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Compare on-ramp connectivity and inspected traffic from an appliance behind the branch edge. [Case R161-C106; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0529.]
Incorrect Answers
A:The Sovereign access-point selection diagnosis does not explain the observed case: A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support. The supported diagnosis is: A per-user agent tunnel cannot be assumed on unmanaged factory endpoints.
C:Incorrect diagnosis: this describes a different operational mechanism (Agentless browser-only internet access), not the documented observation (A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support.). The supported case diagnosis is 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-Q0529.]
D:The Private TCP and UDP application access diagnosis does not explain the observed case: A factory branch needs FortiSASE web inspection but its terminals lack FortiClient support. The supported diagnosis is: A per-user agent tunnel cannot be assumed on unmanaged factory endpoints.
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.
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests