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

Question 680

At Westport Managed Security, the team administers SASE policy enforcement and device compliance and must validate matched user groups, controls and independent security outcomes. Operational incident: A recently upgraded laptop continues failing endpoint compliance checks even after required encryption and AV settings are confirmed. Confirmed observation: FortiClient management telemetry shows the endpoint's last reported posture predates the remediation and is not refreshed in the SASE service. Which scoped action plus measurable success result should the team choose?

  1. Action: Restore supported telemetry synchronization or re-evaluation and verify fresh posture data before altering the policy baseline. Proof: Current device health is reflected in the cloud compliance record and access follows documented current posture.
  2. Action: Correct the sanctioned DNS resolution and filtering policy for the private namespace and validate with known test names. Proof: Internal names resolve through the approved private resolver and a malicious external domain control remains filtered.
  3. Action: Attach the approved intrusion prevention profile to the appropriate allowed policy and confirm required traffic visibility and signatures. Proof: A benign IPS test signature is detected or blocked and a normal authorized transaction remains successful.
  4. 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.

Explanation

Correct Answer

A:

Action: Restore supported telemetry synchronization or re-evaluation and verify fresh posture data before altering the policy baseline. Proof: Current device health is reflected in the cloud compliance record and access follows documented current posture. The relevant observation at Westport Managed Security is: FortiClient management telemetry shows the endpoint's last reported posture predates the remediation and is not refreshed in the SASE service. The operating rule is: Policy decisions may rely on last reported endpoint posture and stale metadata can misrepresent a fixed device.

Incorrect Answers

B:

Action: Correct the sanctioned DNS resolution and filtering policy for the private namespace and validate with known test names. Proof: Internal names resolve through the approved private resolver and a malicious external domain control remains filtered. It is not sufficient proof of resolution for the stated Westport Managed Security incident: A recently upgraded laptop continues failing endpoint compliance checks even after required encryption and AV settings are confirmed.

C:

Action: Attach the approved intrusion prevention profile to the appropriate allowed policy and confirm required traffic visibility and signatures. Proof: A benign IPS test signature is detected or blocked and a normal authorized transaction remains successful. The recorded evidence at Westport Managed Security is: FortiClient management telemetry shows the endpoint's last reported posture predates the remediation and is not refreshed in the SASE service. The correct outcome to measure is: Current device health is reflected in the cloud compliance record and access follows documented current posture.

D:

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 relevant Westport Managed Security observation is: FortiClient management telemetry shows the endpoint's last reported posture predates the remediation and is not refreshed in the SASE service. Any successful correction still needs to verify: Current device health is reflected in the cloud compliance record and access follows documented current posture.

Question 681

For Evergreen Distribution Security, operators support cloud security filtering and managed endpoint assurance and are expected to inspect authorized content while maintaining user privacy and explicit posture limits. Operational incident: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. Confirmed observation: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. Which supported administrator action should address this issue with the least unrelated impact?

  1. Apply supported stricter inspection only to legally permitted scoped users with a proper trust chain and approved exception handling.
  2. Update the supported endpoint compliance condition to validate required protection currency before granting the protected access class.
  3. Add the verified secondary interface as an eligible SD-WAN member and test controlled failover without weakening firewall segmentation.
  4. Separate supported user and device management groups and apply the documented access restrictions per class.

Explanation

Correct Answer

D:

For Evergreen Distribution Security, the recorded clue is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. The bounded correction is: Separate supported user and device management groups and apply the documented access restrictions per class. Device management state must be reflected in authorization, not inferred solely from an authenticated username. Confirm recovery using this outcome: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.

Incorrect Answers

A:

Another proposed response centers on: Apply supported stricter inspection only to legally permitted scoped users with a proper trust chain and approved exception handling. The reported Evergreen Distribution Security failure is: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. The decisive record shows: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class.

B:

Another suggested intervention is: Update the supported endpoint compliance condition to validate required protection currency before granting the protected access class. It is not sufficient evidence of resolving the Evergreen Distribution Security condition: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. The measurable outcome still required is: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.

C:

Add the verified secondary interface as an eligible SD-WAN member and test controlled failover without weakening firewall segmentation. The reported failure at Evergreen Distribution Security is: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. Its independent recovery check must establish: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.

Question 682

At Evergreen Distribution Security, the team administers cloud security filtering and managed endpoint assurance and must inspect authorized content while maintaining user privacy and explicit posture limits. Operational incident: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. The team must verify the root cause before changing production settings. Which piece of evidence distinguishes this cause from unrelated symptoms?

  1. The active SIA allow policy references a profile group without the required supported IPS inspection component for that traffic.
  2. Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class.
  3. The incident correlation identifies user and timestamp but no usable posture-evaluation event is included in the current analysis view.
  4. SD-WAN configuration shows the interface exists as a member under a separate zone while the relevant steering and firewall rules reference only the old zone.

Explanation

Correct Answer

B:

The most relevant recorded signal is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. That finding belongs to the observed problem at Evergreen Distribution Security: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. The underlying relationship is: Device management state must be reflected in authorization, not inferred solely from an authenticated username.

Incorrect Answers

A:

The active SIA allow policy references a profile group without the required supported IPS inspection component for that traffic. It is not the discriminating clue in this record; that clue is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. The Evergreen Distribution Security issue is: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps.

C:

The incident correlation identifies user and timestamp but no usable posture-evaluation event is included in the current analysis view. The reported Evergreen Distribution Security fault is: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. The signal that actually distinguishes it is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class.

D:

SD-WAN configuration shows the interface exists as a member under a separate zone while the relevant steering and firewall rules reference only the old zone. At Evergreen Distribution Security, the recorded condition is: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. The particular evidence supporting it is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class.

Question 683

For Evergreen Distribution Security, operators support cloud security filtering and managed endpoint assurance and are expected to inspect authorized content while maintaining user privacy and explicit posture limits. Operational incident: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. Confirmed observation: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. Proposed controlled action: Separate supported user and device management groups and apply the documented access restrictions per class. Which accepted outcome confirms the intended behavior?

  1. An updated approved device is allowed and a deliberately stale test device is denied or quarantined with a recorded reason.
  2. The exact failed requirement is identified, remediated, and then access recovers without disabling broader posture enforcement.
  3. The same test target responds to probes via the correct member without changing the approved health thresholds.
  4. Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.

Explanation

Correct Answer

D:

The required post-change observation is: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services. It is tied to the original Evergreen Distribution Security observation: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. The operating rule is: Device management state must be reflected in authorization, not inferred solely from an authenticated username.

Incorrect Answers

A:

An updated approved device is allowed and a deliberately stale test device is denied or quarantined with a recorded reason. The acceptance condition for the stated Evergreen Distribution Security fault is: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services. The tests do not measure the same outcome.

B:

An alternative finding would be: The exact failed requirement is identified, remediated, and then access recovers without disabling broader posture enforcement. The applicable acceptance criterion at Evergreen Distribution Security is: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services. That result is related to the original issue.

C:

The same test target responds to probes via the correct member without changing the approved health thresholds. The recorded clue at Evergreen Distribution Security is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. Closure has to validate the corresponding result: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.

Question 684

At Evergreen Distribution Security, the team administers cloud security filtering and managed endpoint assurance and must inspect authorized content while maintaining user privacy and explicit posture limits. Operational incident: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. Recorded observation: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. Which network security or traffic-steering principle explains this behavior?

  1. Device management state must be reflected in authorization, not inferred solely from an authenticated username.
  2. Installed security software does not necessarily mean endpoint security state satisfies a current compliance requirement.
  3. App classification and the applied control decision are separate; identification alone does not block a service.
  4. A performance SLA can compare only the eligible members it actually measures and the service rule permits.

Explanation

Correct Answer

A:

Device management state must be reflected in authorization, not inferred solely from an authenticated username. The Evergreen Distribution Security incident is: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. The deciding clue is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class.

Incorrect Answers

B:

Installed security software does not necessarily mean endpoint security state satisfies a current compliance requirement. The documented Evergreen Distribution Security failure is: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. The case is instead explained by: Device management state must be reflected in authorization, not inferred solely from an authenticated username.

C:

An alternative explanation is: App classification and the applied control decision are separate; identification alone does not block a service. It is not the reason established by the Evergreen Distribution Security clue: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. The relevant causal relationship is: Device management state must be reflected in authorization, not inferred solely from an authenticated username.

D:

A performance SLA can compare only the eligible members it actually measures and the service rule permits. At Evergreen Distribution Security, the reported issue is: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. The stated observations instead follow from: Device management state must be reflected in authorization, not inferred solely from an authenticated username.

Question 685

For Evergreen Distribution Security, operators support cloud security filtering and managed endpoint assurance and are expected to inspect authorized content while maintaining user privacy and explicit posture limits. Operational incident: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. Confirmed observation: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. What remediation-and-validation combination most directly addresses this incident?

  1. Action: Assign the approved custom security profile group to the correctly scoped user accept rule and verify category action. Proof: A permitted synthetic category test follows the intended block decision and unrelated allowed categories remain reachable.
  2. Action: Separate supported user and device management groups and apply the documented access restrictions per class. Proof: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.
  3. Action: Apply the licensed supported OS posture condition to the narrowly authorized privileged access group and retest endpoints. Proof: The compliant laptop retains access and the controlled obsolete OS test is prevented from entering the sensitive application.
  4. Action: Use current observed classification to correct the approved application or internet-service match and preserve overlay rules for private traffic. Proof: A synthetic approved SaaS session exits locally and a private ERP control remains on its authorized overlay.

Explanation

Correct Answer

B:

Action: Separate supported user and device management groups and apply the documented access restrictions per class. Proof: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services. The Evergreen Distribution Security finding is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. Independent completion must establish: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.

Incorrect Answers

A:

Action: Assign the approved custom security profile group to the correctly scoped user accept rule and verify category action. Proof: A permitted synthetic category test follows the intended block decision and unrelated allowed categories remain reachable. They do not directly establish recovery of the reported Evergreen Distribution Security problem: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. Verification requires: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.

C:

An alternative option suggests: Action: Apply the licensed supported OS posture condition to the narrowly authorized privileged access group and retest endpoints. Proof: The compliant laptop retains access and the controlled obsolete OS test is prevented from entering the sensitive application. The documented Evergreen Distribution Security problem calls for a check against: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services. The original clue is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class.

D:

Action: Use current observed classification to correct the approved application or internet-service match and preserve overlay rules for private traffic. Proof: A synthetic approved SaaS session exits locally and a private ERP control remains on its authorized overlay. At Evergreen Distribution Security, the actual distinguishing clue is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. The related test must establish: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.

Question 686

At Silverpeak Cloud Services, the team administers SASE policy enforcement and device compliance and must validate matched user groups, controls and independent security outcomes. Operational incident: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. Confirmed observation: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. What scoped change is justified by the observed evidence?

  1. Update the supported endpoint compliance condition to validate required protection currency before granting the protected access class.
  2. Separate supported user and device management groups and apply the documented access restrictions per class.
  3. Correct the sanctioned DNS resolution and filtering policy for the private namespace and validate with known test names.
  4. Correct supported identity group synchronization and mapped SASE user/group authorization without a blanket accept rule.

Explanation

Correct Answer

B:

The issue at Silverpeak Cloud Services is: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. Separate supported user and device management groups and apply the documented access restrictions per class. A valid post-change result is: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.

Incorrect Answers

A:

Although that step is: Update the supported endpoint compliance condition to validate required protection currency before granting the protected access class, the decisive observation here is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. That choice alone does not establish the needed correction at Silverpeak Cloud Services.

C:

The suggested alternative is: Correct the sanctioned DNS resolution and filtering policy for the private namespace and validate with known test names. The case identifies the cause at Silverpeak Cloud Services using: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. Implementing that step alone would not verify: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.

D:

Another proposed action is: Correct supported identity group synchronization and mapped SASE user/group authorization without a blanket accept rule. In Silverpeak Cloud Services, the relevant evidence is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. The focused correction should address the root condition shown by that clue.

Question 687

For Silverpeak Cloud Services, operators support SASE policy enforcement and device compliance and are expected to validate matched user groups, controls and independent security outcomes. Operational incident: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. The team must verify the root cause before changing production settings. Which specific observation should determine the next investigation step?

  1. FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category.
  2. The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it.
  3. Routing and service logs show the member health probe reaches the hub but the specific private application destination route is absent.
  4. Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class.

Explanation

Correct Answer

D:

The observation pinpoints the documented weakness: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. The Silverpeak Cloud Services case concerns: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. Device management state must be reflected in authorization, not inferred solely from an authenticated username.

Incorrect Answers

A:

Another possibility is: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. The current case at Silverpeak Cloud Services contains a different identifying observation: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. The relevant mechanism is: Device management state must be reflected in authorization, not inferred solely from an authenticated username.

B:

The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. The original Silverpeak Cloud Services observation is instead: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. That is the evidence tied to the stated failure.

C:

Routing and service logs show the member health probe reaches the hub but the specific private application destination route is absent. It does not directly identify the problem reported at Silverpeak Cloud Services. The determining evidence is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class.

Question 688

At Silverpeak Cloud Services, the team administers SASE policy enforcement and device compliance and must validate matched user groups, controls and independent security outcomes. Operational incident: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. Confirmed observation: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. Proposed controlled action: Separate supported user and device management groups and apply the documented access restrictions per class. What separate result verifies the change without hiding a second failure?

  1. Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.
  2. A permitted synthetic category test follows the intended block decision and unrelated allowed categories remain reachable.
  3. The encrypted device works and a controlled nonencrypted device is blocked with observable compliance results.
  4. The healthy uplink meets the revised check while a deliberately failed link still becomes unavailable to eligible service rules.

Explanation

Correct Answer

A:

The listed result is the right measure for Silverpeak Cloud Services: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services. It verifies the intended effect, whereas the case originally showed: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. The relevant principle is: Device management state must be reflected in authorization, not inferred solely from an authenticated username.

Incorrect Answers

B:

A permitted synthetic category test follows the intended block decision and unrelated allowed categories remain reachable. It is not the evidence needed to close the reported issue. The proper Silverpeak Cloud Services success measure is: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.

C:

An alternative test would show: The encrypted device works and a controlled nonencrypted device is blocked with observable compliance results. It does not show the required post-change result at Silverpeak Cloud Services: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services. The original finding was: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class.

D:

The healthy uplink meets the revised check while a deliberately failed link still becomes unavailable to eligible service rules. That is not sufficient to validate the stated Silverpeak Cloud Services failure, supported by: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. The required check is: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.

Question 689

For Silverpeak Cloud Services, operators support SASE policy enforcement and device compliance and are expected to validate matched user groups, controls and independent security outcomes. Operational incident: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. Recorded observation: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. Which operational principle governs the documented incident?

  1. Compliance exceptions must be time- and identity-scoped; blanket bypass undermines every other endpoint policy.
  2. Device management state must be reflected in authorization, not inferred solely from an authenticated username.
  3. App classification and the applied control decision are separate; identification alone does not block a service.
  4. Tenant-wide policy defaults affect more identities than a narrowly bound user-group exception.

Explanation

Correct Answer

B:

At Silverpeak Cloud Services, the evidence is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. The principle that explains it is: Device management state must be reflected in authorization, not inferred solely from an authenticated username. It connects that clue to the specified failure.

Incorrect Answers

A:

Another relationship would be: Compliance exceptions must be time- and identity-scoped; blanket bypass undermines every other endpoint policy. It does not account for the issue reported by Silverpeak Cloud Services: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. The applicable principle is: Device management state must be reflected in authorization, not inferred solely from an authenticated username.

C:

App classification and the applied control decision are separate; identification alone does not block a service. The failure at Silverpeak Cloud Services is: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. The operating rule directly related to that failure is: Device management state must be reflected in authorization, not inferred solely from an authenticated username.

D:

Tenant-wide policy defaults affect more identities than a narrowly bound user-group exception. In Silverpeak Cloud Services, the actual observation is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. The rule connected to that evidence is: Device management state must be reflected in authorization, not inferred solely from an authenticated username.

Question 690

At Silverpeak Cloud Services, the team administers SASE policy enforcement and device compliance and must validate matched user groups, controls and independent security outcomes. Operational incident: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps. Confirmed observation: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. Which approved change and separate test together resolve the issue?

  1. Action: Separate supported user and device management groups and apply the documented access restrictions per class. Proof: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.
  2. Action: Apply supported stricter inspection only to legally permitted scoped users with a proper trust chain and approved exception handling. Proof: A controlled untrusted-certificate test follows the intended enforcement while valid inspected business services work.
  3. Action: Narrow the exception to the approved vendor and expiry, restore the baseline for everyone else, and verify authorization logs. Proof: The vendor's permitted test is allowed during the exception window and an unrelated failing-posture device remains restricted.
  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

A:

Action: Separate supported user and device management groups and apply the documented access restrictions per class. Proof: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services. The relevant observation at Silverpeak Cloud Services is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. The operating rule is: Device management state must be reflected in authorization, not inferred solely from an authenticated username.

Incorrect Answers

B:

Action: Apply supported stricter inspection only to legally permitted scoped users with a proper trust chain and approved exception handling. Proof: A controlled untrusted-certificate test follows the intended enforcement while valid inspected business services work. It is not sufficient proof of resolution for the stated Silverpeak Cloud Services incident: An organization intends to allow personal devices to low-risk SaaS only but treats them like corporate managed endpoints for sensitive apps.

C:

Action: Narrow the exception to the approved vendor and expiry, restore the baseline for everyone else, and verify authorization logs. Proof: The vendor's permitted test is allowed during the exception window and an unrelated failing-posture device remains restricted. The recorded evidence at Silverpeak Cloud Services is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. The correct outcome to measure is: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.

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. The relevant Silverpeak Cloud Services observation is: Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. Any successful correction still needs to verify: Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.

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