Fortinet NSE7_SSE_AR-26 Practice Test 78 - Prepaway
Practice Exams:

Pass Fortinet NSE7_SSE_AR-26 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$89.99 $98.99

NSE7_SSE_AR-26 Premium ETE File


  • Premium File 50 Questions & Answers. Last Update: Nov 13, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet NSE7_SSE_AR-26 Practice Test 78

Question 770

At fictional Cobalt Client Solutions, the SASE incident response engineering group observes: Two FortiGate peers report healthy IKE negotiation yet encrypted application packets fail because a transport MTU problem fragments the payload. Diagnostic evidence: Small probes pass but larger protected flows exhibit encapsulation drops and path-MTU-related errors. Which scoped action together with a separately measurable acceptance check is best?

  1. For fictional Cobalt Client Solutions, SASE incident response engineering group: Action: Repair the common hub certificate and SPA trust relationship before performing destructive endpoint reenrollment. Independent proof: Previously failing eligible users reconnect without mass reinstall and invalid peer certificates remain blocked.
  2. For fictional Cobalt Client Solutions, SASE incident response engineering group: Action: Inspect tunnel MTU and packet behavior, then apply only supported size/MSS adjustments consistent with the transport design. Independent proof: Small and large authorized test transfers work through the encrypted tunnel without introducing unencrypted bypass.
  3. For fictional Cobalt Client Solutions, SASE incident response engineering group: Action: Select the correct supported capture and FortiClient diagnostics for the actual protected flow and correlate with edge logs. Independent proof: One controlled request is visible along the expected client and service path with matched timestamps and session identifiers.
  4. For fictional Cobalt Client Solutions, SASE incident response engineering group: Action: Correct the protected application's authoritative internal DNS and connector resolver configuration. Independent proof: The approved hostname resolves to the expected private address and the permitted remote user completes a transaction.

Explanation

Correct Answer

B:

The proposed change is to inspect tunnel MTU and packet behavior, then apply only supported size/MSS adjustments consistent with the transport design. The separate proof is small and large authorized test transfers work through the encrypted tunnel without introducing unencrypted bypass. IPsec tunnel control-plane health does not guarantee usable application data-plane packet handling.

Incorrect Answers

A:

Action: Repair the common hub certificate and SPA trust relationship before performing destructive endpoint reenrollment. Independent proof: Previously failing eligible users reconnect without mass reinstall and invalid peer certificates remain blocked. It misses the relevant dependency because IPsec tunnel control-plane health does not guarantee usable application data-plane packet handling. Instead verify that small and large authorized test transfers work through the encrypted tunnel without introducing unencrypted bypass.

C:

The proposed pair addresses Action: Select the correct supported capture and FortiClient diagnostics for the actual protected flow and correlate with edge logs. Independent proof: One controlled request is visible along the expected client and service path with matched timestamps and session identifiers. Here small probes pass but larger protected flows exhibit encapsulation drops and path-MTU-related errors. The bounded response is inspect tunnel MTU and packet behavior, then apply only supported size/MSS adjustments consistent with the transport design with proof that small and large authorized test transfers work through the encrypted tunnel without introducing unencrypted bypass.

D:

The alternative action and test—Action: Correct the protected application's authoritative internal DNS and connector resolver configuration. Independent proof: The approved hostname resolves to the expected private address and the permitted remote user completes a transaction—would measure a different issue. This case requires inspect tunnel MTU and packet behavior, then apply only supported size/MSS adjustments consistent with the transport design and confirmation that small and large authorized test transfers work through the encrypted tunnel without introducing unencrypted bypass.

Question 771

At fictional Brookstone Research, the Fortinet centralized monitoring team correlates FortiManager, FortiAnalyzer and access telemetry. The observed FortiSASE 26/FortiOS 7.4–7.6 issue is: A remote FortiSASE user authenticates and reaches the SPA edge but cannot open one protected app while others work. Distinguishing technical evidence: SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Which bounded response is most defensible?

  1. For fictional Brookstone Research, Fortinet centralized monitoring team: Select the correct supported capture and FortiClient diagnostics for the actual protected flow and correlate with edge logs.
  2. For fictional Brookstone Research, Fortinet centralized monitoring team: Inspect tunnel MTU and packet behavior, then apply only supported size/MSS adjustments consistent with the transport design.
  3. For fictional Brookstone Research, Fortinet centralized monitoring team: Repair the common hub certificate and SPA trust relationship before performing destructive endpoint reenrollment.
  4. For fictional Brookstone Research, Fortinet centralized monitoring team: Correct the protected application's authoritative internal DNS and connector resolver configuration.

Explanation

Correct Answer

D:

Correct the protected application's authoritative internal DNS and connector resolver configuration. This addresses the evidence that SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Validate the outcome by checking that the approved hostname resolves to the expected private address and the permitted remote user completes a transaction. Preserve this constraint during the change: Adding a global DNS override may expose private names or break split-horizon application handling.

Incorrect Answers

A:

Another possible response is to select the correct supported capture and FortiClient diagnostics for the actual protected flow and correlate with edge logs. The case evidence instead shows that SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Private access success depends on authentication, overlay transport, internal name resolution and backend policy together.

B:

Inspect tunnel MTU and packet behavior, then apply only supported size/MSS adjustments consistent with the transport design. This does not address the reported incident: a remote FortiSASE user authenticates and reaches the SPA edge but cannot open one protected app while others work. SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. The case-specific correction is to correct the protected application's authoritative internal DNS and connector resolver configuration.

C:

One alternative would be to repair the common hub certificate and SPA trust relationship before performing destructive endpoint reenrollment. The observed evidence instead shows that SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. The more relevant correction is to correct the protected application's authoritative internal DNS and connector resolver configuration.

Question 772

At fictional Brookstone Research, the Fortinet centralized monitoring team examines this advanced Fortinet architecture incident: A remote FortiSASE user authenticates and reaches the SPA edge but cannot open one protected app while others work. Which observed finding most specifically distinguishes its cause before changing the configuration?

  1. For fictional Brookstone Research, Fortinet centralized monitoring team: SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver.
  2. For fictional Brookstone Research, Fortinet centralized monitoring team: The client's SASE steering creates a protected virtual path and the capture filter monitors only an unrelated adapter.
  3. For fictional Brookstone Research, Fortinet centralized monitoring team: Small probes pass but larger protected flows exhibit encapsulation drops and path-MTU-related errors.
  4. For fictional Brookstone Research, Fortinet centralized monitoring team: Synchronized failures began at certificate rotation and hub negotiation logs show peer trust-chain rejection for every affected client.

Explanation

Correct Answer

A:

SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. The fault is consistent with private access success depends on authentication, overlay transport, internal name resolution and backend policy together. A change targeting the actual dependency is to correct the protected application's authoritative internal DNS and connector resolver configuration.

Incorrect Answers

B:

The client's SASE steering creates a protected virtual path and the capture filter monitors only an unrelated adapter. It does not account for the observation SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver in the reported situation.

C:

One proposed finding is small probes pass but larger protected flows exhibit encapsulation drops and path-MTU-related errors. This would indicate another failure; here SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Private access success depends on authentication, overlay transport, internal name resolution and backend policy together.

D:

The alternative observation, synchronized failures began at certificate rotation and hub negotiation logs show peer trust-chain rejection for every affected client, concerns a different dependency. This incident is distinguished by SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Private access success depends on authentication, overlay transport, internal name resolution and backend policy together.

Question 773

At fictional Brookstone Research, the following problem has been reported: A remote FortiSASE user authenticates and reaches the SPA edge but cannot open one protected app while others work. Evidence: SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Proposed correction: Correct the protected application's authoritative internal DNS and connector resolver configuration. Which separate postchange test most convincingly verifies proper remediation?

  1. For fictional Brookstone Research, Fortinet centralized monitoring team: One controlled request is visible along the expected client and service path with matched timestamps and session identifiers.
  2. For fictional Brookstone Research, Fortinet centralized monitoring team: Previously failing eligible users reconnect without mass reinstall and invalid peer certificates remain blocked.
  3. For fictional Brookstone Research, Fortinet centralized monitoring team: Small and large authorized test transfers work through the encrypted tunnel without introducing unencrypted bypass.
  4. For fictional Brookstone Research, Fortinet centralized monitoring team: The approved hostname resolves to the expected private address and the permitted remote user completes a transaction.

Explanation

Correct Answer

D:

The acceptance evidence is the approved hostname resolves to the expected private address and the permitted remote user completes a transaction. This checks the intended outcome of correct the protected application's authoritative internal DNS and connector resolver configuration. Private access success depends on authentication, overlay transport, internal name resolution and backend policy together.

Incorrect Answers

A:

Even verifying one controlled request is visible along the expected client and service path with matched timestamps and session identifiers leaves the reported failure unproven. An acceptance test must show that the approved hostname resolves to the expected private address and the permitted remote user completes a transaction.

B:

The alternative outcome is previously failing eligible users reconnect without mass reinstall and invalid peer certificates remain blocked. It may validate a separate setting, but not the required action: correct the protected application's authoritative internal DNS and connector resolver configuration. The required observation is the approved hostname resolves to the expected private address and the permitted remote user completes a transaction.

C:

Small and large authorized test transfers work through the encrypted tunnel without introducing unencrypted bypass. The evidence relevant to this incident is SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Confirm the corresponding recovery result: The approved hostname resolves to the expected private address and the permitted remote user completes a transaction.

Question 774

At fictional Brookstone Research, operators encounter: A remote FortiSASE user authenticates and reaches the SPA edge but cannot open one protected app while others work. The key diagnostic observation is: SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Which Fortinet SD-WAN/FortiSASE architectural principle best informs the response?

  1. For fictional Brookstone Research, Fortinet centralized monitoring team: Correlated simultaneous failures often indicate shared service dependencies rather than independent endpoint faults.
  2. For fictional Brookstone Research, Fortinet centralized monitoring team: IPsec tunnel control-plane health does not guarantee usable application data-plane packet handling.
  3. For fictional Brookstone Research, Fortinet centralized monitoring team: Private access success depends on authentication, overlay transport, internal name resolution and backend policy together.
  4. For fictional Brookstone Research, Fortinet centralized monitoring team: Packet capture placement must follow actual data-path interfaces and encryption boundaries to produce meaningful evidence.

Explanation

Correct Answer

C:

Private access success depends on authentication, overlay transport, internal name resolution and backend policy together. This matters because a remote FortiSASE user authenticates and reaches the SPA edge but cannot open one protected app while others work. The specific evidence is SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver.

Incorrect Answers

A:

Correlated simultaneous failures often indicate shared service dependencies rather than independent endpoint faults. The decisive observation, SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver, requires a different explanation: Private access success depends on authentication, overlay transport, internal name resolution and backend policy together.

B:

A different principle is: IPsec tunnel control-plane health does not guarantee usable application data-plane packet handling. The causal link actually supported by SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver is private access success depends on authentication, overlay transport, internal name resolution and backend policy together.

D:

Packet capture placement must follow actual data-path interfaces and encryption boundaries to produce meaningful evidence. However, it does not explain SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. The applicable principle is that private access success depends on authentication, overlay transport, internal name resolution and backend policy together.

Question 775

At fictional Brookstone Research, the Fortinet centralized monitoring team observes: A remote FortiSASE user authenticates and reaches the SPA edge but cannot open one protected app while others work. Diagnostic evidence: SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Which scoped action together with a separately measurable acceptance check is best?

  1. For fictional Brookstone Research, Fortinet centralized monitoring team: Action: Correct the protected application's authoritative internal DNS and connector resolver configuration. Independent proof: The approved hostname resolves to the expected private address and the permitted remote user completes a transaction.
  2. For fictional Brookstone Research, Fortinet centralized monitoring team: Action: Repair the common hub certificate and SPA trust relationship before performing destructive endpoint reenrollment. Independent proof: Previously failing eligible users reconnect without mass reinstall and invalid peer certificates remain blocked.
  3. For fictional Brookstone Research, Fortinet centralized monitoring team: Action: Select the correct supported capture and FortiClient diagnostics for the actual protected flow and correlate with edge logs. Independent proof: One controlled request is visible along the expected client and service path with matched timestamps and session identifiers.
  4. For fictional Brookstone Research, Fortinet centralized monitoring team: Action: Inspect tunnel MTU and packet behavior, then apply only supported size/MSS adjustments consistent with the transport design. Independent proof: Small and large authorized test transfers work through the encrypted tunnel without introducing unencrypted bypass.

Explanation

Correct Answer

A:

Correct the protected application's authoritative internal DNS and connector resolver configuration. Confirm success only when the approved hostname resolves to the expected private address and the permitted remote user completes a transaction. The original finding was SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver.

Incorrect Answers

B:

Action: Repair the common hub certificate and SPA trust relationship before performing destructive endpoint reenrollment. Independent proof: Previously failing eligible users reconnect without mass reinstall and invalid peer certificates remain blocked. The pair does not resolve the observed SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Use correct the protected application's authoritative internal DNS and connector resolver configuration and verify the approved hostname resolves to the expected private address and the permitted remote user completes a transaction.

C:

The alternate plan combines Action: Select the correct supported capture and FortiClient diagnostics for the actual protected flow and correlate with edge logs. Independent proof: One controlled request is visible along the expected client and service path with matched timestamps and session identifiers. The identified fault is SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Closing it requires the approved hostname resolves to the expected private address and the permitted remote user completes a transaction.

D:

The alternative proposal is Action: Inspect tunnel MTU and packet behavior, then apply only supported size/MSS adjustments consistent with the transport design. Independent proof: Small and large authorized test transfers work through the encrypted tunnel without introducing unencrypted bypass. It does not address the current evidence: SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. The appropriate action is correct the protected application's authoritative internal DNS and connector resolver configuration.

Question 776

At fictional Maplebridge Systems, the SASE incident response engineering group investigates tunnels, endpoint flows and private access outages. The observed FortiSASE 26/FortiOS 7.4–7.6 issue is: A remote FortiSASE user authenticates and reaches the SPA edge but cannot open one protected app while others work. Distinguishing technical evidence: SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Which bounded response is most defensible?

  1. For fictional Maplebridge Systems, SASE incident response engineering group: Correct the protected application's authoritative internal DNS and connector resolver configuration.
  2. For fictional Maplebridge Systems, SASE incident response engineering group: Inspect tunnel MTU and packet behavior, then apply only supported size/MSS adjustments consistent with the transport design.
  3. For fictional Maplebridge Systems, SASE incident response engineering group: Repair the common hub certificate and SPA trust relationship before performing destructive endpoint reenrollment.
  4. For fictional Maplebridge Systems, SASE incident response engineering group: Select the correct supported capture and FortiClient diagnostics for the actual protected flow and correlate with edge logs.

Explanation

Correct Answer

A:

The evidence that SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver points to the need to correct the protected application's authoritative internal DNS and connector resolver configuration. Private access success depends on authentication, overlay transport, internal name resolution and backend policy together. Success is measured by the approved hostname resolves to the expected private address and the permitted remote user completes a transaction. Preserve this constraint during the change: Adding a global DNS override may expose private names or break split-horizon application handling.

Incorrect Answers

B:

Inspect tunnel MTU and packet behavior, then apply only supported size/MSS adjustments consistent with the transport design. It could be useful for another problem, but it does not change SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. The response needs to correct the protected application's authoritative internal DNS and connector resolver configuration.

C:

An alternative action is repair the common hub certificate and SPA trust relationship before performing destructive endpoint reenrollment. This incident instead involves SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Confirm the scoped change through the approved hostname resolves to the expected private address and the permitted remote user completes a transaction.

D:

Select the correct supported capture and FortiClient diagnostics for the actual protected flow and correlate with edge logs. That would not correct the reported SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. The supported response is to correct the protected application's authoritative internal DNS and connector resolver configuration.

Question 777

At fictional Maplebridge Systems, the SASE incident response engineering group examines this advanced Fortinet architecture incident: A remote FortiSASE user authenticates and reaches the SPA edge but cannot open one protected app while others work. Which observed finding most specifically distinguishes its cause before changing the configuration?

  1. For fictional Maplebridge Systems, SASE incident response engineering group: SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver.
  2. For fictional Maplebridge Systems, SASE incident response engineering group: Synchronized failures began at certificate rotation and hub negotiation logs show peer trust-chain rejection for every affected client.
  3. For fictional Maplebridge Systems, SASE incident response engineering group: Small probes pass but larger protected flows exhibit encapsulation drops and path-MTU-related errors.
  4. For fictional Maplebridge Systems, SASE incident response engineering group: The client's SASE steering creates a protected virtual path and the capture filter monitors only an unrelated adapter.

Explanation

Correct Answer

A:

The diagnostic clue is SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Private access success depends on authentication, overlay transport, internal name resolution and backend policy together. The response should therefore focus on correct the protected application's authoritative internal DNS and connector resolver configuration.

Incorrect Answers

B:

Synchronized failures began at certificate rotation and hub negotiation logs show peer trust-chain rejection for every affected client. That finding does not isolate the reported issue: a remote FortiSASE user authenticates and reaches the SPA edge but cannot open one protected app while others work. The determining evidence is SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver.

C:

That alternative instead describes small probes pass but larger protected flows exhibit encapsulation drops and path-MTU-related errors. The actual diagnostic record shows SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver instead. The difference matters because private access success depends on authentication, overlay transport, internal name resolution and backend policy together.

D:

Even if the client's SASE steering creates a protected virtual path and the capture filter monitors only an unrelated adapter, it would not establish the cause here. SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. The case-specific correction is to correct the protected application's authoritative internal DNS and connector resolver configuration.

Question 778

At fictional Maplebridge Systems, the following problem has been reported: A remote FortiSASE user authenticates and reaches the SPA edge but cannot open one protected app while others work. Evidence: SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Proposed correction: Correct the protected application's authoritative internal DNS and connector resolver configuration. Which separate postchange test most convincingly verifies proper remediation?

  1. For fictional Maplebridge Systems, SASE incident response engineering group: One controlled request is visible along the expected client and service path with matched timestamps and session identifiers.
  2. For fictional Maplebridge Systems, SASE incident response engineering group: Previously failing eligible users reconnect without mass reinstall and invalid peer certificates remain blocked.
  3. For fictional Maplebridge Systems, SASE incident response engineering group: The approved hostname resolves to the expected private address and the permitted remote user completes a transaction.
  4. For fictional Maplebridge Systems, SASE incident response engineering group: Small and large authorized test transfers work through the encrypted tunnel without introducing unencrypted bypass.

Explanation

Correct Answer

C:

The approved hostname resolves to the expected private address and the permitted remote user completes a transaction. Without that result, the finding SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver would remain unresolved.

Incorrect Answers

A:

A test that one controlled request is visible along the expected client and service path with matched timestamps and session identifiers would not demonstrate closure of this condition. The needed proof is the approved hostname resolves to the expected private address and the permitted remote user completes a transaction.

B:

Previously failing eligible users reconnect without mass reinstall and invalid peer certificates remain blocked. That does not demonstrate the case-specific success condition: the approved hostname resolves to the expected private address and the permitted remote user completes a transaction. Private access success depends on authentication, overlay transport, internal name resolution and backend policy together.

D:

Small and large authorized test transfers work through the encrypted tunnel without introducing unencrypted bypass. That result does not test the original problem, identified by SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Recovery must show that the approved hostname resolves to the expected private address and the permitted remote user completes a transaction.

Question 779

At fictional Maplebridge Systems, operators encounter: A remote FortiSASE user authenticates and reaches the SPA edge but cannot open one protected app while others work. The key diagnostic observation is: SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Which Fortinet SD-WAN/FortiSASE architectural principle best informs the response?

  1. For fictional Maplebridge Systems, SASE incident response engineering group: Correlated simultaneous failures often indicate shared service dependencies rather than independent endpoint faults.
  2. For fictional Maplebridge Systems, SASE incident response engineering group: Private access success depends on authentication, overlay transport, internal name resolution and backend policy together.
  3. For fictional Maplebridge Systems, SASE incident response engineering group: IPsec tunnel control-plane health does not guarantee usable application data-plane packet handling.
  4. For fictional Maplebridge Systems, SASE incident response engineering group: Packet capture placement must follow actual data-path interfaces and encryption boundaries to produce meaningful evidence.

Explanation

Correct Answer

B:

Private access success depends on authentication, overlay transport, internal name resolution and backend policy together. The diagnostic record, SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver, fits that mechanism rather than a separate system issue.

Incorrect Answers

A:

A proposed explanation is correlated simultaneous failures often indicate shared service dependencies rather than independent endpoint faults. The present evidence is SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver, which instead follows from private access success depends on authentication, overlay transport, internal name resolution and backend policy together.

C:

IPsec tunnel control-plane health does not guarantee usable application data-plane packet handling. This describes another relationship, not the cause of a remote FortiSASE user authenticates and reaches the SPA edge but cannot open one protected app while others work. Private access success depends on authentication, overlay transport, internal name resolution and backend policy together.

D:

The rule packet capture placement must follow actual data-path interfaces and encryption boundaries to produce meaningful evidence does not account for SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. This case is governed by private access success depends on authentication, overlay transport, internal name resolution and backend policy together.

Question 780

At fictional Maplebridge Systems, the SASE incident response engineering group observes: A remote FortiSASE user authenticates and reaches the SPA edge but cannot open one protected app while others work. Diagnostic evidence: SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. Which scoped action together with a separately measurable acceptance check is best?

  1. For fictional Maplebridge Systems, SASE incident response engineering group: Action: Select the correct supported capture and FortiClient diagnostics for the actual protected flow and correlate with edge logs. Independent proof: One controlled request is visible along the expected client and service path with matched timestamps and session identifiers.
  2. For fictional Maplebridge Systems, SASE incident response engineering group: Action: Correct the protected application's authoritative internal DNS and connector resolver configuration. Independent proof: The approved hostname resolves to the expected private address and the permitted remote user completes a transaction.
  3. For fictional Maplebridge Systems, SASE incident response engineering group: Action: Inspect tunnel MTU and packet behavior, then apply only supported size/MSS adjustments consistent with the transport design. Independent proof: Small and large authorized test transfers work through the encrypted tunnel without introducing unencrypted bypass.
  4. For fictional Maplebridge Systems, SASE incident response engineering group: Action: Repair the common hub certificate and SPA trust relationship before performing destructive endpoint reenrollment. Independent proof: Previously failing eligible users reconnect without mass reinstall and invalid peer certificates remain blocked.

Explanation

Correct Answer

B:

Private access success depends on authentication, overlay transport, internal name resolution and backend policy together. The action is to correct the protected application's authoritative internal DNS and connector resolver configuration; the independent test is that the approved hostname resolves to the expected private address and the permitted remote user completes a transaction.

Incorrect Answers

A:

Action: Select the correct supported capture and FortiClient diagnostics for the actual protected flow and correlate with edge logs. Independent proof: One controlled request is visible along the expected client and service path with matched timestamps and session identifiers. It misses the relevant dependency because private access success depends on authentication, overlay transport, internal name resolution and backend policy together. Instead verify that the approved hostname resolves to the expected private address and the permitted remote user completes a transaction.

C:

The proposed pair addresses Action: Inspect tunnel MTU and packet behavior, then apply only supported size/MSS adjustments consistent with the transport design. Independent proof: Small and large authorized test transfers work through the encrypted tunnel without introducing unencrypted bypass. Here SPA logs show accepted user and connector sessions, but the internal backend FQDN lookup fails from the connector's resolver. The bounded response is correct the protected application's authoritative internal DNS and connector resolver configuration with proof that the approved hostname resolves to the expected private address and the permitted remote user completes a transaction.

D:

The alternative action and test—Action: Repair the common hub certificate and SPA trust relationship before performing destructive endpoint reenrollment. Independent proof: Previously failing eligible users reconnect without mass reinstall and invalid peer certificates remain blocked—would measure a different issue. This case requires correct the protected application's authoritative internal DNS and connector resolver configuration and confirmation that the approved hostname resolves to the expected private address and the permitted remote user completes a transaction.

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