100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 970
Select THREE correct elements of a safe remedy-and-evidence plan for the FortiSASE log forwarding over TLS case. Following a production change affecting Beaconline Support in its metro branch group, a network team receives repeatable user-impact reports. Its fault evidence is: A remote syslog collector is reachable, but encrypted log forwarding fails during certificate validation. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.
- Import and validate the trusted certificate authority chain for the intended external syslog server.
- The browser uses the configured proxy successfully with accepted user credentials.
- A trusted TLS connection delivers events without bypassing certificate verification.
- Verify that the detected endpoint and blocked destination align across security event types.
- Run a log-forwarding test and inspect TLS trust errors plus received log records.
- Examine IKE/IPsec negotiation state and proposal/selector errors before altering routing rules.
Explanation
Correct Answers
A:Correct remediation element: Import and validate the trusted certificate authority chain for the intended external syslog server. It addresses Missing CA trust prevents a legitimate external syslog TLS session. [Case R161-C194; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0970.]
C:A trusted TLS connection delivers events without bypassing certificate verification. This confirms the case-specific path or security boundary.
E:Correct verification element: Run a log-forwarding test and inspect TLS trust errors plus received log records. This independently measures whether the intended change works. [Case R161-C194; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0970.]
Incorrect Answers
B:That intervention addresses Agentless proxy authentication failure: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. The case-specific requirement is: A trusted TLS connection delivers events without bypassing certificate verification. Verify it with: Run a log-forwarding test and inspect TLS trust errors plus received log records.
D:Incorrect for this case: Verify that the detected endpoint and blocked destination align across security event types. concerns the separate issue of Endpoint infection telemetry correlation (An endpoint reports a malware event while the cloud firewall logs show blocked command-and-control traffic.). It does not directly establish Run a log-forwarding test and inspect TLS trust errors plus received log records. The case-specific evidence is Run a log-forwarding test and inspect TLS trust errors plus received log records. [Case R161-C194; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0970.]
F: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: Import and validate the trusted certificate authority chain for the intended external syslog server. Verify it with: Run a log-forwarding test and inspect TLS trust errors plus received log records.
Question 971
Which corrective action MOST DIRECTLY addresses the observed Central SD-WAN monitoring after branch rollout problem within the approved change scope? During a scoped central region deployment across a staged branch cohort, Beaconline Support must commission the planned FortiSASE/SD-WAN control. The operational finding is: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. The change ticket limits modifications to the affected production application and requires a reversible test.
- Correct the authorized private DNS resolution path rather than changing a healthy IPsec or BGP tunnel.
- Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel.
- Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events.
- Examine IKE/IPsec negotiation state and proposal/selector errors before altering routing rules.
Explanation
Correct Answer
C:Correct: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. The targeted remedy is Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events. This addresses disconnected data sources obscure which control plane or member is actually in use. Confirm it by: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. [Case R161-C195; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0971.]
Incorrect Answers
A:Incorrect for this case: Correct the authorized private DNS resolution path rather than changing a healthy IPsec or BGP tunnel. concerns the separate issue of Private-app DNS versus route failure (An SPA application fails by hostname but works by private IP from the same endpoint.). It does not directly establish Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events. The case-specific evidence is Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. [Case R161-C195; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0971.]
B: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 Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events. The case-specific evidence is Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. [Case R161-C195; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0971.]
D: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: Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events. Verify it with: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
Question 972
Which independent diagnostic check best validates that the Central SD-WAN monitoring after branch rollout repair works? During a scoped central region deployment across a staged branch cohort, Beaconline Support must commission the planned FortiSASE/SD-WAN control. The operational finding is: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. The change ticket limits modifications to the affected production application and requires a reversible test.
- Correlate tunnel-reconnect timestamps with packet capture and known-good endpoint comparison.
- Inspect peer negotiation events and test a successful phase-one and phase-two SA establishment.
- Authenticate with a known-good test identity and inspect proxy auth and policy logs.
- Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
Explanation
Correct Answer
D:Correct: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. This directly tests the failure mechanism and the required acceptance evidence: Central dashboards and branch-level evidence agree on the active WAN path. [Case R161-C195; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0972.]
Incorrect Answers
A: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: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
B: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: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
C: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: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
Question 973
What observable result would show that the intended Central SD-WAN monitoring after branch rollout behavior has been restored? During a scoped central region deployment across a staged branch cohort, Beaconline Support must commission the planned FortiSASE/SD-WAN control. The operational finding is: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. The change ticket limits modifications to the affected production application and requires a reversible test.
- The incident can be investigated with linked device and cloud-policy evidence.
- The transport fault is distinguished from application authorization failures.
- Central dashboards and branch-level evidence agree on the active WAN path.
- Reviewers identify the actual security-policy deny instead of blaming identity login.
Explanation
Correct Answer
C:Correct: Central dashboards and branch-level evidence agree on the active WAN path. That result demonstrates the requested controlled repair and avoids the failure mode: Disconnected data sources obscure which control plane or member is actually in use. [Case R161-C195; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0973.]
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: Central dashboards and branch-level evidence agree on the active WAN path. Verify it with: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
B:That intervention addresses FortiClient tunnel failure diagnosis: A remote endpoint reports repeated tunnel reconnects, but application server logs contain no request attempts. The case-specific requirement is: Central dashboards and branch-level evidence agree on the active WAN path. Verify it with: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
D:Incorrect for this case: Reviewers identify the actual security-policy deny instead of blaming identity login. concerns the separate issue of FortiSASE traffic versus user authentication logs (A remote user's login succeeded, but HTTP requests are denied and the team only reviews authentication events.). It does not directly establish Central dashboards and branch-level evidence agree on the active WAN path. The case-specific evidence is Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. [Case R161-C195; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0973.]
Question 974
Which failure mechanism BEST explains the Central SD-WAN monitoring after branch rollout observation before a repair is attempted? During a scoped central region deployment across a staged branch cohort, Beaconline Support must commission the planned FortiSASE/SD-WAN control. The operational finding is: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. The change ticket limits modifications to the affected production application and requires a reversible test.
- Disconnected data sources obscure which control plane or member is actually in use.
- Treating one isolated log type as a complete incident story loses necessary context.
- Cryptographic or selector negotiation failure blocks a tunnel before BGP can help.
- Successful public SIA does not prove protected SPA route or policy health.
Explanation
Correct Answer
A:Correct: Disconnected data sources obscure which control plane or member is actually in use. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. [Case R161-C195; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0974.]
Incorrect Answers
B:The Endpoint infection telemetry correlation diagnosis does not explain the observed case: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. The supported diagnosis is: Disconnected data sources obscure which control plane or member is actually in use.
C:Incorrect diagnosis: this describes a different operational mechanism (IPsec overlay negotiation failure), not the documented observation (Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree.). The supported case diagnosis is Disconnected data sources obscure which control plane or member is actually in use. [Case R161-C195; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0974.]
D:The SPA private path packet trace diagnosis does not explain the observed case: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. The supported diagnosis is: Disconnected data sources obscure which control plane or member is actually in use.
Question 975
Select TWO correct elements of a safe remedy-and-evidence plan for the Central SD-WAN monitoring after branch rollout case. During a scoped central region deployment across a staged branch cohort, Beaconline Support must commission the planned FortiSASE/SD-WAN control. The operational finding is: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. The change ticket limits modifications to the affected production application and requires a reversible test.
- Correct the authorized private DNS resolution path rather than changing a healthy IPsec or BGP tunnel.
- Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
- Verify that the detected endpoint and blocked destination align across security event types.
- A regional report accurately reflects only the intended sites and period.
- Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events.
Explanation
Correct Answers
B:Correct verification element: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. This independently measures whether the intended change works. [Case R161-C195; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0975.]
E:Correct remediation element: Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events. It addresses Disconnected data sources obscure which control plane or member is actually in use. [Case R161-C195; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0975.]
Incorrect Answers
A:Incorrect for this case: Correct the authorized private DNS resolution path rather than changing a healthy IPsec or BGP tunnel. concerns the separate issue of Private-app DNS versus route failure (An SPA application fails by hostname but works by private IP from the same endpoint.). It does not directly establish Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events. The case-specific evidence is Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. [Case R161-C195; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0975.]
C:Incorrect for this case: Verify that the detected endpoint and blocked destination align across security event types. concerns the separate issue of Endpoint infection telemetry correlation (An endpoint reports a malware event while the cloud firewall logs show blocked command-and-control traffic.). It does not directly establish Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. The case-specific evidence is Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. [Case R161-C195; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0975.]
D:Incorrect for this case: A regional report accurately reflects only the intended sites and period. concerns the separate issue of FortiAnalyzer security report scope (A monthly report mixes data from unrelated SD-WAN branches and hides one region's security trend.). It does not directly establish Central dashboards and branch-level evidence agree on the active WAN path. The case-specific evidence is Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. [Case R161-C195; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0975.]
Question 976
Which corrective action MOST DIRECTLY addresses the observed Central SD-WAN monitoring after branch rollout problem within the approved change scope? Following a production change affecting Ironleaf Agriculture in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. 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.
- Analyze SD-WAN event logs and traffic sessions around the member state and SLA transitions.
- Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events.
- Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel.
- Capture and correlate packets at the endpoint, FortiSASE PoP and private hub to locate the first drop.
Explanation
Correct Answer
B:Correct: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. The targeted remedy is Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events. This addresses disconnected data sources obscure which control plane or member is actually in use. Confirm it by: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. [Case R161-C196; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0976.]
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: Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events. Verify it with: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
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 Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events. The case-specific evidence is Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. [Case R161-C196; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0976.]
D: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: Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events. Verify it with: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
Question 977
Which independent diagnostic check best validates that the Central SD-WAN monitoring after branch rollout repair works? Following a production change affecting Ironleaf Agriculture in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. Unrelated services are still operating, so the immediate response must isolate the failing control for the cloud PoP and private hub path without disabling unrelated protections.
- Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
- Inspect first-mile latency and downstream SaaS trace metrics for affected and unaffected users.
- Capture rule diagnostics and per-link SLA values for the same test application session.
- Test the protected destination while checking ingress and egress counters across the overlay.
Explanation
Correct Answer
A:Correct: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. This directly tests the failure mechanism and the required acceptance evidence: Central dashboards and branch-level evidence agree on the active WAN path. [Case R161-C196; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0977.]
Incorrect Answers
B: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: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
C:That intervention addresses SLA path misselection troubleshooting: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. The relevant verification here is: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
D:That intervention addresses SPA private path packet trace: An authenticated user reaches public internet sites but a specific private app times out. The relevant verification here is: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
Question 978
What observable result would show that the intended Central SD-WAN monitoring after branch rollout behavior has been restored? Following a production change affecting Ironleaf Agriculture in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. 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.
- The first missing segment identifies whether route, hub policy or application is blocking SPA.
- Central dashboards and branch-level evidence agree on the active WAN path.
- A regional report accurately reflects only the intended sites and period.
- Reviewers identify the actual security-policy deny instead of blaming identity login.
Explanation
Correct Answer
B:Correct: Central dashboards and branch-level evidence agree on the active WAN path. That result demonstrates the requested controlled repair and avoids the failure mode: Disconnected data sources obscure which control plane or member is actually in use. [Case R161-C196; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0978.]
Incorrect Answers
A: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: Central dashboards and branch-level evidence agree on the active WAN path. Verify it with: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
C:Incorrect for this case: A regional report accurately reflects only the intended sites and period. concerns the separate issue of FortiAnalyzer security report scope (A monthly report mixes data from unrelated SD-WAN branches and hides one region's security trend.). It does not directly establish Central dashboards and branch-level evidence agree on the active WAN path. The case-specific evidence is Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. [Case R161-C196; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0978.]
D:Incorrect for this case: Reviewers identify the actual security-policy deny instead of blaming identity login. concerns the separate issue of FortiSASE traffic versus user authentication logs (A remote user's login succeeded, but HTTP requests are denied and the team only reviews authentication events.). It does not directly establish Central dashboards and branch-level evidence agree on the active WAN path. The case-specific evidence is Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. [Case R161-C196; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0978.]
Question 979
Which failure mechanism BEST explains the Central SD-WAN monitoring after branch rollout observation before a repair is attempted? Following a production change affecting Ironleaf Agriculture in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. 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.
- Disconnected data sources obscure which control plane or member is actually in use.
- A rule candidate or SLA threshold mismatch can create unintended path choice.
- Cryptographic or selector negotiation failure blocks a tunnel before BGP can help.
- A proxy authentication mismatch can persist even when the cloud proxy is reachable.
Explanation
Correct Answer
A:Correct: Disconnected data sources obscure which control plane or member is actually in use. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. [Case R161-C196; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0979.]
Incorrect Answers
B:The SLA path misselection troubleshooting diagnosis does not explain the observed case: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. The supported diagnosis is: Disconnected data sources obscure which control plane or member is actually in use.
C:Incorrect diagnosis: this describes a different operational mechanism (IPsec overlay negotiation failure), not the documented observation (Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree.). The supported case diagnosis is Disconnected data sources obscure which control plane or member is actually in use. [Case R161-C196; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0979.]
D:The Agentless proxy authentication failure diagnosis does not explain the observed case: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. The supported diagnosis is: Disconnected data sources obscure which control plane or member is actually in use.
Question 980
Select THREE correct elements of a safe remedy-and-evidence plan for the Central SD-WAN monitoring after branch rollout case. Following a production change affecting Ironleaf Agriculture in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. 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.
- Verify that the detected endpoint and blocked destination align across security event types.
- Inspect FortiClient diagnostic logs and endpoint-to-PoP transport before changing private application policy.
- Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events.
- A regional report accurately reflects only the intended sites and period.
- Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
- Central dashboards and branch-level evidence agree on the active WAN path.
Explanation
Correct Answers
C:Correct remediation element: Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events. It addresses Disconnected data sources obscure which control plane or member is actually in use. [Case R161-C196; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0980.]
E:Correct verification element: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. This independently measures whether the intended change works. [Case R161-C196; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0980.]
F:Central dashboards and branch-level evidence agree on the active WAN path. This confirms the case-specific path or security boundary.
Incorrect Answers
A:Incorrect for this case: Verify that the detected endpoint and blocked destination align across security event types. concerns the separate issue of Endpoint infection telemetry correlation (An endpoint reports a malware event while the cloud firewall logs show blocked command-and-control traffic.). It does not directly establish Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. The case-specific evidence is Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. [Case R161-C196; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0980.]
B:That intervention addresses FortiClient tunnel failure diagnosis: A remote endpoint reports repeated tunnel reconnects, but application server logs contain no request attempts. The case-specific requirement is: Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events. Verify it with: Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
D:Incorrect for this case: A regional report accurately reflects only the intended sites and period. concerns the separate issue of FortiAnalyzer security report scope (A monthly report mixes data from unrelated SD-WAN branches and hides one region's security trend.). It does not directly establish Central dashboards and branch-level evidence agree on the active WAN path. The case-specific evidence is Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems. [Case R161-C196; Fortinet task O1; anchors EXAM, FMG_TOPO, SASE_LOG.] [Question R161-Q0980.]
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests