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 65

Question 640

After a corrective change at a hospital campus, the team documents: A quarterly SASE adoption report counts all provisioned users as active remote users even though many have never authenticated. Which repeatable control BEST prevents a recurrence?

  1. Review custom report definitions after major SASE policy changes.
  2. Specify timestamps, timezone and cutoffs explicitly for cross-platform reports.
  3. Define active-user criteria and use them consistently in usage reporting.
  4. Require data source and inclusion criteria notes on every custom report.

Explanation

Correct Answer

C:

Define active-user criteria and use them consistently in usage reporting. This control reduces recurrence of the documented mechanism: Provisioned accounts and observed service usage are different measures. It creates a repeatable check around the needed response: Use successful session or login metrics rather than only licensed/provisioned identity counts for adoption.

Incorrect Answers

A:

Review custom report definitions after major SASE policy changes. That safeguard addresses another potential failure: A scheduled report continues showing outdated policy category names after a FortiSASE rule restructuring, confusing auditors despite accurate event counts. It is not the most targeted recurring control for the described cause: Provisioned accounts and observed service usage are different measures.

B:

Specify timestamps, timezone and cutoffs explicitly for cross-platform reports. That safeguard addresses another potential failure: An investigator generates a cloud report for a specific day but compares it with branch logs in another timezone, creating apparently inconsistent access counts. It is not the most targeted recurring control for the described cause: Provisioned accounts and observed service usage are different measures.

D:

Require data source and inclusion criteria notes on every custom report. That safeguard addresses another potential failure: An operator builds a custom report from a filtered set of denied sessions and presents it as total Internet traffic volume for management. It is not the most targeted recurring control for the described cause: Provisioned accounts and observed service usage are different measures.

Question 641

During a security audit at a retail network, analysts observe: Two ISP circuits share similar port labels and an engineer reverses wan1 and wan2 member metadata, sending regulated traffic to the wrong provider. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Correct the member interface-to-provider mapping and review the affected SD-WAN rule and zone constraints.
  2. Restore the backup member's correct next hop and confirm reachability independently.
  3. Update that member's gateway to the address supplied by the new CPE and verify routing.
  4. Update the supported IPsec peer configuration and confirm the tunnel member can carry authenticated traffic.

Explanation

Correct Answer

A:

Correct the member interface-to-provider mapping and review the affected SD-WAN rule and zone constraints. This is the most direct response to the stated incident: Two ISP circuits share similar port labels and an engineer reverses wan1 and wan2 member metadata, sending regulated traffic to the wrong provider. The technical mechanism is: Logical member identifiers must correspond to the actual provider circuits used in policy. Confirmation requires: A controlled regulated session exits through the contractually approved provider address.

Incorrect Answers

B:

Restore the backup member's correct next hop and confirm reachability independently. That could address a different issue in the same blueprint area: A branch moves its default route to the SD-WAN zone but removes the backup member's gateway, so the zone works only while the primary link is alive. It does not directly correct the given incident, whose decisive mechanism is: Logical member identifiers must correspond to the actual provider circuits used in policy.

C:

Update that member's gateway to the address supplied by the new CPE and verify routing. That could address a different issue in the same blueprint area: After replacing an ISP CPE, the old FortiGate member gateway remains configured and SLA probes fail despite the interface showing link up. It does not directly correct the given incident, whose decisive mechanism is: Logical member identifiers must correspond to the actual provider circuits used in policy.

D:

Update the supported IPsec peer configuration and confirm the tunnel member can carry authenticated traffic. That could address a different issue in the same blueprint area: A branch's overlay tunnel is administratively up but points to a remote peer address that changed during cloud migration, so private-app sessions time out. It does not directly correct the given incident, whose decisive mechanism is: Logical member identifiers must correspond to the actual provider circuits used in policy.

Question 642

At a retail network, a test team is validating a change after this incident: Two ISP circuits share similar port labels and an engineer reverses wan1 and wan2 member metadata, sending regulated traffic to the wrong provider. What evidence most directly verifies the intended outcome?

  1. Health probes and test sessions leave with the approved VLAN tag and reach the ISP gateway.
  2. A controlled regulated session exits through the contractually approved provider address.
  3. Business traffic follows the intended private zone and DIA traffic never selects MPLS accidentally.
  4. Only approved critical traffic uses the metered link under failover conditions.

Explanation

Correct Answer

B:

A controlled regulated session exits through the contractually approved provider address. This evidence directly tests the intended corrective action: Correct the member interface-to-provider mapping and review the affected SD-WAN rule and zone constraints. It confirms the failure mechanism—Logical member identifiers must correspond to the actual provider circuits used in policy.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Health probes and test sessions leave with the approved VLAN tag and reach the ISP gateway. This would verify resolution of a different case: A WAN port with a tagged provider VLAN is added to SD-WAN as the physical untagged port, so no valid IP traffic reaches the carrier. It does not show that the reported issue was fixed or that its intended action—Correct the member interface-to-provider mapping and review the affected SD-WAN rule and zone constraints.—worked.

C:

Business traffic follows the intended private zone and DIA traffic never selects MPLS accidentally. This would verify resolution of a different case: An engineer associates a backup MPLS tunnel with the Internet-DIA zone instead of the private overlay zone, exposing it to Internet traffic selection. It does not show that the reported issue was fixed or that its intended action—Correct the member interface-to-provider mapping and review the affected SD-WAN rule and zone constraints.—worked.

D:

Only approved critical traffic uses the metered link under failover conditions. This would verify resolution of a different case: Two Internet uplinks are grouped into one zone but the branch needs separate policy treatment for metered mobile connectivity during outages. It does not show that the reported issue was fixed or that its intended action—Correct the member interface-to-provider mapping and review the affected SD-WAN rule and zone constraints.—worked.

Question 643

A Fortinet administrator at a retail network is assessing: Two ISP circuits share similar port labels and an engineer reverses wan1 and wan2 member metadata, sending regulated traffic to the wrong provider. What is the most relevant root cause?

  1. Default zone assignment may conflict with deliberate security segmentation.
  2. Route next-hop zone references do not automatically follow every member migration.
  3. Logical member identifiers must correspond to the actual provider circuits used in policy.
  4. Referenced members can prevent safe physical-interface deletion or replacement.

Explanation

Correct Answer

C:

Logical member identifiers must correspond to the actual provider circuits used in policy. This explains why the reported condition occurs: Two ISP circuits share similar port labels and an engineer reverses wan1 and wan2 member metadata, sending regulated traffic to the wrong provider. The targeted correction is: Correct the member interface-to-provider mapping and review the affected SD-WAN rule and zone constraints.

Incorrect Answers

A:

Default zone assignment may conflict with deliberate security segmentation. This mechanism instead explains a separate problem: A new tunnel member is added under the default virtual-wan-link zone although the architecture requires region-specific security controls. The current incident requires the more directly applicable cause stated by the correct option.

B:

Route next-hop zone references do not automatically follow every member migration. This mechanism instead explains a separate problem: A fortigate WAN interface is moved between SD-WAN zones while a static route continues to point at its previous zone, leaving a private prefix unreachable. The current incident requires the more directly applicable cause stated by the correct option.

D:

Referenced members can prevent safe physical-interface deletion or replacement. This mechanism instead explains a separate problem: An administrator deletes a physical WAN interface that is still referenced by an active SD-WAN member, resulting in blocked change validation. The current incident requires the more directly applicable cause stated by the correct option.

Question 644

A risk review at a retail network focuses on preventing this issue again: Two ISP circuits share similar port labels and an engineer reverses wan1 and wan2 member metadata, sending regulated traffic to the wrong provider. Which recurring control is most suitable?

  1. Revalidate member gateway and reachability whenever upstream ISP equipment changes.
  2. Include provider-specific backup access devices in real path qualification tests.
  3. Reconcile zone routes whenever moving a member between SD-WAN groups.
  4. Record circuit ID and interface mapping and test egress identity after cabling work.

Explanation

Correct Answer

D:

Record circuit ID and interface mapping and test egress identity after cabling work. This control reduces recurrence of the documented mechanism: Logical member identifiers must correspond to the actual provider circuits used in policy. It creates a repeatable check around the needed response: Correct the member interface-to-provider mapping and review the affected SD-WAN rule and zone constraints.

Incorrect Answers

A:

Revalidate member gateway and reachability whenever upstream ISP equipment changes. That safeguard addresses another potential failure: After replacing an ISP CPE, the old FortiGate member gateway remains configured and SLA probes fail despite the interface showing link up. It is not the most targeted recurring control for the described cause: Logical member identifiers must correspond to the actual provider circuits used in policy.

B:

Include provider-specific backup access devices in real path qualification tests. That safeguard addresses another potential failure: The branch uses a cellular FortiExtender as a third path but engineers mistakenly treat the modem as a conventional Ethernet gateway without verifying supported interface details. It is not the most targeted recurring control for the described cause: Logical member identifiers must correspond to the actual provider circuits used in policy.

C:

Reconcile zone routes whenever moving a member between SD-WAN groups. That safeguard addresses another potential failure: A fortigate WAN interface is moved between SD-WAN zones while a static route continues to point at its previous zone, leaving a private prefix unreachable. It is not the most targeted recurring control for the described cause: Logical member identifiers must correspond to the actual provider circuits used in policy.

Question 645

During an incident triage, an administrator reports at a logistics office: A VPN overlay uses dynamic routing but an old static route for the same branch prefix takes precedence and sends traffic through an unreachable tunnel. What should the team change or investigate FIRST?

  1. Configure supported egress-aware source NAT for both provider paths and verify the selected member.
  2. Adjust competing static and dynamic route preference so the valid overlay next hop is selected.
  3. Review the local-out service routing and source-interface configuration for FortiGate logging independently of user traffic.
  4. Bind the intended gateway or route to the actual selected member interface as supported.

Explanation

Correct Answer

B:

Adjust competing static and dynamic route preference so the valid overlay next hop is selected. This is the most direct response to the stated incident: A VPN overlay uses dynamic routing but an old static route for the same branch prefix takes precedence and sends traffic through an unreachable tunnel. The technical mechanism is: Route administrative distance and priority can make stale static entries override learned paths. Confirmation requires: The active route resolves to the healthy tunnel and the remote branch is reachable.

Incorrect Answers

A:

Configure supported egress-aware source NAT for both provider paths and verify the selected member. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Route administrative distance and priority can make stale static entries override learned paths.

C:

Review the local-out service routing and source-interface configuration for FortiGate logging independently of user traffic. That could address a different issue in the same blueprint area: 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 does not directly correct the given incident, whose decisive mechanism is: Route administrative distance and priority can make stale static entries override learned paths.

D:

Bind the intended gateway or route to the actual selected member interface as supported. That could address a different issue in the same blueprint area: An SD-WAN member has a static route to a provider gateway on the wrong interface, so probes work on another link but traffic drops when it is selected. It does not directly correct the given incident, whose decisive mechanism is: Route administrative distance and priority can make stale static entries override learned paths.

Question 646

Following remediation at a logistics office, engineers revisit: A VPN overlay uses dynamic routing but an old static route for the same branch prefix takes precedence and sends traffic through an unreachable tunnel. Which observation would BEST prove the specific issue is resolved?

  1. The regulated application consistently leaves through the allowed member while ordinary traffic may use both.
  2. New Internet sessions use the SD-WAN zone and rule diagnostics show member selection.
  3. The active route resolves to the healthy tunnel and the remote branch is reachable.
  4. TCP handshakes complete in both directions and session debug shows a consistent path.

Explanation

Correct Answer

C:

The active route resolves to the healthy tunnel and the remote branch is reachable. This evidence directly tests the intended corrective action: Adjust competing static and dynamic route preference so the valid overlay next hop is selected. It confirms the failure mechanism—Route administrative distance and priority can make stale static entries override learned paths.—has been addressed in the actual affected flow.

Incorrect Answers

A:

The regulated application consistently leaves through the allowed member while ordinary traffic may use both. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Adjust competing static and dynamic route preference so the valid overlay next hop is selected.—worked.

B:

New Internet sessions use the SD-WAN zone and rule diagnostics show member selection. This would verify resolution of a different case: A default route to the ISP remains preferred over the SD-WAN zone after migration, causing most traffic to bypass SD-WAN rules. It does not show that the reported issue was fixed or that its intended action—Adjust competing static and dynamic route preference so the valid overlay next hop is selected.—worked.

D:

TCP handshakes complete in both directions and session debug shows a consistent path. This would verify resolution of a different case: 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 does not show that the reported issue was fixed or that its intended action—Adjust competing static and dynamic route preference so the valid overlay next hop is selected.—worked.

Question 647

During an incident triage, this condition is reported: A VPN overlay uses dynamic routing but an old static route for the same branch prefix takes precedence and sends traffic through an unreachable tunnel. Which technical explanation MOST directly accounts for the failure?

  1. SD-WAN route changes and source address translation must remain compatible across failover.
  2. A competing FIB route can redirect packets before expected SD-WAN forwarding decisions.
  3. Health-check measurements must be linked to route/member eligibility actions to change forwarding.
  4. Route administrative distance and priority can make stale static entries override learned paths.

Explanation

Correct Answer

D:

Route administrative distance and priority can make stale static entries override learned paths. This explains why the reported condition occurs: A VPN overlay uses dynamic routing but an old static route for the same branch prefix takes precedence and sends traffic through an unreachable tunnel. The targeted correction is: Adjust competing static and dynamic route preference so the valid overlay next hop is selected.

Incorrect Answers

A:

SD-WAN route changes and source address translation must remain compatible across failover. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

B:

A competing FIB route can redirect packets before expected SD-WAN forwarding decisions. This mechanism instead explains a separate problem: A default route to the ISP remains preferred over the SD-WAN zone after migration, causing most traffic to bypass SD-WAN rules. The current incident requires the more directly applicable cause stated by the correct option.

C:

Health-check measurements must be linked to route/member eligibility actions to change forwarding. This mechanism instead explains a separate problem: A preferred WAN becomes unhealthy and is withdrawn from service, but its route remains installed due to an incorrect health state-action setting. The current incident requires the more directly applicable cause stated by the correct option.

Question 648

During a post-incident review at a logistics office, the original problem was: A VPN overlay uses dynamic routing but an old static route for the same branch prefix takes precedence and sends traffic through an unreachable tunnel. Which preventive practice most directly addresses its cause?

  1. Compare FIB and BGP/OSPF candidates when troubleshooting overlay blackholes.
  2. Test both new and established sessions during WAN failure acceptance criteria.
  3. Inventory policy routes before changing SD-WAN service matching.
  4. Check routing table precedence when replacing legacy default routes.

Explanation

Correct Answer

A:

Compare FIB and BGP/OSPF candidates when troubleshooting overlay blackholes. This control reduces recurrence of the documented mechanism: Route administrative distance and priority can make stale static entries override learned paths. It creates a repeatable check around the needed response: Adjust competing static and dynamic route preference so the valid overlay next hop is selected.

Incorrect Answers

B:

Test both new and established sessions during WAN failure acceptance criteria. That safeguard addresses another potential failure: An Internet route remains valid after wan1 failure but existing long-lived TCP sessions continue using the failed translated path and do not instantly recover. It is not the most targeted recurring control for the described cause: Route administrative distance and priority can make stale static entries override learned paths.

C:

Inventory policy routes before changing SD-WAN service matching. That safeguard addresses another potential failure: Traffic matching a local policy route is forced toward an outdated VPN tunnel instead of following the updated SD-WAN rule. It is not the most targeted recurring control for the described cause: Route administrative distance and priority can make stale static entries override learned paths.

D:

Check routing table precedence when replacing legacy default routes. That safeguard addresses another potential failure: A default route to the ISP remains preferred over the SD-WAN zone after migration, causing most traffic to bypass SD-WAN rules. It is not the most targeted recurring control for the described cause: Route administrative distance and priority can make stale static entries override learned paths.

Question 649

A firewall operations team at a manufacturing plant encounters the following during a controlled failover drill: A site lets users bypass required certificate trust warnings by manually accepting an unexpected FortiSASE proxy certificate on every device. Which action most directly restores the approved security outcome?

  1. Install the approved PAC/manual proxy settings or supported agentless onboarding method for intended browsers.
  2. Synchronize the approved RADIUS client/server shared secret and test authentication exchanges.
  3. Deploy the authorized certificate chain to managed endpoints and investigate unsupported certificate identities.
  4. Apply the approved security coverage rules for each connection mode and document which traffic types each mode protects.

Explanation

Correct Answer

C:

Deploy the authorized certificate chain to managed endpoints and investigate unsupported certificate identities. This is the most direct response to the stated incident: A site lets users bypass required certificate trust warnings by manually accepting an unexpected FortiSASE proxy certificate on every device. The technical mechanism is: Encrypted proxy inspection requires a managed trust relationship with endpoints. Confirmation requires: Managed clients validate legitimate inspection certificates without unsafe click-through exceptions.

Incorrect Answers

A:

Install the approved PAC/manual proxy settings or supported agentless onboarding method for intended browsers. That could address a different issue in the same blueprint area: A team deploys an agentless SWG configuration but omits browser or system proxy settings, causing traffic to connect directly to Internet sites. It does not directly correct the given incident, whose decisive mechanism is: Encrypted proxy inspection requires a managed trust relationship with endpoints.

B:

Synchronize the approved RADIUS client/server shared secret and test authentication exchanges. That could address a different issue in the same blueprint area: A FortiSASE tenant uses RADIUS for user authentication but the RADIUS shared secret was changed on FortiAuthenticator only. It does not directly correct the given incident, whose decisive mechanism is: Encrypted proxy inspection requires a managed trust relationship with endpoints.

D:

Apply the approved security coverage rules for each connection mode and document which traffic types each mode protects. That could address a different issue in the same blueprint area: Remote users experience two different security postures because some are agent-based and others use browser-only SWG; an operator assumes both modes inspect nonweb traffic identically. It does not directly correct the given incident, whose decisive mechanism is: Encrypted proxy inspection requires a managed trust relationship with endpoints.

Question 650

An operations review at a manufacturing plant has corrected: A site lets users bypass required certificate trust warnings by manually accepting an unexpected FortiSASE proxy certificate on every device. Which observation specifically confirms success?

  1. Nonweb and web test cases show explicitly understood protection differences between agent and proxy cohorts.
  2. A deprovisioned test account no longer matches the privileged policy while active users retain access.
  3. A user in the previously omitted OU is found and permitted according to group rules.
  4. Managed clients validate legitimate inspection certificates without unsafe click-through exceptions.

Explanation

Correct Answer

D:

Managed clients validate legitimate inspection certificates without unsafe click-through exceptions. This evidence directly tests the intended corrective action: Deploy the authorized certificate chain to managed endpoints and investigate unsupported certificate identities. It confirms the failure mechanism—Encrypted proxy inspection requires a managed trust relationship with endpoints.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Nonweb and web test cases show explicitly understood protection differences between agent and proxy cohorts. This would verify resolution of a different case: Remote users experience two different security postures because some are agent-based and others use browser-only SWG; an operator assumes both modes inspect nonweb traffic identically. It does not show that the reported issue was fixed or that its intended action—Deploy the authorized certificate chain to managed endpoints and investigate unsupported certificate identities.—worked.

B:

A deprovisioned test account no longer matches the privileged policy while active users retain access. This would verify resolution of a different case: A remote worker successfully authenticates to FortiSASE but a stale identity group cache keeps applying a former privileged access policy. It does not show that the reported issue was fixed or that its intended action—Deploy the authorized certificate chain to managed endpoints and investigate unsupported certificate identities.—worked.

C:

A user in the previously omitted OU is found and permitted according to group rules. This would verify resolution of a different case: A remote user enters a correct password but FortiSASE authentication against a central LDAP directory fails because the configured base DN excludes that organizational unit. It does not show that the reported issue was fixed or that its intended action—Deploy the authorized certificate chain to managed endpoints and investigate unsupported certificate identities.—worked.

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