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 81

Question 800

After a corrective change at a corporate headquarters, the team documents: A FortiGate sends firewall-originated syslog through a nonpreferred management route while user sessions correctly follow SD-WAN, leading staff to blame an SD-WAN rule. Which repeatable control BEST prevents a recurrence?

  1. Test failure-state route updates under controlled link outages.
  2. Review destination prefix-to-zone mapping before enabling new overlays.
  3. Document and test local-out route policy for DNS, NTP, telemetry, and syslog separately.
  4. Test advertised and accepted prefix lists across SD-WAN overlays after address expansion.

Explanation

Correct Answer

C:

Document and test local-out route policy for DNS, NTP, telemetry, and syslog separately. This control reduces recurrence of the documented mechanism: Locally originated system traffic and forwarded sessions can use different routing decisions. It creates a repeatable check around the needed response: Review the local-out service routing and source-interface configuration for FortiGate logging independently of user traffic.

Incorrect Answers

A:

Test failure-state route updates under controlled link outages. That safeguard addresses another potential failure: A preferred WAN becomes unhealthy and is withdrawn from service, but its route remains installed due to an incorrect health state-action setting. It is not the most targeted recurring control for the described cause: Locally originated system traffic and forwarded sessions can use different routing decisions.

B:

Review destination prefix-to-zone mapping before enabling new overlays. That safeguard addresses another potential failure: A branch adds a second SD-WAN zone with private overlay members but the site's route to RFC1918 destinations still points to the DIA zone. It is not the most targeted recurring control for the described cause: Locally originated system traffic and forwarded sessions can use different routing decisions.

D:

Test advertised and accepted prefix lists across SD-WAN overlays after address expansion. That safeguard addresses another potential failure: A branch uses BGP to advertise overlay prefixes but a filtered remote office subnet is missing from received routes. It is not the most targeted recurring control for the described cause: Locally originated system traffic and forwarded sessions can use different routing decisions.

Question 801

During a security audit at a distributed branch estate, analysts observe: A branch integration uses only one FortiSASE cloud gateway despite having a high-availability objective across service locations. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Configure a supported redundant PoP or cloud tunnel design and eligible SD-WAN failover policy.
  2. Narrow the local direct-Internet exception and require approved source traffic to use the cloud-inspected route.
  3. Configure the supported FortiGate-to-FortiSASE service connectivity and correct SD-WAN steering for those source networks.
  4. Configure the appropriate FortiSASE private access or supported site-connected application path and authorize the application.

Explanation

Correct Answer

A:

Configure a supported redundant PoP or cloud tunnel design and eligible SD-WAN failover policy. This is the most direct response to the stated incident: A branch integration uses only one FortiSASE cloud gateway despite having a high-availability objective across service locations. The technical mechanism is: One cloud tunnel is a single connectivity path regardless of FortiGate's number of physical uplinks. Confirmation requires: A controlled primary service-path interruption recovers via the approved backup connection.

Incorrect Answers

B:

Narrow the local direct-Internet exception and require approved source traffic to use the cloud-inspected route. That could address a different issue in the same blueprint area: An administrator activates a branch-to-SASE tunnel but leaves a broad local firewall bypass permitting protected subnets to egress directly. It does not directly correct the given incident, whose decisive mechanism is: One cloud tunnel is a single connectivity path regardless of FortiGate's number of physical uplinks.

C:

Configure the supported FortiGate-to-FortiSASE service connectivity and correct SD-WAN steering for those source networks. That could address a different issue in the same blueprint area: A branch sends protected Internet traffic directly to an ISP even though architecture requires FortiSASE cloud inspection for specified user subnets. It does not directly correct the given incident, whose decisive mechanism is: One cloud tunnel is a single connectivity path regardless of FortiGate's number of physical uplinks.

D:

Configure the appropriate FortiSASE private access or supported site-connected application path and authorize the application. That could address a different issue in the same blueprint area: A company assumes remote FortiClient users can reach branch-only internal apps through the same secure Internet profile without configuring supported private application connectivity. It does not directly correct the given incident, whose decisive mechanism is: One cloud tunnel is a single connectivity path regardless of FortiGate's number of physical uplinks.

Question 802

At a distributed branch estate, a test team is validating a change after this incident: A branch integration uses only one FortiSASE cloud gateway despite having a high-availability objective across service locations. What evidence most directly verifies the intended outcome?

  1. Private database sessions traverse their approved internal overlay and Internet browsing follows FortiSASE.
  2. A controlled primary service-path interruption recovers via the approved backup connection.
  3. Captured flows show response packets returning to the source subnet across the service connection.
  4. The cloud-path SLA fails on gateway outage while the physical ISP can remain up.

Explanation

Correct Answer

B:

A controlled primary service-path interruption recovers via the approved backup connection. This evidence directly tests the intended corrective action: Configure a supported redundant PoP or cloud tunnel design and eligible SD-WAN failover policy. It confirms the failure mechanism—One cloud tunnel is a single connectivity path regardless of FortiGate's number of physical uplinks.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Private database sessions traverse their approved internal overlay and Internet browsing follows FortiSASE. This would verify resolution of a different case: A FortiGate SD-WAN policy sends a critical internal database flow into a FortiSASE Internet security tunnel rather than the private data-center overlay. It does not show that the reported issue was fixed or that its intended action—Configure a supported redundant PoP or cloud tunnel design and eligible SD-WAN failover policy.—worked.

C:

Captured flows show response packets returning to the source subnet across the service connection. This would verify resolution of a different case: A branch sends traffic to a FortiSASE gateway via a tunnel but the return route for its internal subnet is absent, producing one-way web sessions. It does not show that the reported issue was fixed or that its intended action—Configure a supported redundant PoP or cloud tunnel design and eligible SD-WAN failover policy.—worked.

D:

The cloud-path SLA fails on gateway outage while the physical ISP can remain up. This would verify resolution of a different case: A new SASE tunnel is established over one ISP, but FortiGate monitoring treats its health as equivalent to the underlying Internet link and fails to detect cloud-gateway reachability loss. It does not show that the reported issue was fixed or that its intended action—Configure a supported redundant PoP or cloud tunnel design and eligible SD-WAN failover policy.—worked.

Question 803

A Fortinet administrator at a distributed branch estate is assessing: A branch integration uses only one FortiSASE cloud gateway despite having a high-availability objective across service locations. What is the most relevant root cause?

  1. Integrating a site tunnel does not automatically announce every protected branch subnet.
  2. Different traffic entry points can apply different profiles without policy harmonization.
  3. One cloud tunnel is a single connectivity path regardless of FortiGate's number of physical uplinks.
  4. Local DIA alone does not pass branch traffic through the cloud security service.

Explanation

Correct Answer

C:

One cloud tunnel is a single connectivity path regardless of FortiGate's number of physical uplinks. This explains why the reported condition occurs: A branch integration uses only one FortiSASE cloud gateway despite having a high-availability objective across service locations. The targeted correction is: Configure a supported redundant PoP or cloud tunnel design and eligible SD-WAN failover policy.

Incorrect Answers

A:

Integrating a site tunnel does not automatically announce every protected branch subnet. This mechanism instead explains a separate problem: A FortiGate connects to a FortiSASE PoP but its branch LAN subnet is missing from the cloud's permitted network or route configuration. The current incident requires the more directly applicable cause stated by the correct option.

B:

Different traffic entry points can apply different profiles without policy harmonization. This mechanism instead explains a separate problem: An employee receives a SASE secure Internet policy from the cloud while branch local traffic uses a different direct Internet security profile, creating inconsistent URL blocks. The current incident requires the more directly applicable cause stated by the correct option.

D:

Local DIA alone does not pass branch traffic through the cloud security service. This mechanism instead explains a separate problem: A branch sends protected Internet traffic directly to an ISP even though architecture requires FortiSASE cloud inspection for specified user subnets. The current incident requires the more directly applicable cause stated by the correct option.

Question 804

A risk review at a distributed branch estate focuses on preventing this issue again: A branch integration uses only one FortiSASE cloud gateway despite having a high-availability objective across service locations. Which recurring control is most suitable?

  1. Review branch firewall and route bypass paths after integrating with FortiSASE.
  2. Use end-to-end SASE gateway probes for cloud tunnel resiliency decisions.
  3. Audit tunnel member and zone membership after cloud-branch integration.
  4. Include cloud gateway failover tests in SD-WAN resilience acceptance plans.

Explanation

Correct Answer

D:

Include cloud gateway failover tests in SD-WAN resilience acceptance plans. This control reduces recurrence of the documented mechanism: One cloud tunnel is a single connectivity path regardless of FortiGate's number of physical uplinks. It creates a repeatable check around the needed response: Configure a supported redundant PoP or cloud tunnel design and eligible SD-WAN failover policy.

Incorrect Answers

A:

Review branch firewall and route bypass paths after integrating with FortiSASE. That safeguard addresses another potential failure: An administrator activates a branch-to-SASE tunnel but leaves a broad local firewall bypass permitting protected subnets to egress directly. It is not the most targeted recurring control for the described cause: One cloud tunnel is a single connectivity path regardless of FortiGate's number of physical uplinks.

B:

Use end-to-end SASE gateway probes for cloud tunnel resiliency decisions. That safeguard addresses another potential failure: A new SASE tunnel is established over one ISP, but FortiGate monitoring treats its health as equivalent to the underlying Internet link and fails to detect cloud-gateway reachability loss. It is not the most targeted recurring control for the described cause: One cloud tunnel is a single connectivity path regardless of FortiGate's number of physical uplinks.

C:

Audit tunnel member and zone membership after cloud-branch integration. That safeguard addresses another potential failure: An SD-WAN rule sends traffic toward a FortiSASE tunnel but the tunnel is not part of the configured overlay SD-WAN zone. It is not the most targeted recurring control for the described cause: One cloud tunnel is a single connectivity path regardless of FortiGate's number of physical uplinks.

Question 805

During an incident triage, an administrator reports at a research campus: An SD-WAN rule uses a performance SLA name that was replaced during template migration, so it never sees the new health measurements. What should the team change or investigate FIRST?

  1. Inspect both SLA quality and the matching SD-WAN rule mode, priority and eligibility before drawing path conclusions.
  2. Associate the rule with the correct current SLA target and validate all dependent references.
  3. Include both intended members in the health-check configuration and verify probe state per link.
  4. Define appropriate separate private-service and Internet-service health-check targets for the relevant members and rules.

Explanation

Correct Answer

B:

Associate the rule with the correct current SLA target and validate all dependent references. This is the most direct response to the stated incident: An SD-WAN rule uses a performance SLA name that was replaced during template migration, so it never sees the new health measurements. The technical mechanism is: Renaming or recreating a health-check does not guarantee rules reference the replacement. Confirmation requires: The rule diagnostic displays the new SLA ID and responsive member eligibility.

Incorrect Answers

A:

Inspect both SLA quality and the matching SD-WAN rule mode, priority and eligibility before drawing path conclusions. That could address a different issue in the same blueprint area: An administrator reads a performance SLA's zero loss and assumes it guarantees that all business traffic will use that member regardless of steering strategy. It does not directly correct the given incident, whose decisive mechanism is: Renaming or recreating a health-check does not guarantee rules reference the replacement.

C:

Include both intended members in the health-check configuration and verify probe state per link. That could address a different issue in the same blueprint area: An engineer creates a performance SLA but does not associate the backup member with its health-check member list, leaving the backup unmonitored. It does not directly correct the given incident, whose decisive mechanism is: Renaming or recreating a health-check does not guarantee rules reference the replacement.

D:

Define appropriate separate private-service and Internet-service health-check targets for the relevant members and rules. That could address a different issue in the same blueprint area: A site wants link status tracked separately for private data-center traffic and Internet browsing, but uses the same public Internet probe for both SLA decisions. It does not directly correct the given incident, whose decisive mechanism is: Renaming or recreating a health-check does not guarantee rules reference the replacement.

Question 806

Following remediation at a research campus, engineers revisit: An SD-WAN rule uses a performance SLA name that was replaced during template migration, so it never sees the new health measurements. Which observation would BEST prove the specific issue is resolved?

  1. A direct-Internet test agrees with probe state and healthy DIA members become eligible.
  2. The backup probe reaches the target bidirectionally and loss matches packet captures.
  3. The rule diagnostic displays the new SLA ID and responsive member eligibility.
  4. Calls leave a member whose measured loss exceeds the threshold while a healthier option remains eligible.

Explanation

Correct Answer

C:

The rule diagnostic displays the new SLA ID and responsive member eligibility. This evidence directly tests the intended corrective action: Associate the rule with the correct current SLA target and validate all dependent references. It confirms the failure mechanism—Renaming or recreating a health-check does not guarantee rules reference the replacement.—has been addressed in the actual affected flow.

Incorrect Answers

A:

A direct-Internet test agrees with probe state and healthy DIA members become eligible. This would verify resolution of a different case: A branch tests loss toward an internal DNS server reachable through a tunnel, so a public DIA member appears unhealthy despite reliable Internet service. It does not show that the reported issue was fixed or that its intended action—Associate the rule with the correct current SLA target and validate all dependent references.—worked.

B:

The backup probe reaches the target bidirectionally and loss matches packet captures. This would verify resolution of a different case: The performance SLA reports high loss on a backup line because probes use a source address not routed by its provider. It does not show that the reported issue was fixed or that its intended action—Associate the rule with the correct current SLA target and validate all dependent references.—worked.

D:

Calls leave a member whose measured loss exceeds the threshold while a healthier option remains eligible. This would verify resolution of a different case: Voice calls fail during transient packet loss while FortiGate steers calls to the cheapest link because the SLA tracks only latency. It does not show that the reported issue was fixed or that its intended action—Associate the rule with the correct current SLA target and validate all dependent references.—worked.

Question 807

During an incident triage, this condition is reported: An SD-WAN rule uses a performance SLA name that was replaced during template migration, so it never sees the new health measurements. Which technical explanation MOST directly accounts for the failure?

  1. SD-WAN strategies can have defined behavior when no link meets the SLA and require explicit risk review.
  2. Over-sensitive probe state transitions cause steering instability around normal variation.
  3. Performance SLA eligibility depends on which member interfaces are actually monitored.
  4. Renaming or recreating a health-check does not guarantee rules reference the replacement.

Explanation

Correct Answer

D:

Renaming or recreating a health-check does not guarantee rules reference the replacement. This explains why the reported condition occurs: An SD-WAN rule uses a performance SLA name that was replaced during template migration, so it never sees the new health measurements. The targeted correction is: Associate the rule with the correct current SLA target and validate all dependent references.

Incorrect Answers

A:

SD-WAN strategies can have defined behavior when no link meets the SLA and require explicit risk review. This mechanism instead explains a separate problem: An engineer configures SD-WAN latency monitoring but its rule selects a member that meets no required SLA due to an unreviewed fallback behavior. The current incident requires the more directly applicable cause stated by the correct option.

B:

Over-sensitive probe state transitions cause steering instability around normal variation. This mechanism instead explains a separate problem: A branch SLA oscillates between healthy and failed every few seconds because recovery thresholds are too sensitive near its jitter boundary. The current incident requires the more directly applicable cause stated by the correct option.

C:

Performance SLA eligibility depends on which member interfaces are actually monitored. This mechanism instead explains a separate problem: An engineer creates a performance SLA but does not associate the backup member with its health-check member list, leaving the backup unmonitored. The current incident requires the more directly applicable cause stated by the correct option.

Question 808

During a post-incident review at a research campus, the original problem was: An SD-WAN rule uses a performance SLA name that was replaced during template migration, so it never sees the new health measurements. Which preventive practice most directly addresses its cause?

  1. Track health-check identifiers and rule dependencies across template changes.
  2. Document probe target availability and negative tests for monitoring dependency failures.
  3. Baseline latency distributions and application tolerances before setting targets.
  4. Tune monitoring hysteresis with real noisy-link data before production deployment.

Explanation

Correct Answer

A:

Track health-check identifiers and rule dependencies across template changes. This control reduces recurrence of the documented mechanism: Renaming or recreating a health-check does not guarantee rules reference the replacement. It creates a repeatable check around the needed response: Associate the rule with the correct current SLA target and validate all dependent references.

Incorrect Answers

B:

Document probe target availability and negative tests for monitoring dependency failures. That safeguard addresses another potential failure: A branch health-check probes a single maintenance-prone public host; host downtime incorrectly marks both independent ISPs failed. It is not the most targeted recurring control for the described cause: Renaming or recreating a health-check does not guarantee rules reference the replacement.

C:

Baseline latency distributions and application tolerances before setting targets. That safeguard addresses another potential failure: A performance SLA is configured with a 5-ms latency threshold despite a normal 40-ms regional WAN path, excluding all members under healthy conditions. It is not the most targeted recurring control for the described cause: Renaming or recreating a health-check does not guarantee rules reference the replacement.

D:

Tune monitoring hysteresis with real noisy-link data before production deployment. That safeguard addresses another potential failure: A branch SLA oscillates between healthy and failed every few seconds because recovery thresholds are too sensitive near its jitter boundary. It is not the most targeted recurring control for the described cause: Renaming or recreating a health-check does not guarantee rules reference the replacement.

Question 809

A firewall operations team at a service-provider edge encounters the following during a controlled failover drill: A branch adds a second SD-WAN zone with private overlay members but the site's route to RFC1918 destinations still points to the DIA zone. Which action most directly restores the approved security outcome?

  1. Correct the authoritative managed route template and reinstall the approved routing policy.
  2. Bind the intended gateway or route to the actual selected member interface as supported.
  3. Set the private subnet routes toward the approved private SD-WAN zone and verify firewall authorization.
  4. Add the correct private prefix route toward the approved SD-WAN overlay zone or tunnel.

Explanation

Correct Answer

C:

Set the private subnet routes toward the approved private SD-WAN zone and verify firewall authorization. This is the most direct response to the stated incident: A branch adds a second SD-WAN zone with private overlay members but the site's route to RFC1918 destinations still points to the DIA zone. The technical mechanism is: Zone selection follows routing information; adding a private zone alone does not move prefix routes. Confirmation requires: Private addresses use the overlay while Internet destinations use direct access.

Incorrect Answers

A:

Correct the authoritative managed route template and reinstall the approved routing policy. That could address a different issue in the same blueprint area: A FortiGate has the correct SD-WAN zone route for corporate VPN but FortiManager installs a conflicting stale prefix route during configuration synchronization. It does not directly correct the given incident, whose decisive mechanism is: Zone selection follows routing information; adding a private zone alone does not move prefix routes.

B:

Bind the intended gateway or route to the actual selected member interface as supported. That could address a different issue in the same blueprint area: An SD-WAN member has a static route to a provider gateway on the wrong interface, so probes work on another link but traffic drops when it is selected. It does not directly correct the given incident, whose decisive mechanism is: Zone selection follows routing information; adding a private zone alone does not move prefix routes.

D:

Add the correct private prefix route toward the approved SD-WAN overlay zone or tunnel. That could address a different issue in the same blueprint area: A branch firewall policy allows corporate traffic and an SD-WAN service is configured, but the route table lacks a prefix for the data-center network. It does not directly correct the given incident, whose decisive mechanism is: Zone selection follows routing information; adding a private zone alone does not move prefix routes.

Question 810

An operations review at a service-provider edge has corrected: A branch adds a second SD-WAN zone with private overlay members but the site's route to RFC1918 destinations still points to the DIA zone. Which observation specifically confirms success?

  1. New sessions use the surviving ISP and expected legacy-session behavior is documented and tested.
  2. External test services observe a valid address for each ISP and responses return successfully.
  3. TCP handshakes complete in both directions and session debug shows a consistent path.
  4. Private addresses use the overlay while Internet destinations use direct access.

Explanation

Correct Answer

D:

Private addresses use the overlay while Internet destinations use direct access. This evidence directly tests the intended corrective action: Set the private subnet routes toward the approved private SD-WAN zone and verify firewall authorization. It confirms the failure mechanism—Zone selection follows routing information; adding a private zone alone does not move prefix routes.—has been addressed in the actual affected flow.

Incorrect Answers

A:

New sessions use the surviving ISP and expected legacy-session behavior is documented and tested. This would verify resolution of a different case: An Internet route remains valid after wan1 failure but existing long-lived TCP sessions continue using the failed translated path and do not instantly recover. It does not show that the reported issue was fixed or that its intended action—Set the private subnet routes toward the approved private SD-WAN zone and verify firewall authorization.—worked.

B:

External test services observe a valid address for each ISP and responses return successfully. This would verify resolution of a different case: A source NAT policy translates a client to the primary ISP address even after SD-WAN routes traffic out through a backup provider, breaking return traffic. It does not show that the reported issue was fixed or that its intended action—Set the private subnet routes toward the approved private SD-WAN zone and verify firewall authorization.—worked.

C:

TCP handshakes complete in both directions and session debug shows a consistent path. This would verify resolution of a different case: A FortiGate forwards web traffic via DIA but its route back to an internal server uses the wrong LAN interface after a segmentation project. It does not show that the reported issue was fixed or that its intended action—Set the private subnet routes toward the approved private SD-WAN zone and verify firewall authorization.—worked.

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