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

Question 590

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: A SaaS policy should stop uploading regulated spreadsheets, but traffic is permitted after login and application identification. Confirmed observation: Policy shows the correct Inline-CASB rule but SSL deep inspection or required SaaS activity visibility is not applied to the affected HTTPS connection. Which scoped action plus measurable success result should the team choose?

  1. 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.
  2. Action: Configure the appropriate supported encryption posture rule and associate it with approved regulated SaaS access scope. Proof: The encrypted device works and a controlled nonencrypted device is blocked with observable compliance results.
  3. 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.
  4. Action: Use documented application tolerance and observed baseline to tune packet-loss criteria and monitoring stability without disabling protection. Proof: Normal authorized batch traffic stays on a suitable member and a sustained synthetic loss condition triggers the expected fallback.

Explanation

Correct Answer

C:

The option addresses the actual fault and includes measurable proof: 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. The case evidence at Silverpeak Cloud Services is: 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 acceptance target is: A benign sensitive-data control upload is denied or alerted and approved read-only SaaS operations still function.

Incorrect Answers

A:

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 actual issue at Silverpeak Cloud Services is: A SaaS policy should stop uploading regulated spreadsheets, but traffic is permitted after login and application identification. The proposed verification does not establish that the required result is: A benign sensitive-data control upload is denied or alerted and approved read-only SaaS operations still function.

B:

Action: Configure the appropriate supported encryption posture rule and associate it with approved regulated SaaS access scope. Proof: The encrypted device works and a controlled nonencrypted device is blocked with observable compliance results. It is not sufficient proof of resolution for the stated Silverpeak Cloud Services incident: A SaaS policy should stop uploading regulated spreadsheets, but traffic is permitted after login and application identification.

D:

Action: Use documented application tolerance and observed baseline to tune packet-loss criteria and monitoring stability without disabling protection. Proof: Normal authorized batch traffic stays on a suitable member and a sustained synthetic loss condition triggers the expected fallback. The relevant Silverpeak Cloud Services observation is: Policy shows the correct Inline-CASB rule but SSL deep inspection or required SaaS activity visibility is not applied to the affected HTTPS connection. Any successful correction still needs to verify: A benign sensitive-data control upload is denied or alerted and approved read-only SaaS operations still function.

Question 591

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: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. Confirmed observation: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. 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. Apply supported stricter inspection only to legally permitted scoped users with a proper trust chain and approved exception handling.
  3. Set the sanctioned file type block within the correctly applied profile group and verify a safe fixture download.
  4. Resolve the approved tunnel peer and authentication issue before allowing production traffic to select that member.

Explanation

Correct Answer

C:

At Redwood Financial Applications, the evidence establishes the immediate concern: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. The appropriate response is: Set the sanctioned file type block within the correctly applied profile group and verify a safe fixture download. The causal rule is: File-type filtering acts on observed content classification rather than simply the website category or filename extension. The required outcome is: A harmless executable-type test is blocked while the approved PDF control completes with expected logs.

Incorrect Answers

A:

Another proposed response centers on: Correct the sanctioned DNS resolution and filtering policy for the private namespace and validate with known test names. The reported Redwood Financial Applications failure is: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. The decisive record shows: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it.

B:

Another suggested intervention is: Apply supported stricter inspection only to legally permitted scoped users with a proper trust chain and approved exception handling. It is not sufficient evidence of resolving the Redwood Financial Applications condition: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. The measurable outcome still required is: A harmless executable-type test is blocked while the approved PDF control completes with expected logs.

D:

Another option proposes: Resolve the approved tunnel peer and authentication issue before allowing production traffic to select that member. At Redwood Financial Applications, the decisive evidence is: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. That step alone does not demonstrate correction of the specified problem: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries.

Question 592

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: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. The team must verify the root cause before changing production settings. Which piece of evidence distinguishes this cause from unrelated symptoms?

  1. Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class.
  2. URL-filter entries include a wildcard matching the entire provider domain rather than the documented prohibited URL scope.
  3. The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it.
  4. Session logs show the breakout path selects an egress rule that lacks the approved web filtering and intrusion inspection profile set.

Explanation

Correct Answer

C:

At Redwood Financial Applications, the reported condition is: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. The specifically relevant observation is: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. That distinction is explained by: File-type filtering acts on observed content classification rather than simply the website category or filename extension.

Incorrect Answers

A:

Compliance profile assignment combines unmanaged personal devices and managed devices in one permissive identity or posture class. It is not the discriminating clue in this record; that clue is: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. The Redwood Financial Applications issue is: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries.

B:

URL-filter entries include a wildcard matching the entire provider domain rather than the documented prohibited URL scope. The trace for Redwood Financial Applications instead establishes: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. This is the clue to the issue actually described.

D:

Session logs show the breakout path selects an egress rule that lacks the approved web filtering and intrusion inspection profile set. At Redwood Financial Applications, the recorded condition is: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. The particular evidence supporting it is: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it.

Question 593

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: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. Confirmed observation: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. Proposed controlled action: Set the sanctioned file type block within the correctly applied profile group and verify a safe fixture download. Which accepted outcome confirms the intended behavior?

  1. The prohibited test resource is blocked while the approved collaboration hostname remains accessible.
  2. A benign IPS test signature is detected or blocked and a normal authorized transaction remains successful.
  3. A harmless executable-type test is blocked while the approved PDF control completes with expected logs.
  4. New team sessions hit the explicit intended service rule and out-of-scope devices continue using the default route.

Explanation

Correct Answer

C:

The reported failure at Redwood Financial Applications is: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. The necessary independent result is: A harmless executable-type test is blocked while the approved PDF control completes with expected logs. It tests recovery against the original evidence: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it.

Incorrect Answers

A:

The prohibited test resource is blocked while the approved collaboration hostname remains accessible. The acceptance condition for the stated Redwood Financial Applications fault is: A harmless executable-type test is blocked while the approved PDF control completes with expected logs. The tests do not measure the same outcome.

B:

An alternative finding would be: A benign IPS test signature is detected or blocked and a normal authorized transaction remains successful. The applicable acceptance criterion at Redwood Financial Applications is: A harmless executable-type test is blocked while the approved PDF control completes with expected logs. That result is related to the original issue.

D:

New team sessions hit the explicit intended service rule and out-of-scope devices continue using the default route. That alone would not confirm correction of the Redwood Financial Applications problem: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. The necessary proof is: A harmless executable-type test is blocked while the approved PDF control completes with expected logs.

Question 594

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: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. Recorded observation: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. Which network security or traffic-steering principle explains this behavior?

  1. Effective compliance troubleshooting correlates endpoint health evaluation with policy decision and session time.
  2. DLP rules must balance valid pattern specificity with supporting context to avoid false positives.
  3. A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration.
  4. File-type filtering acts on observed content classification rather than simply the website category or filename extension.

Explanation

Correct Answer

D:

File-type filtering acts on observed content classification rather than simply the website category or filename extension. For Redwood Financial Applications, the supporting evidence is: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. The reported condition is: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries.

Incorrect Answers

A:

Another principle is: Effective compliance troubleshooting correlates endpoint health evaluation with policy decision and session time. It is not enough to account for the recorded Redwood Financial Applications evidence: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. The applicable rule is: File-type filtering acts on observed content classification rather than simply the website category or filename extension.

B:

DLP rules must balance valid pattern specificity with supporting context to avoid false positives. The documented Redwood Financial Applications failure is: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. The case is instead explained by: File-type filtering acts on observed content classification rather than simply the website category or filename extension.

C:

An alternative explanation is: A coherent SD-WAN deployment needs consistent forwarding routes as well as member configuration. It is not the reason established by the Redwood Financial Applications clue: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. The relevant causal relationship is: File-type filtering acts on observed content classification rather than simply the website category or filename extension.

Question 595

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: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. Confirmed observation: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. What remediation-and-validation combination most directly addresses this incident?

  1. Action: Set the sanctioned file type block within the correctly applied profile group and verify a safe fixture download. Proof: A harmless executable-type test is blocked while the approved PDF control completes with expected logs.
  2. Action: Configure the appropriate supported encryption posture rule and associate it with approved regulated SaaS access scope. Proof: The encrypted device works and a controlled nonencrypted device is blocked with observable compliance results.
  3. Action: Check the FortiSASE managed endpoint posture record and corresponding compliance or access logs before granting an exception. Proof: The exact failed requirement is identified, remediated, and then access recovers without disabling broader posture enforcement.
  4. Action: Update approved rule source scope to the actual team subnet and check rule matching and precedence without broadening it to all endpoints. Proof: New team sessions hit the explicit intended service rule and out-of-scope devices continue using the default route.

Explanation

Correct Answer

A:

The documented fault is: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. The selected change-plus-verification is: Action: Set the sanctioned file type block within the correctly applied profile group and verify a safe fixture download. Proof: A harmless executable-type test is blocked while the approved PDF control completes with expected logs. That pair responds to the Redwood Financial Applications observation: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it.

Incorrect Answers

B:

Action: Configure the appropriate supported encryption posture rule and associate it with approved regulated SaaS access scope. Proof: The encrypted device works and a controlled nonencrypted device is blocked with observable compliance results. It would not by itself demonstrate correction of the Redwood Financial Applications finding: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. The required outcome is: A harmless executable-type test is blocked while the approved PDF control completes with expected logs.

C:

An alternative option suggests: Action: Check the FortiSASE managed endpoint posture record and corresponding compliance or access logs before granting an exception. Proof: The exact failed requirement is identified, remediated, and then access recovers without disabling broader posture enforcement. The documented Redwood Financial Applications problem calls for a check against: A harmless executable-type test is blocked while the approved PDF control completes with expected logs. The original clue is: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it.

D:

Action: Update approved rule source scope to the actual team subnet and check rule matching and precedence without broadening it to all endpoints. Proof: New team sessions hit the explicit intended service rule and out-of-scope devices continue using the default route. At Redwood Financial Applications, the actual distinguishing clue is: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. The related test must establish: A harmless executable-type test is blocked while the approved PDF control completes with expected logs.

Question 596

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 managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. Confirmed observation: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. What scoped change is justified by the observed evidence?

  1. Enable authorized deep inspection and appropriate Inline-CASB control for the supported SaaS activity while honoring exemptions.
  2. Refine the approved DLP expression and test both synthetic sensitive identifiers and harmless similar-length control data.
  3. Set the sanctioned file type block within the correctly applied profile group and verify a safe fixture download.
  4. Correlate effective service rule, route and application session records to find the scoped routing defect before changing performance thresholds.

Explanation

Correct Answer

C:

At Westport Managed Security, the key finding is: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. The corresponding corrective action is: Set the sanctioned file type block within the correctly applied profile group and verify a safe fixture download. File-type filtering acts on observed content classification rather than simply the website category or filename extension. The separate acceptance check is: A harmless executable-type test is blocked while the approved PDF control completes with expected logs.

Incorrect Answers

A:

Although that step is: Enable authorized deep inspection and appropriate Inline-CASB control for the supported SaaS activity while honoring exemptions, the decisive observation here is: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. That choice alone does not establish the needed correction at Westport Managed Security.

B:

An alternative action is: Refine the approved DLP expression and test both synthetic sensitive identifiers and harmless similar-length control data. The observed evidence in Westport Managed Security instead establishes: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. A relevant response must address that observation and confirm: A harmless executable-type test is blocked while the approved PDF control completes with expected logs.

D:

Another proposed action is: Correlate effective service rule, route and application session records to find the scoped routing defect before changing performance thresholds. In Westport Managed Security, the relevant evidence is: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. The focused correction should address the root condition shown by that clue.

Question 597

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: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. The team must verify the root cause before changing production settings. Which specific observation should determine the next investigation step?

  1. The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it.
  2. DNS filtering or resolution logs show the internal name sent to a public category rule rather than the intended private DNS processing path.
  3. FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category.
  4. FortiSASE security logs show the alerts cluster around a known policy rollout and one approved synthetic validation source rather than diverse attackers.

Explanation

Correct Answer

A:

The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. It supports investigation of the Westport Managed Security issue: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. The governing technical reason is: File-type filtering acts on observed content classification rather than simply the website category or filename extension.

Incorrect Answers

B:

DNS filtering or resolution logs show the internal name sent to a public category rule rather than the intended private DNS processing path. The original Westport Managed Security observation is instead: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. That is the evidence tied to the stated failure.

C:

FortiSASE policy logs show the traffic classified under the relevant application signature while the attached profile permits that application category. It does not directly identify the problem reported at Westport Managed Security. The determining evidence is: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it.

D:

FortiSASE security logs show the alerts cluster around a known policy rollout and one approved synthetic validation source rather than diverse attackers. It does not substantiate the particular Westport Managed Security condition: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. The documented finding is: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it.

Question 598

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 managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. Confirmed observation: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. Proposed controlled action: Set the sanctioned file type block within the correctly applied profile group and verify a safe fixture download. What separate result verifies the change without hiding a second failure?

  1. A harmless executable-type test is blocked while the approved PDF control completes with expected logs.
  2. A benign IPS test signature is detected or blocked and a normal authorized transaction remains successful.
  3. A permitted synthetic category test follows the intended block decision and unrelated allowed categories remain reachable.
  4. Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied.

Explanation

Correct Answer

A:

The listed result is the right measure for Westport Managed Security: A harmless executable-type test is blocked while the approved PDF control completes with expected logs. It verifies the intended effect, whereas the case originally showed: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. The relevant principle is: File-type filtering acts on observed content classification rather than simply the website category or filename extension.

Incorrect Answers

B:

A benign IPS test signature is detected or blocked and a normal authorized transaction remains successful. It is not the evidence needed to close the reported issue. The proper Westport Managed Security success measure is: A harmless executable-type test is blocked while the approved PDF control completes with expected logs.

C:

An alternative test would show: A permitted synthetic category test follows the intended block decision and unrelated allowed categories remain reachable. It does not show the required post-change result at Westport Managed Security: A harmless executable-type test is blocked while the approved PDF control completes with expected logs. The original finding was: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it.

D:

Allowed remote client requests succeed and a synthetic unapproved SASE source or port is still denied. That is not sufficient to validate the stated Westport Managed Security failure, supported by: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. The required check is: A harmless executable-type test is blocked while the approved PDF control completes with expected logs.

Question 599

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: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. Recorded observation: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. Which operational principle governs the documented incident?

  1. File-type filtering acts on observed content classification rather than simply the website category or filename extension.
  2. Encrypted content cannot be fully inspected by content security engines without appropriate SSL inspection and policy binding.
  3. Compliance exceptions must be time- and identity-scoped; blanket bypass undermines every other endpoint policy.
  4. Authentication establishes identity; authorization relies on accurate policy groups and assignment.

Explanation

Correct Answer

A:

The applicable principle is: File-type filtering acts on observed content classification rather than simply the website category or filename extension. It fits the Westport Managed Security evidence: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. The incident is: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries.

Incorrect Answers

B:

Encrypted content cannot be fully inspected by content security engines without appropriate SSL inspection and policy binding. The key evidence is: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. That observation is explained by a different rule: File-type filtering acts on observed content classification rather than simply the website category or filename extension.

C:

Compliance exceptions must be time- and identity-scoped; blanket bypass undermines every other endpoint policy. The failure at Westport Managed Security is: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. The operating rule directly related to that failure is: File-type filtering acts on observed content classification rather than simply the website category or filename extension.

D:

Authentication establishes identity; authorization relies on accurate policy groups and assignment. In Westport Managed Security, the actual observation is: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. The rule connected to that evidence is: File-type filtering acts on observed content classification rather than simply the website category or filename extension.

Question 600

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 managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. Confirmed observation: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. Which approved change and separate test together resolve the issue?

  1. 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.
  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: Assign the official installer matching each approved OS and supported FortiClient version, then complete tenant enrollment. Proof: The test device from each intended platform authenticates and reports a managed SASE session with correct posture.
  4. Action: Set the sanctioned file type block within the correctly applied profile group and verify a safe fixture download. Proof: A harmless executable-type test is blocked while the approved PDF control completes with expected logs.

Explanation

Correct Answer

D:

The selection links action to a separately checked outcome: Action: Set the sanctioned file type block within the correctly applied profile group and verify a safe fixture download. Proof: A harmless executable-type test is blocked while the approved PDF control completes with expected logs. It is grounded in the Westport Managed Security clue: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. Closure must show: A harmless executable-type test is blocked while the approved PDF control completes with expected logs.

Incorrect Answers

A:

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. The actual issue at Westport Managed Security is: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries. The proposed verification does not establish that the required result is: A harmless executable-type test is blocked while the approved PDF control completes with expected logs.

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 Westport Managed Security incident: A managed endpoint downloads an executable from a category where company policy allows documents but forbids binaries.

C:

Action: Assign the official installer matching each approved OS and supported FortiClient version, then complete tenant enrollment. Proof: The test device from each intended platform authenticates and reports a managed SASE session with correct posture. The recorded evidence at Westport Managed Security is: The relevant FortiSASE file-filter profile permits the executable file type even though the approved business rules explicitly restrict it. The correct outcome to measure is: A harmless executable-type test is blocked while the approved PDF control completes with expected logs.

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