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

Question 370

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: A helpdesk analyst can modify security profiles for all remote users although the role should permit only onboarding support. Confirmed observation: The FortiSASE administration role assignment includes configuration privileges outside the analyst's documented operational responsibility. What remediation-and-validation combination most directly addresses this incident?

  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: 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.
  3. Action: Restrict supported FortiSASE client profile and user-group mapping to the approved contractor role and retest enrollment. Proof: A contractor reaches the sanctioned SaaS services but remains unable to reach internal-only destinations that employees can access.
  4. Action: Apply a documented alternative-member and health-aware strategy while preserving payment segmentation and return-path requirements. Proof: During a simulated member outage, the authorized payment session recovers over backup and then behaves according to recovery policy.

Explanation

Correct Answer

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 relevant observation at Silverpeak Cloud Services is: The FortiSASE administration role assignment includes configuration privileges outside the analyst's documented operational responsibility. The operating rule is: Identity-based management permissions must separate observation and support from configuration change authority.

Incorrect Answers

B:

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. It is not sufficient proof of resolution for the stated Silverpeak Cloud Services incident: A helpdesk analyst can modify security profiles for all remote users although the role should permit only onboarding support.

C:

Action: Restrict supported FortiSASE client profile and user-group mapping to the approved contractor role and retest enrollment. Proof: A contractor reaches the sanctioned SaaS services but remains unable to reach internal-only destinations that employees can access. The recorded evidence at Silverpeak Cloud Services is: The FortiSASE administration role assignment includes configuration privileges outside the analyst's documented operational responsibility. The correct outcome to measure is: The analyst can view onboarding status but cannot edit global content policy; authorized security admins retain edit capability.

D:

Action: Apply a documented alternative-member and health-aware strategy while preserving payment segmentation and return-path requirements. Proof: During a simulated member outage, the authorized payment session recovers over backup and then behaves according to recovery policy. The relevant Silverpeak Cloud Services observation is: The FortiSASE administration role assignment includes configuration privileges outside the analyst's documented operational responsibility. Any successful correction still needs to verify: The analyst can view onboarding status but cannot edit global content policy; authorized security admins retain edit capability.

Question 371

For Redwood Financial Applications, operators support FortiSASE tenant administration and user enrollment and are expected to enforce approved identities, tenant boundaries and endpoint licensing. Operational incident: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. Confirmed observation: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. What scoped change is justified by the observed evidence?

  1. Update the approved SSO integration metadata and trust settings, validate the service-provider and identity-provider match and test login.
  2. Correct supported identity group synchronization and mapped SASE user/group authorization without a blanket accept rule.
  3. Deliver the proper tenant-approved installer or manual enrollment configuration and revoke the misplaced onboarding token.
  4. Configure the appropriate supported encryption posture rule and associate it with approved regulated SaaS access scope.

Explanation

Correct Answer

A:

The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. The intervention considered for Redwood Financial Applications is: Update the approved SSO integration metadata and trust settings, validate the service-provider and identity-provider match and test login. It follows this underlying rule: SSO depends on consistent trust metadata and claim mapping between the identity provider and SASE service. Confirm the actual result: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected.

Incorrect Answers

B:

Another suggested intervention is: Correct supported identity group synchronization and mapped SASE user/group authorization without a blanket accept rule. It is not sufficient evidence of resolving the Redwood Financial Applications condition: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. The measurable outcome still required is: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected.

C:

Deliver the proper tenant-approved installer or manual enrollment configuration and revoke the misplaced onboarding token. The reported failure at Redwood Financial Applications is: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. Its independent recovery check must establish: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected.

D:

Another option proposes: Configure the appropriate supported encryption posture rule and associate it with approved regulated SaaS access scope. At Redwood Financial Applications, the decisive evidence is: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. That step alone does not demonstrate correction of the specified problem: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation.

Question 372

At Redwood Financial Applications, the team administers FortiSASE tenant administration and user enrollment and must enforce approved identities, tenant boundaries and endpoint licensing. Operational incident: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. 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 SPA or connected SD-WAN overlay is established, but the FortiSASE routing view lacks the branch private application subnet.
  3. Policy route tracing shows traffic leaves toward a newly named SD-WAN zone not referenced in the authorized security policy.
  4. The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values.

Explanation

Correct Answer

D:

For Redwood Financial Applications, the decisive evidence is: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. It connects the reported failure to the actual operating dependency: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. The relevant rule is: SSO depends on consistent trust metadata and claim mapping between the identity provider and SASE service.

Incorrect Answers

A:

FortiSASE group mapping indicates HR membership but the hub's effective access policy references a different SASE user or source segment. It is not the discriminating clue in this record; that clue is: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. The Redwood Financial Applications issue is: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation.

B:

The SPA or connected SD-WAN overlay is established, but the FortiSASE routing view lacks the branch private application subnet. The trace for Redwood Financial Applications instead establishes: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. This is the clue to the issue actually described.

C:

Policy route tracing shows traffic leaves toward a newly named SD-WAN zone not referenced in the authorized security policy. The reported Redwood Financial Applications fault is: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. The signal that actually distinguishes it is: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values.

Question 373

For Redwood Financial Applications, operators support FortiSASE tenant administration and user enrollment and are expected to enforce approved identities, tenant boundaries and endpoint licensing. Operational incident: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. Confirmed observation: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. Proposed controlled action: Update the approved SSO integration metadata and trust settings, validate the service-provider and identity-provider match and test login. What separate result verifies the change without hiding a second failure?

  1. Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected.
  2. A contractor reaches the sanctioned SaaS services but remains unable to reach internal-only destinations that employees can access.
  3. The authorized managed client registers to the intended tenant and receives its permitted connection configuration.
  4. The encrypted device works and a controlled nonencrypted device is blocked with observable compliance results.

Explanation

Correct Answer

A:

For Redwood Financial Applications, an accepted fix must show: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected. The initial diagnostic clue was: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. The result therefore tests the stated failure rather than a separate control.

Incorrect Answers

B:

An alternative finding would be: A contractor reaches the sanctioned SaaS services but remains unable to reach internal-only destinations that employees can access. The applicable acceptance criterion at Redwood Financial Applications is: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected. That result is related to the original issue.

C:

The authorized managed client registers to the intended tenant and receives its permitted connection configuration. The recorded clue at Redwood Financial Applications is: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. Closure has to validate the corresponding result: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected.

D:

The encrypted device works and a controlled nonencrypted device is blocked with observable compliance results. That alone would not confirm correction of the Redwood Financial Applications problem: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. The necessary proof is: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected.

Question 374

At Redwood Financial Applications, the team administers FortiSASE tenant administration and user enrollment and must enforce approved identities, tenant boundaries and endpoint licensing. Operational incident: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. Recorded observation: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. Which operational principle governs the documented incident?

  1. Cloud-delivered security performance depends on actual service access path and geographic selection as well as access policy.
  2. SSO depends on consistent trust metadata and claim mapping between the identity provider and SASE service.
  3. Client installation and validated tenant enrollment are separate requirements for managed FortiSASE onboarding.
  4. SD-WAN member health measurement depends on probe source, route and return path as well as target availability.

Explanation

Correct Answer

B:

The case is best understood through: SSO depends on consistent trust metadata and claim mapping between the identity provider and SASE service. The record at Redwood Financial Applications shows: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. The failure requiring explanation is: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation.

Incorrect Answers

A:

Another principle is: Cloud-delivered security performance depends on actual service access path and geographic selection as well as access policy. It is not enough to account for the recorded Redwood Financial Applications evidence: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. The applicable rule is: SSO depends on consistent trust metadata and claim mapping between the identity provider and SASE service.

C:

An alternative explanation is: Client installation and validated tenant enrollment are separate requirements for managed FortiSASE onboarding. It is not the reason established by the Redwood Financial Applications clue: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. The relevant causal relationship is: SSO depends on consistent trust metadata and claim mapping between the identity provider and SASE service.

D:

SD-WAN member health measurement depends on probe source, route and return path as well as target availability. At Redwood Financial Applications, the reported issue is: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. The stated observations instead follow from: SSO depends on consistent trust metadata and claim mapping between the identity provider and SASE service.

Question 375

For Redwood Financial Applications, operators support FortiSASE tenant administration and user enrollment and are expected to enforce approved identities, tenant boundaries and endpoint licensing. Operational incident: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. Confirmed observation: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. Which approved change and separate test together resolve the issue?

  1. 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.
  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: 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.
  4. Action: Associate the member with an appropriately authorized zone and update rule references without expanding source access beyond policy. Proof: An allowed test session can select both approved members under the configured conditions and a denied control session remains denied.

Explanation

Correct Answer

A:

The documented fault is: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. The selected change-plus-verification is: 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. That pair responds to the Redwood Financial Applications observation: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values.

Incorrect Answers

B:

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. It would not by itself demonstrate correction of the Redwood Financial Applications finding: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. The required outcome is: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected.

C:

An alternative option suggests: 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. The documented Redwood Financial Applications problem calls for a check against: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected. The original clue is: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values.

D:

Action: Associate the member with an appropriately authorized zone and update rule references without expanding source access beyond policy. Proof: An allowed test session can select both approved members under the configured conditions and a denied control session remains denied. At Redwood Financial Applications, the actual distinguishing clue is: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. The related test must establish: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected.

Question 376

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: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. Confirmed observation: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. Which approved correction best addresses the documented root cause?

  1. Deliver the proper tenant-approved installer or manual enrollment configuration and revoke the misplaced onboarding token.
  2. Confirm the licensed feature and approved entitlement before configuring a supported design or obtaining authorized upgrade.
  3. Update the approved SSO integration metadata and trust settings, validate the service-provider and identity-provider match and test login.
  4. Use an application-appropriate SD-WAN steering strategy and consistent NAT or return-path design for the scoped traffic.

Explanation

Correct Answer

C:

At Westport Managed Security, the key finding is: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. The corresponding corrective action is: Update the approved SSO integration metadata and trust settings, validate the service-provider and identity-provider match and test login. SSO depends on consistent trust metadata and claim mapping between the identity provider and SASE service. The separate acceptance check is: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected.

Incorrect Answers

A:

Although that step is: Deliver the proper tenant-approved installer or manual enrollment configuration and revoke the misplaced onboarding token, the decisive observation here is: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. That choice alone does not establish the needed correction at Westport Managed Security.

B:

An alternative action is: Confirm the licensed feature and approved entitlement before configuring a supported design or obtaining authorized upgrade. The observed evidence in Westport Managed Security instead establishes: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. A relevant response must address that observation and confirm: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected.

D:

Another proposed action is: Use an application-appropriate SD-WAN steering strategy and consistent NAT or return-path design for the scoped traffic. In Westport Managed Security, the relevant evidence is: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. The focused correction should address the root condition shown by that clue.

Question 377

For Westport Managed Security, 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: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. The team must verify the root cause before changing production settings. What measured finding directly supports the recorded issue?

  1. The installed client's preconfigured invitation or bootstrap identifiers are bound to a different tenant than the approved employer.
  2. The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values.
  3. Client DNS diagnostics show internal domain rules are not applied for the application namespace while the private route exists.
  4. The effective FortiSASE compliance rule checks antivirus installed status but does not apply the organization-approved definition freshness criterion.

Explanation

Correct Answer

B:

The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. In Westport Managed Security, the problem described is: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation.

Incorrect Answers

A:

Another possibility is: The installed client's preconfigured invitation or bootstrap identifiers are bound to a different tenant than the approved employer. The current case at Westport Managed Security contains a different identifying observation: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. The relevant mechanism is: SSO depends on consistent trust metadata and claim mapping between the identity provider and SASE service.

C:

Client DNS diagnostics show internal domain rules are not applied for the application namespace while the private route exists. It does not directly identify the problem reported at Westport Managed Security. The determining evidence is: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values.

D:

The effective FortiSASE compliance rule checks antivirus installed status but does not apply the organization-approved definition freshness criterion. It does not substantiate the particular Westport Managed Security condition: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. The documented finding is: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values.

Question 378

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: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. Confirmed observation: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. Proposed controlled action: Update the approved SSO integration metadata and trust settings, validate the service-provider and identity-provider match and test login. Which independent test would establish that the original problem is resolved?

  1. Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.
  2. The approved employee obtains their specific access policy and a control identity outside the group remains restricted.
  3. Current device health is reflected in the cloud compliance record and access follows documented current posture.
  4. Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected.

Explanation

Correct Answer

D:

Independent closure should establish: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected. This directly corresponds to the Westport Managed Security finding: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. It supports recovery of the stated problem: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation.

Incorrect Answers

A:

Another check would be: Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied. The relevant Westport Managed Security problem requires a distinct success condition: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected. The governing rule is: SSO depends on consistent trust metadata and claim mapping between the identity provider and SASE service.

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 Westport Managed Security success measure is: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected.

C:

An alternative test would show: Current device health is reflected in the cloud compliance record and access follows documented current posture. It does not show the required post-change result at Westport Managed Security: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected. The original finding was: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values.

Question 379

For Westport Managed Security, 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: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. Recorded observation: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. What platform design concept best accounts for the symptoms?

  1. SSO depends on consistent trust metadata and claim mapping between the identity provider and SASE service.
  2. SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement.
  3. Configuration alone cannot activate service capabilities outside subscription entitlement.
  4. A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration.

Explanation

Correct Answer

A:

The applicable principle is: SSO depends on consistent trust metadata and claim mapping between the identity provider and SASE service. It fits the Westport Managed Security evidence: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. The incident is: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation.

Incorrect Answers

B:

SSL deep inspection requires an appropriately trusted inspection CA at the endpoint as well as policy enforcement. The key evidence is: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. That observation is explained by a different rule: SSO depends on consistent trust metadata and claim mapping between the identity provider and SASE service.

C:

Configuration alone cannot activate service capabilities outside subscription entitlement. The failure at Westport Managed Security is: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. The operating rule directly related to that failure is: SSO depends on consistent trust metadata and claim mapping between the identity provider and SASE service.

D:

A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration. In Westport Managed Security, the actual observation is: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. The rule connected to that evidence is: SSO depends on consistent trust metadata and claim mapping between the identity provider and SASE service.

Question 380

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: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. Confirmed observation: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. Which scoped action plus measurable success result should the team choose?

  1. Action: Review supported FortiSASE access location and connection selection settings and validate region and policy requirements. Proof: Test users connect through the approved suitable service region and latency improves without loss of security inspection.
  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: Limit internet rules to internet-capable underlay members and keep private application routing eligible for the approved overlay. Proof: Public controls use direct breakout, private test sessions use encrypted transport, and the route logs match the defined segmentation.
  4. 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.

Explanation

Correct Answer

D:

The selection links action to a separately checked outcome: 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. It is grounded in the Westport Managed Security clue: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. Closure must show: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected.

Incorrect Answers

A:

Action: Review supported FortiSASE access location and connection selection settings and validate region and policy requirements. Proof: Test users connect through the approved suitable service region and latency improves without loss of security inspection. The actual issue at Westport Managed Security is: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation. The proposed verification does not establish that the required result is: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected.

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 is not sufficient proof of resolution for the stated Westport Managed Security incident: Employees authenticate to their new corporate identity provider, yet FortiSASE reports a failed SSO assertion validation.

C:

Action: Limit internet rules to internet-capable underlay members and keep private application routing eligible for the approved overlay. Proof: Public controls use direct breakout, private test sessions use encrypted transport, and the route logs match the defined segmentation. The recorded evidence at Westport Managed Security is: The FortiSASE service-provider configuration still references old identity-provider certificate or assertion audience values. The correct outcome to measure is: Authorized managed users authenticate into the correct tenant and invalid issuer or audience controls remain rejected.

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