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 37

Question 360

During a post-incident review at a logistics office, the original problem was: Cloud security events show successful login attempts from an unexpected country, yet the team closes the case because no web filter block occurred. Which preventive practice most directly addresses its cause?

  1. Include identity events and location anomalies in FortiSASE threat hunting.
  2. Require profile type and disposition fields in threat case triage.
  3. Retain user/device attribution and response fields for cloud malware detections.
  4. Require endpoint confirmation before escalating download detections to executed-malware claims.

Explanation

Correct Answer

A:

Include identity events and location anomalies in FortiSASE threat hunting. This control reduces recurrence of the documented mechanism: Login anomalies can matter independently of content filtering categories. It creates a repeatable check around the needed response: Correlate authentication events, geolocation policy and session access outcomes for the affected identity.

Incorrect Answers

B:

Require profile type and disposition fields in threat case triage. That safeguard addresses another potential failure: An SOC receives a FortiSASE Web Filter log for a blocked phishing category but labels it as an antivirus malware detection. It is not the most targeted recurring control for the described cause: Login anomalies can matter independently of content filtering categories.

C:

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: Login anomalies can matter independently of content filtering categories.

D:

Require endpoint confirmation before escalating download detections to executed-malware claims. That safeguard addresses another potential failure: 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. It is not the most targeted recurring control for the described cause: Login anomalies can matter independently of content filtering categories.

Question 361

A firewall operations team at a manufacturing plant encounters the following during a controlled failover drill: After replacing an ISP CPE, the old FortiGate member gateway remains configured and SLA probes fail despite the interface showing link up. Which action most directly restores the approved security outcome?

  1. Update the affected static route to the new correct zone and revalidate forwarding.
  2. Assign the metered backup path to a distinct controlled zone or apply a supported strategy with explicit traffic restrictions.
  3. Update that member's gateway to the address supplied by the new CPE and verify routing.
  4. Move the MPLS tunnel member to its appropriate private network SD-WAN zone and review policy references.

Explanation

Correct Answer

C:

Update that member's gateway to the address supplied by the new CPE and verify routing. This is the most direct response to the stated incident: After replacing an ISP CPE, the old FortiGate member gateway remains configured and SLA probes fail despite the interface showing link up. The technical mechanism is: Physical carrier detection does not confirm a correct next-hop gateway. Confirmation requires: Member health recovers and eligible sessions traverse the replaced ISP link.

Incorrect Answers

A:

Update the affected static route to the new correct zone and revalidate forwarding. That could address a different issue in the same blueprint area: 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 does not directly correct the given incident, whose decisive mechanism is: Physical carrier detection does not confirm a correct next-hop gateway.

B:

Assign the metered backup path to a distinct controlled zone or apply a supported strategy with explicit traffic restrictions. That could address a different issue in the same blueprint area: Two Internet uplinks are grouped into one zone but the branch needs separate policy treatment for metered mobile connectivity during outages. It does not directly correct the given incident, whose decisive mechanism is: Physical carrier detection does not confirm a correct next-hop gateway.

D:

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: Physical carrier detection does not confirm a correct next-hop gateway.

Question 362

An operations review at a manufacturing plant has corrected: After replacing an ISP CPE, the old FortiGate member gateway remains configured and SLA probes fail despite the interface showing link up. Which observation specifically confirms success?

  1. A controlled regulated session exits through the contractually approved provider address.
  2. Configuration install succeeds and each member appears in one approved operational grouping.
  3. Probe packets use the intended routing context and the member reports correct reachability.
  4. Member health recovers and eligible sessions traverse the replaced ISP link.

Explanation

Correct Answer

D:

Member health recovers and eligible sessions traverse the replaced ISP link. This evidence directly tests the intended corrective action: Update that member's gateway to the address supplied by the new CPE and verify routing. It confirms the failure mechanism—Physical carrier detection does not confirm a correct next-hop gateway.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Update that member's gateway to the address supplied by the new CPE and verify routing.—worked.

B:

Configuration install succeeds and each member appears in one approved operational grouping. This would verify resolution of a different case: A configuration template assigns one WAN member to multiple intended zones through duplicated site definitions, causing a conflict during managed deployment. It does not show that the reported issue was fixed or that its intended action—Update that member's gateway to the address supplied by the new CPE and verify routing.—worked.

C:

Probe packets use the intended routing context and the member reports correct reachability. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Update that member's gateway to the address supplied by the new CPE and verify routing.—worked.

Question 363

At a manufacturing plant, investigators observe: After replacing an ISP CPE, the old FortiGate member gateway remains configured and SLA probes fail despite the interface showing link up. Which underlying policy or system mechanism BEST explains this behavior?

  1. Physical carrier detection does not confirm a correct next-hop gateway.
  2. Membership does not guarantee an IPsec overlay's far-end peer is reachable or authenticated.
  3. An invalid preferred member complicates path selection even when a working alternative exists.
  4. One successful member cannot prove every zone member has a valid forwarding gateway.

Explanation

Correct Answer

A:

Physical carrier detection does not confirm a correct next-hop gateway. This explains why the reported condition occurs: After replacing an ISP CPE, the old FortiGate member gateway remains configured and SLA probes fail despite the interface showing link up. The targeted correction is: Update that member's gateway to the address supplied by the new CPE and verify routing.

Incorrect Answers

B:

Membership does not guarantee an IPsec overlay's far-end peer is reachable or authenticated. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

C:

An invalid preferred member complicates path selection even when a working alternative exists. This mechanism instead explains a separate problem: A small branch lists a disconnected spare physical port as the highest-preference member and fails over repeatedly before landing on a working path. The current incident requires the more directly applicable cause stated by the correct option.

D:

One successful member cannot prove every zone member has a valid forwarding gateway. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

Question 364

An operations group at a manufacturing plant resolved: After replacing an ISP CPE, the old FortiGate member gateway remains configured and SLA probes fail despite the interface showing link up. Which ongoing safeguard should become part of its change process?

  1. Document metered paths and verify per-application allowed traffic before deployment.
  2. Revalidate member gateway and reachability whenever upstream ISP equipment changes.
  3. Explicitly specify member zone instead of relying on defaults in site templates.
  4. Check VLAN encapsulation and logical-interface selection during circuit acceptance.

Explanation

Correct Answer

B:

Revalidate member gateway and reachability whenever upstream ISP equipment changes. This control reduces recurrence of the documented mechanism: Physical carrier detection does not confirm a correct next-hop gateway. It creates a repeatable check around the needed response: Update that member's gateway to the address supplied by the new CPE and verify routing.

Incorrect Answers

A:

Document metered paths and verify per-application allowed traffic before deployment. That safeguard addresses another potential failure: Two Internet uplinks are grouped into one zone but the branch needs separate policy treatment for metered mobile connectivity during outages. It is not the most targeted recurring control for the described cause: Physical carrier detection does not confirm a correct next-hop gateway.

C:

Explicitly specify member zone instead of relying on defaults in site templates. That safeguard addresses another potential failure: A new tunnel member is added under the default virtual-wan-link zone although the architecture requires region-specific security controls. It is not the most targeted recurring control for the described cause: Physical carrier detection does not confirm a correct next-hop gateway.

D:

Check VLAN encapsulation and logical-interface selection during circuit acceptance. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Physical carrier detection does not confirm a correct next-hop gateway.

Question 365

At a corporate headquarters, a security analyst is reviewing this failure during a configuration rollout: A high-priority rule for guest Internet traffic mistakenly matches the corporate workstation source segment and sends trusted users over a limited guest ISP. What is the MOST appropriate FIRST corrective step?

  1. Restore the approved primary-versus-backup member order and retain actual failure handling.
  2. Replace the broad category match with the intended recognized application or application object.
  3. Order the narrower business application rule ahead of the broad rule and test classification.
  4. Narrow the guest rule's source network and maintain separate staff policy criteria.

Explanation

Correct Answer

D:

Narrow the guest rule's source network and maintain separate staff policy criteria. This is the most direct response to the stated incident: A high-priority rule for guest Internet traffic mistakenly matches the corporate workstation source segment and sends trusted users over a limited guest ISP. The technical mechanism is: Mis-scoped source matching in ordered rules creates unexpected path selection. Confirmation requires: Guest and corporate test users match their respective expected steering rules.

Incorrect Answers

A:

Restore the approved primary-versus-backup member order and retain actual failure handling. That could address a different issue in the same blueprint area: A manual strategy lists wan2 first for an emergency but it stays preferred after the event, sending ordinary sessions over a low-bandwidth backup link. It does not directly correct the given incident, whose decisive mechanism is: Mis-scoped source matching in ordered rules creates unexpected path selection.

B:

Replace the broad category match with the intended recognized application or application object. That could address a different issue in the same blueprint area: An administrator configures a rule matching application category Social Networking while the approved exception is only for a named conferencing application. It does not directly correct the given incident, whose decisive mechanism is: Mis-scoped source matching in ordered rules creates unexpected path selection.

C:

Order the narrower business application rule ahead of the broad rule and test classification. That could address a different issue in the same blueprint area: A business application has a dedicated SD-WAN rule located below a broad catch-all service rule, so it never uses its premium MPLS path. It does not directly correct the given incident, whose decisive mechanism is: Mis-scoped source matching in ordered rules creates unexpected path selection.

Question 366

During follow-up testing at a corporate headquarters, the original fault was: A high-priority rule for guest Internet traffic mistakenly matches the corporate workstation source segment and sends trusted users over a limited guest ISP. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. Guest and corporate test users match their respective expected steering rules.
  2. A route diagnostic selects a valid current member for the matching session.
  3. A controlled conference flow uses a member satisfying the video jitter target when available.
  4. The affected application's sessions again hit the intended explicit service rule.

Explanation

Correct Answer

A:

Guest and corporate test users match their respective expected steering rules. This evidence directly tests the intended corrective action: Narrow the guest rule's source network and maintain separate staff policy criteria. It confirms the failure mechanism—Mis-scoped source matching in ordered rules creates unexpected path selection.—has been addressed in the actual affected flow.

Incorrect Answers

B:

A route diagnostic selects a valid current member for the matching session. This would verify resolution of a different case: An SD-WAN rule uses a manual preferred member that's no longer provisioned after carrier cutover; otherwise healthy links are ignored. It does not show that the reported issue was fixed or that its intended action—Narrow the guest rule's source network and maintain separate staff policy criteria.—worked.

C:

A controlled conference flow uses a member satisfying the video jitter target when available. This would verify resolution of a different case: A video collaboration app must favor low jitter but the rule uses Manual preference for a congested inexpensive circuit. It does not show that the reported issue was fixed or that its intended action—Narrow the guest rule's source network and maintain separate staff policy criteria.—worked.

D:

The affected application's sessions again hit the intended explicit service rule. This would verify resolution of a different case: A support team disables an SD-WAN service rule during troubleshooting and forgets the implicit rule now controls traffic, degrading latency. It does not show that the reported issue was fixed or that its intended action—Narrow the guest rule's source network and maintain separate staff policy criteria.—worked.

Question 367

The incident investigation at a corporate headquarters records: A high-priority rule for guest Internet traffic mistakenly matches the corporate workstation source segment and sends trusted users over a limited guest ISP. Which mechanism provides the strongest explanation?

  1. An overly narrow or incorrect destination object makes a valid rule ineffective.
  2. Mis-scoped source matching in ordered rules creates unexpected path selection.
  3. Path selection alone does not reserve link bandwidth under contention.
  4. Temporary manual priority edits persist until intentionally reverted.

Explanation

Correct Answer

B:

Mis-scoped source matching in ordered rules creates unexpected path selection. This explains why the reported condition occurs: A high-priority rule for guest Internet traffic mistakenly matches the corporate workstation source segment and sends trusted users over a limited guest ISP. The targeted correction is: Narrow the guest rule's source network and maintain separate staff policy criteria.

Incorrect Answers

A:

An overly narrow or incorrect destination object makes a valid rule ineffective. This mechanism instead explains a separate problem: A newly added SD-WAN rule matches the source office VLAN but mistakenly uses the destination mask 0.0.0.0/32, so no Internet applications hit it. The current incident requires the more directly applicable cause stated by the correct option.

C:

Path selection alone does not reserve link bandwidth under contention. This mechanism instead explains a separate problem: A UDP voice service needs preferential bandwidth during outages, but a general traffic shaping policy consumes the member capacity first. The current incident requires the more directly applicable cause stated by the correct option.

D:

Temporary manual priority edits persist until intentionally reverted. This mechanism instead explains a separate problem: A manual strategy lists wan2 first for an emergency but it stays preferred after the event, sending ordinary sessions over a low-bandwidth backup link. The current incident requires the more directly applicable cause stated by the correct option.

Question 368

After a corrective change at a corporate headquarters, the team documents: A high-priority rule for guest Internet traffic mistakenly matches the corporate workstation source segment and sends trusted users over a limited guest ISP. Which repeatable control BEST prevents a recurrence?

  1. Test rule selection, route lookup and firewall policy together for each service.
  2. Map application class to correct quality or capacity decision policy.
  3. Test boundary source addresses for each overlapping SD-WAN rule after subnet changes.
  4. Audit private-data rule eligible members against network encryption requirements.

Explanation

Correct Answer

C:

Test boundary source addresses for each overlapping SD-WAN rule after subnet changes. This control reduces recurrence of the documented mechanism: Mis-scoped source matching in ordered rules creates unexpected path selection. It creates a repeatable check around the needed response: Narrow the guest rule's source network and maintain separate staff policy criteria.

Incorrect Answers

A:

Test rule selection, route lookup and firewall policy together for each service. That safeguard addresses another potential failure: A transaction flow is directed to a preferred member despite no matching route for its destination through that member, producing packet drops. It is not the most targeted recurring control for the described cause: Mis-scoped source matching in ordered rules creates unexpected path selection.

B:

Map application class to correct quality or capacity decision policy. That safeguard addresses another potential failure: A link quality rule is configured to prefer the lowest measured latency but remote workers need consistent performance for large backups over a higher-capacity path. It is not the most targeted recurring control for the described cause: Mis-scoped source matching in ordered rules creates unexpected path selection.

D:

Audit private-data rule eligible members against network encryption requirements. That safeguard addresses another potential failure: A branch needs a private application to use the encrypted overlay but an SD-WAN rule includes the direct Internet underlay in its eligible members. It is not the most targeted recurring control for the described cause: Mis-scoped source matching in ordered rules creates unexpected path selection.

Question 369

During a quarterly compliance review at a distributed branch estate, analysts observe: Remote employees are instructed to use FortiSASE agent-based protection but no FortiClient installation or managed registration has been completed. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Deploy and register the compatible FortiClient agent using the approved enrollment process.
  2. Correct the supported group-specific onboarding and region assignment while preserving identity and security controls.
  3. Correct the approved agentless proxy SAML redirect and reply URLs at the application and identity provider.
  4. Synchronize the approved RADIUS client/server shared secret and test authentication exchanges.

Explanation

Correct Answer

A:

Deploy and register the compatible FortiClient agent using the approved enrollment process. This is the most direct response to the stated incident: Remote employees are instructed to use FortiSASE agent-based protection but no FortiClient installation or managed registration has been completed. The technical mechanism is: Agent-based access requires a working client installation and service enrollment. Confirmation requires: The employee device appears as enrolled and traffic uses the expected FortiSASE connection.

Incorrect Answers

B:

Correct the supported group-specific onboarding and region assignment while preserving identity and security controls. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Agent-based access requires a working client installation and service enrollment.

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: Agent-based access requires a working client installation and service enrollment.

D:

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: Agent-based access requires a working client installation and service enrollment.

Question 370

At a distributed branch estate, a test team is validating a change after this incident: Remote employees are instructed to use FortiSASE agent-based protection but no FortiClient installation or managed registration has been completed. What evidence most directly verifies the intended outcome?

  1. A browser-only test reaches approved web destinations through the intended proxy without a managed VPN agent.
  2. The employee device appears as enrolled and traffic uses the expected FortiSASE connection.
  3. The local user receives only the allowed policy rather than unrestricted default access.
  4. A deprovisioned test account no longer matches the privileged policy while active users retain access.

Explanation

Correct Answer

B:

The employee device appears as enrolled and traffic uses the expected FortiSASE connection. This evidence directly tests the intended corrective action: Deploy and register the compatible FortiClient agent using the approved enrollment process. It confirms the failure mechanism—Agent-based access requires a working client installation and service enrollment.—has been addressed in the actual affected flow.

Incorrect Answers

A:

A browser-only test reaches approved web destinations through the intended proxy without a managed VPN agent. This would verify resolution of a different case: A company plans browser-only secure web gateway use for contractors but distributes an agent-based full-tunnel guide requiring managed endpoint enrollment. It does not show that the reported issue was fixed or that its intended action—Deploy and register the compatible FortiClient agent using the approved enrollment process.—worked.

C:

The local user receives only the allowed policy rather than unrestricted default access. This would verify resolution of a different case: An administrator creates a local FortiSASE user but assumes LDAP group restrictions apply automatically although the account is not mapped to a corresponding local service group. It does not show that the reported issue was fixed or that its intended action—Deploy and register the compatible FortiClient agent using the approved enrollment process.—worked.

D:

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 and register the compatible FortiClient agent using the approved enrollment process.—worked.

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