Fortinet NSE7_SSE_AR-26 Exam Dumps, Practice Test Questions

100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!

Fortinet NSE7_SSE_AR-26  Premium File
$76.99
$69.99

NSE7_SSE_AR-26 Premium File

  • Premium File: 50 Questions & Answers. Last update: Nov 5, 2026
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

NSE7_SSE_AR-26 Premium File

Fortinet NSE7_SSE_AR-26  Premium File
  • Premium File: 50 Questions & Answers. Last update: Nov 5, 2026
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
$76.99
$69.99

Fortinet NSE7_SSE_AR-26 Practice Test 107

Question 1060

Select THREE correct elements of a safe remedy-and-evidence plan for the IPsec overlay negotiation failure case. Following a production change affecting Stonebridge Markets in its northern sites, a network team receives repeatable user-impact reports. Its fault evidence is: A branch tunnel stays down after a change despite underlay connectivity and valid peer addresses. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.

  1. The managed configuration persists consistently without fighting the template source of truth.
  2. Inspect peer negotiation events and test a successful phase-one and phase-two SA establishment.
  3. Correct the FortiManager device-group assignment and associated SD-WAN overlay template scope.
  4. Match the user, timestamp, destination and policy action across authentication and traffic records.
  5. Examine IKE/IPsec negotiation state and proposal/selector errors before altering routing rules.
  6. The secure overlay establishes and routing tests can proceed on a valid tunnel.

Explanation

Correct Answers

B:

Correct verification element: Inspect peer negotiation events and test a successful phase-one and phase-two SA establishment. This independently measures whether the intended change works. [Case R161-C212; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1060.]

E:

Correct remediation element: Examine IKE/IPsec negotiation state and proposal/selector errors before altering routing rules. It addresses Cryptographic or selector negotiation failure blocks a tunnel before BGP can help. [Case R161-C212; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1060.]

F:

The secure overlay establishes and routing tests can proceed on a valid tunnel. This confirms the case-specific path or security boundary.

Incorrect Answers

A:

Incorrect for this case: The managed configuration persists consistently without fighting the template source of truth. concerns the separate issue of FortiManager overlay orchestration scope (An engineer edits one branch's IPsec tunnel manually, but a managed overlay template overwrites the change.). It does not directly establish The secure overlay establishes and routing tests can proceed on a valid tunnel. The case-specific evidence is Inspect peer negotiation events and test a successful phase-one and phase-two SA establishment. [Case R161-C212; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1060.]

C:

Incorrect for this case: Correct the FortiManager device-group assignment and associated SD-WAN overlay template scope. concerns the separate issue of FortiManager device group assignment (A new spoke inherits the wrong regional hub because it was imported into an unrelated device group.). It does not directly establish Examine IKE/IPsec negotiation state and proposal/selector errors before altering routing rules. The case-specific evidence is Inspect peer negotiation events and test a successful phase-one and phase-two SA establishment. [Case R161-C212; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1060.]

D:

Incorrect for this case: Match the user, timestamp, destination and policy action across authentication and traffic records. 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 Inspect peer negotiation events and test a successful phase-one and phase-two SA establishment. The case-specific evidence is Inspect peer negotiation events and test a successful phase-one and phase-two SA establishment. [Case R161-C212; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1060.]

Question 1061

Which corrective action MOST DIRECTLY addresses the observed SLA path misselection troubleshooting problem within the approved change scope? During a scoped cross-border operations deployment across a staged branch cohort, Aster Research must commission the planned FortiSASE/SD-WAN control. The operational finding is: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. The change ticket limits modifications to the affected production application and requires a reversible test.

  1. Inspect the matched SD-WAN rule, member eligibility and current SLA targets together.
  2. Compare DEM measurements from endpoint to PoP and PoP to SaaS while accounting for local device load.
  3. Stage deployment using a scoped device group and review the install preview before pushing the change.
  4. Import and validate the trusted certificate authority chain for the intended external syslog server.

Explanation

Correct Answer

A:

Correct: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. The targeted remedy is Inspect the matched SD-WAN rule, member eligibility and current SLA targets together. This addresses a rule candidate or sla threshold mismatch can create unintended path choice. Confirm it by: Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C213; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1061.]

Incorrect Answers

B:

Incorrect for this case: Compare DEM measurements from endpoint to PoP and PoP to SaaS while accounting for local device load. concerns the separate issue of DEM first-mile versus SaaS-path diagnostics (A remote user complains of SaaS slowness, but the PoP appears generally healthy.). It does not directly establish Inspect the matched SD-WAN rule, member eligibility and current SLA targets together. The case-specific evidence is Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C213; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1061.]

C:

That intervention addresses Managed template change blast radius: A policy update is intended for ten pilot branches but targets the entire global branch device group. The case-specific requirement is: Inspect the matched SD-WAN rule, member eligibility and current SLA targets together. Verify it with: Capture rule diagnostics and per-link SLA values for the same test application session.

D:

That intervention addresses FortiSASE log forwarding over TLS: A remote syslog collector is reachable, but encrypted log forwarding fails during certificate validation. The case-specific requirement is: Inspect the matched SD-WAN rule, member eligibility and current SLA targets together. Verify it with: Capture rule diagnostics and per-link SLA values for the same test application session.

Question 1062

Which independent diagnostic check best validates that the SLA path misselection troubleshooting repair works? During a scoped cross-border operations deployment across a staged branch cohort, Aster Research must commission the planned FortiSASE/SD-WAN control. The operational finding is: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. The change ticket limits modifications to the affected production application and requires a reversible test.

  1. Capture rule diagnostics and per-link SLA values for the same test application session.
  2. Inspect first-mile latency and downstream SaaS trace metrics for affected and unaffected users.
  3. Compare generated configuration and installed revision for a staged branch in the affected group.
  4. Match the user, timestamp, destination and policy action across authentication and traffic records.

Explanation

Correct Answer

A:

Correct: Capture rule diagnostics and per-link SLA values for the same test application session. This directly tests the failure mechanism and the required acceptance evidence: The selected member is explained by actual rule and health evidence, then corrected in scope. [Case R161-C213; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1062.]

Incorrect Answers

B:

Incorrect for this case: Inspect first-mile latency and downstream SaaS trace metrics for affected and unaffected users. concerns the separate issue of DEM first-mile versus SaaS-path diagnostics (A remote user complains of SaaS slowness, but the PoP appears generally healthy.). It does not directly establish Capture rule diagnostics and per-link SLA values for the same test application session. The case-specific evidence is Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C213; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1062.]

C:

Incorrect for this case: Compare generated configuration and installed revision for a staged branch in the affected group. concerns the separate issue of FortiManager overlay orchestration scope (An engineer edits one branch's IPsec tunnel manually, but a managed overlay template overwrites the change.). It does not directly establish Capture rule diagnostics and per-link SLA values for the same test application session. The case-specific evidence is Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C213; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1062.]

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 relevant verification here is: Capture rule diagnostics and per-link SLA values for the same test application session.

Question 1063

What observable result would show that the intended SLA path misselection troubleshooting behavior has been restored? During a scoped cross-border operations deployment across a staged branch cohort, Aster Research must commission the planned FortiSASE/SD-WAN control. The operational finding is: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. The change ticket limits modifications to the affected production application and requires a reversible test.

  1. Only the intended region's spokes receive the approved overlay settings.
  2. The managed configuration persists consistently without fighting the template source of truth.
  3. The selected member is explained by actual rule and health evidence, then corrected in scope.
  4. The fault is isolated to the actual degraded segment, not inferred from PoP uptime alone.

Explanation

Correct Answer

C:

Correct: The selected member is explained by actual rule and health evidence, then corrected in scope. That result demonstrates the requested controlled repair and avoids the failure mode: A rule candidate or SLA threshold mismatch can create unintended path choice. [Case R161-C213; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1063.]

Incorrect Answers

A:

That intervention addresses FortiManager device group assignment: A new spoke inherits the wrong regional hub because it was imported into an unrelated device group. The case-specific requirement is: The selected member is explained by actual rule and health evidence, then corrected in scope. Verify it with: Capture rule diagnostics and per-link SLA values for the same test application session.

B:

Incorrect for this case: The managed configuration persists consistently without fighting the template source of truth. concerns the separate issue of FortiManager overlay orchestration scope (An engineer edits one branch's IPsec tunnel manually, but a managed overlay template overwrites the change.). It does not directly establish The selected member is explained by actual rule and health evidence, then corrected in scope. The case-specific evidence is Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C213; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1063.]

D:

Incorrect for this case: The fault is isolated to the actual degraded segment, not inferred from PoP uptime alone. concerns the separate issue of DEM first-mile versus SaaS-path diagnostics (A remote user complains of SaaS slowness, but the PoP appears generally healthy.). It does not directly establish The selected member is explained by actual rule and health evidence, then corrected in scope. The case-specific evidence is Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C213; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1063.]

Question 1064

Which failure mechanism BEST explains the SLA path misselection troubleshooting observation before a repair is attempted? During a scoped cross-border operations deployment across a staged branch cohort, Aster Research must commission the planned FortiSASE/SD-WAN control. The operational finding is: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. The change ticket limits modifications to the affected production application and requires a reversible test.

  1. Missing CA trust prevents a legitimate external syslog TLS session.
  2. Disconnected data sources obscure which control plane or member is actually in use.
  3. Public-only log forwarding cannot reach a private collector behind SPA.
  4. A rule candidate or SLA threshold mismatch can create unintended path choice.

Explanation

Correct Answer

D:

Correct: A rule candidate or SLA threshold mismatch can create unintended path choice. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C213; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1064.]

Incorrect Answers

A:

The FortiSASE log forwarding over TLS diagnosis does not explain the observed case: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. The supported diagnosis is: A rule candidate or SLA threshold mismatch can create unintended path choice.

B:

The Central SD-WAN monitoring after branch rollout diagnosis does not explain the observed case: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. The supported diagnosis is: A rule candidate or SLA threshold mismatch can create unintended path choice.

C:

The FortiSASE log forwarding to private FortiAnalyzer diagnosis does not explain the observed case: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. The supported diagnosis is: A rule candidate or SLA threshold mismatch can create unintended path choice.

Question 1065

Select TWO correct elements of a safe remedy-and-evidence plan for the SLA path misselection troubleshooting case. During a scoped cross-border operations deployment across a staged branch cohort, Aster Research must commission the planned FortiSASE/SD-WAN control. The operational finding is: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. The change ticket limits modifications to the affected production application and requires a reversible test.

  1. Capture rule diagnostics and per-link SLA values for the same test application session.
  2. The fault is isolated to the actual degraded segment, not inferred from PoP uptime alone.
  3. Compare generated configuration and installed revision for a staged branch in the affected group.
  4. Filter device, tenant, time range and relevant event types before analyzing FortiAnalyzer reports.
  5. Inspect the matched SD-WAN rule, member eligibility and current SLA targets together.

Explanation

Correct Answers

A:

Correct verification element: Capture rule diagnostics and per-link SLA values for the same test application session. This independently measures whether the intended change works. [Case R161-C213; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1065.]

E:

Correct remediation element: Inspect the matched SD-WAN rule, member eligibility and current SLA targets together. It addresses A rule candidate or SLA threshold mismatch can create unintended path choice. [Case R161-C213; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1065.]

Incorrect Answers

B:

Incorrect for this case: The fault is isolated to the actual degraded segment, not inferred from PoP uptime alone. concerns the separate issue of DEM first-mile versus SaaS-path diagnostics (A remote user complains of SaaS slowness, but the PoP appears generally healthy.). It does not directly establish The selected member is explained by actual rule and health evidence, then corrected in scope. The case-specific evidence is Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C213; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1065.]

C:

Incorrect for this case: Compare generated configuration and installed revision for a staged branch in the affected group. concerns the separate issue of FortiManager overlay orchestration scope (An engineer edits one branch's IPsec tunnel manually, but a managed overlay template overwrites the change.). It does not directly establish Capture rule diagnostics and per-link SLA values for the same test application session. The case-specific evidence is Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C213; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1065.]

D:

Incorrect for this case: Filter device, tenant, time range and relevant event types before analyzing FortiAnalyzer reports. 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 Inspect the matched SD-WAN rule, member eligibility and current SLA targets together. The case-specific evidence is Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C213; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1065.]

Question 1066

Which corrective action MOST DIRECTLY addresses the observed SLA path misselection troubleshooting problem within the approved change scope? Following a production change affecting Marbleton Energy in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. 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.

  1. Inspect the matched SD-WAN rule, member eligibility and current SLA targets together.
  2. Compare DEM measurements from endpoint to PoP and PoP to SaaS while accounting for local device load.
  3. Correlate endpoint security events with SASE UTM and forward-traffic logs by device, user and time.
  4. Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector.

Explanation

Correct Answer

A:

Correct: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. The targeted remedy is Inspect the matched SD-WAN rule, member eligibility and current SLA targets together. This addresses a rule candidate or sla threshold mismatch can create unintended path choice. Confirm it by: Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C214; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1066.]

Incorrect Answers

B:

Incorrect for this case: Compare DEM measurements from endpoint to PoP and PoP to SaaS while accounting for local device load. concerns the separate issue of DEM first-mile versus SaaS-path diagnostics (A remote user complains of SaaS slowness, but the PoP appears generally healthy.). It does not directly establish Inspect the matched SD-WAN rule, member eligibility and current SLA targets together. The case-specific evidence is Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C214; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1066.]

C:

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: Inspect the matched SD-WAN rule, member eligibility and current SLA targets together. Verify it with: Capture rule diagnostics and per-link SLA values for the same test application session.

D:

That intervention addresses FortiSASE log forwarding to private FortiAnalyzer: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. The case-specific requirement is: Inspect the matched SD-WAN rule, member eligibility and current SLA targets together. Verify it with: Capture rule diagnostics and per-link SLA values for the same test application session.

Question 1067

Which independent diagnostic check best validates that the SLA path misselection troubleshooting repair works? Following a production change affecting Marbleton Energy in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. 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.

  1. Verify that the detected endpoint and blocked destination align across security event types.
  2. Inspect first-mile latency and downstream SaaS trace metrics for affected and unaffected users.
  3. Compare generated configuration and installed revision for a staged branch in the affected group.
  4. Capture rule diagnostics and per-link SLA values for the same test application session.

Explanation

Correct Answer

D:

Correct: Capture rule diagnostics and per-link SLA values for the same test application session. This directly tests the failure mechanism and the required acceptance evidence: The selected member is explained by actual rule and health evidence, then corrected in scope. [Case R161-C214; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1067.]

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 relevant verification here is: Capture rule diagnostics and per-link SLA values for the same test application session.

B:

Incorrect for this case: Inspect first-mile latency and downstream SaaS trace metrics for affected and unaffected users. concerns the separate issue of DEM first-mile versus SaaS-path diagnostics (A remote user complains of SaaS slowness, but the PoP appears generally healthy.). It does not directly establish Capture rule diagnostics and per-link SLA values for the same test application session. The case-specific evidence is Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C214; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1067.]

C:

Incorrect for this case: Compare generated configuration and installed revision for a staged branch in the affected group. concerns the separate issue of FortiManager overlay orchestration scope (An engineer edits one branch's IPsec tunnel manually, but a managed overlay template overwrites the change.). It does not directly establish Capture rule diagnostics and per-link SLA values for the same test application session. The case-specific evidence is Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C214; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1067.]

Question 1068

What observable result would show that the intended SLA path misselection troubleshooting behavior has been restored? Following a production change affecting Marbleton Energy in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. 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.

  1. A regional report accurately reflects only the intended sites and period.
  2. Only approved pilot devices receive the change with a documented rollback.
  3. The selected member is explained by actual rule and health evidence, then corrected in scope.
  4. Central dashboards and branch-level evidence agree on the active WAN path.

Explanation

Correct Answer

C:

Correct: The selected member is explained by actual rule and health evidence, then corrected in scope. That result demonstrates the requested controlled repair and avoids the failure mode: A rule candidate or SLA threshold mismatch can create unintended path choice. [Case R161-C214; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1068.]

Incorrect Answers

A:

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: The selected member is explained by actual rule and health evidence, then corrected in scope. Verify it with: Capture rule diagnostics and per-link SLA values for the same test application session.

B:

That intervention addresses Managed template change blast radius: A policy update is intended for ten pilot branches but targets the entire global branch device group. The case-specific requirement is: The selected member is explained by actual rule and health evidence, then corrected in scope. Verify it with: Capture rule diagnostics and per-link SLA values for the same test application session.

D:

That intervention addresses Central SD-WAN monitoring after branch rollout: Operations cannot tell whether a new branch uses the planned hub because its local and central monitors disagree. The case-specific requirement is: The selected member is explained by actual rule and health evidence, then corrected in scope. Verify it with: Capture rule diagnostics and per-link SLA values for the same test application session.

Question 1069

Which failure mechanism BEST explains the SLA path misselection troubleshooting observation before a repair is attempted? Following a production change affecting Marbleton Energy in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. 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.

  1. A rule candidate or SLA threshold mismatch can create unintended path choice.
  2. Incorrect device grouping selects the wrong managed template.
  3. Aggregate throughput charts hide exact member selection and session changes.
  4. Overly broad centralized assignment expands an otherwise narrow configuration change.

Explanation

Correct Answer

A:

Correct: A rule candidate or SLA threshold mismatch can create unintended path choice. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C214; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1069.]

Incorrect Answers

B:

The FortiManager device group assignment diagnosis does not explain the observed case: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. The supported diagnosis is: A rule candidate or SLA threshold mismatch can create unintended path choice.

C:

The SD-WAN member change incident reconstruction diagnosis does not explain the observed case: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. The supported diagnosis is: A rule candidate or SLA threshold mismatch can create unintended path choice.

D:

The Managed template change blast radius diagnosis does not explain the observed case: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. The supported diagnosis is: A rule candidate or SLA threshold mismatch can create unintended path choice.

Question 1070

Select THREE correct elements of a safe remedy-and-evidence plan for the SLA path misselection troubleshooting case. Following a production change affecting Marbleton Energy in its eastern region, a network team receives repeatable user-impact reports. Its fault evidence is: An SD-WAN app chooses an underperforming member even though a healthy alternative is available. 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.

  1. Filter device, tenant, time range and relevant event types before analyzing FortiAnalyzer reports.
  2. Capture rule diagnostics and per-link SLA values for the same test application session.
  3. Inspect the matched SD-WAN rule, member eligibility and current SLA targets together.
  4. Generate a test security event and check the FortiAnalyzer arrival time, source identity and private path.
  5. The managed configuration persists consistently without fighting the template source of truth.
  6. The selected member is explained by actual rule and health evidence, then corrected in scope.

Explanation

Correct Answers

B:

Correct verification element: Capture rule diagnostics and per-link SLA values for the same test application session. This independently measures whether the intended change works. [Case R161-C214; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1070.]

C:

Correct remediation element: Inspect the matched SD-WAN rule, member eligibility and current SLA targets together. It addresses A rule candidate or SLA threshold mismatch can create unintended path choice. [Case R161-C214; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1070.]

F:

The selected member is explained by actual rule and health evidence, then corrected in scope. This confirms the case-specific path or security boundary.

Incorrect Answers

A:

Incorrect for this case: Filter device, tenant, time range and relevant event types before analyzing FortiAnalyzer reports. 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 Inspect the matched SD-WAN rule, member eligibility and current SLA targets together. The case-specific evidence is Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C214; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1070.]

D:

That intervention addresses FortiSASE log forwarding to private FortiAnalyzer: FortiSASE logs must reach an internal FortiAnalyzer whose address is accessible only behind an SPA hub. The relevant verification here is: Capture rule diagnostics and per-link SLA values for the same test application session.

E:

Incorrect for this case: The managed configuration persists consistently without fighting the template source of truth. concerns the separate issue of FortiManager overlay orchestration scope (An engineer edits one branch's IPsec tunnel manually, but a managed overlay template overwrites the change.). It does not directly establish The selected member is explained by actual rule and health evidence, then corrected in scope. The case-specific evidence is Capture rule diagnostics and per-link SLA values for the same test application session. [Case R161-C214; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1070.]

Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests

UP

SPECIAL OFFER: GET 10% OFF

This is ONE TIME OFFER

ExamSnap Discount Offer
Enter Your Email Address to Receive Your 10% Off Discount Code

A confirmation link will be sent to this email address to verify your login. *We value your privacy. We will not rent or sell your email address.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your e-mail address below to get started with our interactive software demo of your free trial.

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.