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 89

Question 880

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

  1. Document active-versus-passive measurement prerequisites in link acceptance procedures.
  2. Document probe target availability and negative tests for monitoring dependency failures.
  3. Create service-specific health-check targets for materially different WAN paths.
  4. Teach operators to correlate SLA state with the actual service-rule selection result.

Explanation

Correct Answer

C:

Create service-specific health-check targets for materially different WAN paths. This control reduces recurrence of the documented mechanism: One public probe cannot establish private destination reachability for an overlay service. It creates a repeatable check around the needed response: Define appropriate separate private-service and Internet-service health-check targets for the relevant members and rules.

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: One public probe cannot establish private destination reachability for an overlay service.

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: One public probe cannot establish private destination reachability for an overlay service.

D:

Teach operators to correlate SLA state with the actual service-rule selection result. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: One public probe cannot establish private destination reachability for an overlay service.

Question 881

During a quarterly compliance review at a retail network, analysts observe: A FortiGate tunnel to the cloud uses an IPsec proposal no longer accepted after a security baseline update, so branch SASE connectivity drops. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Align the supported IPsec proposals and authentication parameters on both sides with the approved baseline.
  2. Update the supported peer settings or cloud integration identity to the current public endpoint.
  3. Configure the appropriate FortiSASE private access or supported site-connected application path and authorize the application.
  4. Configure the supported site identity, subnet or gateway attribution in the integration and analytics setup.

Explanation

Correct Answer

A:

Align the supported IPsec proposals and authentication parameters on both sides with the approved baseline. This is the most direct response to the stated incident: A FortiGate tunnel to the cloud uses an IPsec proposal no longer accepted after a security baseline update, so branch SASE connectivity drops. The technical mechanism is: Cryptographic proposal mismatch can break overlay connectivity while underlay ISP remains healthy. Confirmation requires: The tunnel negotiates successfully and permitted traffic resumes through cloud inspection.

Incorrect Answers

B:

Update the supported peer settings or cloud integration identity to the current public endpoint. That could address a different issue in the same blueprint area: A new FortiSASE tunnel uses the branch's obsolete public IP as its remote peer after an ISP replacement, leaving site traffic uninspected. It does not directly correct the given incident, whose decisive mechanism is: Cryptographic proposal mismatch can break overlay connectivity while underlay ISP remains healthy.

C:

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: Cryptographic proposal mismatch can break overlay connectivity while underlay ISP remains healthy.

D:

Configure the supported site identity, subnet or gateway attribution in the integration and analytics setup. That could address a different issue in the same blueprint area: Branch traffic is correctly forwarded through FortiSASE but security event reports cannot attribute flows to the originating site because site identity mappings are absent. It does not directly correct the given incident, whose decisive mechanism is: Cryptographic proposal mismatch can break overlay connectivity while underlay ISP remains healthy.

Question 882

At a retail network, a test team is validating a change after this incident: A FortiGate tunnel to the cloud uses an IPsec proposal no longer accepted after a security baseline update, so branch SASE connectivity drops. What evidence most directly verifies the intended outcome?

  1. A test event identifies the originating branch and associated user or network context.
  2. The tunnel negotiates successfully and permitted traffic resumes through cloud inspection.
  3. During a primary circuit outage a test cloud-inspected flow recovers through the backup carrier.
  4. Captured flows show response packets returning to the source subnet across the service connection.

Explanation

Correct Answer

B:

The tunnel negotiates successfully and permitted traffic resumes through cloud inspection. This evidence directly tests the intended corrective action: Align the supported IPsec proposals and authentication parameters on both sides with the approved baseline. It confirms the failure mechanism—Cryptographic proposal mismatch can break overlay connectivity while underlay ISP remains healthy.—has been addressed in the actual affected flow.

Incorrect Answers

A:

A test event identifies the originating branch and associated user or network context. This would verify resolution of a different case: Branch traffic is correctly forwarded through FortiSASE but security event reports cannot attribute flows to the originating site because site identity mappings are absent. It does not show that the reported issue was fixed or that its intended action—Align the supported IPsec proposals and authentication parameters on both sides with the approved baseline.—worked.

C:

During a primary circuit outage a test cloud-inspected flow recovers through the backup carrier. This would verify resolution of a different case: 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 does not show that the reported issue was fixed or that its intended action—Align the supported IPsec proposals and authentication parameters on both sides with the approved baseline.—worked.

D:

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—Align the supported IPsec proposals and authentication parameters on both sides with the approved baseline.—worked.

Question 883

A Fortinet administrator at a retail network is assessing: A FortiGate tunnel to the cloud uses an IPsec proposal no longer accepted after a security baseline update, so branch SASE connectivity drops. What is the most relevant root cause?

  1. Different traffic entry points can apply different profiles without policy harmonization.
  2. Successful outbound tunnel forwarding does not prove reverse routing is complete.
  3. Cryptographic proposal mismatch can break overlay connectivity while underlay ISP remains healthy.
  4. Integrating a site tunnel does not automatically announce every protected branch subnet.

Explanation

Correct Answer

C:

Cryptographic proposal mismatch can break overlay connectivity while underlay ISP remains healthy. This explains why the reported condition occurs: A FortiGate tunnel to the cloud uses an IPsec proposal no longer accepted after a security baseline update, so branch SASE connectivity drops. The targeted correction is: Align the supported IPsec proposals and authentication parameters on both sides with the approved baseline.

Incorrect Answers

A:

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.

B:

Successful outbound tunnel forwarding does not prove reverse routing is complete. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

D:

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.

Question 884

A risk review at a retail network focuses on preventing this issue again: A FortiGate tunnel to the cloud uses an IPsec proposal no longer accepted after a security baseline update, so branch SASE connectivity drops. Which recurring control is most suitable?

  1. Audit tunnel member and zone membership after cloud-branch integration.
  2. Review branch firewall and route bypass paths after integrating with FortiSASE.
  3. Test negative private destination cases when expanding SASE branch redirection.
  4. Rehearse proposal changes with both FortiGate and cloud connection owners.

Explanation

Correct Answer

D:

Rehearse proposal changes with both FortiGate and cloud connection owners. This control reduces recurrence of the documented mechanism: Cryptographic proposal mismatch can break overlay connectivity while underlay ISP remains healthy. It creates a repeatable check around the needed response: Align the supported IPsec proposals and authentication parameters on both sides with the approved baseline.

Incorrect Answers

A:

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: Cryptographic proposal mismatch can break overlay connectivity while underlay ISP remains healthy.

B:

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: Cryptographic proposal mismatch can break overlay connectivity while underlay ISP remains healthy.

C:

Test negative private destination cases when expanding SASE branch redirection. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Cryptographic proposal mismatch can break overlay connectivity while underlay ISP remains healthy.

Question 885

During a production service incident, an administrator reports at a logistics office: An engineer configures SD-WAN latency monitoring but its rule selects a member that meets no required SLA due to an unreviewed fallback behavior. What should the team change or investigate FIRST?

  1. Use a supported reliable probe strategy and alternate or representative targets that reduce single-endpoint bias.
  2. Inspect and set the supported fail-SLA fallback strategy for the rule based on the application risk tolerance.
  3. Set a valid supported probe source address or appropriate interface binding for that member.
  4. Define appropriate separate private-service and Internet-service health-check targets for the relevant members and rules.

Explanation

Correct Answer

B:

Inspect and set the supported fail-SLA fallback strategy for the rule based on the application risk tolerance. This is the most direct response to the stated incident: 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 technical mechanism is: SD-WAN strategies can have defined behavior when no link meets the SLA and require explicit risk review. Confirmation requires: When all tested members violate target, the observed fallback matches the documented continuity policy.

Incorrect Answers

A:

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: SD-WAN strategies can have defined behavior when no link meets the SLA and require explicit risk review.

C:

Set a valid supported probe source address or appropriate interface binding for that member. That could address a different issue in the same blueprint area: The performance SLA reports high loss on a backup line because probes use a source address not routed by its provider. It does not directly correct the given incident, whose decisive mechanism is: SD-WAN strategies can have defined behavior when no link meets the SLA and require explicit risk review.

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: SD-WAN strategies can have defined behavior when no link meets the SLA and require explicit risk review.

Question 886

Following remediation at a logistics office, engineers revisit: An engineer configures SD-WAN latency monitoring but its rule selects a member that meets no required SLA due to an unreviewed fallback behavior. Which observation would BEST prove the specific issue is resolved?

  1. A private overlay outage affects only private-path eligibility while healthy Internet DIA remains usable.
  2. The expected active probe values or passive session-based measurements appear under the selected mode.
  3. When all tested members violate target, the observed fallback matches the documented continuity policy.
  4. A controlled upstream failure changes SLA health even while physical carrier stays up.

Explanation

Correct Answer

C:

When all tested members violate target, the observed fallback matches the documented continuity policy. This evidence directly tests the intended corrective action: Inspect and set the supported fail-SLA fallback strategy for the rule based on the application risk tolerance. It confirms the failure mechanism—SD-WAN strategies can have defined behavior when no link meets the SLA and require explicit risk review.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Inspect and set the supported fail-SLA fallback strategy for the rule based on the application risk tolerance.—worked.

B:

The expected active probe values or passive session-based measurements appear under the selected mode. This would verify resolution of a different case: 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 does not show that the reported issue was fixed or that its intended action—Inspect and set the supported fail-SLA fallback strategy for the rule based on the application risk tolerance.—worked.

D:

A controlled upstream failure changes SLA health even while physical carrier stays up. This would verify resolution of a different case: An engineer measures only last-mile interface status to declare a partner API path healthy, overlooking repeated upstream packet drops. It does not show that the reported issue was fixed or that its intended action—Inspect and set the supported fail-SLA fallback strategy for the rule based on the application risk tolerance.—worked.

Question 887

During a production service incident, this condition is reported: An engineer configures SD-WAN latency monitoring but its rule selects a member that meets no required SLA due to an unreviewed fallback behavior. Which technical explanation MOST directly accounts for the failure?

  1. Passive health observations require real sessions to supply path telemetry.
  2. Over-sensitive probe state transitions cause steering instability around normal variation.
  3. A probe target reached through another path can misrepresent a member's real service health.
  4. SD-WAN strategies can have defined behavior when no link meets the SLA and require explicit risk review.

Explanation

Correct Answer

D:

SD-WAN strategies can have defined behavior when no link meets the SLA and require explicit risk review. This explains why the reported condition occurs: 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 targeted correction is: Inspect and set the supported fail-SLA fallback strategy for the rule based on the application risk tolerance.

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:

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:

A probe target reached through another path can misrepresent a member's real service health. This mechanism instead explains a separate problem: A branch tests loss toward an internal DNS server reachable through a tunnel, so a public DIA member appears unhealthy despite reliable Internet service. The current incident requires the more directly applicable cause stated by the correct option.

Question 888

During a post-incident review at a logistics office, the original problem was: An engineer configures SD-WAN latency monitoring but its rule selects a member that meets no required SLA due to an unreviewed fallback behavior. Which preventive practice most directly addresses its cause?

  1. Test no-member-meets-SLA conditions rather than assuming automatic dropping or universal failover.
  2. Monitor loss, latency and jitter against application requirements during call quality testing.
  3. Audit health-check member coverage during each circuit addition.
  4. Validate health-detection delay against payment transaction recovery objectives.

Explanation

Correct Answer

A:

Test no-member-meets-SLA conditions rather than assuming automatic dropping or universal failover. This control reduces recurrence of the documented mechanism: SD-WAN strategies can have defined behavior when no link meets the SLA and require explicit risk review. It creates a repeatable check around the needed response: Inspect and set the supported fail-SLA fallback strategy for the rule based on the application risk tolerance.

Incorrect Answers

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: SD-WAN strategies can have defined behavior when no link meets the SLA and require explicit risk review.

C:

Audit health-check member coverage during each circuit addition. That safeguard addresses another potential failure: An engineer creates a performance SLA but does not associate the backup member with its health-check member list, leaving the backup unmonitored. It is not the most targeted recurring control for the described cause: SD-WAN strategies can have defined behavior when no link meets the SLA and require explicit risk review.

D:

Validate health-detection delay against payment transaction recovery objectives. That safeguard addresses another potential failure: An SLA uses a probe interval too sparse to detect outages quickly enough for a monitored payment application. It is not the most targeted recurring control for the described cause: SD-WAN strategies can have defined behavior when no link meets the SLA and require explicit risk review.

Question 889

A firewall operations team at a manufacturing plant encounters the following during a predeployment acceptance test: 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. Which action most directly restores the approved security outcome?

  1. Add the approved branch prefix and route or policy association to the supported integration.
  2. Create an appropriate service-relevant health monitor for the cloud path and associate it with steering decisions.
  3. Make the supported tunnel endpoint or SD-WAN integration resilient across the approved ISP paths.
  4. Separate private application destinations from cloud-Internet inspection criteria in SD-WAN rules and routes.

Explanation

Correct Answer

C:

Make the supported tunnel endpoint or SD-WAN integration resilient across the approved ISP paths. This is the most direct response to the stated incident: 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 technical mechanism is: Multiple underlay members do not automatically make every overlay endpoint path-independent. Confirmation requires: During a primary circuit outage a test cloud-inspected flow recovers through the backup carrier.

Incorrect Answers

A:

Add the approved branch prefix and route or policy association to the supported integration. That could address a different issue in the same blueprint area: A FortiGate connects to a FortiSASE PoP but its branch LAN subnet is missing from the cloud's permitted network or route configuration. It does not directly correct the given incident, whose decisive mechanism is: Multiple underlay members do not automatically make every overlay endpoint path-independent.

B:

Create an appropriate service-relevant health monitor for the cloud path and associate it with steering decisions. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Multiple underlay members do not automatically make every overlay endpoint path-independent.

D:

Separate private application destinations from cloud-Internet inspection criteria in SD-WAN rules and routes. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Multiple underlay members do not automatically make every overlay endpoint path-independent.

Question 890

An operations review at a manufacturing plant has corrected: 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. Which observation specifically confirms success?

  1. Test branch Internet sessions appear in FortiSASE security logs and follow approved inspection rules.
  2. A protected test subnet cannot bypass FortiSASE while documented exceptions function.
  3. The authenticated tunnel reestablishes and test user sessions appear in cloud inspection logs.
  4. During a primary circuit outage a test cloud-inspected flow recovers through the backup carrier.

Explanation

Correct Answer

D:

During a primary circuit outage a test cloud-inspected flow recovers through the backup carrier. This evidence directly tests the intended corrective action: Make the supported tunnel endpoint or SD-WAN integration resilient across the approved ISP paths. It confirms the failure mechanism—Multiple underlay members do not automatically make every overlay endpoint path-independent.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Test branch Internet sessions appear in FortiSASE security logs and follow approved inspection rules. This would verify resolution of a different case: A branch sends protected Internet traffic directly to an ISP even though architecture requires FortiSASE cloud inspection for specified user subnets. It does not show that the reported issue was fixed or that its intended action—Make the supported tunnel endpoint or SD-WAN integration resilient across the approved ISP paths.—worked.

B:

A protected test subnet cannot bypass FortiSASE while documented exceptions function. This would verify resolution of a different case: An administrator activates a branch-to-SASE tunnel but leaves a broad local firewall bypass permitting protected subnets to egress directly. It does not show that the reported issue was fixed or that its intended action—Make the supported tunnel endpoint or SD-WAN integration resilient across the approved ISP paths.—worked.

C:

The authenticated tunnel reestablishes and test user sessions appear in cloud inspection logs. This would verify resolution of a different case: A new FortiSASE tunnel uses the branch's obsolete public IP as its remote peer after an ISP replacement, leaving site traffic uninspected. It does not show that the reported issue was fixed or that its intended action—Make the supported tunnel endpoint or SD-WAN integration resilient across the approved ISP paths.—worked.

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