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 76

Question 750

During follow-up testing at a corporate headquarters, the original fault was: 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. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. Packet captures show forward and return traffic traversing the intended approved overlay.
  2. After subsequent FortiManager installs the route table retains the intended overlay prefix path.
  3. Syslog reaches the approved destination through its documented service path without altering user steering.
  4. Failure of the first ISP sends sessions through the second member with successful return traffic.

Explanation

Correct Answer

A:

Packet captures show forward and return traffic traversing the intended approved overlay. This evidence directly tests the intended corrective action: Reconcile remote prefix advertisements and return routing to create a supported symmetric path. It confirms the failure mechanism—Asymmetric return routing may invalidate stateful security or NAT expectations.—has been addressed in the actual affected flow.

Incorrect Answers

B:

After subsequent FortiManager installs the route table retains the intended overlay prefix path. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Reconcile remote prefix advertisements and return routing to create a supported symmetric path.—worked.

C:

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—Reconcile remote prefix advertisements and return routing to create a supported symmetric path.—worked.

D:

Failure of the first ISP sends sessions through the second member with successful return traffic. This would verify resolution of a different case: An admin adds a route to an SD-WAN zone but leaves one member without its required gateway or health check, causing failover to an unusable next hop. It does not show that the reported issue was fixed or that its intended action—Reconcile remote prefix advertisements and return routing to create a supported symmetric path.—worked.

Question 751

The incident investigation at a corporate headquarters records: 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. Which mechanism provides the strongest explanation?

  1. Routing uses the configured interface and gateway combination, not the member's label alone.
  2. Asymmetric return routing may invalidate stateful security or NAT expectations.
  3. Health-check measurements must be linked to route/member eligibility actions to change forwarding.
  4. The tunnel peer public endpoint and private protected subnet are different routing destinations.

Explanation

Correct Answer

B:

Asymmetric return routing may invalidate stateful security or NAT expectations. This explains why the reported condition occurs: 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. The targeted correction is: Reconcile remote prefix advertisements and return routing to create a supported symmetric path.

Incorrect Answers

A:

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.

C:

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.

D:

The tunnel peer public endpoint and private protected subnet are different routing destinations. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

Question 752

After a corrective change at a corporate headquarters, the team documents: 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. Which repeatable control BEST prevents a recurrence?

  1. Test both new and established sessions during WAN failure acceptance criteria.
  2. Review competing longer-prefix routes during overlay migration.
  3. Test bidirectional path symmetry during multipath overlay deployment.
  4. Audit per-ISP gateway-interface consistency following port recabling.

Explanation

Correct Answer

C:

Test bidirectional path symmetry during multipath overlay deployment. This control reduces recurrence of the documented mechanism: Asymmetric return routing may invalidate stateful security or NAT expectations. It creates a repeatable check around the needed response: Reconcile remote prefix advertisements and return routing to create a supported symmetric path.

Incorrect Answers

A:

Test both new and established sessions during WAN failure acceptance criteria. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Asymmetric return routing may invalidate stateful security or NAT expectations.

B:

Review competing longer-prefix routes during overlay migration. That safeguard addresses another potential failure: A new branch subnet has a longer specific static route pointing to an old MPLS path, overriding the intended broader overlay route. It is not the most targeted recurring control for the described cause: Asymmetric return routing may invalidate stateful security or NAT expectations.

D:

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: Asymmetric return routing may invalidate stateful security or NAT expectations.

Question 753

During a quarterly compliance review at a distributed branch estate, analysts observe: A branch sends protected Internet traffic directly to an ISP even though architecture requires FortiSASE cloud inspection for specified user subnets. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Configure the supported FortiGate-to-FortiSASE service connectivity and correct SD-WAN steering for those source networks.
  2. Narrow the local direct-Internet exception and require approved source traffic to use the cloud-inspected route.
  3. Align the intended inspection policy between branch-to-cloud and remote-user paths under approved scope.
  4. Add the approved cloud-connected tunnel as a monitored SD-WAN member in the correct zone.

Explanation

Correct Answer

A:

Configure the supported FortiGate-to-FortiSASE service connectivity and correct SD-WAN steering for those source networks. This is the most direct response to the stated incident: A branch sends protected Internet traffic directly to an ISP even though architecture requires FortiSASE cloud inspection for specified user subnets. The technical mechanism is: Local DIA alone does not pass branch traffic through the cloud security service. Confirmation requires: Test branch Internet sessions appear in FortiSASE security logs and follow approved inspection rules.

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: Local DIA alone does not pass branch traffic through the cloud security service.

C:

Align the intended inspection policy between branch-to-cloud and remote-user paths under approved scope. That could address a different issue in the same blueprint area: 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. It does not directly correct the given incident, whose decisive mechanism is: Local DIA alone does not pass branch traffic through the cloud security service.

D:

Add the approved cloud-connected tunnel as a monitored SD-WAN member in the correct zone. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Local DIA alone does not pass branch traffic through the cloud security service.

Question 754

At a distributed branch estate, a test team is validating a change after this incident: A branch sends protected Internet traffic directly to an ISP even though architecture requires FortiSASE cloud inspection for specified user subnets. What evidence most directly verifies the intended outcome?

  1. The tunnel negotiates successfully and permitted traffic resumes through cloud inspection.
  2. Test branch Internet sessions appear in FortiSASE security logs and follow approved inspection rules.
  3. Private database sessions traverse their approved internal overlay and Internet browsing follows FortiSASE.
  4. An authenticated remote test user reaches only the approved private app through the supported service.

Explanation

Correct Answer

B:

Test branch Internet sessions appear in FortiSASE security logs and follow approved inspection rules. This evidence directly tests the intended corrective action: Configure the supported FortiGate-to-FortiSASE service connectivity and correct SD-WAN steering for those source networks. It confirms the failure mechanism—Local DIA alone does not pass branch traffic through the cloud security service.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Configure the supported FortiGate-to-FortiSASE service connectivity and correct SD-WAN steering for those source networks.—worked.

C:

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 the supported FortiGate-to-FortiSASE service connectivity and correct SD-WAN steering for those source networks.—worked.

D:

An authenticated remote test user reaches only the approved private app through the supported service. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Configure the supported FortiGate-to-FortiSASE service connectivity and correct SD-WAN steering for those source networks.—worked.

Question 755

A Fortinet administrator at a distributed branch estate is assessing: A branch sends protected Internet traffic directly to an ISP even though architecture requires FortiSASE cloud inspection for specified user subnets. What is the most relevant root cause?

  1. Multiple underlay members do not automatically make every overlay endpoint path-independent.
  2. Broad cloud steering rules can capture private traffic outside their intended security architecture.
  3. Local DIA alone does not pass branch traffic through the cloud security service.
  4. Cloud tunnel establishment can depend on correct peer address or identity settings.

Explanation

Correct Answer

C:

Local DIA alone does not pass branch traffic through the cloud security service. This explains why the reported condition occurs: A branch sends protected Internet traffic directly to an ISP even though architecture requires FortiSASE cloud inspection for specified user subnets. The targeted correction is: Configure the supported FortiGate-to-FortiSASE service connectivity and correct SD-WAN steering for those source networks.

Incorrect Answers

A:

Multiple underlay members do not automatically make every overlay endpoint path-independent. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

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.

D:

Cloud tunnel establishment can depend on correct peer address or identity settings. This mechanism instead explains a separate problem: A new FortiSASE tunnel uses the branch's obsolete public IP as its remote peer after an ISP replacement, leaving site traffic uninspected. The current incident requires the more directly applicable cause stated by the correct option.

Question 756

A risk review at a distributed branch estate focuses on preventing this issue again: A branch sends protected Internet traffic directly to an ISP even though architecture requires FortiSASE cloud inspection for specified user subnets. Which recurring control is most suitable?

  1. Review local and FortiSASE inspection baselines together before adding branches.
  2. Test cloud tunnel initiation and rebinding under each ISP failure mode.
  3. Test round-trip flows and route symmetry for each branch-to-SASE network range.
  4. Validate cloud service egress and inspection logging during every branch integration.

Explanation

Correct Answer

D:

Validate cloud service egress and inspection logging during every branch integration. This control reduces recurrence of the documented mechanism: Local DIA alone does not pass branch traffic through the cloud security service. It creates a repeatable check around the needed response: Configure the supported FortiGate-to-FortiSASE service connectivity and correct SD-WAN steering for those source networks.

Incorrect Answers

A:

Review local and FortiSASE inspection baselines together before adding branches. That safeguard addresses another potential failure: 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. It is not the most targeted recurring control for the described cause: Local DIA alone does not pass branch traffic through the cloud security service.

B:

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: Local DIA alone does not pass branch traffic through the cloud security service.

C:

Test round-trip flows and route symmetry for each branch-to-SASE network range. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Local DIA alone does not pass branch traffic through the cloud security service.

Question 757

During a production service incident, an administrator reports at a research campus: An engineer creates a performance SLA but does not associate the backup member with its health-check member list, leaving the backup unmonitored. What should the team change or investigate FIRST?

  1. Calibrate the SLA threshold to an achievable business requirement and service geography.
  2. Include both intended members in the health-check configuration and verify probe state per link.
  3. Inspect and set the supported fail-SLA fallback strategy for the rule based on the application risk tolerance.
  4. Restore permitted local DNS resolution for the SLA server or use a validated reachable monitor address.

Explanation

Correct Answer

B:

Include both intended members in the health-check configuration and verify probe state per link. This is the most direct response to the stated incident: An engineer creates a performance SLA but does not associate the backup member with its health-check member list, leaving the backup unmonitored. The technical mechanism is: Performance SLA eligibility depends on which member interfaces are actually monitored. Confirmation requires: Health-check output lists both members with usable measurements and state changes.

Incorrect Answers

A:

Calibrate the SLA threshold to an achievable business requirement and service geography. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Performance SLA eligibility depends on which member interfaces are actually monitored.

C:

Inspect and set the supported fail-SLA fallback strategy for the rule based on the application risk tolerance. That could address a different issue in the same blueprint area: An engineer configures SD-WAN latency monitoring but its rule selects a member that meets no required SLA due to an unreviewed fallback behavior. It does not directly correct the given incident, whose decisive mechanism is: Performance SLA eligibility depends on which member interfaces are actually monitored.

D:

Restore permitted local DNS resolution for the SLA server or use a validated reachable monitor address. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Performance SLA eligibility depends on which member interfaces are actually monitored.

Question 758

Following remediation at a research campus, engineers revisit: An engineer creates a performance SLA but does not associate the backup member with its health-check member list, leaving the backup unmonitored. Which observation would BEST prove the specific issue is resolved?

  1. Normal regional WAN latency passes the approved target, while genuinely poor paths still fail.
  2. Steering diagnostics show a member violating the jitter limit removed from preferred selection.
  3. Health-check output lists both members with usable measurements and state changes.
  4. A private overlay outage affects only private-path eligibility while healthy Internet DIA remains usable.

Explanation

Correct Answer

C:

Health-check output lists both members with usable measurements and state changes. This evidence directly tests the intended corrective action: Include both intended members in the health-check configuration and verify probe state per link. It confirms the failure mechanism—Performance SLA eligibility depends on which member interfaces are actually monitored.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Include both intended members in the health-check configuration and verify probe state per link.—worked.

B:

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—Include both intended members in the health-check configuration and verify probe state per link.—worked.

D:

A private overlay outage affects only private-path eligibility while healthy Internet DIA remains usable. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Include both intended members in the health-check configuration and verify probe state per link.—worked.

Question 759

During a production service incident, this condition is reported: An engineer creates a performance SLA but does not associate the backup member with its health-check member list, leaving the backup unmonitored. Which technical explanation MOST directly accounts for the failure?

  1. Health checks measure quality; rule strategy and matching ultimately determine forwarding.
  2. SD-WAN strategies can have defined behavior when no link meets the SLA and require explicit risk review.
  3. Probe destination failure is not proof of every WAN transport failure.
  4. Performance SLA eligibility depends on which member interfaces are actually monitored.

Explanation

Correct Answer

D:

Performance SLA eligibility depends on which member interfaces are actually monitored. This explains why the reported condition occurs: An engineer creates a performance SLA but does not associate the backup member with its health-check member list, leaving the backup unmonitored. The targeted correction is: Include both intended members in the health-check configuration and verify probe state per link.

Incorrect Answers

A:

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.

B:

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.

C:

Probe destination failure is not proof of every WAN transport failure. This mechanism instead explains a separate problem: A branch health-check probes a single maintenance-prone public host; host downtime incorrectly marks both independent ISPs failed. The current incident requires the more directly applicable cause stated by the correct option.

Question 760

During a post-incident review at a research campus, the original problem was: An engineer creates a performance SLA but does not associate the backup member with its health-check member list, leaving the backup unmonitored. Which preventive practice most directly addresses its cause?

  1. Audit health-check member coverage during each circuit addition.
  2. Review SLA values using measured voice quality and contractual objectives.
  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

A:

Audit health-check member coverage during each circuit addition. This control reduces recurrence of the documented mechanism: Performance SLA eligibility depends on which member interfaces are actually monitored. It creates a repeatable check around the needed response: Include both intended members in the health-check configuration and verify probe state per link.

Incorrect Answers

B:

Review SLA values using measured voice quality and contractual objectives. That safeguard addresses another potential failure: A voice quality rule uses a jitter maximum far above business tolerance so choppy calls continue on a variable-delay ISP. It is not the most targeted recurring control for the described cause: Performance SLA eligibility depends on which member interfaces are actually monitored.

C:

Verify probe source IP and provider return routes during link commissioning. That safeguard addresses another potential failure: The performance SLA reports high loss on a backup line because probes use a source address not routed by its provider. It is not the most targeted recurring control for the described cause: Performance SLA eligibility depends on which member interfaces are actually monitored.

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: Performance SLA eligibility depends on which member interfaces are actually monitored.

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