Fortinet NSE5_SSE_AD-7.6 Practice Test 45 - 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 45

Question 440

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: A new employee passes single sign-on but has no permitted tunnel or security-group policy after onboarding. Confirmed observation: Authentication is successful in logs while group claim mapping omits the employee's approved access group in the FortiSASE policy scope. Which scoped action plus measurable success result should the team choose?

  1. 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.
  2. Action: Correct supported identity group synchronization and mapped SASE user/group authorization without a blanket accept rule. Proof: The approved employee obtains their specific access policy and a control identity outside the group remains restricted.
  3. Action: Configure approved split DNS or internal resolver forwarding for that specific namespace and validate private service reachability. Proof: The corporate name resolves to the approved private target and a permitted SASE client completes its secured private session.
  4. Action: Create a narrowly scoped firewall policy referencing the appropriate source and SD-WAN destination zone with approved security profiles. Proof: A controlled sanctioned web transaction passes over local internet and an unauthorized source remains denied and logged.

Explanation

Correct Answer

B:

This pair is the bounded choice for Westport Managed Security: Action: Correct supported identity group synchronization and mapped SASE user/group authorization without a blanket accept rule. Proof: The approved employee obtains their specific access policy and a control identity outside the group remains restricted. The underlying issue is: A new employee passes single sign-on but has no permitted tunnel or security-group policy after onboarding. Confirm the recorded outcome: The approved employee obtains their specific access policy and a control identity outside the group remains restricted.

Incorrect Answers

A:

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. The actual issue at Westport Managed Security is: A new employee passes single sign-on but has no permitted tunnel or security-group policy after onboarding. The proposed verification does not establish that the required result is: The approved employee obtains their specific access policy and a control identity outside the group remains restricted.

C:

Action: Configure approved split DNS or internal resolver forwarding for that specific namespace and validate private service reachability. Proof: The corporate name resolves to the approved private target and a permitted SASE client completes its secured private session. The recorded evidence at Westport Managed Security is: Authentication is successful in logs while group claim mapping omits the employee's approved access group in the FortiSASE policy scope. The correct outcome to measure is: The approved employee obtains their specific access policy and a control identity outside the group remains restricted.

D:

Action: Create a narrowly scoped firewall policy referencing the appropriate source and SD-WAN destination zone with approved security profiles. Proof: A controlled sanctioned web transaction passes over local internet and an unauthorized source remains denied and logged. The relevant Westport Managed Security observation is: Authentication is successful in logs while group claim mapping omits the employee's approved access group in the FortiSASE policy scope. Any successful correction still needs to verify: The approved employee obtains their specific access policy and a control identity outside the group remains restricted.

Question 441

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: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. Confirmed observation: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. 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. Distribute the approved FortiSASE CA through supported managed endpoint onboarding and validate installation and inspection policy.
  3. Constrain authorized hub routing and SD-WAN service strategy to the correct overlay for the documented SASE client prefixes.
  4. Enroll the approved backup member in the relevant health check and verify the steering strategy's eligible member set.

Explanation

Correct Answer

B:

The offered response addresses Evergreen Distribution Security's specific finding: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. Apply the scoped change: Distribute the approved FortiSASE CA through supported managed endpoint onboarding and validate installation and inspection policy. The underlying mechanism is: SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement. Look for this independent result: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.

Incorrect Answers

A:

Another proposed response centers on: Create a narrow authorized hub security policy for required SASE service-origin sources and private application ports, with inspection. The reported Evergreen Distribution Security failure is: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. The decisive record shows: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store.

C:

Constrain authorized hub routing and SD-WAN service strategy to the correct overlay for the documented SASE client prefixes. The reported failure at Evergreen Distribution Security is: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. Its independent recovery check must establish: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.

D:

Another option proposes: Enroll the approved backup member in the relevant health check and verify the steering strategy's eligible member set. At Evergreen Distribution Security, the decisive evidence is: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. That step alone does not demonstrate correction of the specified problem: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled.

Question 442

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: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. The team must verify the root cause before changing production settings. Which piece of evidence distinguishes this cause from unrelated symptoms?

  1. Client logs report a platform or build mismatch and the FortiSASE portal offers separate platform-specific onboarding packages.
  2. Connection diagnostics show the remote client uses an authorized but distant security PoP despite a nearer supported regional choice.
  3. The routing table installs a more-specific discard route for the application's private subnet above the valid overlay path.
  4. Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store.

Explanation

Correct Answer

D:

For Evergreen Distribution Security, the decisive evidence is: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. It connects the reported failure to the actual operating dependency: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. The relevant rule is: SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement.

Incorrect Answers

A:

Client logs report a platform or build mismatch and the FortiSASE portal offers separate platform-specific onboarding packages. It is not the discriminating clue in this record; that clue is: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. The Evergreen Distribution Security issue is: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled.

B:

Connection diagnostics show the remote client uses an authorized but distant security PoP despite a nearer supported regional choice. The trace for Evergreen Distribution Security instead establishes: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. This is the clue to the issue actually described.

C:

The routing table installs a more-specific discard route for the application's private subnet above the valid overlay path. The reported Evergreen Distribution Security fault is: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. The signal that actually distinguishes it is: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store.

Question 443

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: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. Confirmed observation: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. Proposed controlled action: Distribute the approved FortiSASE CA through supported managed endpoint onboarding and validate installation and inspection policy. Which accepted outcome confirms the intended behavior?

  1. A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.
  2. The authorized managed client registers to the intended tenant and receives its permitted connection configuration.
  3. A sanctioned test user gains only subscribed access after an approved license change, while unsupported options remain unavailable.
  4. A controlled route impairment toward finance is detected before prolonged user loss, while other traffic retains its own policy.

Explanation

Correct Answer

A:

For Evergreen Distribution Security, an accepted fix must show: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked. The initial diagnostic clue was: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. The result therefore tests the stated failure rather than a separate control.

Incorrect Answers

B:

An alternative finding would be: The authorized managed client registers to the intended tenant and receives its permitted connection configuration. The applicable acceptance criterion at Evergreen Distribution Security is: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked. That result is related to the original issue.

C:

A sanctioned test user gains only subscribed access after an approved license change, while unsupported options remain unavailable. The recorded clue at Evergreen Distribution Security is: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. Closure has to validate the corresponding result: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.

D:

A controlled route impairment toward finance is detected before prolonged user loss, while other traffic retains its own policy. That alone would not confirm correction of the Evergreen Distribution Security problem: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. The necessary proof is: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.

Question 444

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: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. Recorded observation: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. Which network security or traffic-steering principle explains this behavior?

  1. Application-specific DNS resolution must align with private routes for split-access designs to work.
  2. Client installation and validated tenant enrollment are separate requirements for managed FortiSASE onboarding.
  3. SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement.
  4. Aggregate security counts can conceal concentrated identity-specific abuse patterns.

Explanation

Correct Answer

C:

The governing principle is: SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement. The Evergreen Distribution Security record contains the corresponding signal: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. This accounts for the stated issue.

Incorrect Answers

A:

Another principle is: Application-specific DNS resolution must align with private routes for split-access designs to work. It is not enough to account for the recorded Evergreen Distribution Security evidence: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. The applicable rule is: SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement.

B:

Client installation and validated tenant enrollment are separate requirements for managed FortiSASE onboarding. The documented Evergreen Distribution Security failure is: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. The case is instead explained by: SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement.

D:

Aggregate security counts can conceal concentrated identity-specific abuse patterns. At Evergreen Distribution Security, the reported issue is: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. The stated observations instead follow from: SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement.

Question 445

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: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. Confirmed observation: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. 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: Confirm the licensed feature and approved entitlement before configuring a supported design or obtaining authorized upgrade. Proof: A sanctioned test user gains only subscribed access after an approved license change, while unsupported options remain unavailable.
  3. Action: Constrain authorized hub routing and SD-WAN service strategy to the correct overlay for the documented SASE client prefixes. Proof: A controlled bidirectional private session keeps both directions on the secure overlay without disrupting branch internet traffic.
  4. Action: Set the sanctioned file type block within the correctly applied profile group and verify a safe fixture download. Proof: A harmless executable-type test is blocked while the approved PDF control completes with expected logs.

Explanation

Correct Answer

A:

The documented fault is: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. The selected change-plus-verification is: 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. That pair responds to the Evergreen Distribution Security observation: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store.

Incorrect Answers

B:

Action: Confirm the licensed feature and approved entitlement before configuring a supported design or obtaining authorized upgrade. Proof: A sanctioned test user gains only subscribed access after an approved license change, while unsupported options remain unavailable. It would not by itself demonstrate correction of the Evergreen Distribution Security finding: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. The required outcome is: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.

C:

An alternative option suggests: Action: Constrain authorized hub routing and SD-WAN service strategy to the correct overlay for the documented SASE client prefixes. Proof: A controlled bidirectional private session keeps both directions on the secure overlay without disrupting branch internet traffic. The documented Evergreen Distribution Security problem calls for a check against: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked. The original clue is: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store.

D:

Action: Set the sanctioned file type block within the correctly applied profile group and verify a safe fixture download. Proof: A harmless executable-type test is blocked while the approved PDF control completes with expected logs. At Evergreen Distribution Security, the actual distinguishing clue is: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. The related test must establish: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.

Question 446

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: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. Confirmed observation: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. What scoped change is justified by the observed evidence?

  1. Configure approved split DNS or internal resolver forwarding for that specific namespace and validate private service reachability.
  2. Distribute the approved FortiSASE CA through supported managed endpoint onboarding and validate installation and inspection policy.
  3. Advertise or install the authorized branch route through the documented SASE-to-FortiGate integration and check return routing.
  4. Add and validate the approved jitter criterion to the relevant SLA target and associate it with the voice and video rule.

Explanation

Correct Answer

B:

The issue at Silverpeak Cloud Services is: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. Distribute the approved FortiSASE CA through supported managed endpoint onboarding and validate installation and inspection policy. A valid post-change result is: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.

Incorrect Answers

A:

Although that step is: Configure approved split DNS or internal resolver forwarding for that specific namespace and validate private service reachability, the decisive observation here is: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. That choice alone does not establish the needed correction at Silverpeak Cloud Services.

C:

The suggested alternative is: Advertise or install the authorized branch route through the documented SASE-to-FortiGate integration and check return routing. The case identifies the cause at Silverpeak Cloud Services using: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. Implementing that step alone would not verify: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.

D:

Another proposed action is: Add and validate the approved jitter criterion to the relevant SLA target and associate it with the voice and video rule. In Silverpeak Cloud Services, the relevant evidence is: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. The focused correction should address the root condition shown by that clue.

Question 447

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: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. The team must verify the root cause before changing production settings. Which specific observation should determine the next investigation step?

  1. FortiSASE group mapping indicates HR membership but the hub's effective access policy references a different SASE user or source segment.
  2. The hub's route and SD-WAN rule selects the public underlay for the SASE client pool, not the intended encrypted overlay member.
  3. The matching SD-WAN rule uses a manual single-member selection and has no approved recovery option for the payment traffic.
  4. Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store.

Explanation

Correct Answer

D:

The observation pinpoints the documented weakness: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. The Silverpeak Cloud Services case concerns: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement.

Incorrect Answers

A:

Another possibility is: FortiSASE group mapping indicates HR membership but the hub's effective access policy references a different SASE user or source segment. The current case at Silverpeak Cloud Services contains a different identifying observation: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. The relevant mechanism is: SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement.

B:

The hub's route and SD-WAN rule selects the public underlay for the SASE client pool, not the intended encrypted overlay member. The original Silverpeak Cloud Services observation is instead: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. That is the evidence tied to the stated failure.

C:

The matching SD-WAN rule uses a manual single-member selection and has no approved recovery option for the payment traffic. It does not directly identify the problem reported at Silverpeak Cloud Services. The determining evidence is: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store.

Question 448

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: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. Confirmed observation: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. Proposed controlled action: Distribute the approved FortiSASE CA through supported managed endpoint onboarding and validate installation and inspection policy. What separate result verifies the change without hiding a second failure?

  1. A permitted remote user reaches the private application and the FortiGate session returns correctly through the intended overlay.
  2. The approved employee obtains their specific access policy and a control identity outside the group remains restricted.
  3. A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.
  4. A controlled full login succeeds across failover tests while other independent internet flows retain eligible balancing.

Explanation

Correct Answer

C:

The measurable recovery condition for Silverpeak Cloud Services is: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked. This checks the actual failure revealed by: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement.

Incorrect Answers

A:

Another check would be: A permitted remote user reaches the private application and the FortiGate session returns correctly through the intended overlay. The relevant Silverpeak Cloud Services problem requires a distinct success condition: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked. The governing rule is: SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement.

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: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.

D:

A controlled full login succeeds across failover tests while other independent internet flows retain eligible balancing. That is not sufficient to validate the stated Silverpeak Cloud Services failure, supported by: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. The required check is: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.

Question 449

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: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. Recorded observation: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. Which operational principle governs the documented incident?

  1. Configuration alone cannot activate service capabilities outside subscription entitlement.
  2. Client connection profiles and authorization groups must reflect the intended access class rather than simply successful sign-in.
  3. Performance SLA acceptance compares measured network quality with configured application-specific targets.
  4. SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement.

Explanation

Correct Answer

D:

SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement. At Silverpeak Cloud Services, the technical clue is: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. That explains the reported condition: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled.

Incorrect Answers

A:

Another relationship would be: Configuration alone cannot activate service capabilities outside subscription entitlement. It does not account for the issue reported by Silverpeak Cloud Services: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. The applicable principle is: SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement.

B:

Client connection profiles and authorization groups must reflect the intended access class rather than simply successful sign-in. The key evidence is: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. That observation is explained by a different rule: SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement.

C:

Performance SLA acceptance compares measured network quality with configured application-specific targets. The failure at Silverpeak Cloud Services is: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. The operating rule directly related to that failure is: SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement.

Question 450

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: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. Confirmed observation: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. Which approved change and separate test together resolve the issue?

  1. 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.
  2. 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.
  3. Action: Configure approved split DNS or internal resolver forwarding for that specific namespace and validate private service reachability. Proof: The corporate name resolves to the approved private target and a permitted SASE client completes its secured private session.
  4. Action: Correlate user, endpoint posture and actual threat categorization and initiate proportionate identity and endpoint investigation. Proof: The suspicious test identity is isolated for authorized review while other unaffected users continue normal browsing.

Explanation

Correct Answer

B:

This pair is the bounded choice for Silverpeak Cloud Services: 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 underlying issue is: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. Confirm the recorded outcome: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.

Incorrect Answers

A:

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 actual issue at Silverpeak Cloud Services is: Managed users connect to FortiSASE yet common permitted HTTPS sites show certificate warnings after deep inspection is enabled. The proposed verification does not establish that the required result is: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.

C:

Action: Configure approved split DNS or internal resolver forwarding for that specific namespace and validate private service reachability. Proof: The corporate name resolves to the approved private target and a permitted SASE client completes its secured private session. The recorded evidence at Silverpeak Cloud Services is: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. The correct outcome to measure is: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.

D:

Action: Correlate user, endpoint posture and actual threat categorization and initiate proportionate identity and endpoint investigation. Proof: The suspicious test identity is isolated for authorized review while other unaffected users continue normal browsing. The relevant Silverpeak Cloud Services observation is: Endpoint trust diagnostics confirm that the FortiSASE inspection CA needed for the active profile is absent from the managed device trust store. Any successful correction still needs to verify: A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.

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