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 47

Question 460

An operations group at a manufacturing plant resolved: A FortiSASE report lists an endpoint as risky after a prohibited download, but response staff cannot determine whether the antivirus engine blocked the file before execution. Which ongoing safeguard should become part of its change process?

  1. Include identity events and location anomalies in FortiSASE threat hunting.
  2. Require endpoint confirmation before escalating download detections to executed-malware claims.
  3. Review configured IPS actions and resulting event disposition during alert triage.
  4. Retain user/device attribution and response fields for cloud malware detections.

Explanation

Correct Answer

B:

Require endpoint confirmation before escalating download detections to executed-malware claims. This control reduces recurrence of the documented mechanism: A cloud download alert does not by itself establish code execution on an endpoint. It creates a repeatable check around the needed response: Inspect antivirus event disposition and corroborating endpoint evidence before asserting execution.

Incorrect Answers

A:

Include identity events and location anomalies in FortiSASE threat hunting. That safeguard addresses another potential failure: Cloud security events show successful login attempts from an unexpected country, yet the team closes the case because no web filter block occurred. It is not the most targeted recurring control for the described cause: A cloud download alert does not by itself establish code execution on an endpoint.

C:

Review configured IPS actions and resulting event disposition during alert triage. That safeguard addresses another potential failure: A cloud log shows repeated IPS detections for an untrusted destination, but staff ignore the action field and assume every signature event was blocked. It is not the most targeted recurring control for the described cause: A cloud download alert does not by itself establish code execution on an endpoint.

D:

Retain user/device attribution and response fields for cloud malware detections. That safeguard addresses another potential failure: An administrator sees antivirus detections in FortiSASE but lacks the affected user and device context to decide where containment is needed. It is not the most targeted recurring control for the described cause: A cloud download alert does not by itself establish code execution on an endpoint.

Question 461

At a corporate headquarters, a security analyst is reviewing this failure during a configuration rollout: An administrator deletes a physical WAN interface that is still referenced by an active SD-WAN member, resulting in blocked change validation. What is the MOST appropriate FIRST corrective step?

  1. Normalize the approved member-to-zone design and adjust rules to reference the correct zone.
  2. Align the member's supported routing context and health-check source with the intended network path.
  3. Move the MPLS tunnel member to its appropriate private network SD-WAN zone and review policy references.
  4. Remove or migrate the dependent SD-WAN member and associated route or rule references before deleting the interface.

Explanation

Correct Answer

D:

Remove or migrate the dependent SD-WAN member and associated route or rule references before deleting the interface. This is the most direct response to the stated incident: An administrator deletes a physical WAN interface that is still referenced by an active SD-WAN member, resulting in blocked change validation. The technical mechanism is: Referenced members can prevent safe physical-interface deletion or replacement. Confirmation requires: Dependency validation succeeds and remaining rules use only existing interface members.

Incorrect Answers

A:

Normalize the approved member-to-zone design and adjust rules to reference the correct zone. That could address a different issue in the same blueprint area: Two independent branch subnets are accidentally assigned to different SD-WAN zones but security policy expects a single Internet zone, causing intermittent authorization gaps. It does not directly correct the given incident, whose decisive mechanism is: Referenced members can prevent safe physical-interface deletion or replacement.

B:

Align the member's supported routing context and health-check source with the intended network path. That could address a different issue in the same blueprint area: An SD-WAN member's configured source interface is still associated with an old VRF and the health check is sent into a nonworking routing table. It does not directly correct the given incident, whose decisive mechanism is: Referenced members can prevent safe physical-interface deletion or replacement.

C:

Move the MPLS tunnel member to its appropriate private network SD-WAN zone and review policy references. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Referenced members can prevent safe physical-interface deletion or replacement.

Question 462

During follow-up testing at a corporate headquarters, the original fault was: An administrator deletes a physical WAN interface that is still referenced by an active SD-WAN member, resulting in blocked change validation. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. Dependency validation succeeds and remaining rules use only existing interface members.
  2. A controlled regulated session exits through the contractually approved provider address.
  3. Both eligible Internet paths are covered by the intended outbound firewall policy.
  4. Utilization during a controlled mixed-load test stays within the secondary link's approved share.

Explanation

Correct Answer

A:

Dependency validation succeeds and remaining rules use only existing interface members. This evidence directly tests the intended corrective action: Remove or migrate the dependent SD-WAN member and associated route or rule references before deleting the interface. It confirms the failure mechanism—Referenced members can prevent safe physical-interface deletion or replacement.—has been addressed in the actual affected flow.

Incorrect Answers

B:

A controlled regulated session exits through the contractually approved provider address. This would verify resolution of a different case: Two ISP circuits share similar port labels and an engineer reverses wan1 and wan2 member metadata, sending regulated traffic to the wrong provider. It does not show that the reported issue was fixed or that its intended action—Remove or migrate the dependent SD-WAN member and associated route or rule references before deleting the interface.—worked.

C:

Both eligible Internet paths are covered by the intended outbound firewall policy. This would verify resolution of a different case: Two independent branch subnets are accidentally assigned to different SD-WAN zones but security policy expects a single Internet zone, causing intermittent authorization gaps. It does not show that the reported issue was fixed or that its intended action—Remove or migrate the dependent SD-WAN member and associated route or rule references before deleting the interface.—worked.

D:

Utilization during a controlled mixed-load test stays within the secondary link's approved share. This would verify resolution of a different case: A newly installed ISP link has a restricted bandwidth plan but its configured SD-WAN member weight causes bulk traffic to consume the entire link. It does not show that the reported issue was fixed or that its intended action—Remove or migrate the dependent SD-WAN member and associated route or rule references before deleting the interface.—worked.

Question 463

The incident investigation at a corporate headquarters records: An administrator deletes a physical WAN interface that is still referenced by an active SD-WAN member, resulting in blocked change validation. Which mechanism provides the strongest explanation?

  1. A broad shared zone may lack required traffic classification for costly backup connectivity.
  2. Referenced members can prevent safe physical-interface deletion or replacement.
  3. Logical member identifiers must correspond to the actual provider circuits used in policy.
  4. Physical carrier detection does not confirm a correct next-hop gateway.

Explanation

Correct Answer

B:

Referenced members can prevent safe physical-interface deletion or replacement. This explains why the reported condition occurs: An administrator deletes a physical WAN interface that is still referenced by an active SD-WAN member, resulting in blocked change validation. The targeted correction is: Remove or migrate the dependent SD-WAN member and associated route or rule references before deleting the interface.

Incorrect Answers

A:

A broad shared zone may lack required traffic classification for costly backup connectivity. This mechanism instead explains a separate problem: Two Internet uplinks are grouped into one zone but the branch needs separate policy treatment for metered mobile connectivity during outages. The current incident requires the more directly applicable cause stated by the correct option.

C:

Logical member identifiers must correspond to the actual provider circuits used in policy. This mechanism instead explains a separate problem: Two ISP circuits share similar port labels and an engineer reverses wan1 and wan2 member metadata, sending regulated traffic to the wrong provider. The current incident requires the more directly applicable cause stated by the correct option.

D:

Physical carrier detection does not confirm a correct next-hop gateway. This mechanism instead explains a separate problem: After replacing an ISP CPE, the old FortiGate member gateway remains configured and SLA probes fail despite the interface showing link up. The current incident requires the more directly applicable cause stated by the correct option.

Question 464

After a corrective change at a corporate headquarters, the team documents: An administrator deletes a physical WAN interface that is still referenced by an active SD-WAN member, resulting in blocked change validation. Which repeatable control BEST prevents a recurrence?

  1. Test representative subnet-to-subnet reachability with reverse-path inspection for every overlay.
  2. Revalidate member gateway and reachability whenever upstream ISP equipment changes.
  3. Inventory SD-WAN references before retiring network ports and circuits.
  4. Review capacity and steering weights whenever a lower-speed member is introduced.

Explanation

Correct Answer

C:

Inventory SD-WAN references before retiring network ports and circuits. This control reduces recurrence of the documented mechanism: Referenced members can prevent safe physical-interface deletion or replacement. It creates a repeatable check around the needed response: Remove or migrate the dependent SD-WAN member and associated route or rule references before deleting the interface.

Incorrect Answers

A:

Test representative subnet-to-subnet reachability with reverse-path inspection for every overlay. That safeguard addresses another potential failure: A FortiGate's overlay member health is green but its associated LAN subnet is not routed at the far end, producing one-way private application traffic. It is not the most targeted recurring control for the described cause: Referenced members can prevent safe physical-interface deletion or replacement.

B:

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: Referenced members can prevent safe physical-interface deletion or replacement.

D:

Review capacity and steering weights whenever a lower-speed member is introduced. That safeguard addresses another potential failure: A newly installed ISP link has a restricted bandwidth plan but its configured SD-WAN member weight causes bulk traffic to consume the entire link. It is not the most targeted recurring control for the described cause: Referenced members can prevent safe physical-interface deletion or replacement.

Question 465

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

  1. Add the correct private prefix route toward the approved SD-WAN overlay zone or tunnel.
  2. Remove or update the conflicting policy route and re-evaluate the real session lookup order.
  3. Correct the authoritative managed route template and reinstall the approved routing policy.
  4. Configure supported SLA member state or route-removal behavior to match documented failover policy.

Explanation

Correct Answer

A:

Add the correct private prefix route toward the approved SD-WAN overlay zone or tunnel. This is the most direct response to the stated incident: 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. The technical mechanism is: Steering policy cannot replace a necessary underlying destination route. Confirmation requires: A route lookup resolves the data-center prefix and a controlled session completes through the overlay.

Incorrect Answers

B:

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: Steering policy cannot replace a necessary underlying destination route.

C:

Correct the authoritative managed route template and reinstall the approved routing policy. That could address a different issue in the same blueprint area: A FortiGate has the correct SD-WAN zone route for corporate VPN but FortiManager installs a conflicting stale prefix route during configuration synchronization. It does not directly correct the given incident, whose decisive mechanism is: Steering policy cannot replace a necessary underlying destination route.

D:

Configure supported SLA member state or route-removal behavior to match documented failover policy. That could address a different issue in the same blueprint area: A preferred WAN becomes unhealthy and is withdrawn from service, but its route remains installed due to an incorrect health state-action setting. It does not directly correct the given incident, whose decisive mechanism is: Steering policy cannot replace a necessary underlying destination route.

Question 466

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

  1. Failure of the first ISP sends sessions through the second member with successful return traffic.
  2. A route lookup resolves the data-center prefix and a controlled session completes through the overlay.
  3. Syslog reaches the approved destination through its documented service path without altering user steering.
  4. The selected private prefix route and forwarding member follow the preferred non-metered path when healthy.

Explanation

Correct Answer

B:

A route lookup resolves the data-center prefix and a controlled session completes through the overlay. This evidence directly tests the intended corrective action: Add the correct private prefix route toward the approved SD-WAN overlay zone or tunnel. It confirms the failure mechanism—Steering policy cannot replace a necessary underlying destination route.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Failure of the first ISP sends sessions through the second member with successful return traffic. This would verify resolution of a different case: An admin adds a route to an SD-WAN zone but leaves one member without its required gateway or health check, causing failover to an unusable next hop. It does not show that the reported issue was fixed or that its intended action—Add the correct private prefix route toward the approved SD-WAN overlay zone or tunnel.—worked.

C:

Syslog reaches the approved destination through its documented service path without altering user steering. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Add the correct private prefix route toward the approved SD-WAN overlay zone or tunnel.—worked.

D:

The selected private prefix route and forwarding member follow the preferred non-metered path when healthy. This would verify resolution of a different case: A BGP route to a private application is learned through both MPLS and Internet overlay with a preference that incorrectly favors the metered link. It does not show that the reported issue was fixed or that its intended action—Add the correct private prefix route toward the approved SD-WAN overlay zone or tunnel.—worked.

Question 467

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

  1. Path steering determines link use; firewall policy separately authorizes traffic.
  2. Ordinary ECMP route eligibility alone does not encode per-application provider restrictions.
  3. Steering policy cannot replace a necessary underlying destination route.
  4. Routing preference is determined by route-selection policies, not by the WAN link's price label.

Explanation

Correct Answer

C:

Steering policy cannot replace a necessary underlying destination route. This explains why the reported condition occurs: 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. The targeted correction is: Add the correct private prefix route toward the approved SD-WAN overlay zone or tunnel.

Incorrect Answers

A:

Path steering determines link use; firewall policy separately authorizes traffic. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

B:

Ordinary ECMP route eligibility alone does not encode per-application provider restrictions. This mechanism instead explains a separate problem: A device has two equal-cost underlay routes but an application must use one provider for compliance while SD-WAN service matching is absent. The current incident requires the more directly applicable cause stated by the correct option.

D:

Routing preference is determined by route-selection policies, not by the WAN link's price label. This mechanism instead explains a separate problem: 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 current incident requires the more directly applicable cause stated by the correct option.

Question 468

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

  1. Compare FIB and BGP/OSPF candidates when troubleshooting overlay blackholes.
  2. Review destination prefix-to-zone mapping before enabling new overlays.
  3. Validate tunneled application prefixes separately from peer reachability.
  4. Reconcile private prefix reachability before enabling application-based path preference.

Explanation

Correct Answer

D:

Reconcile private prefix reachability before enabling application-based path preference. This control reduces recurrence of the documented mechanism: Steering policy cannot replace a necessary underlying destination route. It creates a repeatable check around the needed response: Add the correct private prefix route toward the approved SD-WAN overlay zone or tunnel.

Incorrect Answers

A:

Compare FIB and BGP/OSPF candidates when troubleshooting overlay blackholes. That safeguard addresses another potential failure: 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. It is not the most targeted recurring control for the described cause: Steering policy cannot replace a necessary underlying destination route.

B:

Review destination prefix-to-zone mapping before enabling new overlays. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Steering policy cannot replace a necessary underlying destination route.

C:

Validate tunneled application prefixes separately from peer reachability. That safeguard addresses another potential failure: 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. It is not the most targeted recurring control for the described cause: Steering policy cannot replace a necessary underlying destination route.

Question 469

During a production service incident, an administrator reports at a research campus: 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. What should the team change or investigate FIRST?

  1. Install the approved PAC/manual proxy settings or supported agentless onboarding method for intended browsers.
  2. Correct the supported LDAP search base and bind scope while preserving authorized authentication constraints.
  3. Correct the approved agentless proxy SAML redirect and reply URLs at the application and identity provider.
  4. Restore device time synchronization and test the trusted FortiSASE certificate chain.

Explanation

Correct Answer

B:

Correct the supported LDAP search base and bind scope while preserving authorized authentication constraints. This is the most direct response to the stated incident: 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. The technical mechanism is: Directory lookups are restricted by configured search base and binding scope. Confirmation requires: A user in the previously omitted OU is found and permitted according to group rules.

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: Directory lookups are restricted by configured search base and binding scope.

C:

Correct the approved agentless proxy SAML redirect and reply URLs at the application and identity provider. That could address a different issue in the same blueprint area: A contractor's browser proxy authentication loops because SAML redirect URLs retain an old domain after a secure web gateway hostname change. It does not directly correct the given incident, whose decisive mechanism is: Directory lookups are restricted by configured search base and binding scope.

D:

Restore device time synchronization and test the trusted FortiSASE certificate chain. That could address a different issue in the same blueprint area: An employee's FortiClient connection repeatedly disconnects when the local system clock is wrong and the client rejects a valid service certificate. It does not directly correct the given incident, whose decisive mechanism is: Directory lookups are restricted by configured search base and binding scope.

Question 470

Following remediation at a research campus, engineers revisit: 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. Which observation would BEST prove the specific issue is resolved?

  1. The employee device appears as enrolled and traffic uses the expected FortiSASE connection.
  2. A test user's RADIUS request succeeds with expected acceptance and group behavior.
  3. A user in the previously omitted OU is found and permitted according to group rules.
  4. A test user connects to an approved low-latency PoP and receives the right group policy.

Explanation

Correct Answer

C:

A user in the previously omitted OU is found and permitted according to group rules. This evidence directly tests the intended corrective action: Correct the supported LDAP search base and bind scope while preserving authorized authentication constraints. It confirms the failure mechanism—Directory lookups are restricted by configured search base and binding scope.—has been addressed in the actual affected flow.

Incorrect Answers

A:

The employee device appears as enrolled and traffic uses the expected FortiSASE connection. This would verify resolution of a different case: Remote employees are instructed to use FortiSASE agent-based protection but no FortiClient installation or managed registration has been completed. It does not show that the reported issue was fixed or that its intended action—Correct the supported LDAP search base and bind scope while preserving authorized authentication constraints.—worked.

B:

A test user's RADIUS request succeeds with expected acceptance and group behavior. This would verify resolution of a different case: A FortiSASE tenant uses RADIUS for user authentication but the RADIUS shared secret was changed on FortiAuthenticator only. It does not show that the reported issue was fixed or that its intended action—Correct the supported LDAP search base and bind scope while preserving authorized authentication constraints.—worked.

D:

A test user connects to an approved low-latency PoP and receives the right group policy. This would verify resolution of a different case: An endpoint registers successfully but the FortiClient service profile applies to the wrong geographic user group, routing employees through a distant PoP. It does not show that the reported issue was fixed or that its intended action—Correct the supported LDAP search base and bind scope while preserving authorized authentication constraints.—worked.

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