100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 600
Select THREE correct elements of a safe remedy-and-evidence plan for the SPA route propagation through dual hubs case. Following a production change affecting Bluewater Freight in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Validate return-path routing and test both TCP and UDP private-app sessions through a qualified PoP.
- Both normal and failover hubs advertise viable private application paths to PoPs.
- Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays.
- Agentless branch terminals inherit approved cloud enforcement through the edge.
- Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
- Model FortiSASE PoPs as spokes via the documented SPA IPsec/BGP integration with its FortiGate hubs.
Explanation
Correct Answers
B:Both normal and failover hubs advertise viable private application paths to PoPs. This confirms the case-specific path or security boundary.
C:Correct remediation element: Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays. It addresses Cloud SPA routes were configured only for the primary hub. [Case R161-C120; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0600.]
E:Correct verification element: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. This independently measures whether the intended change works. [Case R161-C120; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0600.]
Incorrect Answers
A:Incorrect for this case: Validate return-path routing and test both TCP and UDP private-app sessions through a qualified PoP. 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 Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. The case-specific evidence is Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. [Case R161-C120; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0600.]
D:Incorrect for this case: Agentless branch terminals inherit approved cloud enforcement through the 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 Both normal and failover hubs advertise viable private application paths to PoPs. The case-specific evidence is Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes. [Case R161-C120; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0600.]
F: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: Ensure the approved private prefixes are propagated consistently across both hub-to-PoP SPA overlays. Verify it with: Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
Question 601
Which corrective action MOST DIRECTLY addresses the observed SD-WAN and SASE split security ownership problem within the approved change scope? During a scoped coastal district deployment across a staged branch cohort, Seaboard Financial must commission the planned FortiSASE/SD-WAN control. The operational finding is: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. The change ticket limits modifications to the new branch group and requires a reversible test.
- Select private log-forwarding access and validate the SPA route and trusted log receiver configuration.
- 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.
- Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership.
Explanation
Correct Answer
D:Correct: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. The targeted remedy is Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership. This addresses a local dia preference silently bypasses the intended sase inspection path. Confirm it by: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. [Case R161-C121; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0601.]
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 case-specific requirement is: Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership. Verify it with: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
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: Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership. Verify it with: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
C: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: Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership. Verify it with: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
Question 602
Which independent diagnostic check best validates that the SD-WAN and SASE split security ownership repair works? During a scoped coastal district deployment across a staged branch cohort, Seaboard Financial must commission the planned FortiSASE/SD-WAN control. The operational finding is: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. The change ticket limits modifications to the new branch group and requires a reversible test.
- Send traffic from an agentless branch host and check the edge-to-PoP transport and applied SIA security policy.
- Test a public website and a private address, recording PoP, return path and matching policy for both.
- Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
- Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
Explanation
Correct Answer
D:Correct: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. This directly tests the failure mechanism and the required acceptance evidence: The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles. [Case R161-C121; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0602.]
Incorrect Answers
A: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: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
B:Incorrect for this case: Test a public website and a private address, recording PoP, return path and matching policy for both. concerns the separate issue of Selective private versus internet access (Remote users must send general web traffic to cloud inspection but private application traffic over approved SPA.). It does not directly establish Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. The case-specific evidence is Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. [Case R161-C121; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0602.]
C:Incorrect for this case: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status. 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 Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. The case-specific evidence is Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. [Case R161-C121; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0602.]
Question 603
What observable result would show that the intended SD-WAN and SASE split security ownership behavior has been restored? During a scoped coastal district deployment across a staged branch cohort, Seaboard Financial must commission the planned FortiSASE/SD-WAN control. The operational finding is: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. The change ticket limits modifications to the new branch group and requires a reversible test.
- Security inspection is routed using the allowed geographic scope with documented exceptions.
- The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles.
- The cloud edge participates in authorized private routing while the hub policy remains in control.
- Remote users retain secure private access through the approved secondary hub.
Explanation
Correct Answer
B:Correct: The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles. That result demonstrates the requested controlled repair and avoids the failure mode: A local DIA preference silently bypasses the intended SASE inspection path. [Case R161-C121; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0603.]
Incorrect Answers
A: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: The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles. Verify it with: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
C: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: The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles. Verify it with: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
D:Incorrect for this case: Remote users retain secure private access through the approved secondary hub. concerns the separate issue of Dual-hub SPA resilience (A remote-user SPA design has two datacenters but only the primary hub is associated with the SASE integration.). It does not directly establish The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles. The case-specific evidence is Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. [Case R161-C121; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0603.]
Question 604
Which failure mechanism BEST explains the SD-WAN and SASE split security ownership observation before a repair is attempted? During a scoped coastal district deployment across a staged branch cohort, Seaboard Financial must commission the planned FortiSASE/SD-WAN control. The operational finding is: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. The change ticket limits modifications to the new branch group and requires a reversible test.
- A local DIA preference silently bypasses the intended SASE inspection path.
- A per-user agent tunnel cannot be assumed on unmanaged factory endpoints.
- A private log endpoint is unreachable using public-only forwarding semantics.
- The cloud SPA connection is a single-hub dependency despite regional redundancy elsewhere.
Explanation
Correct Answer
A:Correct: A local DIA preference silently bypasses the intended SASE inspection path. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. [Case R161-C121; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0604.]
Incorrect Answers
B:The Site on-ramp for nonagent branch users diagnosis does not explain the observed case: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. The supported diagnosis is: A local DIA preference silently bypasses the intended SASE inspection path.
C:The Private FortiAnalyzer behind SPA diagnosis does not explain the observed case: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. The supported diagnosis is: A local DIA preference silently bypasses the intended SASE inspection path.
D:Incorrect diagnosis: this describes a different operational mechanism (Dual-hub SPA resilience), not the documented observation (A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly.). The supported case diagnosis is A local DIA preference silently bypasses the intended SASE inspection path. [Case R161-C121; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0604.]
Question 605
Select TWO correct elements of a safe remedy-and-evidence plan for the SD-WAN and SASE split security ownership case. During a scoped coastal district deployment across a staged branch cohort, Seaboard Financial must commission the planned FortiSASE/SD-WAN control. The operational finding is: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. The change ticket limits modifications to the new branch group and requires a reversible test.
- Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
- Use a FortiGate SD-WAN or supported thin-edge LAN-extension path to FortiSASE for site-based SIA.
- Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership.
- Inspect device registration, edge tunnel and an application policy hit from a WLAN client.
- Internet and private workloads follow their intended separate security paths.
Explanation
Correct Answers
A:Correct verification element: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. This independently measures whether the intended change works. [Case R161-C121; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0605.]
C:Correct remediation element: Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership. It addresses A local DIA preference silently bypasses the intended SASE inspection path. [Case R161-C121; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0605.]
Incorrect Answers
B: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: Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership. Verify it with: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
D:Incorrect for this case: Inspect device registration, edge tunnel and an application policy hit from a WLAN client. concerns the separate issue of Branch FortiAP as SASE edge (An isolated satellite office uses supported FortiAP edge equipment and wants cloud inspection without a local full FortiGate stack.). It does not directly establish Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. The case-specific evidence is Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. [Case R161-C121; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0605.]
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 case-specific requirement is: The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles. Verify it with: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
Question 606
Which corrective action MOST DIRECTLY addresses the observed SD-WAN and SASE split security ownership problem within the approved change scope? Following a production change affecting Orchid Hospitality in its metro branch group, a network team receives repeatable user-impact reports. Its fault evidence is: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- Deploy the supported agentless explicit-proxy/SWG method with user authentication and scoped browser policies.
- Select an SPA architecture using SD-WAN/IPsec overlays that supports private TCP and UDP workloads.
- Create separate policy identities/scopes for site-based edge sessions and individual remote-user sessions.
- Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership.
Explanation
Correct Answer
D:Correct: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. The targeted remedy is Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership. This addresses a local dia preference silently bypasses the intended sase inspection path. Confirm it by: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. [Case R161-C122; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0606.]
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: Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership. Verify it with: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
B: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: Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership. Verify it with: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
C: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: Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership. Verify it with: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
Question 607
Which independent diagnostic check best validates that the SD-WAN and SASE split security ownership repair works? Following a production change affecting Orchid Hospitality in its metro branch group, a network team receives repeatable user-impact reports. Its fault evidence is: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
- Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
- Test a public website and a private address, recording PoP, return path and matching policy for both.
- Inspect device registration, edge tunnel and an application policy hit from a WLAN client.
Explanation
Correct Answer
A:Correct: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. This directly tests the failure mechanism and the required acceptance evidence: The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles. [Case R161-C122; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0607.]
Incorrect Answers
B:Incorrect for this case: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status. 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 Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. The case-specific evidence is Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. [Case R161-C122; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0607.]
C:Incorrect for this case: Test a public website and a private address, recording PoP, return path and matching policy for both. concerns the separate issue of Selective private versus internet access (Remote users must send general web traffic to cloud inspection but private application traffic over approved SPA.). It does not directly establish Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. The case-specific evidence is Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. [Case R161-C122; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0607.]
D:Incorrect for this case: Inspect device registration, edge tunnel and an application policy hit from a WLAN client. concerns the separate issue of Branch FortiAP as SASE edge (An isolated satellite office uses supported FortiAP edge equipment and wants cloud inspection without a local full FortiGate stack.). It does not directly establish Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. The case-specific evidence is Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. [Case R161-C122; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0607.]
Question 608
What observable result would show that the intended SD-WAN and SASE split security ownership behavior has been restored? Following a production change affecting Orchid Hospitality in its metro branch group, a network team receives repeatable user-impact reports. Its fault evidence is: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- Each traffic population receives its appropriate policy without accidental role inheritance.
- The site gains approved SIA through the configured edge device within its supported feature scope.
- Remote users retain secure private access through the approved secondary hub.
- The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles.
Explanation
Correct Answer
D:Correct: The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles. That result demonstrates the requested controlled repair and avoids the failure mode: A local DIA preference silently bypasses the intended SASE inspection path. [Case R161-C122; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0608.]
Incorrect Answers
A: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: The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles. Verify it with: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
B:That intervention addresses Branch FortiAP as SASE edge: An isolated satellite office uses supported FortiAP edge equipment and wants cloud inspection without a local full FortiGate stack. The case-specific requirement is: The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles. Verify it with: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
C:Incorrect for this case: Remote users retain secure private access through the approved secondary hub. concerns the separate issue of Dual-hub SPA resilience (A remote-user SPA design has two datacenters but only the primary hub is associated with the SASE integration.). It does not directly establish The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles. The case-specific evidence is Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. [Case R161-C122; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0608.]
Question 609
Which failure mechanism BEST explains the SD-WAN and SASE split security ownership observation before a repair is attempted? Following a production change affecting Orchid Hospitality in its metro branch group, a network team receives repeatable user-impact reports. Its fault evidence is: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- The cloud SPA connection is a single-hub dependency despite regional redundancy elsewhere.
- Per-device FortiClient deployment is not a viable branch-wide traffic aggregation strategy.
- A local DIA preference silently bypasses the intended SASE inspection path.
- A global proximity-based PoP default does not by itself prove data-residency compliance.
Explanation
Correct Answer
C:Correct: A local DIA preference silently bypasses the intended SASE inspection path. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. [Case R161-C122; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0609.]
Incorrect Answers
A:Incorrect diagnosis: this describes a different operational mechanism (Dual-hub SPA resilience), not the documented observation (A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly.). The supported case diagnosis is A local DIA preference silently bypasses the intended SASE inspection path. [Case R161-C122; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0609.]
B:The Site-based SIA for edge branches diagnosis does not explain the observed case: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. The supported diagnosis is: A local DIA preference silently bypasses the intended SASE inspection path.
D:The Sovereign access-point selection diagnosis does not explain the observed case: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. The supported diagnosis is: A local DIA preference silently bypasses the intended SASE inspection path.
Question 610
Select THREE correct elements of a safe remedy-and-evidence plan for the SD-WAN and SASE split security ownership case. Following a production change affecting Orchid Hospitality in its metro branch group, a network team receives repeatable user-impact reports. Its fault evidence is: A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles.
- Validate the supported FortiAP edge/branch on-ramp deployment model and configure its approved FortiSASE uplink.
- Compare IPsec SA state and BGP advertisements between a PoP and each configured hub.
- Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership.
- The managed endpoint's internet traffic receives the intended cloud security inspection.
- Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
Explanation
Correct Answers
A:The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles. This confirms the case-specific path or security boundary.
D:Correct remediation element: Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership. It addresses A local DIA preference silently bypasses the intended SASE inspection path. [Case R161-C122; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0610.]
F:Correct verification element: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request. This independently measures whether the intended change works. [Case R161-C122; Fortinet task I3; anchors EXAM, SASE_SPA, SPA_ARCH.] [Question R161-Q0610.]
Incorrect Answers
B:That intervention addresses Branch FortiAP as SASE edge: An isolated satellite office uses supported FortiAP edge equipment and wants cloud inspection without a local full FortiGate stack. The case-specific requirement is: Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership. Verify it with: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
C: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 relevant verification here is: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
E: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: The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles. Verify it with: Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests