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 83

Question 820

A risk review at a financial services branch focuses on preventing this issue again: An engineer measures only last-mile interface status to declare a partner API path healthy, overlooking repeated upstream packet drops. Which recurring control is most suitable?

  1. Review SLA values using measured voice quality and contractual objectives.
  2. Test no-member-meets-SLA conditions rather than assuming automatic dropping or universal failover.
  3. Validate health-detection delay against payment transaction recovery objectives.
  4. Include representative distant probes, not just carrier state, for critical services.

Explanation

Correct Answer

D:

Include representative distant probes, not just carrier state, for critical services. This control reduces recurrence of the documented mechanism: Layer 1 connectivity cannot reveal upstream reachability or path-quality failures. It creates a repeatable check around the needed response: Use a performance SLA that probes an appropriate end-to-end service path beyond the local link.

Incorrect Answers

A:

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: Layer 1 connectivity cannot reveal upstream reachability or path-quality failures.

B:

Test no-member-meets-SLA conditions rather than assuming automatic dropping or universal failover. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Layer 1 connectivity cannot reveal upstream reachability or path-quality failures.

C:

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: Layer 1 connectivity cannot reveal upstream reachability or path-quality failures.

Question 821

During a production service incident, an administrator reports at a regional data center: A preferred WAN becomes unhealthy and is withdrawn from service, but its route remains installed due to an incorrect health state-action setting. What should the team change or investigate FIRST?

  1. Define the appropriate scoped SD-WAN service rule to enforce provider preference over equal-cost eligible routes.
  2. Configure supported SLA member state or route-removal behavior to match documented failover policy.
  3. Add the correct private prefix route toward the approved SD-WAN overlay zone or tunnel.
  4. Add a narrowly scoped firewall permit for the partner application and correct SD-WAN destination zone.

Explanation

Correct Answer

B:

Configure supported SLA member state or route-removal behavior to match documented failover policy. This is the most direct response to the stated incident: A preferred WAN becomes unhealthy and is withdrawn from service, but its route remains installed due to an incorrect health state-action setting. The technical mechanism is: Health-check measurements must be linked to route/member eligibility actions to change forwarding. Confirmation requires: Failure probes trigger the expected routing/member eligibility change and traffic uses an alternate path.

Incorrect Answers

A:

Define the appropriate scoped SD-WAN service rule to enforce provider preference over equal-cost eligible routes. That could address a different issue in the same blueprint area: A device has two equal-cost underlay routes but an application must use one provider for compliance while SD-WAN service matching is absent. It does not directly correct the given incident, whose decisive mechanism is: Health-check measurements must be linked to route/member eligibility actions to change forwarding.

C:

Add the correct private prefix route toward the approved SD-WAN overlay zone or tunnel. That could address a different issue in the same blueprint area: A branch firewall policy allows corporate traffic and an SD-WAN service is configured, but the route table lacks a prefix for the data-center network. It does not directly correct the given incident, whose decisive mechanism is: Health-check measurements must be linked to route/member eligibility actions to change forwarding.

D:

Add a narrowly scoped firewall permit for the partner application and correct SD-WAN destination zone. That could address a different issue in the same blueprint area: An engineer confuses SD-WAN rules with firewall security policies and creates only an SD-WAN service for a new partner app, which remains denied. It does not directly correct the given incident, whose decisive mechanism is: Health-check measurements must be linked to route/member eligibility actions to change forwarding.

Question 822

Following remediation at a regional data center, engineers revisit: A preferred WAN becomes unhealthy and is withdrawn from service, but its route remains installed due to an incorrect health state-action setting. Which observation would BEST prove the specific issue is resolved?

  1. Routing diagnostics show an eligible default path and the allowed application completes.
  2. Route lookup for the specific host now uses the intended overlay path.
  3. Failure probes trigger the expected routing/member eligibility change and traffic uses an alternate path.
  4. A route lookup resolves the data-center prefix and a controlled session completes through the overlay.

Explanation

Correct Answer

C:

Failure probes trigger the expected routing/member eligibility change and traffic uses an alternate path. This evidence directly tests the intended corrective action: Configure supported SLA member state or route-removal behavior to match documented failover policy. It confirms the failure mechanism—Health-check measurements must be linked to route/member eligibility actions to change forwarding.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Routing diagnostics show an eligible default path and the allowed application completes. This would verify resolution of a different case: A FortiGate Internet flow matches an expected SD-WAN rule but outgoing packets have no policy-approved route because the zone default route was deleted by a script. It does not show that the reported issue was fixed or that its intended action—Configure supported SLA member state or route-removal behavior to match documented failover policy.—worked.

B:

Route lookup for the specific host now uses the intended overlay path. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Configure supported SLA member state or route-removal behavior to match documented failover policy.—worked.

D:

A route lookup resolves the data-center prefix and a controlled session completes through the overlay. This would verify resolution of a different case: A branch firewall policy allows corporate traffic and an SD-WAN service is configured, but the route table lacks a prefix for the data-center network. It does not show that the reported issue was fixed or that its intended action—Configure supported SLA member state or route-removal behavior to match documented failover policy.—worked.

Question 823

During a production service incident, this condition is reported: A preferred WAN becomes unhealthy and is withdrawn from service, but its route remains installed due to an incorrect health state-action setting. Which technical explanation MOST directly accounts for the failure?

  1. Policy routing can supersede expected steering under the platform's route decision order.
  2. Incorrect return routing can interrupt sessions even when Internet SD-WAN egress is correct.
  3. The tunnel peer public endpoint and private protected subnet are different routing destinations.
  4. Health-check measurements must be linked to route/member eligibility actions to change forwarding.

Explanation

Correct Answer

D:

Health-check measurements must be linked to route/member eligibility actions to change forwarding. This explains why the reported condition occurs: A preferred WAN becomes unhealthy and is withdrawn from service, but its route remains installed due to an incorrect health state-action setting. The targeted correction is: Configure supported SLA member state or route-removal behavior to match documented failover policy.

Incorrect Answers

A:

Policy routing can supersede expected steering under the platform's route decision order. This mechanism instead explains a separate problem: Traffic matching a local policy route is forced toward an outdated VPN tunnel instead of following the updated SD-WAN rule. The current incident requires the more directly applicable cause stated by the correct option.

B:

Incorrect return routing can interrupt sessions even when Internet SD-WAN egress is correct. This mechanism instead explains a separate problem: A FortiGate forwards web traffic via DIA but its route back to an internal server uses the wrong LAN interface after a segmentation project. The current incident requires the more directly applicable cause stated by the correct option.

C:

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 824

During a post-incident review at a regional data center, the original problem was: A preferred WAN becomes unhealthy and is withdrawn from service, but its route remains installed due to an incorrect health state-action setting. Which preventive practice most directly addresses its cause?

  1. Test failure-state route updates under controlled link outages.
  2. Document and test local-out route policy for DNS, NTP, telemetry, and syslog separately.
  3. Require matched firewall rule plus route and SD-WAN rule evidence for application go-live.
  4. Verify destination and reverse-path routing whenever moving internal VLANs.

Explanation

Correct Answer

A:

Test failure-state route updates under controlled link outages. This control reduces recurrence of the documented mechanism: Health-check measurements must be linked to route/member eligibility actions to change forwarding. It creates a repeatable check around the needed response: Configure supported SLA member state or route-removal behavior to match documented failover policy.

Incorrect Answers

B:

Document and test local-out route policy for DNS, NTP, telemetry, and syslog separately. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Health-check measurements must be linked to route/member eligibility actions to change forwarding.

C:

Require matched firewall rule plus route and SD-WAN rule evidence for application go-live. That safeguard addresses another potential failure: An engineer confuses SD-WAN rules with firewall security policies and creates only an SD-WAN service for a new partner app, which remains denied. It is not the most targeted recurring control for the described cause: Health-check measurements must be linked to route/member eligibility actions to change forwarding.

D:

Verify destination and reverse-path routing whenever moving internal VLANs. That safeguard addresses another potential failure: A FortiGate forwards web traffic via DIA but its route back to an internal server uses the wrong LAN interface after a segmentation project. It is not the most targeted recurring control for the described cause: Health-check measurements must be linked to route/member eligibility actions to change forwarding.

Question 825

A firewall operations team at a university network encounters the following during a predeployment acceptance test: A new FortiSASE tunnel uses the branch's obsolete public IP as its remote peer after an ISP replacement, leaving site traffic uninspected. Which action most directly restores the approved security outcome?

  1. Configure a supported redundant PoP or cloud tunnel design and eligible SD-WAN failover policy.
  2. Create an appropriate service-relevant health monitor for the cloud path and associate it with steering decisions.
  3. Update the supported peer settings or cloud integration identity to the current public endpoint.
  4. Separate private application destinations from cloud-Internet inspection criteria in SD-WAN rules and routes.

Explanation

Correct Answer

C:

Update the supported peer settings or cloud integration identity to the current public endpoint. This is the most direct response to the stated incident: A new FortiSASE tunnel uses the branch's obsolete public IP as its remote peer after an ISP replacement, leaving site traffic uninspected. The technical mechanism is: Cloud tunnel establishment can depend on correct peer address or identity settings. Confirmation requires: The authenticated tunnel reestablishes and test user sessions appear in cloud inspection logs.

Incorrect Answers

A:

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

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: Cloud tunnel establishment can depend on correct peer address or identity settings.

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: Cloud tunnel establishment can depend on correct peer address or identity settings.

Question 826

An operations review at a university network has corrected: A new FortiSASE tunnel uses the branch's obsolete public IP as its remote peer after an ISP replacement, leaving site traffic uninspected. Which observation specifically confirms success?

  1. Captured flows show response packets returning to the source subnet across the service connection.
  2. The intended source flow matches a policy and exits through the eligible FortiSASE tunnel.
  3. A controlled primary service-path interruption recovers via the approved backup connection.
  4. The authenticated tunnel reestablishes and test user sessions appear in cloud inspection logs.

Explanation

Correct Answer

D:

The authenticated tunnel reestablishes and test user sessions appear in cloud inspection logs. This evidence directly tests the intended corrective action: Update the supported peer settings or cloud integration identity to the current public endpoint. It confirms the failure mechanism—Cloud tunnel establishment can depend on correct peer address or identity settings.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Update the supported peer settings or cloud integration identity to the current public endpoint.—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—Update the supported peer settings or cloud integration identity to the current public endpoint.—worked.

C:

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—Update the supported peer settings or cloud integration identity to the current public endpoint.—worked.

Question 827

At a university network, investigators observe: A new FortiSASE tunnel uses the branch's obsolete public IP as its remote peer after an ISP replacement, leaving site traffic uninspected. Which underlying policy or system mechanism BEST explains this behavior?

  1. Cloud tunnel establishment can depend on correct peer address or identity settings.
  2. DNS reachability is a separate dependency from successful data-tunnel connectivity.
  3. A surviving broad local allow can defeat intended cloud inspection routing.
  4. Different traffic entry points can apply different profiles without policy harmonization.

Explanation

Correct Answer

A:

Cloud tunnel establishment can depend on correct peer address or identity settings. This explains why the reported condition occurs: A new FortiSASE tunnel uses the branch's obsolete public IP as its remote peer after an ISP replacement, leaving site traffic uninspected. The targeted correction is: Update the supported peer settings or cloud integration identity to the current public endpoint.

Incorrect Answers

B:

DNS reachability is a separate dependency from successful data-tunnel connectivity. This mechanism instead explains a separate problem: An engineer connects a branch to cloud inspection but forgets to route internal DNS service requests appropriately, causing only hostname-based access to fail. The current incident requires the more directly applicable cause stated by the correct option.

C:

A surviving broad local allow can defeat intended cloud inspection routing. This mechanism instead explains a separate problem: An administrator activates a branch-to-SASE tunnel but leaves a broad local firewall bypass permitting protected subnets to egress directly. The current incident requires the more directly applicable cause stated by the correct option.

D:

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.

Question 828

An operations group at a university network resolved: A new FortiSASE tunnel uses the branch's obsolete public IP as its remote peer after an ISP replacement, leaving site traffic uninspected. Which ongoing safeguard should become part of its change process?

  1. Reconcile subnet inventory and permitted cloud-network policy after VLAN additions.
  2. Coordinate ISP endpoint changes with FortiSASE tunnel configuration owners.
  3. Use end-to-end SASE gateway probes for cloud tunnel resiliency decisions.
  4. Validate cloud service egress and inspection logging during every branch integration.

Explanation

Correct Answer

B:

Coordinate ISP endpoint changes with FortiSASE tunnel configuration owners. This control reduces recurrence of the documented mechanism: Cloud tunnel establishment can depend on correct peer address or identity settings. It creates a repeatable check around the needed response: Update the supported peer settings or cloud integration identity to the current public endpoint.

Incorrect Answers

A:

Reconcile subnet inventory and permitted cloud-network policy after VLAN additions. That safeguard addresses another potential failure: A FortiGate connects to a FortiSASE PoP but its branch LAN subnet is missing from the cloud's permitted network or route configuration. It is not the most targeted recurring control for the described cause: Cloud tunnel establishment can depend on correct peer address or identity settings.

C:

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: Cloud tunnel establishment can depend on correct peer address or identity settings.

D:

Validate cloud service egress and inspection logging during every branch integration. That safeguard addresses another potential failure: A branch sends protected Internet traffic directly to an ISP even though architecture requires FortiSASE cloud inspection for specified user subnets. It is not the most targeted recurring control for the described cause: Cloud tunnel establishment can depend on correct peer address or identity settings.

Question 829

At a hospital campus, a security analyst is reviewing this failure during a planned policy migration: An SLA uses a probe interval too sparse to detect outages quickly enough for a monitored payment application. What is the MOST appropriate FIRST corrective step?

  1. Set a valid supported probe source address or appropriate interface binding for that member.
  2. Include both intended members in the health-check configuration and verify probe state per link.
  3. Select an appropriate supported HTTP or application-relevant probe target and measure meaningful response behavior.
  4. Tune supported probe interval and failure thresholds to the approved detection goal without excessive probe traffic.

Explanation

Correct Answer

D:

Tune supported probe interval and failure thresholds to the approved detection goal without excessive probe traffic. This is the most direct response to the stated incident: An SLA uses a probe interval too sparse to detect outages quickly enough for a monitored payment application. The technical mechanism is: Probe cadence and failure count control how quickly availability degradation is detected. Confirmation requires: A simulated outage triggers a measured member health state change inside the required window.

Incorrect Answers

A:

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: Probe cadence and failure count control how quickly availability degradation is detected.

B:

Include both intended members in the health-check configuration and verify probe state per link. That could address a different issue in the same blueprint area: An engineer creates a performance SLA but does not associate the backup member with its health-check member list, leaving the backup unmonitored. It does not directly correct the given incident, whose decisive mechanism is: Probe cadence and failure count control how quickly availability degradation is detected.

C:

Select an appropriate supported HTTP or application-relevant probe target and measure meaningful response behavior. That could address a different issue in the same blueprint area: An SLA probes only TCP handshake reachability for a collaboration SaaS even though user complaints concern heavy application-layer response times. It does not directly correct the given incident, whose decisive mechanism is: Probe cadence and failure count control how quickly availability degradation is detected.

Question 830

During follow-up testing at a hospital campus, the original fault was: An SLA uses a probe interval too sparse to detect outages quickly enough for a monitored payment application. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. A simulated outage triggers a measured member health state change inside the required window.
  2. The probe succeeds over the affected member while application policy stays appropriately restricted.
  3. The health-check target resolves through the intended path and member state reflects real connectivity.
  4. Health-check output lists both members with usable measurements and state changes.

Explanation

Correct Answer

A:

A simulated outage triggers a measured member health state change inside the required window. This evidence directly tests the intended corrective action: Tune supported probe interval and failure thresholds to the approved detection goal without excessive probe traffic. It confirms the failure mechanism—Probe cadence and failure count control how quickly availability degradation is detected.—has been addressed in the actual affected flow.

Incorrect Answers

B:

The probe succeeds over the affected member while application policy stays appropriately restricted. This would verify resolution of a different case: A branch's SLA probe targets are blocked by an upstream provider ACL, yet employees can reach normal applications without difficulty. It does not show that the reported issue was fixed or that its intended action—Tune supported probe interval and failure thresholds to the approved detection goal without excessive probe traffic.—worked.

C:

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—Tune supported probe interval and failure thresholds to the approved detection goal without excessive probe traffic.—worked.

D:

Health-check output lists both members with usable measurements and state changes. This would verify resolution of a different case: An engineer creates a performance SLA but does not associate the backup member with its health-check member list, leaving the backup unmonitored. It does not show that the reported issue was fixed or that its intended action—Tune supported probe interval and failure thresholds to the approved detection goal without excessive probe traffic.—worked.

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