Fortinet NSE5_SSE_AD-7.6 Practice Test 49 - Prepaway
Practice Exams:

Pass Fortinet NSE5_SSE_AD-7.6 Exam in First Attempt Guaranteed!

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

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$69.99 $76.99

NSE5_SSE_AD-7.6 Premium ETE File


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

Fortinet NSE5_SSE_AD-7.6 Practice Test 49

Question 480

At Westport Managed Security, the team administers hybrid remote-user and FortiGate private access integration and must preserve correct cloud security service onboarding and private-route scope. Operational incident: Remote FortiSASE users can authenticate and reach internet services but cannot access a private site behind the FortiGate hub. Confirmed observation: The SPA or connected SD-WAN overlay is established, but the FortiSASE routing view lacks the branch private application subnet. Which approved change and separate test together resolve the issue?

  1. Action: Apply the supported least-privilege administrator role and tenant scope, testing with controlled accounts. Proof: The analyst can view onboarding status but cannot edit global content policy; authorized security admins retain edit capability.
  2. Action: Advertise or install the authorized branch route through the documented SASE-to-FortiGate integration and check return routing. Proof: A permitted remote user reaches the private application and the FortiGate session returns correctly through the intended overlay.
  3. Action: Update the approved SSO integration metadata and trust settings, validate the service-provider and identity-provider match and test login. Proof: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected.
  4. Action: Correlate the correct endpoint, URL/file identity, policy outcome and session timestamps before selecting containment. Proof: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.

Explanation

Correct Answer

B:

This pair is the bounded choice for Westport Managed Security: Action: Advertise or install the authorized branch route through the documented SASE-to-FortiGate integration and check return routing. Proof: A permitted remote user reaches the private application and the FortiGate session returns correctly through the intended overlay. The underlying issue is: Remote FortiSASE users can authenticate and reach internet services but cannot access a private site behind the FortiGate hub. Confirm the recorded outcome: A permitted remote user reaches the private application and the FortiGate session returns correctly through the intended overlay.

Incorrect Answers

A:

Action: Apply the supported least-privilege administrator role and tenant scope, testing with controlled accounts. Proof: The analyst can view onboarding status but cannot edit global content policy; authorized security admins retain edit capability. The actual issue at Westport Managed Security is: Remote FortiSASE users can authenticate and reach internet services but cannot access a private site behind the FortiGate hub. The proposed verification does not establish that the required result is: A permitted remote user reaches the private application and the FortiGate session returns correctly through the intended overlay.

C:

Action: Update the approved SSO integration metadata and trust settings, validate the service-provider and identity-provider match and test login. Proof: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected. The recorded evidence at Westport Managed Security is: The SPA or connected SD-WAN overlay is established, but the FortiSASE routing view lacks the branch private application subnet. The correct outcome to measure is: A permitted remote user reaches the private application and the FortiGate session returns correctly through the intended overlay.

D:

Action: Correlate the correct endpoint, URL/file identity, policy outcome and session timestamps before selecting containment. Proof: The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation. The relevant Westport Managed Security observation is: The SPA or connected SD-WAN overlay is established, but the FortiSASE routing view lacks the branch private application subnet. Any successful correction still needs to verify: A permitted remote user reaches the private application and the FortiGate session returns correctly through the intended overlay.

Question 481

For Evergreen Distribution Security, operators support FortiSASE tenant administration and user enrollment and are expected to enforce approved identities, tenant boundaries and endpoint licensing. Operational incident: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. Confirmed observation: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. Which approved correction best addresses the documented root cause?

  1. Validate the actual SASE-to-hub source and identity context and correct the approved HR-only rule rather than allowing every remote user.
  2. Apply the supported least-privilege administrator role and tenant scope, testing with controlled accounts.
  3. Create a narrow authorized hub security policy for required SASE service-origin sources and private application ports, with inspection.
  4. Update SD-WAN membership bindings and dependent zone and rule scope to the active approved interface.

Explanation

Correct Answer

C:

At Evergreen Distribution Security, the evidence establishes the immediate concern: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. The appropriate response is: Create a narrow authorized hub security policy for required SASE service-origin sources and private application ports, with inspection. The causal rule is: Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub. The required outcome is: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

Incorrect Answers

A:

Another proposed response centers on: Validate the actual SASE-to-hub source and identity context and correct the approved HR-only rule rather than allowing every remote user. The reported Evergreen Distribution Security failure is: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. The decisive record shows: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service.

B:

Another suggested intervention is: Apply the supported least-privilege administrator role and tenant scope, testing with controlled accounts. It is not sufficient evidence of resolving the Evergreen Distribution Security condition: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. The measurable outcome still required is: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

D:

Another option proposes: Update SD-WAN membership bindings and dependent zone and rule scope to the active approved interface. At Evergreen Distribution Security, the decisive evidence is: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. That step alone does not demonstrate correction of the specified problem: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall.

Question 482

At Evergreen Distribution Security, the team administers FortiSASE tenant administration and user enrollment and must enforce approved identities, tenant boundaries and endpoint licensing. Operational incident: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. The team must verify the root cause before changing production settings. What measured finding directly supports the recorded issue?

  1. Effective group-to-client profile mappings show the contractor identity is included in an inherited general employee assignment.
  2. Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store.
  3. Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service.
  4. The approved secondary WAN interface is operational at layer 3 but is absent from the effective FortiGate SD-WAN membership list.

Explanation

Correct Answer

C:

At Evergreen Distribution Security, the reported condition is: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. The specifically relevant observation is: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. That distinction is explained by: Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub.

Incorrect Answers

A:

Effective group-to-client profile mappings show the contractor identity is included in an inherited general employee assignment. It is not the discriminating clue in this record; that clue is: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. The Evergreen Distribution Security issue is: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall.

B:

Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. The trace for Evergreen Distribution Security instead establishes: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. This is the clue to the issue actually described.

D:

The approved secondary WAN interface is operational at layer 3 but is absent from the effective FortiGate SD-WAN membership list. At Evergreen Distribution Security, the recorded condition is: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. The particular evidence supporting it is: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service.

Question 483

For Evergreen Distribution Security, operators support FortiSASE tenant administration and user enrollment and are expected to enforce approved identities, tenant boundaries and endpoint licensing. Operational incident: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. Confirmed observation: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. Proposed controlled action: Create a narrow authorized hub security policy for required SASE service-origin sources and private application ports, with inspection. Which independent test would establish that the original problem is resolved?

  1. The test device from each intended platform authenticates and reports a managed SASE session with correct posture.
  2. A sanctioned test user gains only subscribed access after an approved license change, while unsupported options remain unavailable.
  3. Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.
  4. The application prefix resolves to the correct overlay next hop and unrelated intentionally blocked prefixes remain dropped.

Explanation

Correct Answer

C:

The reported failure at Evergreen Distribution Security is: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. The necessary independent result is: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied. It tests recovery against the original evidence: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service.

Incorrect Answers

A:

The test device from each intended platform authenticates and reports a managed SASE session with correct posture. The acceptance condition for the stated Evergreen Distribution Security fault is: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied. The tests do not measure the same outcome.

B:

An alternative finding would be: A sanctioned test user gains only subscribed access after an approved license change, while unsupported options remain unavailable. The applicable acceptance criterion at Evergreen Distribution Security is: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied. That result is related to the original issue.

D:

The application prefix resolves to the correct overlay next hop and unrelated intentionally blocked prefixes remain dropped. That alone would not confirm correction of the Evergreen Distribution Security problem: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. The necessary proof is: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

Question 484

At Evergreen Distribution Security, the team administers FortiSASE tenant administration and user enrollment and must enforce approved identities, tenant boundaries and endpoint licensing. Operational incident: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. Recorded observation: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. What platform design concept best accounts for the symptoms?

  1. Preconfigured enrollment packages carry tenant identity and must not be exchanged across customer organizations.
  2. Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub.
  3. Authentication establishes identity; authorization relies on accurate policy groups and assignment.
  4. Stateful applications and their remote peers may depend on stable path and source identity even when links individually work.

Explanation

Correct Answer

B:

The case is best understood through: Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub. The record at Evergreen Distribution Security shows: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. The failure requiring explanation is: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall.

Incorrect Answers

A:

Another principle is: Preconfigured enrollment packages carry tenant identity and must not be exchanged across customer organizations. It is not enough to account for the recorded Evergreen Distribution Security evidence: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. The applicable rule is: Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub.

C:

An alternative explanation is: Authentication establishes identity; authorization relies on accurate policy groups and assignment. It is not the reason established by the Evergreen Distribution Security clue: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. The relevant causal relationship is: Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub.

D:

Stateful applications and their remote peers may depend on stable path and source identity even when links individually work. At Evergreen Distribution Security, the reported issue is: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. The stated observations instead follow from: Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub.

Question 485

For Evergreen Distribution Security, operators support FortiSASE tenant administration and user enrollment and are expected to enforce approved identities, tenant boundaries and endpoint licensing. Operational incident: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. Confirmed observation: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. Which scoped action plus measurable success result should the team choose?

  1. Action: Restore the baseline and implement a supported narrower exception assigned to only the permitted user group. Proof: The approved department can access its justified site while the same site remains restricted for out-of-scope users.
  2. Action: Apply the supported least-privilege administrator role and tenant scope, testing with controlled accounts. Proof: The analyst can view onboarding status but cannot edit global content policy; authorized security admins retain edit capability.
  3. Action: Create a narrow authorized hub security policy for required SASE service-origin sources and private application ports, with inspection. Proof: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.
  4. Action: Correct analytic scope and event severity filters, preserving source logs, and correlate link events with session impact. Proof: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms.

Explanation

Correct Answer

C:

Action: Create a narrow authorized hub security policy for required SASE service-origin sources and private application ports, with inspection. Proof: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied. The Evergreen Distribution Security incident is: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. The required result is: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

Incorrect Answers

A:

Action: Restore the baseline and implement a supported narrower exception assigned to only the permitted user group. Proof: The approved department can access its justified site while the same site remains restricted for out-of-scope users. They do not directly establish recovery of the reported Evergreen Distribution Security problem: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. Verification requires: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

B:

Action: Apply the supported least-privilege administrator role and tenant scope, testing with controlled accounts. Proof: The analyst can view onboarding status but cannot edit global content policy; authorized security admins retain edit capability. It would not by itself demonstrate correction of the Evergreen Distribution Security finding: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. The required outcome is: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

D:

Action: Correct analytic scope and event severity filters, preserving source logs, and correlate link events with session impact. Proof: The rebuilt incident timeline shows the link transitions and affected application sessions without false link alarms. At Evergreen Distribution Security, the actual distinguishing clue is: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. The related test must establish: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

Question 486

At Silverpeak Cloud Services, the team administers hybrid remote-user and FortiGate private access integration and must preserve correct cloud security service onboarding and private-route scope. Operational incident: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. Confirmed observation: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. Which supported administrator action should address this issue with the least unrelated impact?

  1. Create a narrow authorized hub security policy for required SASE service-origin sources and private application ports, with inspection.
  2. Advertise or install the authorized branch route through the documented SASE-to-FortiGate integration and check return routing.
  3. Apply the supported least-privilege administrator role and tenant scope, testing with controlled accounts.
  4. Align the SLA target with measured voice requirements and choose the appropriate service steering rule and eligible links.

Explanation

Correct Answer

A:

The issue at Silverpeak Cloud Services is: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. The proposed action follows the discriminating evidence: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. The change is: Create a narrow authorized hub security policy for required SASE service-origin sources and private application ports, with inspection. Check that: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

Incorrect Answers

B:

An alternative action is: Advertise or install the authorized branch route through the documented SASE-to-FortiGate integration and check return routing. The observed evidence in Silverpeak Cloud Services instead establishes: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. A relevant response must address that observation and confirm: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

C:

The suggested alternative is: Apply the supported least-privilege administrator role and tenant scope, testing with controlled accounts. The case identifies the cause at Silverpeak Cloud Services using: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. Implementing that step alone would not verify: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

D:

Another proposed action is: Align the SLA target with measured voice requirements and choose the appropriate service steering rule and eligible links. In Silverpeak Cloud Services, the relevant evidence is: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. The focused correction should address the root condition shown by that clue.

Question 487

For Silverpeak Cloud Services, operators support hybrid remote-user and FortiGate private access integration and are expected to preserve correct cloud security service onboarding and private-route scope. Operational incident: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. The team must verify the root cause before changing production settings. Which piece of evidence distinguishes this cause from unrelated symptoms?

  1. Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store.
  2. Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service.
  3. Client logs report a platform or build mismatch and the FortiSASE portal offers separate platform-specific onboarding packages.
  4. SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay.

Explanation

Correct Answer

B:

Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. In Silverpeak Cloud Services, the problem described is: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall.

Incorrect Answers

A:

Another possibility is: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. The current case at Silverpeak Cloud Services contains a different identifying observation: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. The relevant mechanism is: Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub.

C:

Client logs report a platform or build mismatch and the FortiSASE portal offers separate platform-specific onboarding packages. It does not directly identify the problem reported at Silverpeak Cloud Services. The determining evidence is: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service.

D:

SD-WAN session logs show a fallback rule ID and route lookup to the general internet zone rather than the private overlay. It does not substantiate the particular Silverpeak Cloud Services condition: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. The documented finding is: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service.

Question 488

At Silverpeak Cloud Services, the team administers hybrid remote-user and FortiGate private access integration and must preserve correct cloud security service onboarding and private-route scope. Operational incident: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. Confirmed observation: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. Proposed controlled action: Create a narrow authorized hub security policy for required SASE service-origin sources and private application ports, with inspection. Which accepted outcome confirms the intended behavior?

  1. A controlled bidirectional private session keeps both directions on the secure overlay without disrupting branch internet traffic.
  2. The approved employee obtains their specific access policy and a control identity outside the group remains restricted.
  3. A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.
  4. Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

Explanation

Correct Answer

D:

Independent closure should establish: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied. This directly corresponds to the Silverpeak Cloud Services finding: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. It supports recovery of the stated problem: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall.

Incorrect Answers

A:

Another check would be: A controlled bidirectional private session keeps both directions on the secure overlay without disrupting branch internet traffic. The relevant Silverpeak Cloud Services problem requires a distinct success condition: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied. The governing rule is: Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub.

B:

The approved employee obtains their specific access policy and a control identity outside the group remains restricted. It is not the evidence needed to close the reported issue. The proper Silverpeak Cloud Services success measure is: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

C:

An alternative test would show: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited. It does not show the required post-change result at Silverpeak Cloud Services: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied. The original finding was: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service.

Question 489

For Silverpeak Cloud Services, operators support hybrid remote-user and FortiGate private access integration and are expected to preserve correct cloud security service onboarding and private-route scope. Operational incident: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. Recorded observation: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. Which network security or traffic-steering principle explains this behavior?

  1. Identity-based management permissions must separate observation and support from configuration change authority.
  2. Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub.
  3. SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement.
  4. A failed monitoring endpoint is not always equivalent to failure of the transport carrying business traffic.

Explanation

Correct Answer

B:

At Silverpeak Cloud Services, the evidence is: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. The principle that explains it is: Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub. It connects that clue to the specified failure.

Incorrect Answers

A:

Another relationship would be: Identity-based management permissions must separate observation and support from configuration change authority. It does not account for the issue reported by Silverpeak Cloud Services: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. The applicable principle is: Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub.

C:

SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement. The failure at Silverpeak Cloud Services is: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. The operating rule directly related to that failure is: Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub.

D:

A failed monitoring endpoint is not always equivalent to failure of the transport carrying business traffic. In Silverpeak Cloud Services, the actual observation is: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. The rule connected to that evidence is: Integrating SASE and SD-WAN requires matching firewall admission and route reachability at the private-access hub.

Question 490

At Silverpeak Cloud Services, the team administers hybrid remote-user and FortiGate private access integration and must preserve correct cloud security service onboarding and private-route scope. Operational incident: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. Confirmed observation: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. What remediation-and-validation combination most directly addresses this incident?

  1. Action: Distribute the approved FortiSASE CA through supported managed endpoint onboarding and validate installation and inspection policy. Proof: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.
  2. Action: Issue a fresh supported tenant-scoped onboarding invitation and verify enrollment using an approved test endpoint. Proof: The authorized managed client registers to the intended tenant and receives its permitted connection configuration.
  3. Action: Create a narrow authorized hub security policy for required SASE service-origin sources and private application ports, with inspection. Proof: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.
  4. Action: Add the verified overlay member to an appropriate service-specific performance SLA and establish a valid reachable probe target. Proof: Its own latency and loss observations appear and a controlled impairment updates its status without changing unrelated paths.

Explanation

Correct Answer

C:

The option addresses the actual fault and includes measurable proof: Action: Create a narrow authorized hub security policy for required SASE service-origin sources and private application ports, with inspection. Proof: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied. The case evidence at Silverpeak Cloud Services is: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. The acceptance target is: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

Incorrect Answers

A:

Action: Distribute the approved FortiSASE CA through supported managed endpoint onboarding and validate installation and inspection policy. Proof: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked. The actual issue at Silverpeak Cloud Services is: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall. The proposed verification does not establish that the required result is: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

B:

Action: Issue a fresh supported tenant-scoped onboarding invitation and verify enrollment using an approved test endpoint. Proof: The authorized managed client registers to the intended tenant and receives its permitted connection configuration. It is not sufficient proof of resolution for the stated Silverpeak Cloud Services incident: FortiSASE users can reach the branch VPN hub but their permitted private application sessions are denied at the hub firewall.

D:

Action: Add the verified overlay member to an appropriate service-specific performance SLA and establish a valid reachable probe target. Proof: Its own latency and loss observations appear and a controlled impairment updates its status without changing unrelated paths. The relevant Silverpeak Cloud Services observation is: Hub firewall logs identify traffic from the approved FortiSASE service endpoints matched by an unintended implicit deny before the application service. Any successful correction still needs to verify: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests