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 27

Question 260

A risk review at a retail network focuses on preventing this issue again: An SOC receives a FortiSASE Web Filter log for a blocked phishing category but labels it as an antivirus malware detection. Which recurring control is most suitable?

  1. Define forensic attribution and privacy requirements before selecting log anonymization settings.
  2. Require actual DLP enforcement action and session outcome before assigning incident severity.
  3. Review configured IPS actions and resulting event disposition during alert triage.
  4. Require profile type and disposition fields in threat case triage.

Explanation

Correct Answer

D:

Require profile type and disposition fields in threat case triage. This control reduces recurrence of the documented mechanism: Different FortiSASE security profiles generate different evidence about threats. It creates a repeatable check around the needed response: Classify the event by actual log type, profile, category and action before raising an incident.

Incorrect Answers

A:

Define forensic attribution and privacy requirements before selecting log anonymization settings. That safeguard addresses another potential failure: The SOC receives an external log copy with missing source identities due to anonymization settings and assumes all events came from the same user. It is not the most targeted recurring control for the described cause: Different FortiSASE security profiles generate different evidence about threats.

B:

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: Different FortiSASE security profiles generate different evidence about threats.

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: Different FortiSASE security profiles generate different evidence about threats.

Question 261

During an incident triage, an administrator reports at a logistics office: A failover test shows Internet reachability succeeds through the alternate ISP but the default DNS resolver is reachable only through the failed primary provider. What should the team change or investigate FIRST?

  1. Reconcile route distance, priority, and zone route design so the approved SD-WAN route wins.
  2. Configure reachable DNS resolvers or an appropriate surviving DNS route for both SD-WAN failure states.
  3. Add a narrowly scoped firewall policy for the correct private overlay zone and application destinations.
  4. Correct the firewall rule's actual LAN ingress zone while retaining the SD-WAN zone for egress.

Explanation

Correct Answer

B:

Configure reachable DNS resolvers or an appropriate surviving DNS route for both SD-WAN failure states. This is the most direct response to the stated incident: 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 technical mechanism is: Application reachability can fail from DNS path dependencies even when SD-WAN transport works. Confirmation requires: Client name resolution and HTTPS access both succeed during primary and backup link tests.

Incorrect Answers

A:

Reconcile route distance, priority, and zone route design so the approved SD-WAN route wins. That could address a different issue in the same blueprint area: 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. It does not directly correct the given incident, whose decisive mechanism is: Application reachability can fail from DNS path dependencies even when SD-WAN transport works.

C:

Add a narrowly scoped firewall policy for the correct private overlay zone and application destinations. That could address a different issue in the same blueprint area: 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. It does not directly correct the given incident, whose decisive mechanism is: Application reachability can fail from DNS path dependencies even when SD-WAN transport works.

D:

Correct the firewall rule's actual LAN ingress zone while retaining the SD-WAN zone for egress. That could address a different issue in the same blueprint area: An engineer enables SD-WAN but points the Internet firewall rule at the wrong source zone after moving the internal LAN port to a new VLAN. It does not directly correct the given incident, whose decisive mechanism is: Application reachability can fail from DNS path dependencies even when SD-WAN transport works.

Question 262

Following remediation at a logistics office, engineers revisit: A failover test shows Internet reachability succeeds through the alternate ISP but the default DNS resolver is reachable only through the failed primary provider. Which observation would BEST prove the specific issue is resolved?

  1. Local FortiGate requests and client sessions follow their separately documented routing paths.
  2. A sample office host matches the permit while unrelated subnets remain denied.
  3. Client name resolution and HTTPS access both succeed during primary and backup link tests.
  4. Configuration validation succeeds and a rule diagnostic resolves a real member with expected egress.

Explanation

Correct Answer

C:

Client name resolution and HTTPS access both succeed during primary and backup link tests. This evidence directly tests the intended corrective action: Configure reachable DNS resolvers or an appropriate surviving DNS route for both SD-WAN failure states. It confirms the failure mechanism—Application reachability can fail from DNS path dependencies even when SD-WAN transport works.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Local FortiGate requests and client sessions follow their separately documented routing paths. This would verify resolution of a different case: A FortiGate uses an SD-WAN zone for office traffic while FortiGate-originated DNS probes follow an unrelated management path, so user and device tests disagree. It does not show that the reported issue was fixed or that its intended action—Configure reachable DNS resolvers or an appropriate surviving DNS route for both SD-WAN failure states.—worked.

B:

A sample office host matches the permit while unrelated subnets remain denied. This would verify resolution of a different case: 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 does not show that the reported issue was fixed or that its intended action—Configure reachable DNS resolvers or an appropriate surviving DNS route for both SD-WAN failure states.—worked.

D:

Configuration validation succeeds and a rule diagnostic resolves a real member with expected egress. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Configure reachable DNS resolvers or an appropriate surviving DNS route for both SD-WAN failure states.—worked.

Question 263

During an incident triage, this condition is reported: A failover test shows Internet reachability succeeds through the alternate ISP but the default DNS resolver is reachable only through the failed primary provider. Which technical explanation MOST directly accounts for the failure?

  1. Competing static routes can alter forwarding before the SD-WAN strategy is evaluated as expected.
  2. An unscoped all-sources Internet rule can redirect traffic outside intended trust boundaries.
  3. Successful SD-WAN path selection does not guarantee the NAT address is routable through that ISP.
  4. Application reachability can fail from DNS path dependencies even when SD-WAN transport works.

Explanation

Correct Answer

D:

Application reachability can fail from DNS path dependencies even when SD-WAN transport works. This explains why the reported condition occurs: 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 targeted correction is: Configure reachable DNS resolvers or an appropriate surviving DNS route for both SD-WAN failure states.

Incorrect Answers

A:

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.

B:

An unscoped all-sources Internet rule can redirect traffic outside intended trust boundaries. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

C:

Successful SD-WAN path selection does not guarantee the NAT address is routable through that ISP. This mechanism instead explains a separate problem: A branch internet edge is changed from a single WAN link to dual links while the old SNAT pool remains usable only on the primary ISP. The current incident requires the more directly applicable cause stated by the correct option.

Question 264

During a post-incident review at a logistics office, the original problem was: A failover test shows Internet reachability succeeds through the alternate ISP but the default DNS resolver is reachable only through the failed primary provider. Which preventive practice most directly addresses its cause?

  1. Test DNS resolution separately from ping and transport during link failover exercises.
  2. Require representative guest and production negative tests before activating shared DIA rules.
  3. Include per-member NAT and reverse-path checks in dual-ISP migration regression tests.
  4. Validate FIB routes alongside zone and member configuration at every site acceptance test.

Explanation

Correct Answer

A:

Test DNS resolution separately from ping and transport during link failover exercises. This control reduces recurrence of the documented mechanism: Application reachability can fail from DNS path dependencies even when SD-WAN transport works. It creates a repeatable check around the needed response: Configure reachable DNS resolvers or an appropriate surviving DNS route for both SD-WAN failure states.

Incorrect Answers

B:

Require representative guest and production negative tests before activating shared DIA rules. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Application reachability can fail from DNS path dependencies even when SD-WAN transport works.

C:

Include per-member NAT and reverse-path checks in dual-ISP migration regression tests. That safeguard addresses another potential failure: A branch internet edge is changed from a single WAN link to dual links while the old SNAT pool remains usable only on the primary ISP. It is not the most targeted recurring control for the described cause: Application reachability can fail from DNS path dependencies even when SD-WAN transport works.

D:

Validate FIB routes alongside zone and member configuration at every site acceptance test. That safeguard addresses another potential failure: A remote site adds both ISP links to SD-WAN but omits a default static route toward the zone, leaving client traffic with no usable route. It is not the most targeted recurring control for the described cause: Application reachability can fail from DNS path dependencies even when SD-WAN transport works.

Question 265

A firewall operations team at a manufacturing plant encounters the following during a controlled failover drill: An engineer enables load-balancing mode expecting packet-level striping of one TCP session, then diagnoses normal single-link session affinity as a fault. Which action most directly restores the approved security outcome?

  1. Restrict the private application rule to appropriate overlay members and verify the destination route and firewall permit.
  2. Use a quality-aware SD-WAN rule strategy with relevant jitter SLA matching for video traffic.
  3. Set expectations for the supported per-session hash or balancing method and select a method appropriate to traffic distribution.
  4. Replace the broad category match with the intended recognized application or application object.

Explanation

Correct Answer

C:

Set expectations for the supported per-session hash or balancing method and select a method appropriate to traffic distribution. This is the most direct response to the stated incident: An engineer enables load-balancing mode expecting packet-level striping of one TCP session, then diagnoses normal single-link session affinity as a fault. The technical mechanism is: Most SD-WAN load balancing strategies select paths at session granularity rather than striping every packet. Confirmation requires: Multiple independent test sessions distribute as configured while each session remains coherent.

Incorrect Answers

A:

Restrict the private application rule to appropriate overlay members and verify the destination route and firewall permit. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Most SD-WAN load balancing strategies select paths at session granularity rather than striping every packet.

B:

Use a quality-aware SD-WAN rule strategy with relevant jitter SLA matching for video traffic. That could address a different issue in the same blueprint area: A video collaboration app must favor low jitter but the rule uses Manual preference for a congested inexpensive circuit. It does not directly correct the given incident, whose decisive mechanism is: Most SD-WAN load balancing strategies select paths at session granularity rather than striping every packet.

D:

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: Most SD-WAN load balancing strategies select paths at session granularity rather than striping every packet.

Question 266

An operations review at a manufacturing plant has corrected: An engineer enables load-balancing mode expecting packet-level striping of one TCP session, then diagnoses normal single-link session affinity as a fault. Which observation specifically confirms success?

  1. Controlled mixed traffic shows the voice application receives priority while bulk transfers are limited.
  2. The approved conferencing app takes the exception path while other social applications do not.
  3. New SaaS sessions match the intended rule instead of the implicit catch-all.
  4. Multiple independent test sessions distribute as configured while each session remains coherent.

Explanation

Correct Answer

D:

Multiple independent test sessions distribute as configured while each session remains coherent. This evidence directly tests the intended corrective action: Set expectations for the supported per-session hash or balancing method and select a method appropriate to traffic distribution. It confirms the failure mechanism—Most SD-WAN load balancing strategies select paths at session granularity rather than striping every packet.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Set expectations for the supported per-session hash or balancing method and select a method appropriate to traffic distribution.—worked.

B:

The approved conferencing app takes the exception path while other social applications do not. This would verify resolution of a different case: An administrator configures a rule matching application category Social Networking while the approved exception is only for a named conferencing application. It does not show that the reported issue was fixed or that its intended action—Set expectations for the supported per-session hash or balancing method and select a method appropriate to traffic distribution.—worked.

C:

New SaaS sessions match the intended rule instead of the implicit catch-all. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Set expectations for the supported per-session hash or balancing method and select a method appropriate to traffic distribution.—worked.

Question 267

At a manufacturing plant, investigators observe: An engineer enables load-balancing mode expecting packet-level striping of one TCP session, then diagnoses normal single-link session affinity as a fault. Which underlying policy or system mechanism BEST explains this behavior?

  1. Most SD-WAN load balancing strategies select paths at session granularity rather than striping every packet.
  2. Broad Internet-service categories can capture unrelated destinations.
  3. Address-only rule criteria drift as cloud service destinations change.
  4. Path selection alone does not reserve link bandwidth under contention.

Explanation

Correct Answer

A:

Most SD-WAN load balancing strategies select paths at session granularity rather than striping every packet. This explains why the reported condition occurs: An engineer enables load-balancing mode expecting packet-level striping of one TCP session, then diagnoses normal single-link session affinity as a fault. The targeted correction is: Set expectations for the supported per-session hash or balancing method and select a method appropriate to traffic distribution.

Incorrect Answers

B:

Broad Internet-service categories can capture unrelated destinations. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

C:

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.

D:

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.

Question 268

An operations group at a manufacturing plant resolved: An engineer enables load-balancing mode expecting packet-level striping of one TCP session, then diagnoses normal single-link session affinity as a fault. Which ongoing safeguard should become part of its change process?

  1. Classify source-IP-sensitive applications before choosing load-balancing strategies.
  2. Document the balancing unit and validate with multiple sessions and clients.
  3. Test boundary source addresses for each overlapping SD-WAN rule after subnet changes.
  4. Review rule precedence and match counters whenever inserting new steering policies.

Explanation

Correct Answer

B:

Document the balancing unit and validate with multiple sessions and clients. This control reduces recurrence of the documented mechanism: Most SD-WAN load balancing strategies select paths at session granularity rather than striping every packet. It creates a repeatable check around the needed response: Set expectations for the supported per-session hash or balancing method and select a method appropriate to traffic distribution.

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: Most SD-WAN load balancing strategies select paths at session granularity rather than striping every packet.

C:

Test boundary source addresses for each overlapping SD-WAN rule after subnet changes. That safeguard addresses another potential failure: A high-priority rule for guest Internet traffic mistakenly matches the corporate workstation source segment and sends trusted users over a limited guest ISP. It is not the most targeted recurring control for the described cause: Most SD-WAN load balancing strategies select paths at session granularity rather than striping every packet.

D:

Review rule precedence and match counters whenever inserting new steering policies. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Most SD-WAN load balancing strategies select paths at session granularity rather than striping every packet.

Question 269

At a corporate headquarters, a security analyst is reviewing this failure during a configuration rollout: An admin selects a PoP for remote users based only on geographic distance even though upstream ISP routing gives that location poor responsiveness. What is the MOST appropriate FIRST corrective step?

  1. Define the approved regional identity group and associate its specific security inspection policy.
  2. Reconcile active entitlements and the planned user population before extending invitations.
  3. Migrate changes to individually attributable administrators with supported audit logging enabled.
  4. Evaluate actual user-to-PoP latency and supported service-selection options before final assignment.

Explanation

Correct Answer

D:

Evaluate actual user-to-PoP latency and supported service-selection options before final assignment. This is the most direct response to the stated incident: An admin selects a PoP for remote users based only on geographic distance even though upstream ISP routing gives that location poor responsiveness. The technical mechanism is: Geographical proximity does not prove low operational round-trip latency. Confirmation requires: Test users connect through a reachable PoP with response measurements meeting the approved target.

Incorrect Answers

A:

Define the approved regional identity group and associate its specific security inspection policy. That could address a different issue in the same blueprint area: A regional office needs stricter web filtering than headquarters, but its users are placed into a generic global group with unchanged default policy. It does not directly correct the given incident, whose decisive mechanism is: Geographical proximity does not prove low operational round-trip latency.

B:

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: Geographical proximity does not prove low operational round-trip latency.

C:

Migrate changes to individually attributable administrators with supported audit logging enabled. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Geographical proximity does not prove low operational round-trip latency.

Question 270

During follow-up testing at a corporate headquarters, the original fault was: An admin selects a PoP for remote users based only on geographic distance even though upstream ISP routing gives that location poor responsiveness. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. Test users connect through a reachable PoP with response measurements meeting the approved target.
  2. Migrated test users retain permitted access and previous policy is recoverable if needed.
  3. Named admins sign in with appropriate privilege while unauthorized use of the shared credential is blocked.
  4. Helpdesk accounts can inspect authorized status while policy edits require designated administrators.

Explanation

Correct Answer

A:

Test users connect through a reachable PoP with response measurements meeting the approved target. This evidence directly tests the intended corrective action: Evaluate actual user-to-PoP latency and supported service-selection options before final assignment. It confirms the failure mechanism—Geographical proximity does not prove low operational round-trip latency.—has been addressed in the actual affected flow.

Incorrect Answers

B:

Migrated test users retain permitted access and previous policy is recoverable if needed. This would verify resolution of a different case: An operations team prepares to migrate an existing group to a new FortiSASE subscription while leaving policy ownership and rollback undefined. It does not show that the reported issue was fixed or that its intended action—Evaluate actual user-to-PoP latency and supported service-selection options before final assignment.—worked.

C:

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—Evaluate actual user-to-PoP latency and supported service-selection options before final assignment.—worked.

D:

Helpdesk accounts can inspect authorized status while policy edits require designated administrators. This would verify resolution of a different case: An administrator grants every helpdesk analyst full policy-change rights because some staff need to view remote user connection status. It does not show that the reported issue was fixed or that its intended action—Evaluate actual user-to-PoP latency and supported service-selection options before final assignment.—worked.

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