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 43

Question 420

A risk review at a distributed branch estate focuses on preventing this issue again: A FortiSASE security incident is attributed to a blocked malicious domain, but cloud DNS and web events show the domain never resolved for the affected client. Which recurring control is most suitable?

  1. Separate prechange and postchange log samples in cloud policy validation.
  2. Retain authenticated user and SaaS session fields for data-exfiltration investigations.
  3. Include identity events and location anomalies in FortiSASE threat hunting.
  4. Cross-check DNS resolution before claiming confirmed access to a malicious site.

Explanation

Correct Answer

D:

Cross-check DNS resolution before claiming confirmed access to a malicious site. This control reduces recurrence of the documented mechanism: Threat indicator match attempts and successful sessions have different evidentiary meaning. It creates a repeatable check around the needed response: Correlate DNS resolution and web security events using the relevant time and source fields.

Incorrect Answers

A:

Separate prechange and postchange log samples in cloud policy validation. That safeguard addresses another potential failure: An analyst sees one outdated antivirus alert after a profile change and assumes the new policy is still failing without checking its log timestamp. It is not the most targeted recurring control for the described cause: Threat indicator match attempts and successful sessions have different evidentiary meaning.

B:

Retain authenticated user and SaaS session fields for data-exfiltration investigations. That safeguard addresses another potential failure: A compliance investigation needs to identify which sanctioned SaaS user moved sensitive files, but the SOC looks only at source public IP shared by many remote clients. It is not the most targeted recurring control for the described cause: Threat indicator match attempts and successful sessions have different evidentiary meaning.

C:

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: Threat indicator match attempts and successful sessions have different evidentiary meaning.

Question 421

During an incident triage, an administrator reports at a research campus: An engineer associates a backup MPLS tunnel with the Internet-DIA zone instead of the private overlay zone, exposing it to Internet traffic selection. What should the team change or investigate FIRST?

  1. Update the affected static route to the new correct zone and revalidate forwarding.
  2. Move the MPLS tunnel member to its appropriate private network SD-WAN zone and review policy references.
  3. Correct the supported far-end route or overlay advertisement for the missing branch subnet.
  4. Create or select the region-approved SD-WAN zone and assign the tunnel member to it.

Explanation

Correct Answer

B:

Move the MPLS tunnel member to its appropriate private network SD-WAN zone and review policy references. This is the most direct response to the stated incident: An engineer associates a backup MPLS tunnel with the Internet-DIA zone instead of the private overlay zone, exposing it to Internet traffic selection. The technical mechanism is: Zone assignment determines which grouped members are eligible for zone-based routing and policies. Confirmation requires: Business traffic follows the intended private zone and DIA traffic never selects MPLS accidentally.

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: Zone assignment determines which grouped members are eligible for zone-based routing and policies.

C:

Correct the supported far-end route or overlay advertisement for the missing branch subnet. That could address a different issue in the same blueprint area: 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 does not directly correct the given incident, whose decisive mechanism is: Zone assignment determines which grouped members are eligible for zone-based routing and policies.

D:

Create or select the region-approved SD-WAN zone and assign the tunnel member to it. That could address a different issue in the same blueprint area: A new tunnel member is added under the default virtual-wan-link zone although the architecture requires region-specific security controls. It does not directly correct the given incident, whose decisive mechanism is: Zone assignment determines which grouped members are eligible for zone-based routing and policies.

Question 422

Following remediation at a research campus, engineers revisit: An engineer associates a backup MPLS tunnel with the Internet-DIA zone instead of the private overlay zone, exposing it to Internet traffic selection. Which observation would BEST prove the specific issue is resolved?

  1. Utilization during a controlled mixed-load test stays within the secondary link's approved share.
  2. Member health recovers and eligible sessions traverse the replaced ISP link.
  3. Business traffic follows the intended private zone and DIA traffic never selects MPLS accidentally.
  4. Health probes and test sessions leave with the approved VLAN tag and reach the ISP gateway.

Explanation

Correct Answer

C:

Business traffic follows the intended private zone and DIA traffic never selects MPLS accidentally. This evidence directly tests the intended corrective action: Move the MPLS tunnel member to its appropriate private network SD-WAN zone and review policy references. It confirms the failure mechanism—Zone assignment determines which grouped members are eligible for zone-based routing and policies.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Move the MPLS tunnel member to its appropriate private network SD-WAN zone and review policy references.—worked.

B:

Member health recovers and eligible sessions traverse the replaced ISP link. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Move the MPLS tunnel member to its appropriate private network SD-WAN zone and review policy references.—worked.

D:

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—Move the MPLS tunnel member to its appropriate private network SD-WAN zone and review policy references.—worked.

Question 423

During an incident triage, this condition is reported: An engineer associates a backup MPLS tunnel with the Internet-DIA zone instead of the private overlay zone, exposing it to Internet traffic selection. Which technical explanation MOST directly accounts for the failure?

  1. An invalid preferred member complicates path selection even when a working alternative exists.
  2. SD-WAN health checks depend on the member's valid routing and probe source context.
  3. Physical carrier detection does not confirm a correct next-hop gateway.
  4. Zone assignment determines which grouped members are eligible for zone-based routing and policies.

Explanation

Correct Answer

D:

Zone assignment determines which grouped members are eligible for zone-based routing and policies. This explains why the reported condition occurs: An engineer associates a backup MPLS tunnel with the Internet-DIA zone instead of the private overlay zone, exposing it to Internet traffic selection. The targeted correction is: Move the MPLS tunnel member to its appropriate private network SD-WAN zone and review policy references.

Incorrect Answers

A:

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.

B:

SD-WAN health checks depend on the member's valid routing and probe source context. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

C:

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 424

During a post-incident review at a research campus, the original problem was: An engineer associates a backup MPLS tunnel with the Internet-DIA zone instead of the private overlay zone, exposing it to Internet traffic selection. Which preventive practice most directly addresses its cause?

  1. Inspect member-to-zone assignments during every underlay and overlay design review.
  2. Explicitly specify member zone instead of relying on defaults in site templates.
  3. Revalidate member gateway and reachability whenever upstream ISP equipment changes.
  4. Confirm peer endpoints and cryptographic state before advertising overlay members healthy.

Explanation

Correct Answer

A:

Inspect member-to-zone assignments during every underlay and overlay design review. This control reduces recurrence of the documented mechanism: Zone assignment determines which grouped members are eligible for zone-based routing and policies. It creates a repeatable check around the needed response: Move the MPLS tunnel member to its appropriate private network SD-WAN zone and review policy references.

Incorrect Answers

B:

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: Zone assignment determines which grouped members are eligible for zone-based routing and policies.

C:

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: Zone assignment determines which grouped members are eligible for zone-based routing and policies.

D:

Confirm peer endpoints and cryptographic state before advertising overlay members healthy. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Zone assignment determines which grouped members are eligible for zone-based routing and policies.

Question 425

A firewall operations team at a service-provider edge encounters the following during a controlled failover drill: 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. Which action most directly restores the approved security outcome?

  1. Replace the broad category match with the intended recognized application or application object.
  2. Inspect the documented application learning and session steering stages, then align the fallback and app-based rule with the supported detection sequence.
  3. Restore the approved primary-versus-backup member order and retain actual failure handling.
  4. Add the supported user or group match condition to the finance steering policy while retaining network scope.

Explanation

Correct Answer

C:

Restore the approved primary-versus-backup member order and retain actual failure handling. This is the most direct response to the stated incident: 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 technical mechanism is: Temporary manual priority edits persist until intentionally reverted. Confirmation requires: Normal traffic returns to the primary and failover still selects backup when appropriate.

Incorrect Answers

A:

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: Temporary manual priority edits persist until intentionally reverted.

B:

Inspect the documented application learning and session steering stages, then align the fallback and app-based rule with the supported detection sequence. That could address a different issue in the same blueprint area: An application-based SD-WAN rule steers initial traffic through the wrong link before the application can be classified, confusing testers. It does not directly correct the given incident, whose decisive mechanism is: Temporary manual priority edits persist until intentionally reverted.

D:

Add the supported user or group match condition to the finance steering policy while retaining network scope. That could address a different issue in the same blueprint area: A rule intended to steer only an authenticated finance group has a source address match but no required user-identity criterion, including guests on that subnet. It does not directly correct the given incident, whose decisive mechanism is: Temporary manual priority edits persist until intentionally reverted.

Question 426

An operations review at a service-provider edge has corrected: 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. Which observation specifically confirms success?

  1. With one healthy eligible path, the rule behaves as intended without unnecessarily denying the application.
  2. Private sessions traverse the encrypted tunnel and cannot egress through unapproved cleartext DIA.
  3. Controlled mixed traffic shows the voice application receives priority while bulk transfers are limited.
  4. Normal traffic returns to the primary and failover still selects backup when appropriate.

Explanation

Correct Answer

D:

Normal traffic returns to the primary and failover still selects backup when appropriate. This evidence directly tests the intended corrective action: Restore the approved primary-versus-backup member order and retain actual failure handling. It confirms the failure mechanism—Temporary manual priority edits persist until intentionally reverted.—has been addressed in the actual affected flow.

Incorrect Answers

A:

With one healthy eligible path, the rule behaves as intended without unnecessarily denying the application. This would verify resolution of a different case: A rule is configured to require two SLA-compliant members for load balancing but only one ISP meets the target during minor outages, making the rule unavailable. It does not show that the reported issue was fixed or that its intended action—Restore the approved primary-versus-backup member order and retain actual failure handling.—worked.

B:

Private sessions traverse the encrypted tunnel and cannot egress through unapproved cleartext DIA. This would verify resolution of a different case: 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 does not show that the reported issue was fixed or that its intended action—Restore the approved primary-versus-backup member order and retain actual failure handling.—worked.

C:

Controlled mixed traffic shows the voice application receives priority while bulk transfers are limited. This would verify resolution of a different case: A UDP voice service needs preferential bandwidth during outages, but a general traffic shaping policy consumes the member capacity first. It does not show that the reported issue was fixed or that its intended action—Restore the approved primary-versus-backup member order and retain actual failure handling.—worked.

Question 427

At a service-provider edge, investigators observe: 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. Which underlying policy or system mechanism BEST explains this behavior?

  1. Temporary manual priority edits persist until intentionally reverted.
  2. Source subnet membership is not equivalent to authenticated user-group membership.
  3. SD-WAN service rules have ordered matching and an earlier broad rule can shadow a narrow one.
  4. Address-only rule criteria drift as cloud service destinations change.

Explanation

Correct Answer

A:

Temporary manual priority edits persist until intentionally reverted. This explains why the reported condition occurs: 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 targeted correction is: Restore the approved primary-versus-backup member order and retain actual failure handling.

Incorrect Answers

B:

Source subnet membership is not equivalent to authenticated user-group membership. This mechanism instead explains a separate problem: A rule intended to steer only an authenticated finance group has a source address match but no required user-identity criterion, including guests on that subnet. The current incident requires the more directly applicable cause stated by the correct option.

C:

SD-WAN service rules have ordered matching and an earlier broad rule can shadow a narrow one. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

D:

Address-only rule criteria drift as cloud service destinations change. This mechanism instead explains a separate problem: A rule uses a destination subnet from last year's SaaS allocation and new addresses take the implicit rule instead of the low-latency path. The current incident requires the more directly applicable cause stated by the correct option.

Question 428

An operations group at a service-provider edge resolved: 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. Which ongoing safeguard should become part of its change process?

  1. Classify source-IP-sensitive applications before choosing load-balancing strategies.
  2. Apply time-boxed change tickets and restoration tests to emergency steering rules.
  3. Refresh SD-WAN costs when tariff or bandwidth contracts change.
  4. Map application class to correct quality or capacity decision policy.

Explanation

Correct Answer

B:

Apply time-boxed change tickets and restoration tests to emergency steering rules. This control reduces recurrence of the documented mechanism: Temporary manual priority edits persist until intentionally reverted. It creates a repeatable check around the needed response: Restore the approved primary-versus-backup member order and retain actual failure handling.

Incorrect Answers

A:

Classify source-IP-sensitive applications before choosing load-balancing strategies. That safeguard addresses another potential failure: A payment service is set to load-balance across WAN links despite a vendor requiring a stable public source address for the entire session. It is not the most targeted recurring control for the described cause: Temporary manual priority edits persist until intentionally reverted.

C:

Refresh SD-WAN costs when tariff or bandwidth contracts change. That safeguard addresses another potential failure: An administrator selects the lowest-cost SLA mode but assigns the same cost to a metered cellular link and unlimited broadband, overusing cellular service. It is not the most targeted recurring control for the described cause: Temporary manual priority edits persist until intentionally reverted.

D:

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: Temporary manual priority edits persist until intentionally reverted.

Question 429

At a national SOC, a security analyst is reviewing this failure during a configuration rollout: Users are assigned to a FortiSASE SAML login profile but the identity provider does not trust the current service provider entity ID. What is the MOST appropriate FIRST corrective step?

  1. Restore device time synchronization and test the trusted FortiSASE certificate chain.
  2. Correct the supported group-specific onboarding and region assignment while preserving identity and security controls.
  3. Assign an appropriate available user entitlement and repeat the supported client activation process.
  4. Update the approved SAML trust, entity ID and assertion configuration on both FortiSASE and IdP.

Explanation

Correct Answer

D:

Update the approved SAML trust, entity ID and assertion configuration on both FortiSASE and IdP. This is the most direct response to the stated incident: Users are assigned to a FortiSASE SAML login profile but the identity provider does not trust the current service provider entity ID. The technical mechanism is: SAML login requires matching service-provider and identity-provider trust metadata. Confirmation requires: A managed user completes SSO and FortiSASE identifies the correct account.

Incorrect Answers

A:

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: SAML login requires matching service-provider and identity-provider trust metadata.

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: SAML login requires matching service-provider and identity-provider trust metadata.

C:

Assign an appropriate available user entitlement and repeat the supported client activation process. That could address a different issue in the same blueprint area: A newly hired employee follows an agent-based FortiSASE onboarding link but has no active licensed seat and receives a misleading generic sign-in error. It does not directly correct the given incident, whose decisive mechanism is: SAML login requires matching service-provider and identity-provider trust metadata.

Question 430

During follow-up testing at a national SOC, the original fault was: Users are assigned to a FortiSASE SAML login profile but the identity provider does not trust the current service provider entity ID. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. A managed user completes SSO and FortiSASE identifies the correct account.
  2. A user in the previously omitted OU is found and permitted according to group rules.
  3. The local user receives only the allowed policy rather than unrestricted default access.
  4. Test web access appears in FortiSASE SWG logs and nonproxy direct browsing is appropriately restricted.

Explanation

Correct Answer

A:

A managed user completes SSO and FortiSASE identifies the correct account. This evidence directly tests the intended corrective action: Update the approved SAML trust, entity ID and assertion configuration on both FortiSASE and IdP. It confirms the failure mechanism—SAML login requires matching service-provider and identity-provider trust metadata.—has been addressed in the actual affected flow.

Incorrect Answers

B:

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—Update the approved SAML trust, entity ID and assertion configuration on both FortiSASE and IdP.—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—Update the approved SAML trust, entity ID and assertion configuration on both FortiSASE and IdP.—worked.

D:

Test web access appears in FortiSASE SWG logs and nonproxy direct browsing is appropriately restricted. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Update the approved SAML trust, entity ID and assertion configuration on both FortiSASE and IdP.—worked.

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