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 78

Question 770

At a financial services branch, a test team is validating a change after this incident: A branch health-check probes a single maintenance-prone public host; host downtime incorrectly marks both independent ISPs failed. What evidence most directly verifies the intended outcome?

  1. The probe succeeds over the affected member while application policy stays appropriately restricted.
  2. Healthy ISP paths remain usable during an isolated public probe-target outage under the approved policy.
  3. Normal regional WAN latency passes the approved target, while genuinely poor paths still fail.
  4. Health-check output lists both members with usable measurements and state changes.

Explanation

Correct Answer

B:

Healthy ISP paths remain usable during an isolated public probe-target outage under the approved policy. This evidence directly tests the intended corrective action: Use a supported reliable probe strategy and alternate or representative targets that reduce single-endpoint bias. It confirms the failure mechanism—Probe destination failure is not proof of every WAN transport failure.—has been addressed in the actual affected flow.

Incorrect Answers

A:

The probe succeeds over the affected member while application policy stays appropriately restricted. This would verify resolution of a different case: A branch's SLA probe targets are blocked by an upstream provider ACL, yet employees can reach normal applications without difficulty. It does not show that the reported issue was fixed or that its intended action—Use a supported reliable probe strategy and alternate or representative targets that reduce single-endpoint bias.—worked.

C:

Normal regional WAN latency passes the approved target, while genuinely poor paths still fail. This would verify resolution of a different case: 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 does not show that the reported issue was fixed or that its intended action—Use a supported reliable probe strategy and alternate or representative targets that reduce single-endpoint bias.—worked.

D:

Health-check output lists both members with usable measurements and state changes. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Use a supported reliable probe strategy and alternate or representative targets that reduce single-endpoint bias.—worked.

Question 771

A Fortinet administrator at a financial services branch is assessing: A branch health-check probes a single maintenance-prone public host; host downtime incorrectly marks both independent ISPs failed. What is the most relevant root cause?

  1. Passive health observations require real sessions to supply path telemetry.
  2. Layer 1 connectivity cannot reveal upstream reachability or path-quality failures.
  3. Probe destination failure is not proof of every WAN transport failure.
  4. Health checks measure quality; rule strategy and matching ultimately determine forwarding.

Explanation

Correct Answer

C:

Probe destination failure is not proof of every WAN transport failure. This explains why the reported condition occurs: A branch health-check probes a single maintenance-prone public host; host downtime incorrectly marks both independent ISPs failed. The targeted correction is: Use a supported reliable probe strategy and alternate or representative targets that reduce single-endpoint bias.

Incorrect Answers

A:

Passive health observations require real sessions to supply path telemetry. This mechanism instead explains a separate problem: Network staff assume passive WAN measurements will be available before any traffic is sent through a new link, causing an empty dashboard to be interpreted as a fault. The current incident requires the more directly applicable cause stated by the correct option.

B:

Layer 1 connectivity cannot reveal upstream reachability or path-quality failures. This mechanism instead explains a separate problem: An engineer measures only last-mile interface status to declare a partner API path healthy, overlooking repeated upstream packet drops. The current incident requires the more directly applicable cause stated by the correct option.

D:

Health checks measure quality; rule strategy and matching ultimately determine forwarding. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

Question 772

A risk review at a financial services branch focuses on preventing this issue again: A branch health-check probes a single maintenance-prone public host; host downtime incorrectly marks both independent ISPs failed. Which recurring control is most suitable?

  1. Document active-versus-passive measurement prerequisites in link acceptance procedures.
  2. Include representative distant probes, not just carrier state, for critical services.
  3. Include DNS health in monitoring target configuration and outage triage.
  4. Document probe target availability and negative tests for monitoring dependency failures.

Explanation

Correct Answer

D:

Document probe target availability and negative tests for monitoring dependency failures. This control reduces recurrence of the documented mechanism: Probe destination failure is not proof of every WAN transport failure. It creates a repeatable check around the needed response: Use a supported reliable probe strategy and alternate or representative targets that reduce single-endpoint bias.

Incorrect Answers

A:

Document active-versus-passive measurement prerequisites in link acceptance procedures. That safeguard addresses another potential failure: Network staff assume passive WAN measurements will be available before any traffic is sent through a new link, causing an empty dashboard to be interpreted as a fault. It is not the most targeted recurring control for the described cause: Probe destination failure is not proof of every WAN transport failure.

B:

Include representative distant probes, not just carrier state, for critical services. That safeguard addresses another potential failure: An engineer measures only last-mile interface status to declare a partner API path healthy, overlooking repeated upstream packet drops. It is not the most targeted recurring control for the described cause: Probe destination failure is not proof of every WAN transport failure.

C:

Include DNS health in monitoring target configuration and outage triage. That safeguard addresses another potential failure: A remote edge reports a member unreachable after DNS changes because its health-check server is configured as a hostname and the FortiGate cannot resolve it. It is not the most targeted recurring control for the described cause: Probe destination failure is not proof of every WAN transport failure.

Question 773

During an incident triage, an administrator reports at a regional data center: A FortiGate has the correct SD-WAN zone route for corporate VPN but FortiManager installs a conflicting stale prefix route during configuration synchronization. What should the team change or investigate FIRST?

  1. Correct static route distance, priority or route target to prefer the approved SD-WAN zone.
  2. Correct the authoritative managed route template and reinstall the approved routing policy.
  3. Add the correct route for the private app subnet toward the associated tunnel or zone.
  4. Add the correct private prefix route toward the approved SD-WAN overlay zone or tunnel.

Explanation

Correct Answer

B:

Correct the authoritative managed route template and reinstall the approved routing policy. This is the most direct response to the stated incident: A FortiGate has the correct SD-WAN zone route for corporate VPN but FortiManager installs a conflicting stale prefix route during configuration synchronization. The technical mechanism is: Central route templates can override manually repaired local routes during later installs. Confirmation requires: After subsequent FortiManager installs the route table retains the intended overlay prefix path.

Incorrect Answers

A:

Correct static route distance, priority or route target to prefer the approved SD-WAN zone. That could address a different issue in the same blueprint area: A default route to the ISP remains preferred over the SD-WAN zone after migration, causing most traffic to bypass SD-WAN rules. It does not directly correct the given incident, whose decisive mechanism is: Central route templates can override manually repaired local routes during later installs.

C:

Add the correct route for the private app subnet toward the associated tunnel or zone. That could address a different issue in the same blueprint area: A tunnel interface is a zone member but its route uses the remote gateway's public IP instead of the private destination prefix, leaving internal apps unrouteable. It does not directly correct the given incident, whose decisive mechanism is: Central route templates can override manually repaired local routes during later installs.

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: Central route templates can override manually repaired local routes during later installs.

Question 774

Following remediation at a regional data center, engineers revisit: A FortiGate has the correct SD-WAN zone route for corporate VPN but FortiManager installs a conflicting stale prefix route during configuration synchronization. Which observation would BEST prove the specific issue is resolved?

  1. The active route resolves to the healthy tunnel and the remote branch is reachable.
  2. New Internet sessions use the SD-WAN zone and rule diagnostics show member selection.
  3. After subsequent FortiManager installs the route table retains the intended overlay prefix path.
  4. Packet captures show forward and return traffic traversing the intended approved overlay.

Explanation

Correct Answer

C:

After subsequent FortiManager installs the route table retains the intended overlay prefix path. This evidence directly tests the intended corrective action: Correct the authoritative managed route template and reinstall the approved routing policy. It confirms the failure mechanism—Central route templates can override manually repaired local routes during later installs.—has been addressed in the actual affected flow.

Incorrect Answers

A:

The active route resolves to the healthy tunnel and the remote branch is reachable. This would verify resolution of a different case: A VPN overlay uses dynamic routing but an old static route for the same branch prefix takes precedence and sends traffic through an unreachable tunnel. It does not show that the reported issue was fixed or that its intended action—Correct the authoritative managed route template and reinstall the approved routing policy.—worked.

B:

New Internet sessions use the SD-WAN zone and rule diagnostics show member selection. This would verify resolution of a different case: A default route to the ISP remains preferred over the SD-WAN zone after migration, causing most traffic to bypass SD-WAN rules. It does not show that the reported issue was fixed or that its intended action—Correct the authoritative managed route template and reinstall the approved routing policy.—worked.

D:

Packet captures show forward and return traffic traversing the intended approved overlay. This would verify resolution of a different case: A new IPsec tunnel is added as an SD-WAN member yet the remote LAN gateway replies through a third-party cloud path because route advertisement is asymmetric. It does not show that the reported issue was fixed or that its intended action—Correct the authoritative managed route template and reinstall the approved routing policy.—worked.

Question 775

During an incident triage, this condition is reported: A FortiGate has the correct SD-WAN zone route for corporate VPN but FortiManager installs a conflicting stale prefix route during configuration synchronization. Which technical explanation MOST directly accounts for the failure?

  1. Existing stateful sessions and NAT mappings may not transfer transparently between providers.
  2. Health-check measurements must be linked to route/member eligibility actions to change forwarding.
  3. SD-WAN route changes and source address translation must remain compatible across failover.
  4. Central route templates can override manually repaired local routes during later installs.

Explanation

Correct Answer

D:

Central route templates can override manually repaired local routes during later installs. This explains why the reported condition occurs: A FortiGate has the correct SD-WAN zone route for corporate VPN but FortiManager installs a conflicting stale prefix route during configuration synchronization. The targeted correction is: Correct the authoritative managed route template and reinstall the approved routing policy.

Incorrect Answers

A:

Existing stateful sessions and NAT mappings may not transfer transparently between providers. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

B:

Health-check measurements must be linked to route/member eligibility actions to change forwarding. This mechanism instead explains a separate problem: A preferred WAN becomes unhealthy and is withdrawn from service, but its route remains installed due to an incorrect health state-action setting. The current incident requires the more directly applicable cause stated by the correct option.

C:

SD-WAN route changes and source address translation must remain compatible across failover. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

Question 776

During a post-incident review at a regional data center, the original problem was: A FortiGate has the correct SD-WAN zone route for corporate VPN but FortiManager installs a conflicting stale prefix route during configuration synchronization. Which preventive practice most directly addresses its cause?

  1. Make permanent route corrections in the authoritative centralized configuration source.
  2. Test advertised and accepted prefix lists across SD-WAN overlays after address expansion.
  3. Reconcile private prefix reachability before enabling application-based path preference.
  4. Validate tunneled application prefixes separately from peer reachability.

Explanation

Correct Answer

A:

Make permanent route corrections in the authoritative centralized configuration source. This control reduces recurrence of the documented mechanism: Central route templates can override manually repaired local routes during later installs. It creates a repeatable check around the needed response: Correct the authoritative managed route template and reinstall the approved routing policy.

Incorrect Answers

B:

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: Central route templates can override manually repaired local routes during later installs.

C:

Reconcile private prefix reachability before enabling application-based path preference. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Central route templates can override manually repaired local routes during later installs.

D:

Validate tunneled application prefixes separately from peer reachability. That safeguard addresses another potential failure: A tunnel interface is a zone member but its route uses the remote gateway's public IP instead of the private destination prefix, leaving internal apps unrouteable. It is not the most targeted recurring control for the described cause: Central route templates can override manually repaired local routes during later installs.

Question 777

A firewall operations team at a university network encounters the following during a controlled failover drill: An SD-WAN rule sends traffic toward a FortiSASE tunnel but the tunnel is not part of the configured overlay SD-WAN zone. Which action most directly restores the approved security outcome?

  1. Correct the approved DNS resolution path and security policy for the cloud-inspected segment.
  2. Narrow the local direct-Internet exception and require approved source traffic to use the cloud-inspected route.
  3. Add the approved cloud-connected tunnel as a monitored SD-WAN member in the correct zone.
  4. Configure a supported redundant PoP or cloud tunnel design and eligible SD-WAN failover policy.

Explanation

Correct Answer

C:

Add the approved cloud-connected tunnel as a monitored SD-WAN member in the correct zone. This is the most direct response to the stated incident: An SD-WAN rule sends traffic toward a FortiSASE tunnel but the tunnel is not part of the configured overlay SD-WAN zone. The technical mechanism is: A tunnel interface is not a selectable SD-WAN service path until correctly included. Confirmation requires: The intended source flow matches a policy and exits through the eligible FortiSASE tunnel.

Incorrect Answers

A:

Correct the approved DNS resolution path and security policy for the cloud-inspected segment. That could address a different issue in the same blueprint area: An engineer connects a branch to cloud inspection but forgets to route internal DNS service requests appropriately, causing only hostname-based access to fail. It does not directly correct the given incident, whose decisive mechanism is: A tunnel interface is not a selectable SD-WAN service path until correctly included.

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: A tunnel interface is not a selectable SD-WAN service path until correctly included.

D:

Configure a supported redundant PoP or cloud tunnel design and eligible SD-WAN failover policy. That could address a different issue in the same blueprint area: A branch integration uses only one FortiSASE cloud gateway despite having a high-availability objective across service locations. It does not directly correct the given incident, whose decisive mechanism is: A tunnel interface is not a selectable SD-WAN service path until correctly included.

Question 778

An operations review at a university network has corrected: An SD-WAN rule sends traffic toward a FortiSASE tunnel but the tunnel is not part of the configured overlay SD-WAN zone. Which observation specifically confirms success?

  1. DNS name lookup and downstream HTTPS access both complete through intended service paths.
  2. Private database sessions traverse their approved internal overlay and Internet browsing follows FortiSASE.
  3. Captured flows show response packets returning to the source subnet across the service connection.
  4. The intended source flow matches a policy and exits through the eligible FortiSASE tunnel.

Explanation

Correct Answer

D:

The intended source flow matches a policy and exits through the eligible FortiSASE tunnel. This evidence directly tests the intended corrective action: Add the approved cloud-connected tunnel as a monitored SD-WAN member in the correct zone. It confirms the failure mechanism—A tunnel interface is not a selectable SD-WAN service path until correctly included.—has been addressed in the actual affected flow.

Incorrect Answers

A:

DNS name lookup and downstream HTTPS access both complete through intended service paths. This would verify resolution of a different case: An engineer connects a branch to cloud inspection but forgets to route internal DNS service requests appropriately, causing only hostname-based access to fail. It does not show that the reported issue was fixed or that its intended action—Add the approved cloud-connected tunnel as a monitored SD-WAN member in the correct zone.—worked.

B:

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—Add the approved cloud-connected tunnel as a monitored SD-WAN member in the correct zone.—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—Add the approved cloud-connected tunnel as a monitored SD-WAN member in the correct zone.—worked.

Question 779

At a university network, investigators observe: An SD-WAN rule sends traffic toward a FortiSASE tunnel but the tunnel is not part of the configured overlay SD-WAN zone. Which underlying policy or system mechanism BEST explains this behavior?

  1. A tunnel interface is not a selectable SD-WAN service path until correctly included.
  2. Broad cloud steering rules can capture private traffic outside their intended security architecture.
  3. Cryptographic proposal mismatch can break overlay connectivity while underlay ISP remains healthy.
  4. Local DIA alone does not pass branch traffic through the cloud security service.

Explanation

Correct Answer

A:

A tunnel interface is not a selectable SD-WAN service path until correctly included. This explains why the reported condition occurs: An SD-WAN rule sends traffic toward a FortiSASE tunnel but the tunnel is not part of the configured overlay SD-WAN zone. The targeted correction is: Add the approved cloud-connected tunnel as a monitored SD-WAN member in the correct zone.

Incorrect Answers

B:

Broad cloud steering rules can capture private traffic outside their intended security architecture. This mechanism instead explains a separate problem: A FortiGate SD-WAN policy sends a critical internal database flow into a FortiSASE Internet security tunnel rather than the private data-center overlay. The current incident requires the more directly applicable cause stated by the correct option.

C:

Cryptographic proposal mismatch can break overlay connectivity while underlay ISP remains healthy. This mechanism instead explains a separate problem: A FortiGate tunnel to the cloud uses an IPsec proposal no longer accepted after a security baseline update, so branch SASE connectivity drops. 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 780

An operations group at a university network resolved: An SD-WAN rule sends traffic toward a FortiSASE tunnel but the tunnel is not part of the configured overlay SD-WAN zone. Which ongoing safeguard should become part of its change process?

  1. Test cloud tunnel initiation and rebinding under each ISP failure mode.
  2. Audit tunnel member and zone membership after cloud-branch integration.
  3. Test private-app reachability and group authorization independently of Internet browsing.
  4. Include cloud gateway failover tests in SD-WAN resilience acceptance plans.

Explanation

Correct Answer

B:

Audit tunnel member and zone membership after cloud-branch integration. This control reduces recurrence of the documented mechanism: A tunnel interface is not a selectable SD-WAN service path until correctly included. It creates a repeatable check around the needed response: Add the approved cloud-connected tunnel as a monitored SD-WAN member in the correct zone.

Incorrect Answers

A:

Test cloud tunnel initiation and rebinding under each ISP failure mode. That safeguard addresses another potential failure: A branch has two physical ISP links but the cloud security tunnel is pinned only to the primary interface, preventing SASE traffic from using the backup. It is not the most targeted recurring control for the described cause: A tunnel interface is not a selectable SD-WAN service path until correctly included.

C:

Test private-app reachability and group authorization independently of Internet browsing. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: A tunnel interface is not a selectable SD-WAN service path until correctly included.

D:

Include cloud gateway failover tests in SD-WAN resilience acceptance plans. That safeguard addresses another potential failure: A branch integration uses only one FortiSASE cloud gateway despite having a high-availability objective across service locations. It is not the most targeted recurring control for the described cause: A tunnel interface is not a selectable SD-WAN service path until correctly included.

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