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 13

Question 120

During a post-incident review at a logistics office, the original problem was: A branch's rule switches from best-quality to fallback during one hour, but the report includes only successful sessions and omits SLA state changes. Which preventive practice most directly addresses its cause?

  1. Collect and retain both traffic and health events for failover analysis.
  2. Use session IDs or supported correlation keys when measuring failover connection counts.
  3. Retain performance SLA history alongside application experience incidents.
  4. Label and report implicit rule traffic separately from named application steering.

Explanation

Correct Answer

A:

Collect and retain both traffic and health events for failover analysis. This control reduces recurrence of the documented mechanism: Session allow logs and SLA transition events document different parts of path selection. It creates a repeatable check around the needed response: Correlate SD-WAN event logs with session traffic and health-check state transitions for that window.

Incorrect Answers

B:

Use session IDs or supported correlation keys when measuring failover connection counts. That safeguard addresses another potential failure: A site sees duplicate-looking flow logs for retransmissions during an SD-WAN failover, and analysts count them as distinct user sessions. It is not the most targeted recurring control for the described cause: Session allow logs and SLA transition events document different parts of path selection.

C:

Retain performance SLA history alongside application experience incidents. That safeguard addresses another potential failure: Voice complaints occur after WAN jitter spikes but the incident review relies on total traffic-byte reports without any performance SLA history. It is not the most targeted recurring control for the described cause: Session allow logs and SLA transition events document different parts of path selection.

D:

Label and report implicit rule traffic separately from named application steering. That safeguard addresses another potential failure: An analyst confuses implicit SD-WAN rule hits with explicit application-specific rule selection during a monthly performance review. It is not the most targeted recurring control for the described cause: Session allow logs and SLA transition events document different parts of path selection.

Question 121

A firewall operations team at a manufacturing plant encounters the following during a predeployment acceptance test: A backup LTE interface is physically up but never added as an SD-WAN member, so WAN failure does not activate cellular continuity. Which action most directly restores the approved security outcome?

  1. Separate overlay and underlay members into zones appropriate to their security and routing roles.
  2. Create appropriate outbound source translation for each supported SD-WAN egress path and test return traffic.
  3. Add the supported LTE interface as a monitored member with the intended zone and backup preference.
  4. Enable the approved backup member and confirm interface link, gateway, and health status.

Explanation

Correct Answer

C:

Add the supported LTE interface as a monitored member with the intended zone and backup preference. This is the most direct response to the stated incident: A backup LTE interface is physically up but never added as an SD-WAN member, so WAN failure does not activate cellular continuity. The technical mechanism is: An interface cannot be selected by an SD-WAN rule until it is included as an eligible member. Confirmation requires: Disabling both fixed-line paths permits controlled traffic through the cellular backup under policy.

Incorrect Answers

A:

Separate overlay and underlay members into zones appropriate to their security and routing roles. That could address a different issue in the same blueprint area: 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 does not directly correct the given incident, whose decisive mechanism is: An interface cannot be selected by an SD-WAN rule until it is included as an eligible member.

B:

Create appropriate outbound source translation for each supported SD-WAN egress path and test return traffic. That could address a different issue in the same blueprint area: 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 does not directly correct the given incident, whose decisive mechanism is: An interface cannot be selected by an SD-WAN rule until it is included as an eligible member.

D:

Enable the approved backup member and confirm interface link, gateway, and health status. That could address a different issue in the same blueprint area: An engineer treats all link members as active after adding them but a new backup member is administratively disabled in its SD-WAN entry. It does not directly correct the given incident, whose decisive mechanism is: An interface cannot be selected by an SD-WAN rule until it is included as an eligible member.

Question 122

An operations review at a manufacturing plant has corrected: A backup LTE interface is physically up but never added as an SD-WAN member, so WAN failure does not activate cellular continuity. Which observation specifically confirms success?

  1. Configuration validation succeeds and a rule diagnostic resolves a real member with expected egress.
  2. Connections use translated addresses valid for their selected ISP and return packets reach the FortiGate.
  3. FortiManager device validation succeeds and both branch paths appear as intended SD-WAN members.
  4. Disabling both fixed-line paths permits controlled traffic through the cellular backup under policy.

Explanation

Correct Answer

D:

Disabling both fixed-line paths permits controlled traffic through the cellular backup under policy. This evidence directly tests the intended corrective action: Add the supported LTE interface as a monitored member with the intended zone and backup preference. It confirms the failure mechanism—An interface cannot be selected by an SD-WAN rule until it is included as an eligible member.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Add the supported LTE interface as a monitored member with the intended zone and backup preference.—worked.

B:

Connections use translated addresses valid for their selected ISP and return packets reach the FortiGate. This would verify resolution of a different case: 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 does not show that the reported issue was fixed or that its intended action—Add the supported LTE interface as a monitored member with the intended zone and backup preference.—worked.

C:

FortiManager device validation succeeds and both branch paths appear as intended SD-WAN members. This would verify resolution of a different case: A central FortiManager template pushes a new SD-WAN rule but fails on one branch because its secondary interface exists under a different name. It does not show that the reported issue was fixed or that its intended action—Add the supported LTE interface as a monitored member with the intended zone and backup preference.—worked.

Question 123

At a manufacturing plant, investigators observe: A backup LTE interface is physically up but never added as an SD-WAN member, so WAN failure does not activate cellular continuity. Which underlying policy or system mechanism BEST explains this behavior?

  1. An interface cannot be selected by an SD-WAN rule until it is included as an eligible member.
  2. A configured but administratively disabled member is not a live candidate for steering.
  3. Competing static routes can alter forwarding before the SD-WAN strategy is evaluated as expected.
  4. Membership alone does not install every route needed for off-subnet forwarding.

Explanation

Correct Answer

A:

An interface cannot be selected by an SD-WAN rule until it is included as an eligible member. This explains why the reported condition occurs: A backup LTE interface is physically up but never added as an SD-WAN member, so WAN failure does not activate cellular continuity. The targeted correction is: Add the supported LTE interface as a monitored member with the intended zone and backup preference.

Incorrect Answers

B:

A configured but administratively disabled member is not a live candidate for steering. This mechanism instead explains a separate problem: An engineer treats all link members as active after adding them but a new backup member is administratively disabled in its SD-WAN entry. The current incident requires the more directly applicable cause stated by the correct option.

C:

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.

D:

Membership alone does not install every route needed for off-subnet forwarding. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

Question 124

An operations group at a manufacturing plant resolved: A backup LTE interface is physically up but never added as an SD-WAN member, so WAN failure does not activate cellular continuity. Which ongoing safeguard should become part of its change process?

  1. Pair each new SD-WAN zone with an explicit least-privilege security-policy review.
  2. Check actual member inventory against every documented backup medium during failover rehearsals.
  3. Include per-member NAT and reverse-path checks in dual-ISP migration regression tests.
  4. Review member selection strategy separately from health-check configuration at policy signoff.

Explanation

Correct Answer

B:

Check actual member inventory against every documented backup medium during failover rehearsals. This control reduces recurrence of the documented mechanism: An interface cannot be selected by an SD-WAN rule until it is included as an eligible member. It creates a repeatable check around the needed response: Add the supported LTE interface as a monitored member with the intended zone and backup preference.

Incorrect Answers

A:

Pair each new SD-WAN zone with an explicit least-privilege security-policy review. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: An interface cannot be selected by an SD-WAN rule until it is included as an eligible member.

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: An interface cannot be selected by an SD-WAN rule until it is included as an eligible member.

D:

Review member selection strategy separately from health-check configuration at policy signoff. That safeguard addresses another potential failure: A support engineer assumes the presence of an SD-WAN health-check means all employee traffic is being load-balanced, yet the policy uses a manual priority path. It is not the most targeted recurring control for the described cause: An interface cannot be selected by an SD-WAN rule until it is included as an eligible member.

Question 125

At a corporate headquarters, a security analyst is reviewing this failure during a planned policy migration: A payment service is set to load-balance across WAN links despite a vendor requiring a stable public source address for the entire session. What is the MOST appropriate FIRST corrective step?

  1. Use the specific current Internet-service identifier or supported destination criteria for the approved cloud service.
  2. Set actual approved link costs and preference appropriate to metered versus fixed services.
  3. Use a quality-aware SD-WAN rule strategy with relevant jitter SLA matching for video traffic.
  4. Select an appropriate fixed preferred member or session-persistent supported hash strategy for payment flows.

Explanation

Correct Answer

D:

Select an appropriate fixed preferred member or session-persistent supported hash strategy for payment flows. This is the most direct response to the stated incident: A payment service is set to load-balance across WAN links despite a vendor requiring a stable public source address for the entire session. The technical mechanism is: Inappropriate path distribution can conflict with applications bound to fixed egress identity. Confirmation requires: A test transaction maintains a stable expected source identity across its session.

Incorrect Answers

A:

Use the specific current Internet-service identifier or supported destination criteria for the approved cloud service. That could address a different issue in the same blueprint area: 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 does not directly correct the given incident, whose decisive mechanism is: Inappropriate path distribution can conflict with applications bound to fixed egress identity.

B:

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: Inappropriate path distribution can conflict with applications bound to fixed egress identity.

C:

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: Inappropriate path distribution can conflict with applications bound to fixed egress identity.

Question 126

During follow-up testing at a corporate headquarters, the original fault was: A payment service is set to load-balance across WAN links despite a vendor requiring a stable public source address for the entire session. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. A test transaction maintains a stable expected source identity across its session.
  2. A test transaction matches its SD-WAN rule and succeeds through a valid route and next hop.
  3. The tested application hits its dedicated rule ID and selects the approved private link.
  4. Multiple independent test sessions distribute as configured while each session remains coherent.

Explanation

Correct Answer

A:

A test transaction maintains a stable expected source identity across its session. This evidence directly tests the intended corrective action: Select an appropriate fixed preferred member or session-persistent supported hash strategy for payment flows. It confirms the failure mechanism—Inappropriate path distribution can conflict with applications bound to fixed egress identity.—has been addressed in the actual affected flow.

Incorrect Answers

B:

A test transaction matches its SD-WAN rule and succeeds through a valid route and next hop. This would verify resolution of a different case: A transaction flow is directed to a preferred member despite no matching route for its destination through that member, producing packet drops. It does not show that the reported issue was fixed or that its intended action—Select an appropriate fixed preferred member or session-persistent supported hash strategy for payment flows.—worked.

C:

The tested application hits its dedicated rule ID and selects the approved private link. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Select an appropriate fixed preferred member or session-persistent supported hash strategy for payment flows.—worked.

D:

Multiple independent test sessions distribute as configured while each session remains coherent. This would verify resolution of a different case: An engineer enables load-balancing mode expecting packet-level striping of one TCP session, then diagnoses normal single-link session affinity as a fault. It does not show that the reported issue was fixed or that its intended action—Select an appropriate fixed preferred member or session-persistent supported hash strategy for payment flows.—worked.

Question 127

The incident investigation at a corporate headquarters records: A payment service is set to load-balance across WAN links despite a vendor requiring a stable public source address for the entire session. Which mechanism provides the strongest explanation?

  1. SD-WAN selection depends on an appropriate routing context and cannot create missing reachability.
  2. Inappropriate path distribution can conflict with applications bound to fixed egress identity.
  3. Lowest Cost selection can only choose from eligible configured members that satisfy rule conditions.
  4. Temporary manual priority edits persist until intentionally reverted.

Explanation

Correct Answer

B:

Inappropriate path distribution can conflict with applications bound to fixed egress identity. This explains why the reported condition occurs: A payment service is set to load-balance across WAN links despite a vendor requiring a stable public source address for the entire session. The targeted correction is: Select an appropriate fixed preferred member or session-persistent supported hash strategy for payment flows.

Incorrect Answers

A:

SD-WAN selection depends on an appropriate routing context and cannot create missing reachability. This mechanism instead explains a separate problem: A transaction flow is directed to a preferred member despite no matching route for its destination through that member, producing packet drops. The current incident requires the more directly applicable cause stated by the correct option.

C:

Lowest Cost selection can only choose from eligible configured members that satisfy rule conditions. This mechanism instead explains a separate problem: A Least Cost SLA policy prefers an inexpensive link even after it fails the required loss target because the expensive backup is not included among preferred members. 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 128

After a corrective change at a corporate headquarters, the team documents: A payment service is set to load-balance across WAN links despite a vendor requiring a stable public source address for the entire session. Which repeatable control BEST prevents a recurrence?

  1. Test video traffic steering against real jitter impairment rather than member link-up alone.
  2. Test boundary source addresses for each overlapping SD-WAN rule after subnet changes.
  3. Classify source-IP-sensitive applications before choosing load-balancing strategies.
  4. Include identity-positive and guest-negative path tests for group-aware SD-WAN policies.

Explanation

Correct Answer

C:

Classify source-IP-sensitive applications before choosing load-balancing strategies. This control reduces recurrence of the documented mechanism: Inappropriate path distribution can conflict with applications bound to fixed egress identity. It creates a repeatable check around the needed response: Select an appropriate fixed preferred member or session-persistent supported hash strategy for payment flows.

Incorrect Answers

A:

Test video traffic steering against real jitter impairment rather than member link-up alone. That safeguard addresses another potential failure: A video collaboration app must favor low jitter but the rule uses Manual preference for a congested inexpensive circuit. It is not the most targeted recurring control for the described cause: Inappropriate path distribution can conflict with applications bound to fixed egress identity.

B:

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: Inappropriate path distribution can conflict with applications bound to fixed egress identity.

D:

Include identity-positive and guest-negative path tests for group-aware SD-WAN policies. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Inappropriate path distribution can conflict with applications bound to fixed egress identity.

Question 129

During a security audit at a distributed branch estate, analysts observe: An organization creates a new SASE security policy but forgets to associate it with the intended employee group, leaving staff on the broad default rule. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Assign the reviewed policy to the appropriate supported user or group scope and verify rule priority.
  2. Inspect the actual supported policy scope and narrow the deployment to the approved department population.
  3. Choose a supported PoP or service location and subscription design that satisfies the documented sovereignty requirements.
  4. Evaluate actual user-to-PoP latency and supported service-selection options before final assignment.

Explanation

Correct Answer

A:

Assign the reviewed policy to the appropriate supported user or group scope and verify rule priority. This is the most direct response to the stated incident: An organization creates a new SASE security policy but forgets to associate it with the intended employee group, leaving staff on the broad default rule. The technical mechanism is: A configured policy has no intended audience effect until scope and precedence match live sessions. Confirmation requires: A controlled employee session matches its intended policy while other users retain their approved behavior.

Incorrect Answers

B:

Inspect the actual supported policy scope and narrow the deployment to the approved department population. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: A configured policy has no intended audience effect until scope and precedence match live sessions.

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: A configured policy has no intended audience effect until scope and precedence match live sessions.

D:

Evaluate actual user-to-PoP latency and supported service-selection options before final assignment. That could address a different issue in the same blueprint area: An admin selects a PoP for remote users based only on geographic distance even though upstream ISP routing gives that location poor responsiveness. It does not directly correct the given incident, whose decisive mechanism is: A configured policy has no intended audience effect until scope and precedence match live sessions.

Question 130

At a distributed branch estate, a test team is validating a change after this incident: An organization creates a new SASE security policy but forgets to associate it with the intended employee group, leaving staff on the broad default rule. What evidence most directly verifies the intended outcome?

  1. Migrated test users retain permitted access and previous policy is recoverable if needed.
  2. A controlled employee session matches its intended policy while other users retain their approved behavior.
  3. Licensed test employees authenticate individually and are counted under their intended entitlement model.
  4. Pilot users retain required business access and the security categories enforce the intended controls.

Explanation

Correct Answer

B:

A controlled employee session matches its intended policy while other users retain their approved behavior. This evidence directly tests the intended corrective action: Assign the reviewed policy to the appropriate supported user or group scope and verify rule priority. It confirms the failure mechanism—A configured policy has no intended audience effect until scope and precedence match live sessions.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Assign the reviewed policy to the appropriate supported user or group scope and verify rule priority.—worked.

C:

Licensed test employees authenticate individually and are counted under their intended entitlement model. This would verify resolution of a different case: A security team allocates a single FortiSASE license to a shared administrative account while expecting hundreds of individual employees to gain their own protected Internet sessions. It does not show that the reported issue was fixed or that its intended action—Assign the reviewed policy to the appropriate supported user or group scope and verify rule priority.—worked.

D:

Pilot users retain required business access and the security categories enforce the intended controls. This would verify resolution of a different case: An operator applies a new global URL Filtering profile during business hours without a pilot, interrupting legitimate applications across the tenant. It does not show that the reported issue was fixed or that its intended action—Assign the reviewed policy to the appropriate supported user or group scope and verify rule priority.—worked.

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