100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 570
Select THREE correct elements of a safe remedy-and-evidence plan for the FortiSASE as SD-WAN spoke case. Following a production change affecting Juniper Transit Services in its metro branch group, a network team receives repeatable user-impact reports. Its fault evidence is: An enterprise wants SASE PoPs to participate in its existing hub-and-spoke routing rather than build unrelated public paths. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Inspect chosen PoP region and data-flow documentation for a geographically restricted test cohort.
- The cloud edge participates in authorized private routing while the hub policy remains in control.
- The managed endpoint's internet traffic receives the intended cloud security inspection.
- Compare IPsec SA state and BGP advertisements between a PoP and each configured hub.
- Model FortiSASE PoPs as spokes via the documented SPA IPsec/BGP integration with its FortiGate hubs.
- Check hub-to-spoke private routing and firewall permissions in addition to the PoP-to-hub SPA overlay.
Explanation
Correct Answers
B:The cloud edge participates in authorized private routing while the hub policy remains in control. This confirms the case-specific path or security boundary.
D:Correct verification element: Compare IPsec SA state and BGP advertisements between a PoP and each configured hub. This independently measures whether the intended change works. [Case R161-C114; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0570.]
E:Correct remediation element: Model FortiSASE PoPs as spokes via the documented SPA IPsec/BGP integration with its FortiGate hubs. It addresses A disconnected SASE tenant cannot automatically learn protected WAN routes. [Case R161-C114; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0570.]
Incorrect Answers
A:Incorrect for this case: Inspect chosen PoP region and data-flow documentation for a geographically restricted test cohort. 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 Compare IPsec SA state and BGP advertisements between a PoP and each configured hub. The case-specific evidence is Compare IPsec SA state and BGP advertisements between a PoP and each configured hub. [Case R161-C114; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0570.]
C:Incorrect for this case: The managed endpoint's internet traffic receives the intended cloud security inspection. concerns the separate issue of Agent-based remote-user secure internet access (Managed laptops require full-tunnel policy enforcement when users browse from unmanaged networks.). It does not directly establish The cloud edge participates in authorized private routing while the hub policy remains in control. The case-specific evidence is Compare IPsec SA state and BGP advertisements between a PoP and each configured hub. [Case R161-C114; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0570.]
F:That intervention addresses SD-WAN hub as private-access exchange: Cloud-authenticated remote users can reach the corporate hub but not a spoke-hosted file service. The case-specific requirement is: Model FortiSASE PoPs as spokes via the documented SPA IPsec/BGP integration with its FortiGate hubs. Verify it with: Compare IPsec SA state and BGP advertisements between a PoP and each configured hub.
Question 571
Which corrective action MOST DIRECTLY addresses the observed Private FortiAnalyzer behind SPA problem within the approved change scope? During a scoped central region deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. The change ticket limits modifications to the new branch group and requires a reversible test.
- Grant only the approved PoP-origin and private-service flows in the FortiGate SPA hub security 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.
- Validate FortiSASE PoP and data-residency capabilities against the contractual geography before user rollout.
Explanation
Correct Answer
C:Correct: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. The targeted remedy is Select private log-forwarding access and validate the SPA route and trusted log receiver configuration. This addresses a private log endpoint is unreachable using public-only forwarding semantics. Confirm it by: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status. [Case R161-C115; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0571.]
Incorrect Answers
A:Incorrect for this case: Grant only the approved PoP-origin and private-service flows in the FortiGate SPA hub security policy. concerns the separate issue of Policy boundary between SASE and FortiGate (A private service works from the branch network but not from FortiSASE because its hub policy lacks the PoP source range.). It does not directly establish Select private log-forwarding access and validate the SPA route and trusted log receiver configuration. The case-specific evidence is Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status. [Case R161-C115; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0571.]
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: Select private log-forwarding access and validate the SPA route and trusted log receiver configuration. Verify it with: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
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: Select private log-forwarding access and validate the SPA route and trusted log receiver configuration. Verify it with: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
Question 572
Which independent diagnostic check best validates that the Private FortiAnalyzer behind SPA repair works? During a scoped central region deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. The change ticket limits modifications to the new branch group and requires a reversible test.
- Audit who can see each tenant's policies and verify licensed services and PoP assignments separately.
- Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
- Connect a compliant remote laptop and observe its FortiSASE tunnel, PoP path and inspected internet request.
- Correlate branch egress member, PoP arrival and cloud policy hit for a representative web request.
Explanation
Correct Answer
B:Correct: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status. This directly tests the failure mechanism and the required acceptance evidence: Cloud events arrive securely at the internal collector without public exposure. [Case R161-C115; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0572.]
Incorrect Answers
A:That intervention addresses MSSP customer provisioning separation: An MSSP operator is onboarding two customers with different licenses, policies and delegated admins. The relevant verification here is: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
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 relevant verification here is: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
D: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: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
Question 573
What observable result would show that the intended Private FortiAnalyzer behind SPA behavior has been restored? During a scoped central region deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. The change ticket limits modifications to the new branch group and requires a reversible test.
- Cloud events arrive securely at the internal collector without public exposure.
- Both normal and failover hubs advertise viable private application paths to PoPs.
- The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles.
- The managed endpoint's internet traffic receives the intended cloud security inspection.
Explanation
Correct Answer
A:Correct: Cloud events arrive securely at the internal collector without public exposure. That result demonstrates the requested controlled repair and avoids the failure mode: A private log endpoint is unreachable using public-only forwarding semantics. [Case R161-C115; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0573.]
Incorrect Answers
B:That intervention addresses SPA route propagation through dual hubs: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. The case-specific requirement is: Cloud events arrive securely at the internal collector without public exposure. Verify it with: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
C:Incorrect for this case: The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles. concerns the separate issue of SD-WAN and SASE split security ownership (A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly.). It does not directly establish Cloud events arrive securely at the internal collector without public exposure. The case-specific evidence is Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status. [Case R161-C115; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0573.]
D:Incorrect for this case: The managed endpoint's internet traffic receives the intended cloud security inspection. concerns the separate issue of Agent-based remote-user secure internet access (Managed laptops require full-tunnel policy enforcement when users browse from unmanaged networks.). It does not directly establish Cloud events arrive securely at the internal collector without public exposure. The case-specific evidence is Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status. [Case R161-C115; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0573.]
Question 574
Which failure mechanism BEST explains the Private FortiAnalyzer behind SPA observation before a repair is attempted? During a scoped central region deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. 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.
- Redundant branch uplinks alone do not remove a single SPA hub dependency.
- Treating all traffic as public web browsing masks private-app routing requirements.
- A private log endpoint is unreachable using public-only forwarding semantics.
Explanation
Correct Answer
D:Correct: A private log endpoint is unreachable using public-only forwarding semantics. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status. [Case R161-C115; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0574.]
Incorrect Answers
A:The SD-WAN and SASE split security ownership diagnosis does not explain the observed case: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. The supported diagnosis is: A private log endpoint is unreachable using public-only forwarding semantics.
B:The Single-hub versus dual-hub SPA design diagnosis does not explain the observed case: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. The supported diagnosis is: A private log endpoint is unreachable using public-only forwarding semantics.
C:The Selective private versus internet access diagnosis does not explain the observed case: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. The supported diagnosis is: A private log endpoint is unreachable using public-only forwarding semantics.
Question 575
Select TWO correct elements of a safe remedy-and-evidence plan for the Private FortiAnalyzer behind SPA case. During a scoped central region deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. The change ticket limits modifications to the new branch group and requires a reversible test.
- Test a public website and a private address, recording PoP, return path and matching policy for both.
- Approved private UDP services become reachable without exposing them to the public internet.
- Select private log-forwarding access and validate the SPA route and trusted log receiver configuration.
- Grant only the approved PoP-origin and private-service flows in the FortiGate SPA hub security policy.
- Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
Explanation
Correct Answers
C:Correct remediation element: Select private log-forwarding access and validate the SPA route and trusted log receiver configuration. It addresses A private log endpoint is unreachable using public-only forwarding semantics. [Case R161-C115; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0575.]
E:Correct verification element: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status. This independently measures whether the intended change works. [Case R161-C115; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0575.]
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: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
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: Cloud events arrive securely at the internal collector without public exposure. Verify it with: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
D:Incorrect for this case: Grant only the approved PoP-origin and private-service flows in the FortiGate SPA hub security policy. concerns the separate issue of Policy boundary between SASE and FortiGate (A private service works from the branch network but not from FortiSASE because its hub policy lacks the PoP source range.). It does not directly establish Select private log-forwarding access and validate the SPA route and trusted log receiver configuration. The case-specific evidence is Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status. [Case R161-C115; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0575.]
Question 576
Which corrective action MOST DIRECTLY addresses the observed Private FortiAnalyzer behind SPA problem within the approved change scope? Following a production change affecting Mistral Education in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- Make return-route and firewall session symmetry consistent with the documented hub-and-spoke SPA design.
- Use a supported dedicated public IP egress capability with validated policy and licensing assumptions.
- Use the supported FortiClient agent-based SIA mode with the appropriate endpoint profile and FortiSASE security policy.
- Select private log-forwarding access and validate the SPA route and trusted log receiver configuration.
Explanation
Correct Answer
D:Correct: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. The targeted remedy is Select private log-forwarding access and validate the SPA route and trusted log receiver configuration. This addresses a private log endpoint is unreachable using public-only forwarding semantics. Confirm it by: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status. [Case R161-C116; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0576.]
Incorrect Answers
A: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: Select private log-forwarding access and validate the SPA route and trusted log receiver configuration. Verify it with: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
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: Select private log-forwarding access and validate the SPA route and trusted log receiver configuration. Verify it with: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
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: Select private log-forwarding access and validate the SPA route and trusted log receiver configuration. Verify it with: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
Question 577
Which independent diagnostic check best validates that the Private FortiAnalyzer behind SPA repair works? Following a production change affecting Mistral Education in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
- Validate return-path routing and test both TCP and UDP private-app sessions through a qualified PoP.
- Send traffic from an agentless branch host and check the edge-to-PoP transport and applied SIA security policy.
- Inspect chosen PoP region and data-flow documentation for a geographically restricted test cohort.
Explanation
Correct Answer
A:Correct: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status. This directly tests the failure mechanism and the required acceptance evidence: Cloud events arrive securely at the internal collector without public exposure. [Case R161-C116; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0577.]
Incorrect Answers
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 relevant verification here is: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
C: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: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
D: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: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
Question 578
What observable result would show that the intended Private FortiAnalyzer behind SPA behavior has been restored? Following a production change affecting Mistral Education in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- The managed endpoint's internet traffic receives the intended cloud security inspection.
- Authorized private-service traffic passes while unrelated PoP-origin flows stay blocked.
- The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles.
- Cloud events arrive securely at the internal collector without public exposure.
Explanation
Correct Answer
D:Correct: Cloud events arrive securely at the internal collector without public exposure. That result demonstrates the requested controlled repair and avoids the failure mode: A private log endpoint is unreachable using public-only forwarding semantics. [Case R161-C116; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0578.]
Incorrect Answers
A:Incorrect for this case: The managed endpoint's internet traffic receives the intended cloud security inspection. concerns the separate issue of Agent-based remote-user secure internet access (Managed laptops require full-tunnel policy enforcement when users browse from unmanaged networks.). It does not directly establish Cloud events arrive securely at the internal collector without public exposure. The case-specific evidence is Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status. [Case R161-C116; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0578.]
B:That intervention addresses Policy boundary between SASE and FortiGate: A private service works from the branch network but not from FortiSASE because its hub policy lacks the PoP source range. The case-specific requirement is: Cloud events arrive securely at the internal collector without public exposure. Verify it with: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
C:Incorrect for this case: The branch's selected web traffic reaches cloud security inspection with clear local/cloud enforcement roles. concerns the separate issue of SD-WAN and SASE split security ownership (A remote branch bypasses intended FortiSASE inspection because local DIA rules forward cloud-bound browsing directly.). It does not directly establish Cloud events arrive securely at the internal collector without public exposure. The case-specific evidence is Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status. [Case R161-C116; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0578.]
Question 579
Which failure mechanism BEST explains the Private FortiAnalyzer behind SPA observation before a repair is attempted? Following a production change affecting Mistral Education in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- Successful PoP-to-hub tunnel health does not prove downstream spoke reachability.
- A global proximity-based PoP default does not by itself prove data-residency compliance.
- An overlooked hub firewall scope blocks otherwise healthy SASE tunnels and routes.
- A private log endpoint is unreachable using public-only forwarding semantics.
Explanation
Correct Answer
D:Correct: A private log endpoint is unreachable using public-only forwarding semantics. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status. [Case R161-C116; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0579.]
Incorrect Answers
A:The SD-WAN hub as private-access exchange diagnosis does not explain the observed case: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. The supported diagnosis is: A private log endpoint is unreachable using public-only forwarding semantics.
B:The Sovereign access-point selection diagnosis does not explain the observed case: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. The supported diagnosis is: A private log endpoint is unreachable using public-only forwarding semantics.
C:The Policy boundary between SASE and FortiGate diagnosis does not explain the observed case: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. The supported diagnosis is: A private log endpoint is unreachable using public-only forwarding semantics.
Question 580
Select THREE correct elements of a safe remedy-and-evidence plan for the Private FortiAnalyzer behind SPA case. Following a production change affecting Mistral Education in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: The customer must forward FortiSASE logs to an internal FortiAnalyzer instance accessible only through a private hub. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- Cloud events arrive securely at the internal collector without public exposure.
- Align branch SD-WAN destination steering with the site-based FortiSASE on-ramp and intended security-policy ownership.
- Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
- Authorized users reach spoke-hosted services through the hub's protected WAN routing.
- Repeat a remote-user private-app test during a controlled datacenter failover and inspect route changes.
- Select private log-forwarding access and validate the SPA route and trusted log receiver configuration.
Explanation
Correct Answers
A:Cloud events arrive securely at the internal collector without public exposure. This confirms the case-specific path or security boundary.
C:Correct verification element: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status. This independently measures whether the intended change works. [Case R161-C116; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0580.]
F:Correct remediation element: Select private log-forwarding access and validate the SPA route and trusted log receiver configuration. It addresses A private log endpoint is unreachable using public-only forwarding semantics. [Case R161-C116; Fortinet task I2; anchors EXAM, SPA_ARCH, SASE_SPA.] [Question R161-Q0580.]
Incorrect Answers
B: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: Select private log-forwarding access and validate the SPA route and trusted log receiver configuration. Verify it with: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
D:That intervention addresses SD-WAN hub as private-access exchange: Cloud-authenticated remote users can reach the corporate hub but not a spoke-hosted file service. The case-specific requirement is: Cloud events arrive securely at the internal collector without public exposure. Verify it with: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
E:That intervention addresses SPA route propagation through dual hubs: An SD-WAN branch can reach a private app but FortiSASE users fail after the hub shifts to its secondary datacenter. The relevant verification here is: Receive a test event on FortiAnalyzer and inspect the private path and FortiSASE forwarding status.
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests