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 77

Question 760

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

  1. Audit health-check member coverage during each circuit addition.
  2. Review SLA values using measured voice quality and contractual objectives.
  3. Verify probe source IP and provider return routes during link commissioning.
  4. Baseline latency distributions and application tolerances before setting targets.

Explanation

Correct Answer

A:

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

Incorrect Answers

B:

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

C:

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

D:

Baseline latency distributions and application tolerances before setting targets. That safeguard addresses another potential failure: A performance SLA is configured with a 5-ms latency threshold despite a normal 40-ms regional WAN path, excluding all members under healthy conditions. It is not the most targeted recurring control for the described cause: Performance SLA eligibility depends on which member interfaces are actually monitored.

Question 761

A firewall operations team at a service-provider edge encounters the following during a predeployment acceptance test: A BGP route to a private application is learned through both MPLS and Internet overlay with a preference that incorrectly favors the metered link. Which action most directly restores the approved security outcome?

  1. Add a narrowly scoped firewall permit for the partner application and correct SD-WAN destination zone.
  2. Correct the approved prefix advertisement or route filter on the relevant BGP peers.
  3. Adjust routing policy attributes or supported SD-WAN route preference according to the approved private-link design.
  4. Remove or update the conflicting policy route and re-evaluate the real session lookup order.

Explanation

Correct Answer

C:

Adjust routing policy attributes or supported SD-WAN route preference according to the approved private-link design. This is the most direct response to the stated incident: A BGP route to a private application is learned through both MPLS and Internet overlay with a preference that incorrectly favors the metered link. The technical mechanism is: Routing preference is determined by route-selection policies, not by the WAN link's price label. Confirmation requires: The selected private prefix route and forwarding member follow the preferred non-metered path when healthy.

Incorrect Answers

A:

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: Routing preference is determined by route-selection policies, not by the WAN link's price label.

B:

Correct the approved prefix advertisement or route filter on the relevant BGP peers. That could address a different issue in the same blueprint area: A branch uses BGP to advertise overlay prefixes but a filtered remote office subnet is missing from received routes. It does not directly correct the given incident, whose decisive mechanism is: Routing preference is determined by route-selection policies, not by the WAN link's price label.

D:

Remove or update the conflicting policy route and re-evaluate the real session lookup order. That could address a different issue in the same blueprint area: Traffic matching a local policy route is forced toward an outdated VPN tunnel instead of following the updated SD-WAN rule. It does not directly correct the given incident, whose decisive mechanism is: Routing preference is determined by route-selection policies, not by the WAN link's price label.

Question 762

An operations review at a service-provider edge has corrected: A BGP route to a private application is learned through both MPLS and Internet overlay with a preference that incorrectly favors the metered link. Which observation specifically confirms success?

  1. External test services observe a valid address for each ISP and responses return successfully.
  2. Private addresses use the overlay while Internet destinations use direct access.
  3. Routing diagnostics show an eligible default path and the allowed application completes.
  4. The selected private prefix route and forwarding member follow the preferred non-metered path when healthy.

Explanation

Correct Answer

D:

The selected private prefix route and forwarding member follow the preferred non-metered path when healthy. This evidence directly tests the intended corrective action: Adjust routing policy attributes or supported SD-WAN route preference according to the approved private-link design. It confirms the failure mechanism—Routing preference is determined by route-selection policies, not by the WAN link's price label.—has been addressed in the actual affected flow.

Incorrect Answers

A:

External test services observe a valid address for each ISP and responses return successfully. This would verify resolution of a different case: A source NAT policy translates a client to the primary ISP address even after SD-WAN routes traffic out through a backup provider, breaking return traffic. It does not show that the reported issue was fixed or that its intended action—Adjust routing policy attributes or supported SD-WAN route preference according to the approved private-link design.—worked.

B:

Private addresses use the overlay while Internet destinations use direct access. This would verify resolution of a different case: A branch adds a second SD-WAN zone with private overlay members but the site's route to RFC1918 destinations still points to the DIA zone. It does not show that the reported issue was fixed or that its intended action—Adjust routing policy attributes or supported SD-WAN route preference according to the approved private-link design.—worked.

C:

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—Adjust routing policy attributes or supported SD-WAN route preference according to the approved private-link design.—worked.

Question 763

At a service-provider edge, investigators observe: A BGP route to a private application is learned through both MPLS and Internet overlay with a preference that incorrectly favors the metered link. Which underlying policy or system mechanism BEST explains this behavior?

  1. Routing preference is determined by route-selection policies, not by the WAN link's price label.
  2. Longest-prefix routing can outweigh less-specific zone routes regardless of apparent preference.
  3. Tunnel establishment is not proof that remote routing tables know the branch source network.
  4. The tunnel peer public endpoint and private protected subnet are different routing destinations.

Explanation

Correct Answer

A:

Routing preference is determined by route-selection policies, not by the WAN link's price label. This explains why the reported condition occurs: A BGP route to a private application is learned through both MPLS and Internet overlay with a preference that incorrectly favors the metered link. The targeted correction is: Adjust routing policy attributes or supported SD-WAN route preference according to the approved private-link design.

Incorrect Answers

B:

Longest-prefix routing can outweigh less-specific zone routes regardless of apparent preference. This mechanism instead explains a separate problem: A new branch subnet has a longer specific static route pointing to an old MPLS path, overriding the intended broader overlay route. The current incident requires the more directly applicable cause stated by the correct option.

C:

Tunnel establishment is not proof that remote routing tables know the branch source network. This mechanism instead explains a separate problem: An IPsec tunnel is up and part of an SD-WAN zone but remote servers cannot reply because their route to the branch subnet is absent. The current incident requires the more directly applicable cause stated by the correct option.

D:

The tunnel peer public endpoint and private protected subnet are different routing destinations. This mechanism instead explains a separate problem: A tunnel interface is a zone member but its route uses the remote gateway's public IP instead of the private destination prefix, leaving internal apps unrouteable. The current incident requires the more directly applicable cause stated by the correct option.

Question 764

An operations group at a service-provider edge resolved: A BGP route to a private application is learned through both MPLS and Internet overlay with a preference that incorrectly favors the metered link. Which ongoing safeguard should become part of its change process?

  1. Add route-table verification to automated SD-WAN rule deployment pipelines.
  2. Document routing priorities for overlays with multiple learned next hops.
  3. Test advertised and accepted prefix lists across SD-WAN overlays after address expansion.
  4. Require matched firewall rule plus route and SD-WAN rule evidence for application go-live.

Explanation

Correct Answer

B:

Document routing priorities for overlays with multiple learned next hops. This control reduces recurrence of the documented mechanism: Routing preference is determined by route-selection policies, not by the WAN link's price label. It creates a repeatable check around the needed response: Adjust routing policy attributes or supported SD-WAN route preference according to the approved private-link design.

Incorrect Answers

A:

Add route-table verification to automated SD-WAN rule deployment pipelines. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Routing preference is determined by route-selection policies, not by the WAN link's price label.

C:

Test advertised and accepted prefix lists across SD-WAN overlays after address expansion. That safeguard addresses another potential failure: A branch uses BGP to advertise overlay prefixes but a filtered remote office subnet is missing from received routes. It is not the most targeted recurring control for the described cause: Routing preference is determined by route-selection policies, not by the WAN link's price label.

D:

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: Routing preference is determined by route-selection policies, not by the WAN link's price label.

Question 765

At a national SOC, a security analyst is reviewing this failure during a planned policy migration: A FortiGate connects to a FortiSASE PoP but its branch LAN subnet is missing from the cloud's permitted network or route configuration. What is the MOST appropriate FIRST corrective step?

  1. Create an appropriate service-relevant health monitor for the cloud path and associate it with steering decisions.
  2. Configure the supported site identity, subnet or gateway attribution in the integration and analytics setup.
  3. Narrow the local direct-Internet exception and require approved source traffic to use the cloud-inspected route.
  4. Add the approved branch prefix and route or policy association to the supported integration.

Explanation

Correct Answer

D:

Add the approved branch prefix and route or policy association to the supported integration. This is the most direct response to the stated incident: A FortiGate connects to a FortiSASE PoP but its branch LAN subnet is missing from the cloud's permitted network or route configuration. The technical mechanism is: Integrating a site tunnel does not automatically announce every protected branch subnet. Confirmation requires: Users in the new subnet reach allowed destinations through the cloud security path.

Incorrect Answers

A:

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: Integrating a site tunnel does not automatically announce every protected branch subnet.

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: Integrating a site tunnel does not automatically announce every protected branch subnet.

C:

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: Integrating a site tunnel does not automatically announce every protected branch subnet.

Question 766

During follow-up testing at a national SOC, the original fault was: A FortiGate connects to a FortiSASE PoP but its branch LAN subnet is missing from the cloud's permitted network or route configuration. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. Users in the new subnet reach allowed destinations through the cloud security path.
  2. A test event identifies the originating branch and associated user or network context.
  3. The tunnel negotiates successfully and permitted traffic resumes through cloud inspection.
  4. The cloud-path SLA fails on gateway outage while the physical ISP can remain up.

Explanation

Correct Answer

A:

Users in the new subnet reach allowed destinations through the cloud security path. This evidence directly tests the intended corrective action: Add the approved branch prefix and route or policy association to the supported integration. It confirms the failure mechanism—Integrating a site tunnel does not automatically announce every protected branch subnet.—has been addressed in the actual affected flow.

Incorrect Answers

B:

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—Add the approved branch prefix and route or policy association to the supported integration.—worked.

C:

The tunnel negotiates successfully and permitted traffic resumes through cloud inspection. This would verify resolution of a different case: A FortiGate tunnel to the cloud uses an IPsec proposal no longer accepted after a security baseline update, so branch SASE connectivity drops. It does not show that the reported issue was fixed or that its intended action—Add the approved branch prefix and route or policy association to the supported integration.—worked.

D:

The cloud-path SLA fails on gateway outage while the physical ISP can remain up. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Add the approved branch prefix and route or policy association to the supported integration.—worked.

Question 767

The incident investigation at a national SOC records: A FortiGate connects to a FortiSASE PoP but its branch LAN subnet is missing from the cloud's permitted network or route configuration. Which mechanism provides the strongest explanation?

  1. Cloud-connected site identity and gateway association must be unique to the approved deployment context.
  2. Integrating a site tunnel does not automatically announce every protected branch subnet.
  3. Local DIA alone does not pass branch traffic through the cloud security service.
  4. Successful outbound tunnel forwarding does not prove reverse routing is complete.

Explanation

Correct Answer

B:

Integrating a site tunnel does not automatically announce every protected branch subnet. This explains why the reported condition occurs: A FortiGate connects to a FortiSASE PoP but its branch LAN subnet is missing from the cloud's permitted network or route configuration. The targeted correction is: Add the approved branch prefix and route or policy association to the supported integration.

Incorrect Answers

A:

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:

Local DIA alone does not pass branch traffic through the cloud security service. This mechanism instead explains a separate problem: A branch sends protected Internet traffic directly to an ISP even though architecture requires FortiSASE cloud inspection for specified user subnets. The current incident requires the more directly applicable cause stated by the correct option.

D:

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.

Question 768

After a corrective change at a national SOC, the team documents: A FortiGate connects to a FortiSASE PoP but its branch LAN subnet is missing from the cloud's permitted network or route configuration. Which repeatable control BEST prevents a recurrence?

  1. Validate source-site labeling in analytics when onboarding each branch.
  2. Review local and FortiSASE inspection baselines together before adding branches.
  3. Reconcile subnet inventory and permitted cloud-network policy after VLAN additions.
  4. Review branch firewall and route bypass paths after integrating with FortiSASE.

Explanation

Correct Answer

C:

Reconcile subnet inventory and permitted cloud-network policy after VLAN additions. This control reduces recurrence of the documented mechanism: Integrating a site tunnel does not automatically announce every protected branch subnet. It creates a repeatable check around the needed response: Add the approved branch prefix and route or policy association to the supported integration.

Incorrect Answers

A:

Validate source-site labeling in analytics when onboarding each branch. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Integrating a site tunnel does not automatically announce every protected branch subnet.

B:

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: Integrating a site tunnel does not automatically announce every protected branch subnet.

D:

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: Integrating a site tunnel does not automatically announce every protected branch subnet.

Question 769

During a security audit at a financial services branch, analysts observe: A branch health-check probes a single maintenance-prone public host; host downtime incorrectly marks both independent ISPs failed. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Use a supported reliable probe strategy and alternate or representative targets that reduce single-endpoint bias.
  2. Associate the rule with the correct current SLA target and validate all dependent references.
  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

A:

Use a supported reliable probe strategy and alternate or representative targets that reduce single-endpoint bias. This is the most direct response to the stated incident: A branch health-check probes a single maintenance-prone public host; host downtime incorrectly marks both independent ISPs failed. The technical mechanism is: Probe destination failure is not proof of every WAN transport failure. Confirmation requires: Healthy ISP paths remain usable during an isolated public probe-target outage under the approved policy.

Incorrect Answers

B:

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: Probe destination failure is not proof of every WAN transport failure.

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 destination failure is not proof of every WAN transport failure.

D:

Tune supported probe interval and failure thresholds to the approved detection goal without excessive probe traffic. That could address a different issue in the same blueprint area: An SLA uses a probe interval too sparse to detect outages quickly enough for a monitored payment application. It does not directly correct the given incident, whose decisive mechanism is: Probe destination failure is not proof of every WAN transport failure.

Question 770

At a financial services branch, a test team is validating a change after this incident: A branch health-check probes a single maintenance-prone public host; host downtime incorrectly marks both independent ISPs failed. What evidence most directly verifies the intended outcome?

  1. The probe succeeds over the affected member while application policy stays appropriately restricted.
  2. Healthy ISP paths remain usable during an isolated public probe-target outage under the approved policy.
  3. Normal regional WAN latency passes the approved target, while genuinely poor paths still fail.
  4. Health-check output lists both members with usable measurements and state changes.

Explanation

Correct Answer

B:

Healthy ISP paths remain usable during an isolated public probe-target outage under the approved policy. This evidence directly tests the intended corrective action: Use a supported reliable probe strategy and alternate or representative targets that reduce single-endpoint bias. It confirms the failure mechanism—Probe destination failure is not proof of every WAN transport failure.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Use a supported reliable probe strategy and alternate or representative targets that reduce single-endpoint bias.—worked.

C:

Normal regional WAN latency passes the approved target, while genuinely poor paths still fail. This would verify resolution of a different case: A performance SLA is configured with a 5-ms latency threshold despite a normal 40-ms regional WAN path, excluding all members under healthy conditions. It does not show that the reported issue was fixed or that its intended action—Use a supported reliable probe strategy and alternate or representative targets that reduce single-endpoint bias.—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—Use a supported reliable probe strategy and alternate or representative targets that reduce single-endpoint bias.—worked.

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