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 79

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.

Question 781

At a hospital campus, a security analyst is reviewing this failure during a configuration rollout: The performance SLA reports high loss on a backup line because probes use a source address not routed by its provider. What is the MOST appropriate FIRST corrective step?

  1. Inspect both SLA quality and the matching SD-WAN rule mode, priority and eligibility before drawing path conclusions.
  2. Use a supported reliable probe strategy and alternate or representative targets that reduce single-endpoint bias.
  3. Use a performance SLA that probes an appropriate end-to-end service path beyond the local link.
  4. Set a valid supported probe source address or appropriate interface binding for that member.

Explanation

Correct Answer

D:

Set a valid supported probe source address or appropriate interface binding for that member. This is the most direct response to the stated incident: The performance SLA reports high loss on a backup line because probes use a source address not routed by its provider. The technical mechanism is: Incorrect probe source addressing can create false loss independent of application throughput. Confirmation requires: The backup probe reaches the target bidirectionally and loss matches packet captures.

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: Incorrect probe source addressing can create false loss independent of application throughput.

B:

Use a supported reliable probe strategy and alternate or representative targets that reduce single-endpoint bias. That could address a different issue in the same blueprint area: A branch health-check probes a single maintenance-prone public host; host downtime incorrectly marks both independent ISPs failed. It does not directly correct the given incident, whose decisive mechanism is: Incorrect probe source addressing can create false loss independent of application throughput.

C:

Use a performance SLA that probes an appropriate end-to-end service path beyond the local link. That could address a different issue in the same blueprint area: An engineer measures only last-mile interface status to declare a partner API path healthy, overlooking repeated upstream packet drops. It does not directly correct the given incident, whose decisive mechanism is: Incorrect probe source addressing can create false loss independent of application throughput.

Question 782

During follow-up testing at a hospital campus, the original fault was: The performance SLA reports high loss on a backup line because probes use a source address not routed by its provider. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. The backup probe reaches the target bidirectionally and loss matches packet captures.
  2. A simulated outage triggers a measured member health state change inside the required window.
  3. Steering diagnostics show a member violating the jitter limit removed from preferred selection.
  4. The health-check target resolves through the intended path and member state reflects real connectivity.

Explanation

Correct Answer

A:

The backup probe reaches the target bidirectionally and loss matches packet captures. This evidence directly tests the intended corrective action: Set a valid supported probe source address or appropriate interface binding for that member. It confirms the failure mechanism—Incorrect probe source addressing can create false loss independent of application throughput.—has been addressed in the actual affected flow.

Incorrect Answers

B:

A simulated outage triggers a measured member health state change inside the required window. This would verify resolution of a different case: An SLA uses a probe interval too sparse to detect outages quickly enough for a monitored payment application. It does not show that the reported issue was fixed or that its intended action—Set a valid supported probe source address or appropriate interface binding for that member.—worked.

C:

Steering diagnostics show a member violating the jitter limit removed from preferred selection. This would verify resolution of a different case: A voice quality rule uses a jitter maximum far above business tolerance so choppy calls continue on a variable-delay ISP. It does not show that the reported issue was fixed or that its intended action—Set a valid supported probe source address or appropriate interface binding for that member.—worked.

D:

The health-check target resolves through the intended path and member state reflects real connectivity. This would verify resolution of a different case: 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 does not show that the reported issue was fixed or that its intended action—Set a valid supported probe source address or appropriate interface binding for that member.—worked.

Question 783

The incident investigation at a hospital campus records: The performance SLA reports high loss on a backup line because probes use a source address not routed by its provider. Which mechanism provides the strongest explanation?

  1. Layer 1 connectivity cannot reveal upstream reachability or path-quality failures.
  2. Incorrect probe source addressing can create false loss independent of application throughput.
  3. Renaming or recreating a health-check does not guarantee rules reference the replacement.
  4. SD-WAN strategies can have defined behavior when no link meets the SLA and require explicit risk review.

Explanation

Correct Answer

B:

Incorrect probe source addressing can create false loss independent of application throughput. This explains why the reported condition occurs: The performance SLA reports high loss on a backup line because probes use a source address not routed by its provider. The targeted correction is: Set a valid supported probe source address or appropriate interface binding for that member.

Incorrect Answers

A:

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.

C:

Renaming or recreating a health-check does not guarantee rules reference the replacement. This mechanism instead explains a separate problem: An SD-WAN rule uses a performance SLA name that was replaced during template migration, so it never sees the new health measurements. The current incident requires the more directly applicable cause stated by the correct option.

D:

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.

Question 784

After a corrective change at a hospital campus, the team documents: The performance SLA reports high loss on a backup line because probes use a source address not routed by its provider. Which repeatable control BEST prevents a recurrence?

  1. Document probe target availability and negative tests for monitoring dependency failures.
  2. Monitor loss, latency and jitter against application requirements during call quality testing.
  3. Verify probe source IP and provider return routes during link commissioning.
  4. Baseline latency distributions and application tolerances before setting targets.

Explanation

Correct Answer

C:

Verify probe source IP and provider return routes during link commissioning. This control reduces recurrence of the documented mechanism: Incorrect probe source addressing can create false loss independent of application throughput. It creates a repeatable check around the needed response: Set a valid supported probe source address or appropriate interface binding for that member.

Incorrect Answers

A:

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: Incorrect probe source addressing can create false loss independent of application throughput.

B:

Monitor loss, latency and jitter against application requirements during call quality testing. That safeguard addresses another potential failure: Voice calls fail during transient packet loss while FortiGate steers calls to the cheapest link because the SLA tracks only latency. It is not the most targeted recurring control for the described cause: Incorrect probe source addressing can create false loss independent of application throughput.

D:

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: Incorrect probe source addressing can create false loss independent of application throughput.

Question 785

During a quarterly compliance review at a retail network, analysts observe: 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. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Inspect session reevaluation and supported failover behavior, then design application reconnection and NAT handling appropriately.
  2. Configure supported SLA member state or route-removal behavior to match documented failover policy.
  3. Remove or update the conflicting policy route and re-evaluate the real session lookup order.
  4. Remove or update the stale more-specific route so the approved path has correct longest-prefix precedence.

Explanation

Correct Answer

A:

Inspect session reevaluation and supported failover behavior, then design application reconnection and NAT handling appropriately. This is the most direct response to the stated incident: 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 technical mechanism is: Existing stateful sessions and NAT mappings may not transfer transparently between providers. Confirmation requires: New sessions use the surviving ISP and expected legacy-session behavior is documented and tested.

Incorrect Answers

B:

Configure supported SLA member state or route-removal behavior to match documented failover policy. That could address a different issue in the same blueprint area: A preferred WAN becomes unhealthy and is withdrawn from service, but its route remains installed due to an incorrect health state-action setting. It does not directly correct the given incident, whose decisive mechanism is: Existing stateful sessions and NAT mappings may not transfer transparently between providers.

C:

Remove or update the conflicting policy route and re-evaluate the real session lookup order. That could address a different issue in the same blueprint area: Traffic matching a local policy route is forced toward an outdated VPN tunnel instead of following the updated SD-WAN rule. It does not directly correct the given incident, whose decisive mechanism is: Existing stateful sessions and NAT mappings may not transfer transparently between providers.

D:

Remove or update the stale more-specific route so the approved path has correct longest-prefix precedence. That could address a different issue in the same blueprint area: A new branch subnet has a longer specific static route pointing to an old MPLS path, overriding the intended broader overlay route. It does not directly correct the given incident, whose decisive mechanism is: Existing stateful sessions and NAT mappings may not transfer transparently between providers.

Question 786

At a retail network, a test team is validating a change after this incident: 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. What evidence most directly verifies the intended outcome?

  1. Syslog reaches the approved destination through its documented service path without altering user steering.
  2. New sessions use the surviving ISP and expected legacy-session behavior is documented and tested.
  3. The missing subnet appears in the routing information base and private sessions complete.
  4. Private destination lookup selects the encrypted overlay path and clients connect.

Explanation

Correct Answer

B:

New sessions use the surviving ISP and expected legacy-session behavior is documented and tested. This evidence directly tests the intended corrective action: Inspect session reevaluation and supported failover behavior, then design application reconnection and NAT handling appropriately. It confirms the failure mechanism—Existing stateful sessions and NAT mappings may not transfer transparently between providers.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Syslog reaches the approved destination through its documented service path without altering user steering. This would verify resolution of a different case: 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. It does not show that the reported issue was fixed or that its intended action—Inspect session reevaluation and supported failover behavior, then design application reconnection and NAT handling appropriately.—worked.

C:

The missing subnet appears in the routing information base and private sessions complete. This would verify resolution of a different case: A branch uses BGP to advertise overlay prefixes but a filtered remote office subnet is missing from received routes. It does not show that the reported issue was fixed or that its intended action—Inspect session reevaluation and supported failover behavior, then design application reconnection and NAT handling appropriately.—worked.

D:

Private destination lookup selects the encrypted overlay path and clients connect. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Inspect session reevaluation and supported failover behavior, then design application reconnection and NAT handling appropriately.—worked.

Question 787

A Fortinet administrator at a retail network is assessing: 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. What is the most relevant root cause?

  1. Central route templates can override manually repaired local routes during later installs.
  2. Routing uses the configured interface and gateway combination, not the member's label alone.
  3. Existing stateful sessions and NAT mappings may not transfer transparently between providers.
  4. Ordinary ECMP route eligibility alone does not encode per-application provider restrictions.

Explanation

Correct Answer

C:

Existing stateful sessions and NAT mappings may not transfer transparently between providers. This explains why the reported condition occurs: 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 targeted correction is: Inspect session reevaluation and supported failover behavior, then design application reconnection and NAT handling appropriately.

Incorrect Answers

A:

Central route templates can override manually repaired local routes during later installs. This mechanism instead explains a separate problem: A FortiGate has the correct SD-WAN zone route for corporate VPN but FortiManager installs a conflicting stale prefix route during configuration synchronization. The current incident requires the more directly applicable cause stated by the correct option.

B:

Routing uses the configured interface and gateway combination, not the member's label alone. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

D:

Ordinary ECMP route eligibility alone does not encode per-application provider restrictions. This mechanism instead explains a separate problem: A device has two equal-cost underlay routes but an application must use one provider for compliance while SD-WAN service matching is absent. The current incident requires the more directly applicable cause stated by the correct option.

Question 788

A risk review at a retail network focuses on preventing this issue again: 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. Which recurring control is most suitable?

  1. Validate tunneled application prefixes separately from peer reachability.
  2. Audit per-ISP gateway-interface consistency following port recabling.
  3. Test failure-state route updates under controlled link outages.
  4. Test both new and established sessions during WAN failure acceptance criteria.

Explanation

Correct Answer

D:

Test both new and established sessions during WAN failure acceptance criteria. This control reduces recurrence of the documented mechanism: Existing stateful sessions and NAT mappings may not transfer transparently between providers. It creates a repeatable check around the needed response: Inspect session reevaluation and supported failover behavior, then design application reconnection and NAT handling appropriately.

Incorrect Answers

A:

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: Existing stateful sessions and NAT mappings may not transfer transparently between providers.

B:

Audit per-ISP gateway-interface consistency following port recabling. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Existing stateful sessions and NAT mappings may not transfer transparently between providers.

C:

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: Existing stateful sessions and NAT mappings may not transfer transparently between providers.

Question 789

During a production service incident, an administrator reports at a logistics office: 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. What should the team change or investigate FIRST?

  1. Correct the approved DNS resolution path and security policy for the cloud-inspected segment.
  2. Align the intended inspection policy between branch-to-cloud and remote-user paths under approved scope.
  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

B:

Align the intended inspection policy between branch-to-cloud and remote-user paths under approved scope. This is the most direct response to the stated incident: 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 technical mechanism is: Different traffic entry points can apply different profiles without policy harmonization. Confirmation requires: The same restricted test category receives the required action across both protected access modes.

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: Different traffic entry points can apply different profiles without policy harmonization.

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: Different traffic entry points can apply different profiles without policy harmonization.

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: Different traffic entry points can apply different profiles without policy harmonization.

Question 790

Following remediation at a logistics office, engineers revisit: 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. Which observation would BEST prove the specific issue is resolved?

  1. A controlled primary service-path interruption recovers via the approved backup connection.
  2. The intended source flow matches a policy and exits through the eligible FortiSASE tunnel.
  3. The same restricted test category receives the required action across both protected access modes.
  4. The tunnel negotiates successfully and permitted traffic resumes through cloud inspection.

Explanation

Correct Answer

C:

The same restricted test category receives the required action across both protected access modes. This evidence directly tests the intended corrective action: Align the intended inspection policy between branch-to-cloud and remote-user paths under approved scope. It confirms the failure mechanism—Different traffic entry points can apply different profiles without policy harmonization.—has been addressed in the actual affected flow.

Incorrect Answers

A:

A controlled primary service-path interruption recovers via the approved backup connection. This would verify resolution of a different case: A branch integration uses only one FortiSASE cloud gateway despite having a high-availability objective across service locations. It does not show that the reported issue was fixed or that its intended action—Align the intended inspection policy between branch-to-cloud and remote-user paths under approved scope.—worked.

B:

The intended source flow matches a policy and exits through the eligible FortiSASE tunnel. This would verify resolution of a different case: An SD-WAN rule sends traffic toward a FortiSASE tunnel but the tunnel is not part of the configured overlay SD-WAN zone. It does not show that the reported issue was fixed or that its intended action—Align the intended inspection policy between branch-to-cloud and remote-user paths under approved scope.—worked.

D:

The tunnel negotiates successfully and permitted traffic resumes through cloud inspection. This would verify resolution of a different case: A FortiGate tunnel to the cloud uses an IPsec proposal no longer accepted after a security baseline update, so branch SASE connectivity drops. It does not show that the reported issue was fixed or that its intended action—Align the intended inspection policy between branch-to-cloud and remote-user paths under approved scope.—worked.

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