McAfee-Secured Website

Exam Code: NSE5_SSE_AD-7.6

Exam Name: Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator

Certification Provider: Fortinet

Corresponding Certification: NSE5

100% Fortinet NSE5_SSE_AD-7.6 Guaranteed Success With Testking Training Materials

Get Real NSE5_SSE_AD-7.6 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

54 Questions & Answers with Testing Engine

"Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator Exam", also known as NSE5_SSE_AD-7.6 exam, is a Fortinet certification exam.

Pass your tests with the always up-to-date NSE5_SSE_AD-7.6 Exam Engine. Your NSE5_SSE_AD-7.6 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Fortinet NSE5_SSE_AD-7.6 Practice Test 18

Question 170

An operations review at a manufacturing plant has corrected: A security operations center cannot trace who altered a FortiSASE inspection rule because several operators log in using the same administrator account. Which observation specifically confirms success?

  1. The correct customer tenant is operational and authorized users can begin the supported enrollment process.
  2. Test users connect through a reachable PoP with response measurements meeting the approved target.
  3. A compliance review confirms the chosen service region and processing arrangements meet approved data-location obligations.
  4. Each authorized policy modification is attributed to an identifiable operator in the relevant audit record.

Explanation

Correct Answer

D:

Each authorized policy modification is attributed to an identifiable operator in the relevant audit record. This evidence directly tests the intended corrective action: Migrate changes to individually attributable administrators with supported audit logging enabled. It confirms the failure mechanism—Shared logins destroy reliable per-person policy change provenance.—has been addressed in the actual affected flow.

Incorrect Answers

A:

The correct customer tenant is operational and authorized users can begin the supported enrollment process. This would verify resolution of a different case: A new FortiSASE tenant has been purchased but remote users cannot sign in because the initial tenant provisioning and entitlement activation are incomplete. It does not show that the reported issue was fixed or that its intended action—Migrate changes to individually attributable administrators with supported audit logging enabled.—worked.

B:

Test users connect through a reachable PoP with response measurements meeting the approved target. This would verify resolution of a different case: An admin selects a PoP for remote users based only on geographic distance even though upstream ISP routing gives that location poor responsiveness. It does not show that the reported issue was fixed or that its intended action—Migrate changes to individually attributable administrators with supported audit logging enabled.—worked.

C:

A compliance review confirms the chosen service region and processing arrangements meet approved data-location obligations. This would verify resolution of a different case: An enterprise with a strict data-residency requirement selects a FortiSASE region solely for lower latency without assessing where relevant security logs and data are processed. It does not show that the reported issue was fixed or that its intended action—Migrate changes to individually attributable administrators with supported audit logging enabled.—worked.

Question 171

At a manufacturing plant, investigators observe: A security operations center cannot trace who altered a FortiSASE inspection rule because several operators log in using the same administrator account. Which underlying policy or system mechanism BEST explains this behavior?

  1. Shared logins destroy reliable per-person policy change provenance.
  2. A licensed administrative identity cannot substitute for correctly entitled individual service users.
  3. Administrative viewing and policy modification should not require the same privileges.
  4. Global group membership without scoped policy cannot express country-specific web restrictions.

Explanation

Correct Answer

A:

Shared logins destroy reliable per-person policy change provenance. This explains why the reported condition occurs: A security operations center cannot trace who altered a FortiSASE inspection rule because several operators log in using the same administrator account. The targeted correction is: Migrate changes to individually attributable administrators with supported audit logging enabled.

Incorrect Answers

B:

A licensed administrative identity cannot substitute for correctly entitled individual service users. This mechanism instead explains a separate problem: A security team allocates a single FortiSASE license to a shared administrative account while expecting hundreds of individual employees to gain their own protected Internet sessions. The current incident requires the more directly applicable cause stated by the correct option.

C:

Administrative viewing and policy modification should not require the same privileges. This mechanism instead explains a separate problem: An administrator grants every helpdesk analyst full policy-change rights because some staff need to view remote user connection status. The current incident requires the more directly applicable cause stated by the correct option.

D:

Global group membership without scoped policy cannot express country-specific web restrictions. This mechanism instead explains a separate problem: A regional office needs stricter web filtering than headquarters, but its users are placed into a generic global group with unchanged default policy. The current incident requires the more directly applicable cause stated by the correct option.

Question 172

An operations group at a manufacturing plant resolved: A security operations center cannot trace who altered a FortiSASE inspection rule because several operators log in using the same administrator account. Which ongoing safeguard should become part of its change process?

  1. Measure representative carrier paths and remote-user experience during PoP planning.
  2. Audit administrative identity uniqueness and change event capture regularly.
  3. Require active policy confirmation rather than save status alone at change closure.
  4. Test representative country and group combinations before international FortiSASE rollout.

Explanation

Correct Answer

B:

Audit administrative identity uniqueness and change event capture regularly. This control reduces recurrence of the documented mechanism: Shared logins destroy reliable per-person policy change provenance. It creates a repeatable check around the needed response: Migrate changes to individually attributable administrators with supported audit logging enabled.

Incorrect Answers

A:

Measure representative carrier paths and remote-user experience during PoP planning. That safeguard addresses another potential failure: An admin selects a PoP for remote users based only on geographic distance even though upstream ISP routing gives that location poor responsiveness. It is not the most targeted recurring control for the described cause: Shared logins destroy reliable per-person policy change provenance.

C:

Require active policy confirmation rather than save status alone at change closure. That safeguard addresses another potential failure: A security change is saved in FortiSASE management but not deployed or activated through the required service workflow, so remote users still see old behavior. It is not the most targeted recurring control for the described cause: Shared logins destroy reliable per-person policy change provenance.

D:

Test representative country and group combinations before international FortiSASE rollout. That safeguard addresses another potential failure: A company expects users in two countries to be assigned the same inspection region despite a requirement for country-specific enforcement policies. It is not the most targeted recurring control for the described cause: Shared logins destroy reliable per-person policy change provenance.

Question 173

At a corporate headquarters, a security analyst is reviewing this failure during a configuration rollout: A video streaming restriction is requested for a classroom network but the only policy is a bandwidth cap that does not distinguish approved educational video categories. What is the MOST appropriate FIRST corrective step?

  1. Apply supported geo-location or geofencing conditions to the relevant contractor service policy.
  2. Reclassify or narrowly exempt the approved payroll portal under the supported web policy workflow.
  3. Review supported decryption mode and DLP enforcement compatibility for the approved traffic, with lawful exceptions.
  4. Configure the appropriate supported video filtering controls for the intended categories or channels.

Explanation

Correct Answer

D:

Configure the appropriate supported video filtering controls for the intended categories or channels. This is the most direct response to the stated incident: A video streaming restriction is requested for a classroom network but the only policy is a bandwidth cap that does not distinguish approved educational video categories. The technical mechanism is: Bandwidth shaping and category-specific video filtering solve different policy problems. Confirmation requires: Approved educational videos continue while prohibited entertainment samples are restricted.

Incorrect Answers

A:

Apply supported geo-location or geofencing conditions to the relevant contractor service policy. That could address a different issue in the same blueprint area: A contractor should have access only from approved countries but a FortiSASE security rule permits the identity from all geographic locations. It does not directly correct the given incident, whose decisive mechanism is: Bandwidth shaping and category-specific video filtering solve different policy problems.

B:

Reclassify or narrowly exempt the approved payroll portal under the supported web policy workflow. That could address a different issue in the same blueprint area: A FortiSASE administrator applies a broad URL block on a critical payroll portal because its vendor changed categories and no business exception review is in place. It does not directly correct the given incident, whose decisive mechanism is: Bandwidth shaping and category-specific video filtering solve different policy problems.

C:

Review supported decryption mode and DLP enforcement compatibility for the approved traffic, with lawful exceptions. That could address a different issue in the same blueprint area: A security team expects a cloud DLP policy to inspect private encrypted transfers but has configured only certificate inspection, leaving content unreadable. It does not directly correct the given incident, whose decisive mechanism is: Bandwidth shaping and category-specific video filtering solve different policy problems.

Question 174

During follow-up testing at a corporate headquarters, the original fault was: A video streaming restriction is requested for a classroom network but the only policy is a bandwidth cap that does not distinguish approved educational video categories. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. Approved educational videos continue while prohibited entertainment samples are restricted.
  2. A controlled invalid-chain test fails as required while properly trusted service sessions proceed.
  3. The tested legacy transfer is protected by a documented compatible control with appropriate event evidence.
  4. A safe category test is denied and the corresponding web filtering log records the action.

Explanation

Correct Answer

A:

Approved educational videos continue while prohibited entertainment samples are restricted. This evidence directly tests the intended corrective action: Configure the appropriate supported video filtering controls for the intended categories or channels. It confirms the failure mechanism—Bandwidth shaping and category-specific video filtering solve different policy problems.—has been addressed in the actual affected flow.

Incorrect Answers

B:

A controlled invalid-chain test fails as required while properly trusted service sessions proceed. This would verify resolution of a different case: A cloud security profile accepts every certificate signed by a private untrusted authority because the inspection policy does not check server certificate validation failures. It does not show that the reported issue was fixed or that its intended action—Configure the appropriate supported video filtering controls for the intended categories or channels.—worked.

C:

The tested legacy transfer is protected by a documented compatible control with appropriate event evidence. This would verify resolution of a different case: An operator applies a DLP rule to browser uploads but expects it to inspect an unsupported nonweb protocol used by a legacy application. It does not show that the reported issue was fixed or that its intended action—Configure the appropriate supported video filtering controls for the intended categories or channels.—worked.

D:

A safe category test is denied and the corresponding web filtering log records the action. This would verify resolution of a different case: A category listed as malicious remains accessible because the FortiSASE web filter profile action is set to Monitor rather than Block. It does not show that the reported issue was fixed or that its intended action—Configure the appropriate supported video filtering controls for the intended categories or channels.—worked.

Question 175

The incident investigation at a corporate headquarters records: A video streaming restriction is requested for a classroom network but the only policy is a bandwidth cap that does not distinguish approved educational video categories. Which mechanism provides the strongest explanation?

  1. Discovery or monitor mode reports activity without necessarily enforcing a prohibition.
  2. Bandwidth shaping and category-specific video filtering solve different policy problems.
  3. SASE inspection capabilities depend on supported traffic mode and protocol visibility.
  4. Inspection behavior and application compatibility depend on the exact protocol and profile choice.

Explanation

Correct Answer

B:

Bandwidth shaping and category-specific video filtering solve different policy problems. This explains why the reported condition occurs: A video streaming restriction is requested for a classroom network but the only policy is a bandwidth cap that does not distinguish approved educational video categories. The targeted correction is: Configure the appropriate supported video filtering controls for the intended categories or channels.

Incorrect Answers

A:

Discovery or monitor mode reports activity without necessarily enforcing a prohibition. This mechanism instead explains a separate problem: An inline CASB policy detects unauthorized cloud storage usage but is configured in monitor-only mode despite a requirement to block uploads. The current incident requires the more directly applicable cause stated by the correct option.

C:

SASE inspection capabilities depend on supported traffic mode and protocol visibility. This mechanism instead explains a separate problem: An operator applies a DLP rule to browser uploads but expects it to inspect an unsupported nonweb protocol used by a legacy application. The current incident requires the more directly applicable cause stated by the correct option.

D:

Inspection behavior and application compatibility depend on the exact protocol and profile choice. This mechanism instead explains a separate problem: A managed endpoint's FortiSASE SIA policy uses web filtering but sends video conferencing traffic through an unnecessarily intensive inspection profile that breaks media startup. The current incident requires the more directly applicable cause stated by the correct option.

Question 176

After a corrective change at a corporate headquarters, the team documents: A video streaming restriction is requested for a classroom network but the only policy is a bandwidth cap that does not distinguish approved educational video categories. Which repeatable control BEST prevents a recurrence?

  1. Monitor business-critical category changes and validate exceptions with risk owners.
  2. Correlate SSL inspection coverage with each DLP rule at control validation.
  3. Map acceptable video sources and categories before applying broad controls.
  4. Audit profile group completeness for every Internet allow policy.

Explanation

Correct Answer

C:

Map acceptable video sources and categories before applying broad controls. This control reduces recurrence of the documented mechanism: Bandwidth shaping and category-specific video filtering solve different policy problems. It creates a repeatable check around the needed response: Configure the appropriate supported video filtering controls for the intended categories or channels.

Incorrect Answers

A:

Monitor business-critical category changes and validate exceptions with risk owners. That safeguard addresses another potential failure: A FortiSASE administrator applies a broad URL block on a critical payroll portal because its vendor changed categories and no business exception review is in place. It is not the most targeted recurring control for the described cause: Bandwidth shaping and category-specific video filtering solve different policy problems.

B:

Correlate SSL inspection coverage with each DLP rule at control validation. That safeguard addresses another potential failure: A security team expects a cloud DLP policy to inspect private encrypted transfers but has configured only certificate inspection, leaving content unreadable. It is not the most targeted recurring control for the described cause: Bandwidth shaping and category-specific video filtering solve different policy problems.

D:

Audit profile group completeness for every Internet allow policy. That safeguard addresses another potential failure: FortiSASE remote web browsing is allowed under a policy with web filtering but no Antivirus profile, leaving risky downloads without intended malware inspection. It is not the most targeted recurring control for the described cause: Bandwidth shaping and category-specific video filtering solve different policy problems.

Question 177

During a quarterly compliance review at a distributed branch estate, analysts observe: A FortiView traffic view shows large outgoing usage attributed to one user but the SOC assumes the user is malicious without examining applications or time context. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Drill down to the relevant user, application, source, destination and session details before attributing the traffic.
  2. Restore supported time synchronization and normalize timestamps or timezone when correlating logs.
  3. Review rule hit status, match criteria and session source before changing member health settings.
  4. Add appropriate interface utilization, drop and SLA metrics to the operational analysis alongside session volume.

Explanation

Correct Answer

A:

Drill down to the relevant user, application, source, destination and session details before attributing the traffic. This is the most direct response to the stated incident: A FortiView traffic view shows large outgoing usage attributed to one user but the SOC assumes the user is malicious without examining applications or time context. The technical mechanism is: High traffic volume alone does not prove a security incident. Confirmation requires: The investigation identifies the legitimate backup application or specific anomalous flow with evidence.

Incorrect Answers

B:

Restore supported time synchronization and normalize timestamps or timezone when correlating logs. That could address a different issue in the same blueprint area: A security operations team compares FortiGate SD-WAN log times with FortiSASE events and misorders an incident because the branch clock is unsynchronized. It does not directly correct the given incident, whose decisive mechanism is: High traffic volume alone does not prove a security incident.

C:

Review rule hit status, match criteria and session source before changing member health settings. That could address a different issue in the same blueprint area: An engineer states SD-WAN ignored a rule because the interface was healthy, but rule diagnostics show no source-address match for the problem client. It does not directly correct the given incident, whose decisive mechanism is: High traffic volume alone does not prove a security incident.

D:

Add appropriate interface utilization, drop and SLA metrics to the operational analysis alongside session volume. That could address a different issue in the same blueprint area: A branch link becomes congested yet a report labels all sessions as normal because the dashboard tracks bytes and not interface drops or SLA degradation. It does not directly correct the given incident, whose decisive mechanism is: High traffic volume alone does not prove a security incident.

Question 178

At a distributed branch estate, a test team is validating a change after this incident: A FortiView traffic view shows large outgoing usage attributed to one user but the SOC assumes the user is malicious without examining applications or time context. What evidence most directly verifies the intended outcome?

  1. After correcting the rule source scope the test client hits the intended service ID.
  2. The investigation identifies the legitimate backup application or specific anomalous flow with evidence.
  3. A jitter threshold violation and corresponding link selection change appear at the call disruption time.
  4. Test sessions are grouped by the actual explicit service ID or documented implicit rule.

Explanation

Correct Answer

B:

The investigation identifies the legitimate backup application or specific anomalous flow with evidence. This evidence directly tests the intended corrective action: Drill down to the relevant user, application, source, destination and session details before attributing the traffic. It confirms the failure mechanism—High traffic volume alone does not prove a security incident.—has been addressed in the actual affected flow.

Incorrect Answers

A:

After correcting the rule source scope the test client hits the intended service ID. This would verify resolution of a different case: An engineer states SD-WAN ignored a rule because the interface was healthy, but rule diagnostics show no source-address match for the problem client. It does not show that the reported issue was fixed or that its intended action—Drill down to the relevant user, application, source, destination and session details before attributing the traffic.—worked.

C:

A jitter threshold violation and corresponding link selection change appear at the call disruption time. This would verify resolution of a different case: Voice complaints occur after WAN jitter spikes but the incident review relies on total traffic-byte reports without any performance SLA history. It does not show that the reported issue was fixed or that its intended action—Drill down to the relevant user, application, source, destination and session details before attributing the traffic.—worked.

D:

Test sessions are grouped by the actual explicit service ID or documented implicit rule. This would verify resolution of a different case: An analyst confuses implicit SD-WAN rule hits with explicit application-specific rule selection during a monthly performance review. It does not show that the reported issue was fixed or that its intended action—Drill down to the relevant user, application, source, destination and session details before attributing the traffic.—worked.

Question 179

A Fortinet administrator at a distributed branch estate is assessing: A FortiView traffic view shows large outgoing usage attributed to one user but the SOC assumes the user is malicious without examining applications or time context. What is the most relevant root cause?

  1. Aggregated zone totals hide per-member traffic distribution.
  2. Unsynchronized system clocks can produce misleading cross-device event sequence.
  3. High traffic volume alone does not prove a security incident.
  4. Packet retransmissions and new sessions are different events even if addresses match.

Explanation

Correct Answer

C:

High traffic volume alone does not prove a security incident. This explains why the reported condition occurs: A FortiView traffic view shows large outgoing usage attributed to one user but the SOC assumes the user is malicious without examining applications or time context. The targeted correction is: Drill down to the relevant user, application, source, destination and session details before attributing the traffic.

Incorrect Answers

A:

Aggregated zone totals hide per-member traffic distribution. This mechanism instead explains a separate problem: An operations dashboard shows an unexpected surge on cellular backup but a report aggregates all WAN members, obscuring the affected interface. The current incident requires the more directly applicable cause stated by the correct option.

B:

Unsynchronized system clocks can produce misleading cross-device event sequence. This mechanism instead explains a separate problem: A security operations team compares FortiGate SD-WAN log times with FortiSASE events and misorders an incident because the branch clock is unsynchronized. The current incident requires the more directly applicable cause stated by the correct option.

D:

Packet retransmissions and new sessions are different events even if addresses match. This mechanism instead explains a separate problem: A site sees duplicate-looking flow logs for retransmissions during an SD-WAN failover, and analysts count them as distinct user sessions. The current incident requires the more directly applicable cause stated by the correct option.

Question 180

A risk review at a distributed branch estate focuses on preventing this issue again: A FortiView traffic view shows large outgoing usage attributed to one user but the SOC assumes the user is malicious without examining applications or time context. Which recurring control is most suitable?

  1. Maintain per-member utilization dashboards with cost thresholds.
  2. Monitor NTP drift and preserve timezone metadata in security log analysis.
  3. Review link saturation metrics and health-check measurements in combined WAN performance reports.
  4. Require application and temporal context before escalating bandwidth anomalies as threats.

Explanation

Correct Answer

D:

Require application and temporal context before escalating bandwidth anomalies as threats. This control reduces recurrence of the documented mechanism: High traffic volume alone does not prove a security incident. It creates a repeatable check around the needed response: Drill down to the relevant user, application, source, destination and session details before attributing the traffic.

Incorrect Answers

A:

Maintain per-member utilization dashboards with cost thresholds. That safeguard addresses another potential failure: An operations dashboard shows an unexpected surge on cellular backup but a report aggregates all WAN members, obscuring the affected interface. It is not the most targeted recurring control for the described cause: High traffic volume alone does not prove a security incident.

B:

Monitor NTP drift and preserve timezone metadata in security log analysis. That safeguard addresses another potential failure: A security operations team compares FortiGate SD-WAN log times with FortiSASE events and misorders an incident because the branch clock is unsynchronized. It is not the most targeted recurring control for the described cause: High traffic volume alone does not prove a security incident.

C:

Review link saturation metrics and health-check measurements in combined WAN performance reports. That safeguard addresses another potential failure: A branch link becomes congested yet a report labels all sessions as normal because the dashboard tracks bytes and not interface drops or SLA degradation. It is not the most targeted recurring control for the described cause: High traffic volume alone does not prove a security incident.

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