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 85

Question 840

During a post-incident review at a logistics office, the original problem was: A branch SLA oscillates between healthy and failed every few seconds because recovery thresholds are too sensitive near its jitter boundary. Which preventive practice most directly addresses its cause?

  1. Tune monitoring hysteresis with real noisy-link data before production deployment.
  2. Baseline latency distributions and application tolerances before setting targets.
  3. Verify probe source IP and provider return routes during link commissioning.
  4. Include DNS health in monitoring target configuration and outage triage.

Explanation

Correct Answer

A:

Tune monitoring hysteresis with real noisy-link data before production deployment. This control reduces recurrence of the documented mechanism: Over-sensitive probe state transitions cause steering instability around normal variation. It creates a repeatable check around the needed response: Adjust supported threshold, fail/recover criteria or hysteresis behavior using measured path stability.

Incorrect Answers

B:

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: Over-sensitive probe state transitions cause steering instability around normal variation.

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: Over-sensitive probe state transitions cause steering instability around normal variation.

D:

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: Over-sensitive probe state transitions cause steering instability around normal variation.

Question 841

A firewall operations team at a manufacturing plant encounters the following during a controlled failover drill: A FortiGate SD-WAN policy sends a critical internal database flow into a FortiSASE Internet security tunnel rather than the private data-center overlay. Which action most directly restores the approved security outcome?

  1. Configure the supported FortiGate-to-FortiSASE service connectivity and correct SD-WAN steering for those source networks.
  2. Configure the supported site identity, subnet or gateway attribution in the integration and analytics setup.
  3. Separate private application destinations from cloud-Internet inspection criteria in SD-WAN rules and routes.
  4. Narrow the local direct-Internet exception and require approved source traffic to use the cloud-inspected route.

Explanation

Correct Answer

C:

Separate private application destinations from cloud-Internet inspection criteria in SD-WAN rules and routes. This is the most direct response to the stated incident: 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 technical mechanism is: Broad cloud steering rules can capture private traffic outside their intended security architecture. Confirmation requires: Private database sessions traverse their approved internal overlay and Internet browsing follows FortiSASE.

Incorrect Answers

A:

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: Broad cloud steering rules can capture private traffic outside their intended security architecture.

B:

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: Broad cloud steering rules can capture private traffic outside their intended security architecture.

D:

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: Broad cloud steering rules can capture private traffic outside their intended security architecture.

Question 842

An operations review at a manufacturing plant has corrected: A FortiGate SD-WAN policy sends a critical internal database flow into a FortiSASE Internet security tunnel rather than the private data-center overlay. Which observation specifically confirms success?

  1. A test event identifies the originating branch and associated user or network context.
  2. An authenticated remote test user reaches only the approved private app through the supported service.
  3. The intended source flow matches a policy and exits through the eligible FortiSASE tunnel.
  4. Private database sessions traverse their approved internal overlay and Internet browsing follows FortiSASE.

Explanation

Correct Answer

D:

Private database sessions traverse their approved internal overlay and Internet browsing follows FortiSASE. This evidence directly tests the intended corrective action: Separate private application destinations from cloud-Internet inspection criteria in SD-WAN rules and routes. It confirms the failure mechanism—Broad cloud steering rules can capture private traffic outside their intended security architecture.—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—Separate private application destinations from cloud-Internet inspection criteria in SD-WAN rules and routes.—worked.

B:

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—Separate private application destinations from cloud-Internet inspection criteria in SD-WAN rules and routes.—worked.

C:

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—Separate private application destinations from cloud-Internet inspection criteria in SD-WAN rules and routes.—worked.

Question 843

At a manufacturing plant, investigators observe: A FortiGate SD-WAN policy sends a critical internal database flow into a FortiSASE Internet security tunnel rather than the private data-center overlay. Which underlying policy or system mechanism BEST explains this behavior?

  1. Broad cloud steering rules can capture private traffic outside their intended security architecture.
  2. Cloud-connected site identity and gateway association must be unique to the approved deployment context.
  3. Secure Internet Access and connectivity to private branch applications are distinct services.
  4. A tunnel interface is not a selectable SD-WAN service path until correctly included.

Explanation

Correct Answer

A:

Broad cloud steering rules can capture private traffic outside their intended security architecture. This explains why the reported condition occurs: 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 targeted correction is: Separate private application destinations from cloud-Internet inspection criteria in SD-WAN rules and routes.

Incorrect Answers

B:

Cloud-connected site identity and gateway association must be unique to the approved deployment context. This mechanism instead explains a separate problem: An engineer adds a third region to a managed SD-WAN-to-SASE topology but reuses another region's cloud gateway identifier, assigning traffic to the wrong tenant service. The current incident requires the more directly applicable cause stated by the correct option.

C:

Secure Internet Access and connectivity to private branch applications are distinct services. This mechanism instead explains a separate problem: A company assumes remote FortiClient users can reach branch-only internal apps through the same secure Internet profile without configuring supported private application connectivity. The current incident requires the more directly applicable cause stated by the correct option.

D:

A tunnel interface is not a selectable SD-WAN service path until correctly included. This mechanism instead explains a separate problem: An SD-WAN rule sends traffic toward a FortiSASE tunnel but the tunnel is not part of the configured overlay SD-WAN zone. The current incident requires the more directly applicable cause stated by the correct option.

Question 844

An operations group at a manufacturing plant resolved: A FortiGate SD-WAN policy sends a critical internal database flow into a FortiSASE Internet security tunnel rather than the private data-center overlay. Which ongoing safeguard should become part of its change process?

  1. Use end-to-end SASE gateway probes for cloud tunnel resiliency decisions.
  2. Test negative private destination cases when expanding SASE branch redirection.
  3. Rehearse proposal changes with both FortiGate and cloud connection owners.
  4. Test round-trip flows and route symmetry for each branch-to-SASE network range.

Explanation

Correct Answer

B:

Test negative private destination cases when expanding SASE branch redirection. This control reduces recurrence of the documented mechanism: Broad cloud steering rules can capture private traffic outside their intended security architecture. It creates a repeatable check around the needed response: Separate private application destinations from cloud-Internet inspection criteria in SD-WAN rules and routes.

Incorrect Answers

A:

Use end-to-end SASE gateway probes for cloud tunnel resiliency decisions. That safeguard addresses another potential failure: A new SASE tunnel is established over one ISP, but FortiGate monitoring treats its health as equivalent to the underlying Internet link and fails to detect cloud-gateway reachability loss. It is not the most targeted recurring control for the described cause: Broad cloud steering rules can capture private traffic outside their intended security architecture.

C:

Rehearse proposal changes with both FortiGate and cloud connection owners. That safeguard addresses another potential failure: A FortiGate tunnel to the cloud uses an IPsec proposal no longer accepted after a security baseline update, so branch SASE connectivity drops. It is not the most targeted recurring control for the described cause: Broad cloud steering rules can capture private traffic outside their intended security architecture.

D:

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: Broad cloud steering rules can capture private traffic outside their intended security architecture.

Question 845

At a corporate headquarters, a security analyst is reviewing this failure during a configuration rollout: 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. What is the MOST appropriate FIRST corrective step?

  1. Associate the rule with the correct current SLA target and validate all dependent references.
  2. Set a valid supported probe source address or appropriate interface binding for that member.
  3. Correct the jitter SLA target for the application and link it to the appropriate SD-WAN rule.
  4. Use supported active health checks for pre-traffic baselining or observe passive measurements once eligible sessions exist.

Explanation

Correct Answer

D:

Use supported active health checks for pre-traffic baselining or observe passive measurements once eligible sessions exist. This is the most direct response to the stated incident: 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 technical mechanism is: Passive health observations require real sessions to supply path telemetry. Confirmation requires: The expected active probe values or passive session-based measurements appear under the selected mode.

Incorrect Answers

A:

Associate the rule with the correct current SLA target and validate all dependent references. That could address a different issue in the same blueprint area: An SD-WAN rule uses a performance SLA name that was replaced during template migration, so it never sees the new health measurements. It does not directly correct the given incident, whose decisive mechanism is: Passive health observations require real sessions to supply path telemetry.

B:

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: Passive health observations require real sessions to supply path telemetry.

C:

Correct the jitter SLA target for the application and link it to the appropriate SD-WAN rule. That could address a different issue in the same blueprint area: A voice quality rule uses a jitter maximum far above business tolerance so choppy calls continue on a variable-delay ISP. It does not directly correct the given incident, whose decisive mechanism is: Passive health observations require real sessions to supply path telemetry.

Question 846

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

  1. The expected active probe values or passive session-based measurements appear under the selected mode.
  2. During a controlled borderline-quality test link status does not flap excessively, but major failures still trigger action.
  3. A controlled upstream failure changes SLA health even while physical carrier stays up.
  4. The rule diagnostic displays the new SLA ID and responsive member eligibility.

Explanation

Correct Answer

A:

The expected active probe values or passive session-based measurements appear under the selected mode. This evidence directly tests the intended corrective action: Use supported active health checks for pre-traffic baselining or observe passive measurements once eligible sessions exist. It confirms the failure mechanism—Passive health observations require real sessions to supply path telemetry.—has been addressed in the actual affected flow.

Incorrect Answers

B:

During a controlled borderline-quality test link status does not flap excessively, but major failures still trigger action. This would verify resolution of a different case: A branch SLA oscillates between healthy and failed every few seconds because recovery thresholds are too sensitive near its jitter boundary. It does not show that the reported issue was fixed or that its intended action—Use supported active health checks for pre-traffic baselining or observe passive measurements once eligible sessions exist.—worked.

C:

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—Use supported active health checks for pre-traffic baselining or observe passive measurements once eligible sessions exist.—worked.

D:

The rule diagnostic displays the new SLA ID and responsive member eligibility. This would verify resolution of a different case: An SD-WAN rule uses a performance SLA name that was replaced during template migration, so it never sees the new health measurements. It does not show that the reported issue was fixed or that its intended action—Use supported active health checks for pre-traffic baselining or observe passive measurements once eligible sessions exist.—worked.

Question 847

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

  1. A successful transport connection may not represent usable application response.
  2. Passive health observations require real sessions to supply path telemetry.
  3. A blocked synthetic probe may cause false member failure separate from ordinary sessions.
  4. Performance SLA eligibility depends on which member interfaces are actually monitored.

Explanation

Correct Answer

B:

Passive health observations require real sessions to supply path telemetry. This explains why the reported condition occurs: 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 targeted correction is: Use supported active health checks for pre-traffic baselining or observe passive measurements once eligible sessions exist.

Incorrect Answers

A:

A successful transport connection may not represent usable application response. This mechanism instead explains a separate problem: An SLA probes only TCP handshake reachability for a collaboration SaaS even though user complaints concern heavy application-layer response times. The current incident requires the more directly applicable cause stated by the correct option.

C:

A blocked synthetic probe may cause false member failure separate from ordinary sessions. This mechanism instead explains a separate problem: A branch's SLA probe targets are blocked by an upstream provider ACL, yet employees can reach normal applications without difficulty. The current incident requires the more directly applicable cause stated by the correct option.

D:

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

Question 848

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

  1. Teach operators to correlate SLA state with the actual service-rule selection result.
  2. Include representative distant probes, not just carrier state, for critical services.
  3. Document active-versus-passive measurement prerequisites in link acceptance procedures.
  4. Create service-specific health-check targets for materially different WAN paths.

Explanation

Correct Answer

C:

Document active-versus-passive measurement prerequisites in link acceptance procedures. This control reduces recurrence of the documented mechanism: Passive health observations require real sessions to supply path telemetry. It creates a repeatable check around the needed response: Use supported active health checks for pre-traffic baselining or observe passive measurements once eligible sessions exist.

Incorrect Answers

A:

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: Passive health observations require real sessions to supply path telemetry.

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: Passive health observations require real sessions to supply path telemetry.

D:

Create service-specific health-check targets for materially different WAN paths. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Passive health observations require real sessions to supply path telemetry.

Question 849

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

  1. Create an appropriate service-relevant health monitor for the cloud path and associate it with steering decisions.
  2. Configure the appropriate FortiSASE private access or supported site-connected application path and authorize the application.
  3. Configure the supported site identity, subnet or gateway attribution in the integration and analytics setup.
  4. Add the approved branch prefix and route or policy association to the supported integration.

Explanation

Correct Answer

A:

Create an appropriate service-relevant health monitor for the cloud path and associate it with steering decisions. This is the most direct response to the stated incident: 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. The technical mechanism is: Carrier link health and cloud security gateway availability are distinct signals. Confirmation requires: The cloud-path SLA fails on gateway outage while the physical ISP can remain up.

Incorrect Answers

B:

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: Carrier link health and cloud security gateway availability are distinct signals.

C:

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: Carrier link health and cloud security gateway availability are distinct signals.

D:

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: Carrier link health and cloud security gateway availability are distinct signals.

Question 850

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

  1. The same restricted test category receives the required action across both protected access modes.
  2. The cloud-path SLA fails on gateway outage while the physical ISP can remain up.
  3. A protected test subnet cannot bypass FortiSASE while documented exceptions function.
  4. The authenticated tunnel reestablishes and test user sessions appear in cloud inspection logs.

Explanation

Correct Answer

B:

The cloud-path SLA fails on gateway outage while the physical ISP can remain up. This evidence directly tests the intended corrective action: Create an appropriate service-relevant health monitor for the cloud path and associate it with steering decisions. It confirms the failure mechanism—Carrier link health and cloud security gateway availability are distinct signals.—has been addressed in the actual affected flow.

Incorrect Answers

A:

The same restricted test category receives the required action across both protected access modes. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Create an appropriate service-relevant health monitor for the cloud path and associate it with steering decisions.—worked.

C:

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—Create an appropriate service-relevant health monitor for the cloud path and associate it with steering decisions.—worked.

D:

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—Create an appropriate service-relevant health monitor for the cloud path and associate it with steering decisions.—worked.

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