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 90

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.

Question 891

At a manufacturing plant, investigators observe: 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 underlying policy or system mechanism BEST explains this behavior?

  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. A surviving broad local allow can defeat intended cloud inspection routing.
  4. Carrier link health and cloud security gateway availability are distinct signals.

Explanation

Correct Answer

A:

Multiple underlay members do not automatically make every overlay endpoint path-independent. This explains why the reported condition occurs: 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 targeted correction is: Make the supported tunnel endpoint or SD-WAN integration resilient across the approved ISP paths.

Incorrect Answers

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.

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:

Carrier link health and cloud security gateway availability are distinct signals. This mechanism instead explains a separate problem: 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 current incident requires the more directly applicable cause stated by the correct option.

Question 892

An operations group at a manufacturing plant resolved: 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 ongoing safeguard should become part of its change process?

  1. Test round-trip flows and route symmetry for each branch-to-SASE network range.
  2. Test cloud tunnel initiation and rebinding under each ISP failure mode.
  3. Use end-to-end SASE gateway probes for cloud tunnel resiliency decisions.
  4. Review local and FortiSASE inspection baselines together before adding branches.

Explanation

Correct Answer

B:

Test cloud tunnel initiation and rebinding under each ISP failure mode. This control reduces recurrence of the documented mechanism: Multiple underlay members do not automatically make every overlay endpoint path-independent. It creates a repeatable check around the needed response: Make the supported tunnel endpoint or SD-WAN integration resilient across the approved ISP paths.

Incorrect Answers

A:

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: Multiple underlay members do not automatically make every overlay endpoint path-independent.

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: Multiple underlay members do not automatically make every overlay endpoint path-independent.

D:

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: Multiple underlay members do not automatically make every overlay endpoint path-independent.

Question 893

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

  1. Use supported active health checks for pre-traffic baselining or observe passive measurements once eligible sessions exist.
  2. Include both intended members in the health-check configuration and verify probe state per link.
  3. Correct the jitter SLA target for the application and link it to the appropriate SD-WAN rule.
  4. Restore permitted local DNS resolution for the SLA server or use a validated reachable monitor address.

Explanation

Correct Answer

D:

Restore permitted local DNS resolution for the SLA server or use a validated reachable monitor address. This is the most direct response to the stated incident: 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. The technical mechanism is: Hostname-based probes depend on working device name resolution before quality can be measured. Confirmation requires: The health-check target resolves through the intended path and member state reflects real connectivity.

Incorrect Answers

A:

Use supported active health checks for pre-traffic baselining or observe passive measurements once eligible sessions exist. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Hostname-based probes depend on working device name resolution before quality can be measured.

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: Hostname-based probes depend on working device name resolution before quality can be measured.

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: Hostname-based probes depend on working device name resolution before quality can be measured.

Question 894

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

  1. The health-check target resolves through the intended path and member state reflects real connectivity.
  2. A simulated outage triggers a measured member health state change inside the required window.
  3. Health-check output lists both members with usable measurements and state changes.
  4. The SLA measurement indicates degraded application reachability that a bare TCP handshake missed.

Explanation

Correct Answer

A:

The health-check target resolves through the intended path and member state reflects real connectivity. This evidence directly tests the intended corrective action: Restore permitted local DNS resolution for the SLA server or use a validated reachable monitor address. It confirms the failure mechanism—Hostname-based probes depend on working device name resolution before quality can be measured.—has been addressed in the actual affected flow.

Incorrect Answers

B:

A simulated outage triggers a measured member health state change inside the required window. This would verify resolution of a different case: An SLA uses a probe interval too sparse to detect outages quickly enough for a monitored payment application. It does not show that the reported issue was fixed or that its intended action—Restore permitted local DNS resolution for the SLA server or use a validated reachable monitor address.—worked.

C:

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—Restore permitted local DNS resolution for the SLA server or use a validated reachable monitor address.—worked.

D:

The SLA measurement indicates degraded application reachability that a bare TCP handshake missed. This would verify resolution of a different case: An SLA probes only TCP handshake reachability for a collaboration SaaS even though user complaints concern heavy application-layer response times. It does not show that the reported issue was fixed or that its intended action—Restore permitted local DNS resolution for the SLA server or use a validated reachable monitor address.—worked.

Question 895

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

  1. Over-sensitive probe state transitions cause steering instability around normal variation.
  2. Hostname-based probes depend on working device name resolution before quality can be measured.
  3. A blocked synthetic probe may cause false member failure separate from ordinary sessions.
  4. Passive health observations require real sessions to supply path telemetry.

Explanation

Correct Answer

B:

Hostname-based probes depend on working device name resolution before quality can be measured. This explains why the reported condition occurs: 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. The targeted correction is: Restore permitted local DNS resolution for the SLA server or use a validated reachable monitor address.

Incorrect Answers

A:

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 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:

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.

Question 896

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

  1. Tune monitoring hysteresis with real noisy-link data before production deployment.
  2. Verify probe source IP and provider return routes during link commissioning.
  3. Include DNS health in monitoring target configuration and outage triage.
  4. Teach operators to correlate SLA state with the actual service-rule selection result.

Explanation

Correct Answer

C:

Include DNS health in monitoring target configuration and outage triage. This control reduces recurrence of the documented mechanism: Hostname-based probes depend on working device name resolution before quality can be measured. It creates a repeatable check around the needed response: Restore permitted local DNS resolution for the SLA server or use a validated reachable monitor address.

Incorrect Answers

A:

Tune monitoring hysteresis with real noisy-link data before production deployment. That safeguard addresses another potential failure: A branch SLA oscillates between healthy and failed every few seconds because recovery thresholds are too sensitive near its jitter boundary. It is not the most targeted recurring control for the described cause: Hostname-based probes depend on working device name resolution before quality can be measured.

B:

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: Hostname-based probes depend on working device name resolution before quality can be measured.

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: Hostname-based probes depend on working device name resolution before quality can be measured.

Question 897

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

  1. Provision and reference the authorized regional cloud gateway or connection identifier for that site.
  2. Configure the supported site identity, subnet or gateway attribution in the integration and analytics setup.
  3. Correct the approved DNS resolution path and security policy for the cloud-inspected segment.
  4. Add the approved cloud-connected tunnel as a monitored SD-WAN member in the correct zone.

Explanation

Correct Answer

A:

Provision and reference the authorized regional cloud gateway or connection identifier for that site. This is the most direct response to the stated incident: 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 technical mechanism is: Cloud-connected site identity and gateway association must be unique to the approved deployment context. Confirmation requires: Traffic from the new region arrives under the intended tenant and security policy without cross-region leakage.

Incorrect Answers

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: Cloud-connected site identity and gateway association must be unique to the approved deployment context.

C:

Correct the approved DNS resolution path and security policy for the cloud-inspected segment. That could address a different issue in the same blueprint area: An engineer connects a branch to cloud inspection but forgets to route internal DNS service requests appropriately, causing only hostname-based access to fail. It does not directly correct the given incident, whose decisive mechanism is: Cloud-connected site identity and gateway association must be unique to the approved deployment context.

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: Cloud-connected site identity and gateway association must be unique to the approved deployment context.

Question 898

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

  1. The intended source flow matches a policy and exits through the eligible FortiSASE tunnel.
  2. Traffic from the new region arrives under the intended tenant and security policy without cross-region leakage.
  3. The same restricted test category receives the required action across both protected access modes.
  4. Users in the new subnet reach allowed destinations through the cloud security path.

Explanation

Correct Answer

B:

Traffic from the new region arrives under the intended tenant and security policy without cross-region leakage. This evidence directly tests the intended corrective action: Provision and reference the authorized regional cloud gateway or connection identifier for that site. It confirms the failure mechanism—Cloud-connected site identity and gateway association must be unique to the approved deployment context.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Provision and reference the authorized regional cloud gateway or connection identifier for that site.—worked.

C:

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—Provision and reference the authorized regional cloud gateway or connection identifier for that site.—worked.

D:

Users in the new subnet reach allowed destinations through the cloud security path. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Provision and reference the authorized regional cloud gateway or connection identifier for that site.—worked.

Question 899

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

  1. Carrier link health and cloud security gateway availability are distinct signals.
  2. Multiple underlay members do not automatically make every overlay endpoint path-independent.
  3. Cloud-connected site identity and gateway association must be unique to the approved deployment context.
  4. Cryptographic proposal mismatch can break overlay connectivity while underlay ISP remains healthy.

Explanation

Correct Answer

C:

Cloud-connected site identity and gateway association must be unique to the approved deployment context. This explains why the reported condition occurs: 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 targeted correction is: Provision and reference the authorized regional cloud gateway or connection identifier for that site.

Incorrect Answers

A:

Carrier link health and cloud security gateway availability are distinct signals. This mechanism instead explains a separate problem: 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 current incident requires the more directly applicable cause stated by the correct option.

B:

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.

D:

Cryptographic proposal mismatch can break overlay connectivity while underlay ISP remains healthy. This mechanism instead explains a separate problem: A FortiGate tunnel to the cloud uses an IPsec proposal no longer accepted after a security baseline update, so branch SASE connectivity drops. The current incident requires the more directly applicable cause stated by the correct option.

Question 900

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

  1. Coordinate ISP endpoint changes with FortiSASE tunnel configuration owners.
  2. Test private-app reachability and group authorization independently of Internet browsing.
  3. Audit tunnel member and zone membership after cloud-branch integration.
  4. Validate tenant, gateway and regional labels in every new SD-WAN/SASE connection.

Explanation

Correct Answer

D:

Validate tenant, gateway and regional labels in every new SD-WAN/SASE connection. This control reduces recurrence of the documented mechanism: Cloud-connected site identity and gateway association must be unique to the approved deployment context. It creates a repeatable check around the needed response: Provision and reference the authorized regional cloud gateway or connection identifier for that site.

Incorrect Answers

A:

Coordinate ISP endpoint changes with FortiSASE tunnel configuration owners. That safeguard addresses another potential failure: A new FortiSASE tunnel uses the branch's obsolete public IP as its remote peer after an ISP replacement, leaving site traffic uninspected. It is not the most targeted recurring control for the described cause: Cloud-connected site identity and gateway association must be unique to the approved deployment context.

B:

Test private-app reachability and group authorization independently of Internet browsing. That safeguard addresses another potential failure: A company assumes remote FortiClient users can reach branch-only internal apps through the same secure Internet profile without configuring supported private application connectivity. It is not the most targeted recurring control for the described cause: Cloud-connected site identity and gateway association must be unique to the approved deployment context.

C:

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: Cloud-connected site identity and gateway association must be unique to the approved deployment context.

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