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 109

Question 1080

Select THREE correct elements of a safe remedy-and-evidence plan for the SPA private path packet trace case. Following a production change affecting HelioCare Clinics in its western region, a network team receives repeatable user-impact reports. Its fault evidence is: An authenticated user reaches public internet sites but a specific private app times out. Unrelated services are still operating, so the immediate response must isolate the failing control for one approved pilot tenant without disabling unrelated protections.

  1. The first missing segment identifies whether route, hub policy or application is blocking SPA.
  2. Capture and correlate packets at the endpoint, FortiSASE PoP and private hub to locate the first drop.
  3. Correlate a specific failover timestamp, member-health event and matching application session.
  4. Central dashboards and branch-level evidence agree on the active WAN path.
  5. Test the protected destination while checking ingress and egress counters across the overlay.
  6. Import and validate the trusted certificate authority chain for the intended external syslog server.

Explanation

Correct Answers

A:

The first missing segment identifies whether route, hub policy or application is blocking SPA. This confirms the case-specific path or security boundary.

B:

Correct remediation element: Capture and correlate packets at the endpoint, FortiSASE PoP and private hub to locate the first drop. It addresses Successful public SIA does not prove protected SPA route or policy health. [Case R161-C216; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1080.]

E:

Correct verification element: Test the protected destination while checking ingress and egress counters across the overlay. This independently measures whether the intended change works. [Case R161-C216; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1080.]

Incorrect Answers

C:

Incorrect for this case: Correlate a specific failover timestamp, member-health event and matching application session. 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 Test the protected destination while checking ingress and egress counters across the overlay. The case-specific evidence is Test the protected destination while checking ingress and egress counters across the overlay. [Case R161-C216; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1080.]

D:

Incorrect for this case: Central dashboards and branch-level evidence agree on the active WAN path. concerns the separate issue of 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.). It does not directly establish The first missing segment identifies whether route, hub policy or application is blocking SPA. The case-specific evidence is Test the protected destination while checking ingress and egress counters across the overlay. [Case R161-C216; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1080.]

F:

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: Capture and correlate packets at the endpoint, FortiSASE PoP and private hub to locate the first drop. Verify it with: Test the protected destination while checking ingress and egress counters across the overlay.

Question 1081

Which corrective action MOST DIRECTLY addresses the observed Agentless proxy authentication failure problem within the approved change scope? During a scoped coastal district deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. The change ticket limits modifications to the new branch group and requires a reversible test.

  1. Configure FortiSASE private external-server log forwarding and verify a working SPA route to the collector.
  2. Correct the FortiManager device-group assignment and associated SD-WAN overlay template scope.
  3. Update the authoritative FortiManager SD-WAN overlay template and review deployment scope before installing.
  4. Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel.

Explanation

Correct Answer

D:

Correct: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. The targeted remedy is Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel. This addresses a proxy authentication mismatch can persist even when the cloud proxy is reachable. Confirm it by: Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C217; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1081.]

Incorrect Answers

A:

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 proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel. Verify it with: Authenticate with a known-good test identity and inspect proxy auth and policy logs.

B:

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 Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel. The case-specific evidence is Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C217; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1081.]

C:

Incorrect for this case: Update the authoritative FortiManager SD-WAN overlay template and review deployment scope before installing. 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 Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel. The case-specific evidence is Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C217; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1081.]

Question 1082

Which independent diagnostic check best validates that the Agentless proxy authentication failure repair works? During a scoped coastal district deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. The change ticket limits modifications to the new branch group and requires a reversible test.

  1. Correlate a specific failover timestamp, member-health event and matching application session.
  2. Authenticate with a known-good test identity and inspect proxy auth and policy logs.
  3. Correlate the same branch's tunnel ID, selected member and event timestamp across the three systems.
  4. Inspect first-mile latency and downstream SaaS trace metrics for affected and unaffected users.

Explanation

Correct Answer

B:

Correct: Authenticate with a known-good test identity and inspect proxy auth and policy logs. This directly tests the failure mechanism and the required acceptance evidence: The browser uses the configured proxy successfully with accepted user credentials. [Case R161-C217; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1082.]

Incorrect Answers

A:

Incorrect for this case: Correlate a specific failover timestamp, member-health event and matching application session. 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 Authenticate with a known-good test identity and inspect proxy auth and policy logs. The case-specific evidence is Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C217; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1082.]

C:

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 relevant verification here is: Authenticate with a known-good test identity and inspect proxy auth and policy logs.

D:

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: Authenticate with a known-good test identity and inspect proxy auth and policy logs.

Question 1083

What observable result would show that the intended Agentless proxy authentication failure behavior has been restored? During a scoped coastal district deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. The change ticket limits modifications to the new branch group and requires a reversible test.

  1. The browser uses the configured proxy successfully with accepted user credentials.
  2. The incident can be investigated with linked device and cloud-policy evidence.
  3. The managed configuration persists consistently without fighting the template source of truth.
  4. Reviewers identify the actual security-policy deny instead of blaming identity login.

Explanation

Correct Answer

A:

Correct: The browser uses the configured proxy successfully with accepted user credentials. That result demonstrates the requested controlled repair and avoids the failure mode: A proxy authentication mismatch can persist even when the cloud proxy is reachable. [Case R161-C217; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1083.]

Incorrect Answers

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 case-specific requirement is: The browser uses the configured proxy successfully with accepted user credentials. Verify it with: Authenticate with a known-good test identity and inspect proxy auth and policy logs.

C:

That intervention addresses FortiManager overlay orchestration scope: An engineer edits one branch's IPsec tunnel manually, but a managed overlay template overwrites the change. The case-specific requirement is: The browser uses the configured proxy successfully with accepted user credentials. Verify it with: Authenticate with a known-good test identity and inspect proxy auth and policy logs.

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 The browser uses the configured proxy successfully with accepted user credentials. The case-specific evidence is Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C217; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1083.]

Question 1084

Which failure mechanism BEST explains the Agentless proxy authentication failure observation before a repair is attempted? During a scoped coastal district deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. The change ticket limits modifications to the new branch group and requires a reversible test.

  1. Aggregate throughput charts hide exact member selection and session changes.
  2. A proxy authentication mismatch can persist even when the cloud proxy is reachable.
  3. An end-to-end experience issue needs segment-level evidence.
  4. Overbroad device scope produces misleading aggregate security analytics.

Explanation

Correct Answer

B:

Correct: A proxy authentication mismatch can persist even when the cloud proxy is reachable. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C217; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1084.]

Incorrect Answers

A:

Incorrect diagnosis: this describes a different operational mechanism (SD-WAN member change incident reconstruction), not the documented observation (A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts.). The supported case diagnosis is A proxy authentication mismatch can persist even when the cloud proxy is reachable. [Case R161-C217; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1084.]

C:

The DEM first-mile versus SaaS-path diagnostics diagnosis does not explain the observed case: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. The supported diagnosis is: A proxy authentication mismatch can persist even when the cloud proxy is reachable.

D:

The FortiAnalyzer security report scope diagnosis does not explain the observed case: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. The supported diagnosis is: A proxy authentication mismatch can persist even when the cloud proxy is reachable.

Question 1085

Select TWO correct elements of a safe remedy-and-evidence plan for the Agentless proxy authentication failure case. During a scoped coastal district deployment across a staged branch cohort, Stonebridge Markets must commission the planned FortiSASE/SD-WAN control. The operational finding is: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. The change ticket limits modifications to the new branch group and requires a reversible test.

  1. The fault is isolated to the actual degraded segment, not inferred from PoP uptime alone.
  2. Authenticate with a known-good test identity and inspect proxy auth and policy logs.
  3. Update the authoritative FortiManager SD-WAN overlay template and review deployment scope before installing.
  4. Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel.
  5. Match the user, timestamp, destination and policy action across authentication and traffic records.

Explanation

Correct Answers

B:

Correct verification element: Authenticate with a known-good test identity and inspect proxy auth and policy logs. This independently measures whether the intended change works. [Case R161-C217; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1085.]

D:

Correct remediation element: Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel. It addresses A proxy authentication mismatch can persist even when the cloud proxy is reachable. [Case R161-C217; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1085.]

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 case-specific requirement is: The browser uses the configured proxy successfully with accepted user credentials. Verify it with: Authenticate with a known-good test identity and inspect proxy auth and policy logs.

C:

Incorrect for this case: Update the authoritative FortiManager SD-WAN overlay template and review deployment scope before installing. 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 Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel. The case-specific evidence is Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C217; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1085.]

E:

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 Authenticate with a known-good test identity and inspect proxy auth and policy logs. The case-specific evidence is Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C217; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1085.]

Question 1086

Which corrective action MOST DIRECTLY addresses the observed Agentless proxy authentication failure problem within the approved change scope? Following a production change affecting Mistral Education in its metro branch group, a network team receives repeatable user-impact reports. Its fault evidence is: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.

  1. Correlate FortiSASE user authentication events with forward traffic and UTM policy logs for that session.
  2. Reconcile FortiManager overlay status with FortiGate member health and FortiAnalyzer SD-WAN events.
  3. Correct the FortiManager device-group assignment and associated SD-WAN overlay template scope.
  4. Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel.

Explanation

Correct Answer

D:

Correct: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. The targeted remedy is Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel. This addresses a proxy authentication mismatch can persist even when the cloud proxy is reachable. Confirm it by: Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C218; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1086.]

Incorrect Answers

A:

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: Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel. Verify it with: Authenticate with a known-good test identity and inspect proxy auth and policy logs.

B:

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: Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel. Verify it with: Authenticate with a known-good test identity and inspect proxy auth and policy logs.

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 Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel. The case-specific evidence is Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C218; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1086.]

Question 1087

Which independent diagnostic check best validates that the Agentless proxy authentication failure repair works? Following a production change affecting Mistral Education in its metro branch group, a network team receives repeatable user-impact reports. Its fault evidence is: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.

  1. Verify that the detected endpoint and blocked destination align across security event types.
  2. Reconcile report totals with sampled raw events for one authorized region.
  3. Correlate a specific failover timestamp, member-health event and matching application session.
  4. Authenticate with a known-good test identity and inspect proxy auth and policy logs.

Explanation

Correct Answer

D:

Correct: Authenticate with a known-good test identity and inspect proxy auth and policy logs. This directly tests the failure mechanism and the required acceptance evidence: The browser uses the configured proxy successfully with accepted user credentials. [Case R161-C218; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1087.]

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: Authenticate with a known-good test identity and inspect proxy auth and policy logs.

B:

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 relevant verification here is: Authenticate with a known-good test identity and inspect proxy auth and policy logs.

C:

Incorrect for this case: Correlate a specific failover timestamp, member-health event and matching application session. 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 Authenticate with a known-good test identity and inspect proxy auth and policy logs. The case-specific evidence is Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C218; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1087.]

Question 1088

What observable result would show that the intended Agentless proxy authentication failure behavior has been restored? Following a production change affecting Mistral Education in its metro branch group, a network team receives repeatable user-impact reports. Its fault evidence is: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.

  1. Reviewers identify the actual security-policy deny instead of blaming identity login.
  2. Only approved pilot devices receive the change with a documented rollback.
  3. The browser uses the configured proxy successfully with accepted user credentials.
  4. The incident timeline reveals whether health-driven path change caused the interruption.

Explanation

Correct Answer

C:

Correct: The browser uses the configured proxy successfully with accepted user credentials. That result demonstrates the requested controlled repair and avoids the failure mode: A proxy authentication mismatch can persist even when the cloud proxy is reachable. [Case R161-C218; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1088.]

Incorrect Answers

A:

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 The browser uses the configured proxy successfully with accepted user credentials. The case-specific evidence is Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C218; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1088.]

B:

Incorrect for this case: Only approved pilot devices receive the change with a documented rollback. concerns the separate issue of Managed template change blast radius (A policy update is intended for ten pilot branches but targets the entire global branch device group.). It does not directly establish The browser uses the configured proxy successfully with accepted user credentials. The case-specific evidence is Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C218; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1088.]

D:

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: The browser uses the configured proxy successfully with accepted user credentials. Verify it with: Authenticate with a known-good test identity and inspect proxy auth and policy logs.

Question 1089

Which failure mechanism BEST explains the Agentless proxy authentication failure observation before a repair is attempted? Following a production change affecting Mistral Education in its metro branch group, a network team receives repeatable user-impact reports. Its fault evidence is: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.

  1. Disconnected data sources obscure which control plane or member is actually in use.
  2. Overly broad centralized assignment expands an otherwise narrow configuration change.
  3. Aggregate throughput charts hide exact member selection and session changes.
  4. A proxy authentication mismatch can persist even when the cloud proxy is reachable.

Explanation

Correct Answer

D:

Correct: A proxy authentication mismatch can persist even when the cloud proxy is reachable. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C218; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1089.]

Incorrect Answers

A:

The Central SD-WAN monitoring after branch rollout diagnosis does not explain the observed case: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. The supported diagnosis is: A proxy authentication mismatch can persist even when the cloud proxy is reachable.

B:

The Managed template change blast radius diagnosis does not explain the observed case: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. The supported diagnosis is: A proxy authentication mismatch can persist even when the cloud proxy is reachable.

C:

Incorrect diagnosis: this describes a different operational mechanism (SD-WAN member change incident reconstruction), not the documented observation (A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts.). The supported case diagnosis is A proxy authentication mismatch can persist even when the cloud proxy is reachable. [Case R161-C218; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1089.]

Question 1090

Select THREE correct elements of a safe remedy-and-evidence plan for the Agentless proxy authentication failure case. Following a production change affecting Mistral Education in its metro branch group, a network team receives repeatable user-impact reports. Its fault evidence is: A browser can reach a FortiSASE explicit-proxy endpoint but receives repeated credential prompts. Unrelated services are still operating, so the immediate response must isolate the failing control for the designated privileged users without disabling unrelated protections.

  1. Authenticate with a known-good test identity and inspect proxy auth and policy logs.
  2. Only approved pilot devices receive the change with a documented rollback.
  3. Update the authoritative FortiManager SD-WAN overlay template and review deployment scope before installing.
  4. The browser uses the configured proxy successfully with accepted user credentials.
  5. Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel.
  6. Match the user, timestamp, destination and policy action across authentication and traffic records.

Explanation

Correct Answers

A:

Correct verification element: Authenticate with a known-good test identity and inspect proxy auth and policy logs. This independently measures whether the intended change works. [Case R161-C218; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1090.]

D:

The browser uses the configured proxy successfully with accepted user credentials. This confirms the case-specific path or security boundary.

E:

Correct remediation element: Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel. It addresses A proxy authentication mismatch can persist even when the cloud proxy is reachable. [Case R161-C218; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1090.]

Incorrect Answers

B:

Incorrect for this case: Only approved pilot devices receive the change with a documented rollback. concerns the separate issue of Managed template change blast radius (A policy update is intended for ten pilot branches but targets the entire global branch device group.). It does not directly establish The browser uses the configured proxy successfully with accepted user credentials. The case-specific evidence is Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C218; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1090.]

C:

Incorrect for this case: Update the authoritative FortiManager SD-WAN overlay template and review deployment scope before installing. 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 Inspect proxy identity-source mapping and browser proxy settings rather than debugging an agent tunnel. The case-specific evidence is Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C218; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1090.]

F:

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 Authenticate with a known-good test identity and inspect proxy auth and policy logs. The case-specific evidence is Authenticate with a known-good test identity and inspect proxy auth and policy logs. [Case R161-C218; Fortinet task O3; anchors EXAM, SASE_DEM, SASE_LOG.] [Question R161-Q1090.]

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.