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 31

Question 300

An operations group at a university network resolved: An administrator sees antivirus detections in FortiSASE but lacks the affected user and device context to decide where containment is needed. Which ongoing safeguard should become part of its change process?

  1. Require actual DLP enforcement action and session outcome before assigning incident severity.
  2. Retain user/device attribution and response fields for cloud malware detections.
  3. Require endpoint confirmation before escalating download detections to executed-malware claims.
  4. Include identity events and location anomalies in FortiSASE threat hunting.

Explanation

Correct Answer

B:

Retain user/device attribution and response fields for cloud malware detections. This control reduces recurrence of the documented mechanism: Isolated malware events do not provide full scope without identity and session correlation. It creates a repeatable check around the needed response: Correlate malware log entries with user identity, endpoint, session, file metadata and action.

Incorrect Answers

A:

Require actual DLP enforcement action and session outcome before assigning incident severity. That safeguard addresses another potential failure: A DLP violation is reported for a synthetic payment identifier, but the SOC incorrectly concludes the file was exfiltrated without checking the enforcement action. It is not the most targeted recurring control for the described cause: Isolated malware events do not provide full scope without identity and session correlation.

C:

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: Isolated malware events do not provide full scope without identity and session correlation.

D:

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: Isolated malware events do not provide full scope without identity and session correlation.

Question 301

At a hospital campus, a security analyst is reviewing this failure during a configuration rollout: A branch policy allows only one SD-WAN zone while a new private overlay zone is created for internal applications, leaving internal site traffic denied. What is the MOST appropriate FIRST corrective step?

  1. Remove or correct the stale policy route so the approved SD-WAN route and rules can select the outbound path.
  2. Constrain the Internet-bound firewall rule and SD-WAN steering rule by the guest source segment and approved destinations.
  3. Align the deployed zone and member references to the actual supported interface identifiers before pushing.
  4. Add a narrowly scoped firewall policy for the correct private overlay zone and application destinations.

Explanation

Correct Answer

D:

Add a narrowly scoped firewall policy for the correct private overlay zone and application destinations. This is the most direct response to the stated incident: A branch policy allows only one SD-WAN zone while a new private overlay zone is created for internal applications, leaving internal site traffic denied. The technical mechanism is: Establishing an SD-WAN zone does not automatically authorize traffic to or from that zone. Confirmation requires: Private application sessions traverse the intended overlay with the proper security logging.

Incorrect Answers

A:

Remove or correct the stale policy route so the approved SD-WAN route and rules can select the outbound path. That could address a different issue in the same blueprint area: A new branch configures link monitoring but still sends Internet traffic through a legacy policy route bound to an obsolete gateway. It does not directly correct the given incident, whose decisive mechanism is: Establishing an SD-WAN zone does not automatically authorize traffic to or from that zone.

B:

Constrain the Internet-bound firewall rule and SD-WAN steering rule by the guest source segment and approved destinations. That could address a different issue in the same blueprint area: An operator uses a policy rule for all Internet users when only approved guest users should employ direct Internet access, causing internal workloads to bypass private inspection. It does not directly correct the given incident, whose decisive mechanism is: Establishing an SD-WAN zone does not automatically authorize traffic to or from that zone.

C:

Align the deployed zone and member references to the actual supported interface identifiers before pushing. That could address a different issue in the same blueprint area: A branch upgrades FortiOS and observes SD-WAN rule policy using an old physical egress interface name no longer valid in its deployment template. It does not directly correct the given incident, whose decisive mechanism is: Establishing an SD-WAN zone does not automatically authorize traffic to or from that zone.

Question 302

During follow-up testing at a hospital campus, the original fault was: A branch policy allows only one SD-WAN zone while a new private overlay zone is created for internal applications, leaving internal site traffic denied. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. Private application sessions traverse the intended overlay with the proper security logging.
  2. Client name resolution and HTTPS access both succeed during primary and backup link tests.
  3. A test client accesses the Internet through the zone and steering follows the enabled member selection.
  4. A route diagnostic shows sessions are evaluated using the intended SD-WAN member rather than the old gateway.

Explanation

Correct Answer

A:

Private application sessions traverse the intended overlay with the proper security logging. This evidence directly tests the intended corrective action: Add a narrowly scoped firewall policy for the correct private overlay zone and application destinations. It confirms the failure mechanism—Establishing an SD-WAN zone does not automatically authorize traffic to or from that zone.—has been addressed in the actual affected flow.

Incorrect Answers

B:

Client name resolution and HTTPS access both succeed during primary and backup link tests. This would verify resolution of a different case: A failover test shows Internet reachability succeeds through the alternate ISP but the default DNS resolver is reachable only through the failed primary provider. It does not show that the reported issue was fixed or that its intended action—Add a narrowly scoped firewall policy for the correct private overlay zone and application destinations.—worked.

C:

A test client accesses the Internet through the zone and steering follows the enabled member selection. This would verify resolution of a different case: A two-ISP FortiGate has working physical WAN interfaces but no SD-WAN configuration, so a branch cannot steer applications by link health. It does not show that the reported issue was fixed or that its intended action—Add a narrowly scoped firewall policy for the correct private overlay zone and application destinations.—worked.

D:

A route diagnostic shows sessions are evaluated using the intended SD-WAN member rather than the old gateway. This would verify resolution of a different case: A new branch configures link monitoring but still sends Internet traffic through a legacy policy route bound to an obsolete gateway. It does not show that the reported issue was fixed or that its intended action—Add a narrowly scoped firewall policy for the correct private overlay zone and application destinations.—worked.

Question 303

The incident investigation at a hospital campus records: A branch policy allows only one SD-WAN zone while a new private overlay zone is created for internal applications, leaving internal site traffic denied. Which mechanism provides the strongest explanation?

  1. Application reachability can fail from DNS path dependencies even when SD-WAN transport works.
  2. Establishing an SD-WAN zone does not automatically authorize traffic to or from that zone.
  3. Central rule reuse requires correct per-device interface resolution.
  4. Competing static routes can alter forwarding before the SD-WAN strategy is evaluated as expected.

Explanation

Correct Answer

B:

Establishing an SD-WAN zone does not automatically authorize traffic to or from that zone. This explains why the reported condition occurs: A branch policy allows only one SD-WAN zone while a new private overlay zone is created for internal applications, leaving internal site traffic denied. The targeted correction is: Add a narrowly scoped firewall policy for the correct private overlay zone and application destinations.

Incorrect Answers

A:

Application reachability can fail from DNS path dependencies even when SD-WAN transport works. This mechanism instead explains a separate problem: A failover test shows Internet reachability succeeds through the alternate ISP but the default DNS resolver is reachable only through the failed primary provider. The current incident requires the more directly applicable cause stated by the correct option.

C:

Central rule reuse requires correct per-device interface resolution. This mechanism instead explains a separate problem: A central FortiManager template pushes a new SD-WAN rule but fails on one branch because its secondary interface exists under a different name. The current incident requires the more directly applicable cause stated by the correct option.

D:

Competing static routes can alter forwarding before the SD-WAN strategy is evaluated as expected. This mechanism instead explains a separate problem: Two WAN links share a configured zone, but a second default route via a physical member is preferred and bypasses the planned SD-WAN gateway abstraction. The current incident requires the more directly applicable cause stated by the correct option.

Question 304

After a corrective change at a hospital campus, the team documents: A branch policy allows only one SD-WAN zone while a new private overlay zone is created for internal applications, leaving internal site traffic denied. Which repeatable control BEST prevents a recurrence?

  1. Test a minimal two-member SD-WAN path before rolling out application-specific rules.
  2. Validate source network inventory and firewall object coverage when adding new VLANs.
  3. Pair each new SD-WAN zone with an explicit least-privilege security-policy review.
  4. Document and validate zone purpose before adding underlay or overlay members.

Explanation

Correct Answer

C:

Pair each new SD-WAN zone with an explicit least-privilege security-policy review. This control reduces recurrence of the documented mechanism: Establishing an SD-WAN zone does not automatically authorize traffic to or from that zone. It creates a repeatable check around the needed response: Add a narrowly scoped firewall policy for the correct private overlay zone and application destinations.

Incorrect Answers

A:

Test a minimal two-member SD-WAN path before rolling out application-specific rules. That safeguard addresses another potential failure: A two-ISP FortiGate has working physical WAN interfaces but no SD-WAN configuration, so a branch cannot steer applications by link health. It is not the most targeted recurring control for the described cause: Establishing an SD-WAN zone does not automatically authorize traffic to or from that zone.

B:

Validate source network inventory and firewall object coverage when adding new VLANs. That safeguard addresses another potential failure: A monitoring dashboard shows multiple healthy WAN members but a test office has no outbound traffic because its LAN network is absent from the configured firewall source address objects. It is not the most targeted recurring control for the described cause: Establishing an SD-WAN zone does not automatically authorize traffic to or from that zone.

D:

Document and validate zone purpose before adding underlay or overlay members. That safeguard addresses another potential failure: An engineer places both an Internet DIA link and an IPsec overlay into one undifferentiated zone, making a direct Internet policy unexpectedly select the overlay. It is not the most targeted recurring control for the described cause: Establishing an SD-WAN zone does not automatically authorize traffic to or from that zone.

Question 305

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

  1. Correct the intended destination address or service match for the required Internet traffic.
  2. Adjust the supported minimum eligible-SLA member requirement to the approved continuity threshold.
  3. Update the destination or supported Internet Service Database criteria to represent the currently approved SaaS endpoint.
  4. Set actual approved link costs and preference appropriate to metered versus fixed services.

Explanation

Correct Answer

A:

Correct the intended destination address or service match for the required Internet traffic. This is the most direct response to the stated incident: 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 technical mechanism is: An overly narrow or incorrect destination object makes a valid rule ineffective. Confirmation requires: Traffic logs and SD-WAN service diagnostics show the intended rule matching real destinations.

Incorrect Answers

B:

Adjust the supported minimum eligible-SLA member requirement to the approved continuity threshold. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: An overly narrow or incorrect destination object makes a valid rule ineffective.

C:

Update the destination or supported Internet Service Database criteria to represent the currently approved SaaS endpoint. That could address a different issue in the same blueprint area: 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. It does not directly correct the given incident, whose decisive mechanism is: An overly narrow or incorrect destination object makes a valid rule ineffective.

D:

Set actual approved link costs and preference appropriate to metered versus fixed services. That could address a different issue in the same blueprint area: 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 does not directly correct the given incident, whose decisive mechanism is: An overly narrow or incorrect destination object makes a valid rule ineffective.

Question 306

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

  1. Normal healthy sessions favor broadband while cellular is selected only under permitted conditions.
  2. Traffic logs and SD-WAN service diagnostics show the intended rule matching real destinations.
  3. Controlled mixed traffic shows the voice application receives priority while bulk transfers are limited.
  4. The selected link matches the configured first eligible priority when cost and SLA results tie.

Explanation

Correct Answer

B:

Traffic logs and SD-WAN service diagnostics show the intended rule matching real destinations. This evidence directly tests the intended corrective action: Correct the intended destination address or service match for the required Internet traffic. It confirms the failure mechanism—An overly narrow or incorrect destination object makes a valid rule ineffective.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Normal healthy sessions favor broadband while cellular is selected only under permitted conditions. This would verify resolution of a different case: 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 does not show that the reported issue was fixed or that its intended action—Correct the intended destination address or service match for the required Internet traffic.—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—Correct the intended destination address or service match for the required Internet traffic.—worked.

D:

The selected link matches the configured first eligible priority when cost and SLA results tie. This would verify resolution of a different case: Two ISP links both meet a rule's SLA target and have identical costs, but traffic favors the unexpected one because member priority order is reversed. It does not show that the reported issue was fixed or that its intended action—Correct the intended destination address or service match for the required Internet traffic.—worked.

Question 307

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

  1. Path selection alone does not reserve link bandwidth under contention.
  2. The best path metric for latency-sensitive media may be inappropriate for bulk transfer applications.
  3. An overly narrow or incorrect destination object makes a valid rule ineffective.
  4. SD-WAN service rules have ordered matching and an earlier broad rule can shadow a narrow one.

Explanation

Correct Answer

C:

An overly narrow or incorrect destination object makes a valid rule ineffective. This explains why the reported condition occurs: 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 targeted correction is: Correct the intended destination address or service match for the required Internet traffic.

Incorrect Answers

A:

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.

B:

The best path metric for latency-sensitive media may be inappropriate for bulk transfer applications. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

D:

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.

Question 308

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

  1. Retire old member IDs from every dependent rule during carrier migration.
  2. Audit private-data rule eligible members against network encryption requirements.
  3. Review ISDB rule IDs and log sample service matching before release.
  4. Require representative destination match tests for every new service rule.

Explanation

Correct Answer

D:

Require representative destination match tests for every new service rule. This control reduces recurrence of the documented mechanism: An overly narrow or incorrect destination object makes a valid rule ineffective. It creates a repeatable check around the needed response: Correct the intended destination address or service match for the required Internet traffic.

Incorrect Answers

A:

Retire old member IDs from every dependent rule during carrier migration. That safeguard addresses another potential failure: An SD-WAN rule uses a manual preferred member that's no longer provisioned after carrier cutover; otherwise healthy links are ignored. It is not the most targeted recurring control for the described cause: An overly narrow or incorrect destination object makes a valid rule ineffective.

B:

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: An overly narrow or incorrect destination object makes a valid rule ineffective.

C:

Review ISDB rule IDs and log sample service matching before release. That safeguard addresses another potential failure: A branch configures an SD-WAN rule with an Internet-service database match intended for cloud storage but chooses the broad all-Internet service definition. It is not the most targeted recurring control for the described cause: An overly narrow or incorrect destination object makes a valid rule ineffective.

Question 309

During a production service incident, an administrator reports at a logistics office: A security change is saved in FortiSASE management but not deployed or activated through the required service workflow, so remote users still see old behavior. What should the team change or investigate FIRST?

  1. Confirm tenant identity and switch to the authorized tenant before editing configuration or deploying policy.
  2. Complete the approved publish or deploy operation and confirm the active policy on a test session.
  3. Choose a supported PoP or service location and subscription design that satisfies the documented sovereignty requirements.
  4. Reconcile active entitlements and the planned user population before extending invitations.

Explanation

Correct Answer

B:

Complete the approved publish or deploy operation and confirm the active policy on a test session. This is the most direct response to the stated incident: A security change is saved in FortiSASE management but not deployed or activated through the required service workflow, so remote users still see old behavior. The technical mechanism is: Saved cloud configuration and running user-facing enforcement may represent separate states. Confirmation requires: The active service policy revision reflects the approved change and generates expected events.

Incorrect Answers

A:

Confirm tenant identity and switch to the authorized tenant before editing configuration or deploying policy. That could address a different issue in the same blueprint area: A managed service provider accidentally opens another customer's FortiSASE tenant because both tenants use similar display names. It does not directly correct the given incident, whose decisive mechanism is: Saved cloud configuration and running user-facing enforcement may represent separate states.

C:

Choose a supported PoP or service location and subscription design that satisfies the documented sovereignty requirements. That could address a different issue in the same blueprint area: An enterprise with a strict data-residency requirement selects a FortiSASE region solely for lower latency without assessing where relevant security logs and data are processed. It does not directly correct the given incident, whose decisive mechanism is: Saved cloud configuration and running user-facing enforcement may represent separate states.

D:

Reconcile active entitlements and the planned user population before extending invitations. That could address a different issue in the same blueprint area: A FortiSASE tenant's administrator sees a warning about insufficient user licensing but continues issuing enrollment invitations that fail at authentication. It does not directly correct the given incident, whose decisive mechanism is: Saved cloud configuration and running user-facing enforcement may represent separate states.

Question 310

Following remediation at a logistics office, engineers revisit: A security change is saved in FortiSASE management but not deployed or activated through the required service workflow, so remote users still see old behavior. Which observation would BEST prove the specific issue is resolved?

  1. Each authorized policy modification is attributed to an identifiable operator in the relevant audit record.
  2. Named admins sign in with appropriate privilege while unauthorized use of the shared credential is blocked.
  3. The active service policy revision reflects the approved change and generates expected events.
  4. A scoped test shows department users receive the rule while other managed groups remain unchanged.

Explanation

Correct Answer

C:

The active service policy revision reflects the approved change and generates expected events. This evidence directly tests the intended corrective action: Complete the approved publish or deploy operation and confirm the active policy on a test session. It confirms the failure mechanism—Saved cloud configuration and running user-facing enforcement may represent separate states.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Each authorized policy modification is attributed to an identifiable operator in the relevant audit record. This would verify resolution of a different case: A security operations center cannot trace who altered a FortiSASE inspection rule because several operators log in using the same administrator account. It does not show that the reported issue was fixed or that its intended action—Complete the approved publish or deploy operation and confirm the active policy on a test session.—worked.

B:

Named admins sign in with appropriate privilege while unauthorized use of the shared credential is blocked. This would verify resolution of a different case: A newly deployed FortiSASE tenant trusts a broad default administrative account even after named administrators receive individual credentials. It does not show that the reported issue was fixed or that its intended action—Complete the approved publish or deploy operation and confirm the active policy on a test session.—worked.

D:

A scoped test shows department users receive the rule while other managed groups remain unchanged. This would verify resolution of a different case: An administrator deploys a cloud policy from a shared template while assuming it cannot affect devices or users outside one department's tenant group. It does not show that the reported issue was fixed or that its intended action—Complete the approved publish or deploy operation and confirm the active policy on a test session.—worked.

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