100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 950
Select THREE correct elements of a safe remedy-and-evidence plan for the FortiManager device group assignment case. Following a production change affecting Cedarline Retail in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: A new spoke inherits the wrong regional hub because it was imported into an unrelated device group. 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.
- Only the intended region's spokes receive the approved overlay settings.
- The browser uses the configured proxy successfully with accepted user credentials.
- Capture and correlate packets at the endpoint, FortiSASE PoP and private hub to locate the first drop.
- Inspect generated hub targets for the moved spoke and a neighboring unaffected branch.
- Correct the FortiManager device-group assignment and associated SD-WAN overlay template scope.
- Correlate tunnel-reconnect timestamps with packet capture and known-good endpoint comparison.
Explanation
Correct Answers
A:Only the intended region's spokes receive the approved overlay settings. This confirms the case-specific path or security boundary.
D:Correct verification element: Inspect generated hub targets for the moved spoke and a neighboring unaffected branch. This independently measures whether the intended change works. [Case R161-C190; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0950.]
E:Correct remediation element: Correct the FortiManager device-group assignment and associated SD-WAN overlay template scope. It addresses Incorrect device grouping selects the wrong managed template. [Case R161-C190; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0950.]
Incorrect Answers
B:Incorrect for this case: The browser uses the configured proxy successfully with accepted user credentials. concerns the separate issue of Agentless proxy authentication failure (A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts.). It does not directly establish Only the intended region's spokes receive the approved overlay settings. The case-specific evidence is Inspect generated hub targets for the moved spoke and a neighboring unaffected branch. [Case R161-C190; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0950.]
C:That intervention addresses SPA private path packet trace: An authenticated user reaches public internet sites but a specific private app times out. The case-specific requirement is: Correct the FortiManager device-group assignment and associated SD-WAN overlay template scope. Verify it with: Inspect generated hub targets for the moved spoke and a neighboring unaffected branch.
F:Incorrect for this case: Correlate tunnel-reconnect timestamps with packet capture and known-good endpoint comparison. concerns the separate issue of FortiClient tunnel failure diagnosis (A remote endpoint reports repeated tunnel reconnects, but application server logs contain no request attempts.). It does not directly establish Inspect generated hub targets for the moved spoke and a neighboring unaffected branch. The case-specific evidence is Inspect generated hub targets for the moved spoke and a neighboring unaffected branch. [Case R161-C190; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0950.]
Question 951
Which corrective action MOST DIRECTLY addresses the observed FortiSASE log forwarding to private FortiAnalyzer problem within the approved change scope? During a scoped remote campus corridor deployment across a staged branch cohort, Cedarline Retail must commission the planned FortiSASE/SD-WAN control. The operational finding is: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector.
- Examine IKE/IPsec negotiation state and proposal/selector errors before altering routing rules.
- Analyze SD-WAN event logs and traffic sessions around the member state and SLA transitions.
- Inspect the matched SD-WAN rule, member eligibility and current SLA targets together.
Explanation
Correct Answer
A:Correct: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. The targeted remedy is Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector. This addresses public-only log forwarding cannot reach a private collector behind spa. Confirm it by: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. [Case R161-C191; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0951.]
Incorrect Answers
B:That intervention addresses IPsec overlay negotiation failure: A branch tunnel stays down after a change despite underlay connectivity and valid peer addresses. The case-specific requirement is: Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector. Verify it with: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
C:Incorrect for this case: Analyze SD-WAN event logs and traffic sessions around the member state and SLA transitions. concerns the separate issue of SD-WAN member change incident reconstruction (A business app fails sporadically during link switchover, but engineers have only periodic bandwidth charts.). It does not directly establish Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector. The case-specific evidence is Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. [Case R161-C191; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0951.]
D:Incorrect for this case: Inspect the matched SD-WAN rule, member eligibility and current SLA targets together. concerns the separate issue of SLA path misselection troubleshooting (An SD-WAN app chooses an underperforming member even though a healthy alternative is available.). It does not directly establish Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector. The case-specific evidence is Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. [Case R161-C191; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0951.]
Question 952
Which independent diagnostic check best validates that the FortiSASE log forwarding to private FortiAnalyzer repair works? During a scoped remote campus corridor deployment across a staged branch cohort, Cedarline Retail must commission the planned FortiSASE/SD-WAN control. The operational finding is: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- Inspect peer negotiation events and test a successful phase-one and phase-two SA establishment.
- Verify that the detected endpoint and blocked destination align across security event types.
- Correlate tunnel-reconnect timestamps with packet capture and known-good endpoint comparison.
- Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
Explanation
Correct Answer
D:Correct: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. This directly tests the failure mechanism and the required acceptance evidence: Required cloud log types arrive at the protected private collector without public exposure. [Case R161-C191; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0952.]
Incorrect Answers
A:That intervention addresses IPsec overlay negotiation failure: A branch tunnel stays down after a change despite underlay connectivity and valid peer addresses. The relevant verification here is: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
B:That intervention addresses Endpoint infection telemetry correlation: An endpoint reports a malware event while the cloud firewall logs show blocked command-and-control traffic. The relevant verification here is: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
C:That intervention addresses FortiClient tunnel failure diagnosis: A remote endpoint reports repeated tunnel reconnects, but application server logs contain no request attempts. The relevant verification here is: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
Question 953
What observable result would show that the intended FortiSASE log forwarding to private FortiAnalyzer behavior has been restored? During a scoped remote campus corridor deployment across a staged branch cohort, Cedarline Retail must commission the planned FortiSASE/SD-WAN control. The operational finding is: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- The secure overlay establishes and routing tests can proceed on a valid tunnel.
- Required cloud log types arrive at the protected private collector without public exposure.
- A regional report accurately reflects only the intended sites and period.
- The selected member is explained by actual rule and health evidence, then corrected in scope.
Explanation
Correct Answer
B:Correct: Required cloud log types arrive at the protected private collector without public exposure. That result demonstrates the requested controlled repair and avoids the failure mode: Public-only log forwarding cannot reach a private collector behind SPA. [Case R161-C191; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0953.]
Incorrect Answers
A:Incorrect for this case: The secure overlay establishes and routing tests can proceed on a valid tunnel. concerns the separate issue of IPsec overlay negotiation failure (A branch tunnel stays down after a change despite underlay connectivity and valid peer addresses.). It does not directly establish Required cloud log types arrive at the protected private collector without public exposure. The case-specific evidence is Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. [Case R161-C191; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0953.]
C:That intervention addresses FortiAnalyzer security report scope: A monthly report mixes data from unrelated SD-WAN branches and hides one region's security trend. The case-specific requirement is: Required cloud log types arrive at the protected private collector without public exposure. Verify it with: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
D:Incorrect for this case: The selected member is explained by actual rule and health evidence, then corrected in scope. concerns the separate issue of SLA path misselection troubleshooting (An SD-WAN app chooses an underperforming member even though a healthy alternative is available.). It does not directly establish Required cloud log types arrive at the protected private collector without public exposure. The case-specific evidence is Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. [Case R161-C191; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0953.]
Question 954
Which failure mechanism BEST explains the FortiSASE log forwarding to private FortiAnalyzer observation before a repair is attempted? During a scoped remote campus corridor deployment across a staged branch cohort, Cedarline Retail must commission the planned FortiSASE/SD-WAN control. The operational finding is: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- Public-only log forwarding cannot reach a private collector behind SPA.
- Successful public SIA does not prove protected SPA route or policy health.
- Overbroad device scope produces misleading aggregate security analytics.
- User logs confirm authentication but not the final traffic/inspection decision.
Explanation
Correct Answer
A:Correct: Public-only log forwarding cannot reach a private collector behind SPA. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. [Case R161-C191; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0954.]
Incorrect Answers
B:The SPA private path packet trace diagnosis does not explain the observed case: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. The supported diagnosis is: Public-only log forwarding cannot reach a private collector behind SPA.
C:The FortiAnalyzer security report scope diagnosis does not explain the observed case: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. The supported diagnosis is: Public-only log forwarding cannot reach a private collector behind SPA.
D:Incorrect diagnosis: this describes a different operational mechanism (FortiSASE traffic versus user authentication logs), not the documented observation (FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub.). The supported case diagnosis is Public-only log forwarding cannot reach a private collector behind SPA. [Case R161-C191; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0954.]
Question 955
Select TWO correct elements of a safe remedy-and-evidence plan for the FortiSASE log forwarding to private FortiAnalyzer case. During a scoped remote campus corridor deployment across a staged branch cohort, Cedarline Retail must commission the planned FortiSASE/SD-WAN control. The operational finding is: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. The change ticket limits modifications to a controlled device cohort and requires a reversible test.
- Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
- Correlate a specific failover timestamp, member-health event and matching application session.
- Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector.
- Reviewers identify the actual security-policy deny instead of blaming identity login.
- Correct the authorized private DNS resolution path rather than changing a healthy IPsec or BGP tunnel.
Explanation
Correct Answers
A:Correct verification element: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. This independently measures whether the intended change works. [Case R161-C191; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0955.]
C:Correct remediation element: Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector. It addresses Public-only log forwarding cannot reach a private collector behind SPA. [Case R161-C191; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0955.]
Incorrect Answers
B:That intervention addresses SD-WAN member change incident reconstruction: A business app fails sporadically during link switchover, but engineers have only periodic bandwidth charts. The relevant verification here is: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
D:That intervention addresses FortiSASE traffic versus user authentication logs: A remote user's login succeeded, but HTTP requests are denied and the team only reviews authentication events. The case-specific requirement is: Required cloud log types arrive at the protected private collector without public exposure. Verify it with: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
E:That intervention addresses Private-app DNS versus route failure: An SPA application fails by hostname but works by private IP from the same endpoint. The case-specific requirement is: Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector. Verify it with: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
Question 956
Which corrective action MOST DIRECTLY addresses the observed FortiSASE log forwarding to private FortiAnalyzer problem within the approved change scope? Following a production change affecting Pinehaven Distribution in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Analyze SD-WAN event logs and traffic sessions around the member state and SLA transitions.
- Inspect the matched SD-WAN rule, member eligibility and current SLA targets together.
- Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel.
- Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector.
Explanation
Correct Answer
D:Correct: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. The targeted remedy is Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector. This addresses public-only log forwarding cannot reach a private collector behind spa. Confirm it by: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. [Case R161-C192; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0956.]
Incorrect Answers
A:Incorrect for this case: Analyze SD-WAN event logs and traffic sessions around the member state and SLA transitions. concerns the separate issue of SD-WAN member change incident reconstruction (A business app fails sporadically during link switchover, but engineers have only periodic bandwidth charts.). It does not directly establish Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector. The case-specific evidence is Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. [Case R161-C192; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0956.]
B:Incorrect for this case: Inspect the matched SD-WAN rule, member eligibility and current SLA targets together. concerns the separate issue of SLA path misselection troubleshooting (An SD-WAN app chooses an underperforming member even though a healthy alternative is available.). It does not directly establish Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector. The case-specific evidence is Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. [Case R161-C192; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0956.]
C:Incorrect for this case: Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel. concerns the separate issue of Agentless proxy authentication failure (A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts.). It does not directly establish Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector. The case-specific evidence is Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. [Case R161-C192; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0956.]
Question 957
Which independent diagnostic check best validates that the FortiSASE log forwarding to private FortiAnalyzer repair works? Following a production change affecting Pinehaven Distribution in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- Inspect first-mile latency and downstream SaaS trace metrics for affected and unaffected users.
- Authenticate with a known-good test identity and inspect proxy auth and policy logs.
- Compare hostname resolution with direct IP connectivity and test the application after DNS change.
- Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
Explanation
Correct Answer
D:Correct: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. This directly tests the failure mechanism and the required acceptance evidence: Required cloud log types arrive at the protected private collector without public exposure. [Case R161-C192; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0957.]
Incorrect Answers
A:That intervention addresses DEM first-mile versus SaaS-path diagnostics: A remote user complains of SaaS slowness, but the PoP appears generally healthy. The relevant verification here is: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
B:That intervention addresses Agentless proxy authentication failure: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. The relevant verification here is: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
C:That intervention addresses Private-app DNS versus route failure: An SPA application fails by hostname but works by private IP from the same endpoint. The relevant verification here is: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
Question 958
What observable result would show that the intended FortiSASE log forwarding to private FortiAnalyzer behavior has been restored? Following a production change affecting Pinehaven Distribution in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- The incident can be investigated with linked device and cloud-policy evidence.
- The secure overlay establishes and routing tests can proceed on a valid tunnel.
- Required cloud log types arrive at the protected private collector without public exposure.
- The selected member is explained by actual rule and health evidence, then corrected in scope.
Explanation
Correct Answer
C:Correct: Required cloud log types arrive at the protected private collector without public exposure. That result demonstrates the requested controlled repair and avoids the failure mode: Public-only log forwarding cannot reach a private collector behind SPA. [Case R161-C192; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0958.]
Incorrect Answers
A:That intervention addresses Endpoint infection telemetry correlation: An endpoint reports a malware event while the cloud firewall logs show blocked command-and-control traffic. The case-specific requirement is: Required cloud log types arrive at the protected private collector without public exposure. Verify it with: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
B:Incorrect for this case: The secure overlay establishes and routing tests can proceed on a valid tunnel. concerns the separate issue of IPsec overlay negotiation failure (A branch tunnel stays down after a change despite underlay connectivity and valid peer addresses.). It does not directly establish Required cloud log types arrive at the protected private collector without public exposure. The case-specific evidence is Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. [Case R161-C192; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0958.]
D:Incorrect for this case: The selected member is explained by actual rule and health evidence, then corrected in scope. concerns the separate issue of SLA path misselection troubleshooting (An SD-WAN app chooses an underperforming member even though a healthy alternative is available.). It does not directly establish Required cloud log types arrive at the protected private collector without public exposure. The case-specific evidence is Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. [Case R161-C192; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0958.]
Question 959
Which failure mechanism BEST explains the FortiSASE log forwarding to private FortiAnalyzer observation before a repair is attempted? Following a production change affecting Pinehaven Distribution in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- A rule candidate or SLA threshold mismatch can create unintended path choice.
- User logs confirm authentication but not the final traffic/inspection decision.
- Public-only log forwarding cannot reach a private collector behind SPA.
- The observed failure is private DNS resolution, not overlay transport reachability.
Explanation
Correct Answer
C:Correct: Public-only log forwarding cannot reach a private collector behind SPA. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. [Case R161-C192; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0959.]
Incorrect Answers
A:The SLA path misselection troubleshooting diagnosis does not explain the observed case: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. The supported diagnosis is: Public-only log forwarding cannot reach a private collector behind SPA.
B:Incorrect diagnosis: this describes a different operational mechanism (FortiSASE traffic versus user authentication logs), not the documented observation (FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub.). The supported case diagnosis is Public-only log forwarding cannot reach a private collector behind SPA. [Case R161-C192; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0959.]
D:The Private-app DNS versus route failure diagnosis does not explain the observed case: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. The supported diagnosis is: Public-only log forwarding cannot reach a private collector behind SPA.
Question 960
Select THREE correct elements of a safe remedy-and-evidence plan for the FortiSASE log forwarding to private FortiAnalyzer case. Following a production change affecting Pinehaven Distribution in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.
- The incident timeline reveals whether health-driven path change caused the interruption.
- Match the user, timestamp, destination and policy action across authentication and traffic records.
- Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
- Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector.
- Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel.
- Required cloud log types arrive at the protected private collector without public exposure.
Explanation
Correct Answers
C:Correct verification element: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. This independently measures whether the intended change works. [Case R161-C192; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0960.]
D:Correct remediation element: Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector. It addresses Public-only log forwarding cannot reach a private collector behind SPA. [Case R161-C192; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0960.]
F:Required cloud log types arrive at the protected private collector without public exposure. This confirms the case-specific path or security boundary.
Incorrect Answers
A:That intervention addresses SD-WAN member change incident reconstruction: A business app fails sporadically during link switchover, but engineers have only periodic bandwidth charts. The case-specific requirement is: Required cloud log types arrive at the protected private collector without public exposure. Verify it with: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
B:That intervention addresses FortiSASE traffic versus user authentication logs: A remote user's login succeeded, but HTTP requests are denied and the team only reviews authentication events. The relevant verification here is: Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
E:Incorrect for this case: Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel. concerns the separate issue of Agentless proxy authentication failure (A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts.). It does not directly establish Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector. The case-specific evidence is Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path. [Case R161-C192; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0960.]
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests