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 17

Question 160

After a corrective change at a hospital campus, the team documents: A new SD-WAN deployment forwards logs only locally but the regional SOC expects searchable centralized traffic events. Which repeatable control BEST prevents a recurrence?

  1. Retain performance SLA history alongside application experience incidents.
  2. Monitor NTP drift and preserve timezone metadata in security log analysis.
  3. Test external log collection as part of SD-WAN commissioning.
  4. Require application and temporal context before escalating bandwidth anomalies as threats.

Explanation

Correct Answer

C:

Test external log collection as part of SD-WAN commissioning. This control reduces recurrence of the documented mechanism: Local log generation does not automatically deliver telemetry to the required central collector. It creates a repeatable check around the needed response: Configure the approved FortiGate log forwarding or central analytics destination and verify delivery.

Incorrect Answers

A:

Retain performance SLA history alongside application experience incidents. That safeguard addresses another potential failure: Voice complaints occur after WAN jitter spikes but the incident review relies on total traffic-byte reports without any performance SLA history. It is not the most targeted recurring control for the described cause: Local log generation does not automatically deliver telemetry to the required central collector.

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: Local log generation does not automatically deliver telemetry to the required central collector.

D:

Require application and temporal context before escalating bandwidth anomalies as threats. That safeguard addresses another potential failure: 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. It is not the most targeted recurring control for the described cause: Local log generation does not automatically deliver telemetry to the required central collector.

Question 161

During a security audit at a retail network, analysts observe: A support engineer assumes the presence of an SD-WAN health-check means all employee traffic is being load-balanced, yet the policy uses a manual priority path. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Inspect the selected SD-WAN strategy and choose a supported load-balance strategy only where the business requires distribution.
  2. Correct the firewall rule's actual LAN ingress zone while retaining the SD-WAN zone for egress.
  3. Enable the approved backup member and confirm interface link, gateway, and health status.
  4. Change the approved outbound firewall policy destination interface to the correct SD-WAN zone.

Explanation

Correct Answer

A:

Inspect the selected SD-WAN strategy and choose a supported load-balance strategy only where the business requires distribution. This is the most direct response to the stated incident: A support engineer assumes the presence of an SD-WAN health-check means all employee traffic is being load-balanced, yet the policy uses a manual priority path. The technical mechanism is: SLA monitoring reports link health but does not independently determine a rule's load-balancing mode. Confirmation requires: Multiple eligible sessions spread over healthy members according to the intended strategy and session hashing.

Incorrect Answers

B:

Correct the firewall rule's actual LAN ingress zone while retaining the SD-WAN zone for egress. That could address a different issue in the same blueprint area: An engineer enables SD-WAN but points the Internet firewall rule at the wrong source zone after moving the internal LAN port to a new VLAN. It does not directly correct the given incident, whose decisive mechanism is: SLA monitoring reports link health but does not independently determine a rule's load-balancing mode.

C:

Enable the approved backup member and confirm interface link, gateway, and health status. That could address a different issue in the same blueprint area: An engineer treats all link members as active after adding them but a new backup member is administratively disabled in its SD-WAN entry. It does not directly correct the given incident, whose decisive mechanism is: SLA monitoring reports link health but does not independently determine a rule's load-balancing mode.

D:

Change the approved outbound firewall policy destination interface to the correct SD-WAN zone. That could address a different issue in the same blueprint area: An administrator creates an SD-WAN zone and members but the outbound firewall policy still references only wan1, so sessions fail on wan2. It does not directly correct the given incident, whose decisive mechanism is: SLA monitoring reports link health but does not independently determine a rule's load-balancing mode.

Question 162

At a retail network, a test team is validating a change after this incident: A support engineer assumes the presence of an SD-WAN health-check means all employee traffic is being load-balanced, yet the policy uses a manual priority path. What evidence most directly verifies the intended outcome?

  1. A sample office host matches the permit while unrelated subnets remain denied.
  2. Multiple eligible sessions spread over healthy members according to the intended strategy and session hashing.
  3. Configuration validation succeeds and a rule diagnostic resolves a real member with expected egress.
  4. An allowed client session matches the intended firewall policy and the SD-WAN path is eligible.

Explanation

Correct Answer

B:

Multiple eligible sessions spread over healthy members according to the intended strategy and session hashing. This evidence directly tests the intended corrective action: Inspect the selected SD-WAN strategy and choose a supported load-balance strategy only where the business requires distribution. It confirms the failure mechanism—SLA monitoring reports link health but does not independently determine a rule's load-balancing mode.—has been addressed in the actual affected flow.

Incorrect Answers

A:

A sample office host matches the permit while unrelated subnets remain denied. This would verify resolution of a different case: A monitoring dashboard shows multiple healthy WAN members but a test office has no outbound traffic because its LAN network is absent from the configured firewall source address objects. It does not show that the reported issue was fixed or that its intended action—Inspect the selected SD-WAN strategy and choose a supported load-balance strategy only where the business requires distribution.—worked.

C:

Configuration validation succeeds and a rule diagnostic resolves a real member with expected egress. This would verify resolution of a different case: A branch upgrades FortiOS and observes SD-WAN rule policy using an old physical egress interface name no longer valid in its deployment template. It does not show that the reported issue was fixed or that its intended action—Inspect the selected SD-WAN strategy and choose a supported load-balance strategy only where the business requires distribution.—worked.

D:

An allowed client session matches the intended firewall policy and the SD-WAN path is eligible. This would verify resolution of a different case: An engineer enables SD-WAN but points the Internet firewall rule at the wrong source zone after moving the internal LAN port to a new VLAN. It does not show that the reported issue was fixed or that its intended action—Inspect the selected SD-WAN strategy and choose a supported load-balance strategy only where the business requires distribution.—worked.

Question 163

A Fortinet administrator at a retail network is assessing: A support engineer assumes the presence of an SD-WAN health-check means all employee traffic is being load-balanced, yet the policy uses a manual priority path. What is the most relevant root cause?

  1. Device-originated local-out traffic does not necessarily inherit the same forwarding behavior as user sessions.
  2. An unscoped all-sources Internet rule can redirect traffic outside intended trust boundaries.
  3. SLA monitoring reports link health but does not independently determine a rule's load-balancing mode.
  4. An interface cannot be selected by an SD-WAN rule until it is included as an eligible member.

Explanation

Correct Answer

C:

SLA monitoring reports link health but does not independently determine a rule's load-balancing mode. This explains why the reported condition occurs: A support engineer assumes the presence of an SD-WAN health-check means all employee traffic is being load-balanced, yet the policy uses a manual priority path. The targeted correction is: Inspect the selected SD-WAN strategy and choose a supported load-balance strategy only where the business requires distribution.

Incorrect Answers

A:

Device-originated local-out traffic does not necessarily inherit the same forwarding behavior as user sessions. This mechanism instead explains a separate problem: A FortiGate uses an SD-WAN zone for office traffic while FortiGate-originated DNS probes follow an unrelated management path, so user and device tests disagree. The current incident requires the more directly applicable cause stated by the correct option.

B:

An unscoped all-sources Internet rule can redirect traffic outside intended trust boundaries. This mechanism instead explains a separate problem: An operator uses a policy rule for all Internet users when only approved guest users should employ direct Internet access, causing internal workloads to bypass private inspection. The current incident requires the more directly applicable cause stated by the correct option.

D:

An interface cannot be selected by an SD-WAN rule until it is included as an eligible member. This mechanism instead explains a separate problem: A backup LTE interface is physically up but never added as an SD-WAN member, so WAN failure does not activate cellular continuity. The current incident requires the more directly applicable cause stated by the correct option.

Question 164

A risk review at a retail network focuses on preventing this issue again: A support engineer assumes the presence of an SD-WAN health-check means all employee traffic is being load-balanced, yet the policy uses a manual priority path. Which recurring control is most suitable?

  1. Require representative guest and production negative tests before activating shared DIA rules.
  2. Validate FIB routes alongside zone and member configuration at every site acceptance test.
  3. Test a minimal two-member SD-WAN path before rolling out application-specific rules.
  4. Review member selection strategy separately from health-check configuration at policy signoff.

Explanation

Correct Answer

D:

Review member selection strategy separately from health-check configuration at policy signoff. This control reduces recurrence of the documented mechanism: SLA monitoring reports link health but does not independently determine a rule's load-balancing mode. It creates a repeatable check around the needed response: Inspect the selected SD-WAN strategy and choose a supported load-balance strategy only where the business requires distribution.

Incorrect Answers

A:

Require representative guest and production negative tests before activating shared DIA rules. That safeguard addresses another potential failure: An operator uses a policy rule for all Internet users when only approved guest users should employ direct Internet access, causing internal workloads to bypass private inspection. It is not the most targeted recurring control for the described cause: SLA monitoring reports link health but does not independently determine a rule's load-balancing mode.

B:

Validate FIB routes alongside zone and member configuration at every site acceptance test. That safeguard addresses another potential failure: A remote site adds both ISP links to SD-WAN but omits a default static route toward the zone, leaving client traffic with no usable route. It is not the most targeted recurring control for the described cause: SLA monitoring reports link health but does not independently determine a rule's load-balancing mode.

C:

Test a minimal two-member SD-WAN path before rolling out application-specific rules. That safeguard addresses another potential failure: A two-ISP FortiGate has working physical WAN interfaces but no SD-WAN configuration, so a branch cannot steer applications by link health. It is not the most targeted recurring control for the described cause: SLA monitoring reports link health but does not independently determine a rule's load-balancing mode.

Question 165

During an incident triage, an administrator reports at a logistics office: A rule intended to steer only an authenticated finance group has a source address match but no required user-identity criterion, including guests on that subnet. What should the team change or investigate FIRST?

  1. Coordinate the relevant SD-WAN steering rule with the approved traffic shaping or QoS settings.
  2. Add the supported user or group match condition to the finance steering policy while retaining network scope.
  3. Restore the approved primary-versus-backup member order and retain actual failure handling.
  4. Set actual approved link costs and preference appropriate to metered versus fixed services.

Explanation

Correct Answer

B:

Add the supported user or group match condition to the finance steering policy while retaining network scope. This is the most direct response to the stated incident: A rule intended to steer only an authenticated finance group has a source address match but no required user-identity criterion, including guests on that subnet. The technical mechanism is: Source subnet membership is not equivalent to authenticated user-group membership. Confirmation requires: Only correctly identified finance sessions match the premium path; guests follow standard policy.

Incorrect Answers

A:

Coordinate the relevant SD-WAN steering rule with the approved traffic shaping or QoS settings. That could address a different issue in the same blueprint area: A UDP voice service needs preferential bandwidth during outages, but a general traffic shaping policy consumes the member capacity first. It does not directly correct the given incident, whose decisive mechanism is: Source subnet membership is not equivalent to authenticated user-group membership.

C:

Restore the approved primary-versus-backup member order and retain actual failure handling. That could address a different issue in the same blueprint area: A manual strategy lists wan2 first for an emergency but it stays preferred after the event, sending ordinary sessions over a low-bandwidth backup link. It does not directly correct the given incident, whose decisive mechanism is: Source subnet membership is not equivalent to authenticated user-group membership.

D:

Set actual approved link costs and preference appropriate to metered versus fixed services. That could address a different issue in the same blueprint area: An administrator selects the lowest-cost SLA mode but assigns the same cost to a metered cellular link and unlimited broadband, overusing cellular service. It does not directly correct the given incident, whose decisive mechanism is: Source subnet membership is not equivalent to authenticated user-group membership.

Question 166

Following remediation at a logistics office, engineers revisit: A rule intended to steer only an authenticated finance group has a source address match but no required user-identity criterion, including guests on that subnet. Which observation would BEST prove the specific issue is resolved?

  1. Controlled induced loss causes the rule to prefer the member with better measured packet delivery.
  2. The tested application hits its dedicated rule ID and selects the approved private link.
  3. Only correctly identified finance sessions match the premium path; guests follow standard policy.
  4. Backup throughput improves on the approved high-capacity link without disturbing voice prioritization.

Explanation

Correct Answer

C:

Only correctly identified finance sessions match the premium path; guests follow standard policy. This evidence directly tests the intended corrective action: Add the supported user or group match condition to the finance steering policy while retaining network scope. It confirms the failure mechanism—Source subnet membership is not equivalent to authenticated user-group membership.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Controlled induced loss causes the rule to prefer the member with better measured packet delivery. This would verify resolution of a different case: An operator selects Best Quality but leaves the metric on latency when the business application is mainly disrupted by packet loss. It does not show that the reported issue was fixed or that its intended action—Add the supported user or group match condition to the finance steering policy while retaining network scope.—worked.

B:

The tested application hits its dedicated rule ID and selects the approved private link. This would verify resolution of a different case: A business application has a dedicated SD-WAN rule located below a broad catch-all service rule, so it never uses its premium MPLS path. It does not show that the reported issue was fixed or that its intended action—Add the supported user or group match condition to the finance steering policy while retaining network scope.—worked.

D:

Backup throughput improves on the approved high-capacity link without disturbing voice prioritization. This would verify resolution of a different case: A link quality rule is configured to prefer the lowest measured latency but remote workers need consistent performance for large backups over a higher-capacity path. It does not show that the reported issue was fixed or that its intended action—Add the supported user or group match condition to the finance steering policy while retaining network scope.—worked.

Question 167

During an incident triage, this condition is reported: A rule intended to steer only an authenticated finance group has a source address match but no required user-identity criterion, including guests on that subnet. Which technical explanation MOST directly accounts for the failure?

  1. Equal or incorrect member costs undermine an economic path-selection policy.
  2. SD-WAN selection depends on an appropriate routing context and cannot create missing reachability.
  3. Application categories can cover far more traffic than a single intended App-ID.
  4. Source subnet membership is not equivalent to authenticated user-group membership.

Explanation

Correct Answer

D:

Source subnet membership is not equivalent to authenticated user-group membership. This explains why the reported condition occurs: A rule intended to steer only an authenticated finance group has a source address match but no required user-identity criterion, including guests on that subnet. The targeted correction is: Add the supported user or group match condition to the finance steering policy while retaining network scope.

Incorrect Answers

A:

Equal or incorrect member costs undermine an economic path-selection policy. This mechanism instead explains a separate problem: An administrator selects the lowest-cost SLA mode but assigns the same cost to a metered cellular link and unlimited broadband, overusing cellular service. The current incident requires the more directly applicable cause stated by the correct option.

B:

SD-WAN selection depends on an appropriate routing context and cannot create missing reachability. This mechanism instead explains a separate problem: A transaction flow is directed to a preferred member despite no matching route for its destination through that member, producing packet drops. The current incident requires the more directly applicable cause stated by the correct option.

C:

Application categories can cover far more traffic than a single intended App-ID. This mechanism instead explains a separate problem: An administrator configures a rule matching application category Social Networking while the approved exception is only for a named conferencing application. The current incident requires the more directly applicable cause stated by the correct option.

Question 168

During a post-incident review at a logistics office, the original problem was: A rule intended to steer only an authenticated finance group has a source address match but no required user-identity criterion, including guests on that subnet. Which preventive practice most directly addresses its cause?

  1. Include identity-positive and guest-negative path tests for group-aware SD-WAN policies.
  2. Document the balancing unit and validate with multiple sessions and clients.
  3. Test boundary source addresses for each overlapping SD-WAN rule after subnet changes.
  4. Audit private-data rule eligible members against network encryption requirements.

Explanation

Correct Answer

A:

Include identity-positive and guest-negative path tests for group-aware SD-WAN policies. This control reduces recurrence of the documented mechanism: Source subnet membership is not equivalent to authenticated user-group membership. It creates a repeatable check around the needed response: Add the supported user or group match condition to the finance steering policy while retaining network scope.

Incorrect Answers

B:

Document the balancing unit and validate with multiple sessions and clients. That safeguard addresses another potential failure: An engineer enables load-balancing mode expecting packet-level striping of one TCP session, then diagnoses normal single-link session affinity as a fault. It is not the most targeted recurring control for the described cause: Source subnet membership is not equivalent to authenticated user-group membership.

C:

Test boundary source addresses for each overlapping SD-WAN rule after subnet changes. That safeguard addresses another potential failure: A high-priority rule for guest Internet traffic mistakenly matches the corporate workstation source segment and sends trusted users over a limited guest ISP. It is not the most targeted recurring control for the described cause: Source subnet membership is not equivalent to authenticated user-group membership.

D:

Audit private-data rule eligible members against network encryption requirements. That safeguard addresses another potential failure: A branch needs a private application to use the encrypted overlay but an SD-WAN rule includes the direct Internet underlay in its eligible members. It is not the most targeted recurring control for the described cause: Source subnet membership is not equivalent to authenticated user-group membership.

Question 169

A firewall operations team at a manufacturing plant encounters the following during a controlled failover drill: A security operations center cannot trace who altered a FortiSASE inspection rule because several operators log in using the same administrator account. Which action most directly restores the approved security outcome?

  1. Reconcile active entitlements and the planned user population before extending invitations.
  2. Normalize identity group naming and map groups to approved, unambiguous service-policy references.
  3. Migrate changes to individually attributable administrators with supported audit logging enabled.
  4. Evaluate actual user-to-PoP latency and supported service-selection options before final assignment.

Explanation

Correct Answer

C:

Migrate changes to individually attributable administrators with supported audit logging enabled. This is the most direct response to the stated incident: A security operations center cannot trace who altered a FortiSASE inspection rule because several operators log in using the same administrator account. The technical mechanism is: Shared logins destroy reliable per-person policy change provenance. Confirmation requires: Each authorized policy modification is attributed to an identifiable operator in the relevant audit record.

Incorrect Answers

A:

Reconcile active entitlements and the planned user population before extending invitations. That could address a different issue in the same blueprint area: A FortiSASE tenant's administrator sees a warning about insufficient user licensing but continues issuing enrollment invitations that fail at authentication. It does not directly correct the given incident, whose decisive mechanism is: Shared logins destroy reliable per-person policy change provenance.

B:

Normalize identity group naming and map groups to approved, unambiguous service-policy references. That could address a different issue in the same blueprint area: A multi-site company creates an SASE administration configuration with duplicated names for user groups that have conflicting policy intent. It does not directly correct the given incident, whose decisive mechanism is: Shared logins destroy reliable per-person policy change provenance.

D:

Evaluate actual user-to-PoP latency and supported service-selection options before final assignment. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Shared logins destroy reliable per-person policy change provenance.

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.

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