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

Question 570

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: Remote workers cannot resolve an approved internal application although the SASE tunnel and route to its private address work. Confirmed observation: DNS filtering or resolution logs show the internal name sent to a public category rule rather than the intended private DNS processing path. Which approved change and separate test together resolve the issue?

  1. 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.
  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: 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.
  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

B:

This pair is the bounded choice for Silverpeak Cloud Services: 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. The underlying issue is: Remote workers cannot resolve an approved internal application although the SASE tunnel and route to its private address work. Confirm the recorded outcome: Internal names resolve through the approved private resolver and a malicious external domain control remains filtered.

Incorrect Answers

A:

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 actual issue at Silverpeak Cloud Services is: Remote workers cannot resolve an approved internal application although the SASE tunnel and route to its private address work. The proposed verification does not establish that the required result is: Internal names resolve through the approved private resolver and a malicious external domain control remains filtered.

C:

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. The recorded evidence at Silverpeak Cloud Services is: DNS filtering or resolution logs show the internal name sent to a public category rule rather than the intended private DNS processing path. The correct outcome to measure is: Internal names resolve through the approved private resolver and a malicious external domain control remains filtered.

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: DNS filtering or resolution logs show the internal name sent to a public category rule rather than the intended private DNS processing path. Any successful correction still needs to verify: Internal names resolve through the approved private resolver and a malicious external domain control remains filtered.

Question 571

For Redwood Financial Applications, 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: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. Confirmed observation: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. Which approved correction best addresses the documented root cause?

  1. Narrow the exception to the approved vendor and expiry, restore the baseline for everyone else, and verify authorization logs.
  2. Restrict the approved application signature or category in the user-group-specific application control profile and validate the policy match.
  3. Configure the appropriate supported encryption posture rule and associate it with approved regulated SaaS access scope.
  4. Constrain authorized hub routing and SD-WAN service strategy to the correct overlay for the documented SASE client prefixes.

Explanation

Correct Answer

B:

The offered response addresses Redwood Financial Applications's specific finding: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. Apply the scoped change: Restrict the approved application signature or category in the user-group-specific application control profile and validate the policy match. The underlying mechanism is: App classification and the applied control decision are separate; identification alone does not block a service. Look for this independent result: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.

Incorrect Answers

A:

Another proposed response centers on: Narrow the exception to the approved vendor and expiry, restore the baseline for everyone else, and verify authorization logs. The reported Redwood Financial Applications failure is: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. The decisive record shows: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category.

C:

Configure the appropriate supported encryption posture rule and associate it with approved regulated SaaS access scope. The reported failure at Redwood Financial Applications is: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. Its independent recovery check must establish: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.

D:

Another option proposes: Constrain authorized hub routing and SD-WAN service strategy to the correct overlay for the documented SASE client prefixes. At Redwood Financial Applications, the decisive evidence is: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. That step alone does not demonstrate correction of the specified problem: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints.

Question 572

At Redwood Financial Applications, 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: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. The team must verify the root cause before changing production settings. What measured finding directly supports the recorded issue?

  1. FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category.
  2. The active SIA allow policy references a profile group without the required supported IPS inspection component for that traffic.
  3. Policy shows the correct Inline-CASB rule but SSL deep inspection or required SaaS activity visibility is not applied to the affected HTTPS connection.
  4. Security logs show a blocked web object and a user ID, but the device telemetry and action result are not joined for the same incident.

Explanation

Correct Answer

A:

The observation directly identifies the cause at Redwood Financial Applications: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. The reported problem is: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. App classification and the applied control decision are separate; identification alone does not block a service.

Incorrect Answers

B:

The active SIA allow policy references a profile group without the required supported IPS inspection component for that traffic. The trace for Redwood Financial Applications instead establishes: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. This is the clue to the issue actually described.

C:

Policy shows the correct Inline-CASB rule but SSL deep inspection or required SaaS activity visibility is not applied to the affected HTTPS connection. The reported Redwood Financial Applications fault is: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. The signal that actually distinguishes it is: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category.

D:

Security logs show a blocked web object and a user ID, but the device telemetry and action result are not joined for the same incident. At Redwood Financial Applications, the recorded condition is: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. The particular evidence supporting it is: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category.

Question 573

For Redwood Financial Applications, 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: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. Confirmed observation: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. Proposed controlled action: Restrict the approved application signature or category in the user-group-specific application control profile and validate the policy match. Which independent test would establish that the original problem is resolved?

  1. A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.
  2. The exact failed requirement is identified, remediated, and then access recovers without disabling broader posture enforcement.
  3. A harmless executable-type test is blocked while the approved PDF control completes with expected logs.
  4. A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked.

Explanation

Correct Answer

A:

For Redwood Financial Applications, an accepted fix must show: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited. The initial diagnostic clue was: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. The result therefore tests the stated failure rather than a separate control.

Incorrect Answers

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 Redwood Financial Applications is: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited. That result is related to the original issue.

C:

A harmless executable-type test is blocked while the approved PDF control completes with expected logs. The recorded clue at Redwood Financial Applications is: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. Closure has to validate the corresponding result: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.

D:

A controlled trusted HTTPS test succeeds under inspection and a deliberately untrusted certificate remains blocked. That alone would not confirm correction of the Redwood Financial Applications problem: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. The necessary proof is: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.

Question 574

At Redwood Financial Applications, 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: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. Recorded observation: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. What platform design concept best accounts for the symptoms?

  1. DLP rules must balance valid pattern specificity with supporting context to avoid false positives.
  2. App classification and the applied control decision are separate; identification alone does not block a service.
  3. Effective compliance troubleshooting correlates endpoint health evaluation with policy decision and session time.
  4. Log filtering can hide real link instability even when underlying events are recorded correctly.

Explanation

Correct Answer

B:

The case is best understood through: App classification and the applied control decision are separate; identification alone does not block a service. The record at Redwood Financial Applications shows: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. The failure requiring explanation is: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints.

Incorrect Answers

A:

Another principle is: DLP rules must balance valid pattern specificity with supporting context to avoid false positives. It is not enough to account for the recorded Redwood Financial Applications evidence: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. The applicable rule is: App classification and the applied control decision are separate; identification alone does not block a service.

C:

An alternative explanation is: Effective compliance troubleshooting correlates endpoint health evaluation with policy decision and session time. It is not the reason established by the Redwood Financial Applications clue: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. The relevant causal relationship is: App classification and the applied control decision are separate; identification alone does not block a service.

D:

Log filtering can hide real link instability even when underlying events are recorded correctly. At Redwood Financial Applications, the reported issue is: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. The stated observations instead follow from: App classification and the applied control decision are separate; identification alone does not block a service.

Question 575

For Redwood Financial Applications, 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: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. Confirmed observation: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. Which scoped action plus measurable success result should the team choose?

  1. 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.
  2. 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.
  3. Action: Adjust the approved application route and service-specific health strategy to reflect the real destination reachability. Proof: When the remote application prefix is withdrawn, traffic stops blackholing and uses only an approved viable path or fails explicitly.
  4. Action: Restrict the approved application signature or category in the user-group-specific application control profile and validate the policy match. Proof: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.

Explanation

Correct Answer

D:

Action: Restrict the approved application signature or category in the user-group-specific application control profile and validate the policy match. Proof: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited. The relevant finding at Redwood Financial Applications is: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category.

Incorrect Answers

A:

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. They do not directly establish recovery of the reported Redwood Financial Applications problem: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. Verification requires: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.

B:

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. It would not by itself demonstrate correction of the Redwood Financial Applications finding: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. The required outcome is: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.

C:

An alternative option suggests: Action: Adjust the approved application route and service-specific health strategy to reflect the real destination reachability. Proof: When the remote application prefix is withdrawn, traffic stops blackholing and uses only an approved viable path or fails explicitly. The documented Redwood Financial Applications problem calls for a check against: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited. The original clue is: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category.

Question 576

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: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. Confirmed observation: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. Which supported administrator action should address this issue with the least unrelated impact?

  1. Correct the sanctioned DNS resolution and filtering policy for the private namespace and validate with known test names.
  2. Attach the approved intrusion prevention profile to the appropriate allowed policy and confirm required traffic visibility and signatures.
  3. Restrict the approved application signature or category in the user-group-specific application control profile and validate the policy match.
  4. Assign the official installer matching each approved OS and supported FortiClient version, then complete tenant enrollment.

Explanation

Correct Answer

C:

At Westport Managed Security, the key finding is: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. The corresponding corrective action is: Restrict the approved application signature or category in the user-group-specific application control profile and validate the policy match. App classification and the applied control decision are separate; identification alone does not block a service. The separate acceptance check is: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.

Incorrect Answers

A:

Although that step is: Correct the sanctioned DNS resolution and filtering policy for the private namespace and validate with known test names, the decisive observation here is: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. That choice alone does not establish the needed correction at Westport Managed Security.

B:

An alternative action is: Attach the approved intrusion prevention profile to the appropriate allowed policy and confirm required traffic visibility and signatures. The observed evidence in Westport Managed Security instead establishes: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. A relevant response must address that observation and confirm: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.

D:

Another proposed action is: Assign the official installer matching each approved OS and supported FortiClient version, then complete tenant enrollment. In Westport Managed Security, the relevant evidence is: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. The focused correction should address the root condition shown by that clue.

Question 577

For Westport Managed Security, operators support SASE policy enforcement and device compliance and are expected to validate matched user groups, controls and independent security outcomes. Operational incident: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. The team must verify the root cause before changing production settings. Which piece of evidence distinguishes this cause from unrelated symptoms?

  1. The active DLP expression matches an overly permissive digit pattern without the required contextual anchors or validation controls.
  2. The active endpoint compliance rule omits the documented supported operating-system version threshold for this privileged user group.
  3. Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority.
  4. FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category.

Explanation

Correct Answer

D:

The observation pinpoints the documented weakness: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. The Westport Managed Security case concerns: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. App classification and the applied control decision are separate; identification alone does not block a service.

Incorrect Answers

A:

Another possibility is: The active DLP expression matches an overly permissive digit pattern without the required contextual anchors or validation controls. The current case at Westport Managed Security contains a different identifying observation: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. The relevant mechanism is: App classification and the applied control decision are separate; identification alone does not block a service.

B:

The active endpoint compliance rule omits the documented supported operating-system version threshold for this privileged user group. The original Westport Managed Security observation is instead: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. That is the evidence tied to the stated failure.

C:

Routing-table inspection reveals a leftover manually configured default path competing with the intended SD-WAN aggregate route under similar administrative priority. It does not directly identify the problem reported at Westport Managed Security. The determining evidence is: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category.

Question 578

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: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. Confirmed observation: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. Proposed controlled action: Restrict the approved application signature or category in the user-group-specific application control profile and validate the policy match. Which accepted outcome confirms the intended behavior?

  1. The prohibited test resource is blocked while the approved collaboration hostname remains accessible.
  2. Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services.
  3. A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.
  4. The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation.

Explanation

Correct Answer

C:

The measurable recovery condition for Westport Managed Security is: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited. This checks the actual failure revealed by: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. App classification and the applied control decision are separate; identification alone does not block a service.

Incorrect Answers

A:

Another check would be: The prohibited test resource is blocked while the approved collaboration hostname remains accessible. The relevant Westport Managed Security problem requires a distinct success condition: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited. The governing rule is: App classification and the applied control decision are separate; identification alone does not block a service.

B:

Corporate compliant devices reach approved sensitive apps, while a personal-device test remains limited to its explicit low-risk services. It is not the evidence needed to close the reported issue. The proper Westport Managed Security success measure is: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.

D:

The incident record distinguishes blocked attempts from successful transfers and validates any needed endpoint remediation. That is not sufficient to validate the stated Westport Managed Security failure, supported by: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. The required check is: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.

Question 579

For Westport Managed Security, operators support SASE policy enforcement and device compliance and are expected to validate matched user groups, controls and independent security outcomes. Operational incident: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. Recorded observation: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. Which network security or traffic-steering principle explains this behavior?

  1. Certificate-only inspection and deep content inspection provide different visibility and must match documented security requirements.
  2. An allow decision does not by itself invoke an absent intrusion-prevention profile.
  3. Time-zone mismatch is an analytics presentation error, not necessarily contradictory underlying security telemetry.
  4. App classification and the applied control decision are separate; identification alone does not block a service.

Explanation

Correct Answer

D:

App classification and the applied control decision are separate; identification alone does not block a service. At Westport Managed Security, the technical clue is: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. That explains the reported condition: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints.

Incorrect Answers

A:

Another relationship would be: Certificate-only inspection and deep content inspection provide different visibility and must match documented security requirements. It does not account for the issue reported by Westport Managed Security: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. The applicable principle is: App classification and the applied control decision are separate; identification alone does not block a service.

B:

An allow decision does not by itself invoke an absent intrusion-prevention profile. The key evidence is: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. That observation is explained by a different rule: App classification and the applied control decision are separate; identification alone does not block a service.

C:

Time-zone mismatch is an analytics presentation error, not necessarily contradictory underlying security telemetry. The failure at Westport Managed Security is: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. The operating rule directly related to that failure is: App classification and the applied control decision are separate; identification alone does not block a service.

Question 580

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: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. Confirmed observation: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. What remediation-and-validation combination most directly addresses this incident?

  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: Enable authorized deep inspection and appropriate Inline-CASB control for the supported SaaS activity while honoring exemptions. Proof: A benign sensitive-data control upload is denied or alerted and approved read-only SaaS operations still function.
  3. Action: Trace the application and source selectors against the rule definition and correct the scoped match if authorized. Proof: A new test call produces the expected rule ID and selected member in SD-WAN logs without altering general traffic routing.
  4. Action: Restrict the approved application signature or category in the user-group-specific application control profile and validate the policy match. Proof: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.

Explanation

Correct Answer

D:

The selection links action to a separately checked outcome: Action: Restrict the approved application signature or category in the user-group-specific application control profile and validate the policy match. Proof: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited. It is grounded in the Westport Managed Security clue: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. Closure must show: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.

Incorrect Answers

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 actual issue at Westport Managed Security is: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints. The proposed verification does not establish that the required result is: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.

B:

Action: Enable authorized deep inspection and appropriate Inline-CASB control for the supported SaaS activity while honoring exemptions. Proof: A benign sensitive-data control upload is denied or alerted and approved read-only SaaS operations still function. It is not sufficient proof of resolution for the stated Westport Managed Security incident: The SOC documents an application category restriction but a nonapproved cloud-storage app still uploads files from managed endpoints.

C:

Action: Trace the application and source selectors against the rule definition and correct the scoped match if authorized. Proof: A new test call produces the expected rule ID and selected member in SD-WAN logs without altering general traffic routing. The recorded evidence at Westport Managed Security is: FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. The correct outcome to measure is: A synthetic nonapproved upload is denied while authorized business cloud storage remains available and audited.

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