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 15

Question 140

An operations group at a service-provider edge resolved: An analyst confuses implicit SD-WAN rule hits with explicit application-specific rule selection during a monthly performance review. Which ongoing safeguard should become part of its change process?

  1. Monitor NTP drift and preserve timezone metadata in security log analysis.
  2. Label and report implicit rule traffic separately from named application steering.
  3. Record data freshness and reporting time boundaries on WAN health dashboards.
  4. Use per-session SD-WAN rule and egress fields during steering incident triage.

Explanation

Correct Answer

B:

Label and report implicit rule traffic separately from named application steering. This control reduces recurrence of the documented mechanism: Implicit fallback can appear similar to a normal rule if logs are read without service context. It creates a repeatable check around the needed response: Inspect matched service-rule identifiers and distinguish explicit versus implicit policy matches.

Incorrect Answers

A:

Monitor NTP drift and preserve timezone metadata in security log analysis. That safeguard addresses another potential failure: A security operations team compares FortiGate SD-WAN log times with FortiSASE events and misorders an incident because the branch clock is unsynchronized. It is not the most targeted recurring control for the described cause: Implicit fallback can appear similar to a normal rule if logs are read without service context.

C:

Record data freshness and reporting time boundaries on WAN health dashboards. That safeguard addresses another potential failure: A service report claims a WAN path is healthy based on an old dashboard snapshot even though the SLA failed later in the review interval. It is not the most targeted recurring control for the described cause: Implicit fallback can appear similar to a normal rule if logs are read without service context.

D:

Use per-session SD-WAN rule and egress fields during steering incident triage. That safeguard addresses another potential failure: A branch's CRM sessions use wan2 instead of preferred wan1 but an engineer looks only at interface uptime rather than the matching SD-WAN service logs. It is not the most targeted recurring control for the described cause: Implicit fallback can appear similar to a normal rule if logs are read without service context.

Question 141

At a national SOC, a security analyst is reviewing this failure during a configuration rollout: A branch upgrades FortiOS and observes SD-WAN rule policy using an old physical egress interface name no longer valid in its deployment template. What is the MOST appropriate FIRST corrective step?

  1. Correct the firewall rule's actual LAN ingress zone while retaining the SD-WAN zone for egress.
  2. Remove or correct the stale policy route so the approved SD-WAN route and rules can select the outbound path.
  3. Inspect the selected SD-WAN strategy and choose a supported load-balance strategy only where the business requires distribution.
  4. Align the deployed zone and member references to the actual supported interface identifiers before pushing.

Explanation

Correct Answer

D:

Align the deployed zone and member references to the actual supported interface identifiers before pushing. This is the most direct response to the stated incident: A branch upgrades FortiOS and observes SD-WAN rule policy using an old physical egress interface name no longer valid in its deployment template. The technical mechanism is: Shared templates can contain stale interface references across hardware revisions. Confirmation requires: Configuration validation succeeds and a rule diagnostic resolves a real member with expected egress.

Incorrect Answers

A:

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: Shared templates can contain stale interface references across hardware revisions.

B:

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: Shared templates can contain stale interface references across hardware revisions.

C:

Inspect the selected SD-WAN strategy and choose a supported load-balance strategy only where the business requires distribution. That could address a different issue in the same blueprint area: 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 does not directly correct the given incident, whose decisive mechanism is: Shared templates can contain stale interface references across hardware revisions.

Question 142

During follow-up testing at a national SOC, the original fault was: A branch upgrades FortiOS and observes SD-WAN rule policy using an old physical egress interface name no longer valid in its deployment template. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. Configuration validation succeeds and a rule diagnostic resolves a real member with expected egress.
  2. An authorized client session can use either eligible member without requiring a per-ISP firewall rule.
  3. An allowed client session matches the intended firewall policy and the SD-WAN path is eligible.
  4. FortiManager device validation succeeds and both branch paths appear as intended SD-WAN members.

Explanation

Correct Answer

A:

Configuration validation succeeds and a rule diagnostic resolves a real member with expected egress. This evidence directly tests the intended corrective action: Align the deployed zone and member references to the actual supported interface identifiers before pushing. It confirms the failure mechanism—Shared templates can contain stale interface references across hardware revisions.—has been addressed in the actual affected flow.

Incorrect Answers

B:

An authorized client session can use either eligible member without requiring a per-ISP firewall rule. This would verify resolution of a different case: An administrator creates an SD-WAN zone and members but the outbound firewall policy still references only wan1, so sessions fail on wan2. It does not show that the reported issue was fixed or that its intended action—Align the deployed zone and member references to the actual supported interface identifiers before pushing.—worked.

C:

An allowed client session matches the intended firewall policy and the SD-WAN path is eligible. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Align the deployed zone and member references to the actual supported interface identifiers before pushing.—worked.

D:

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—Align the deployed zone and member references to the actual supported interface identifiers before pushing.—worked.

Question 143

The incident investigation at a national SOC records: A branch upgrades FortiOS and observes SD-WAN rule policy using an old physical egress interface name no longer valid in its deployment template. Which mechanism provides the strongest explanation?

  1. Central rule reuse requires correct per-device interface resolution.
  2. Shared templates can contain stale interface references across hardware revisions.
  3. Separate usable WAN links do not provide SD-WAN steering until zone, members, routes, and policy are configured together.
  4. A configured but administratively disabled member is not a live candidate for steering.

Explanation

Correct Answer

B:

Shared templates can contain stale interface references across hardware revisions. This explains why the reported condition occurs: A branch upgrades FortiOS and observes SD-WAN rule policy using an old physical egress interface name no longer valid in its deployment template. The targeted correction is: Align the deployed zone and member references to the actual supported interface identifiers before pushing.

Incorrect Answers

A:

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.

C:

Separate usable WAN links do not provide SD-WAN steering until zone, members, routes, and policy are configured together. This mechanism instead explains a separate problem: A two-ISP FortiGate has working physical WAN interfaces but no SD-WAN configuration, so a branch cannot steer applications by link health. The current incident requires the more directly applicable cause stated by the correct option.

D:

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.

Question 144

After a corrective change at a national SOC, the team documents: A branch upgrades FortiOS and observes SD-WAN rule policy using an old physical egress interface name no longer valid in its deployment template. Which repeatable control BEST prevents a recurrence?

  1. Inventory and test inherited policy routes before introducing SD-WAN at older branches.
  2. Validate source network inventory and firewall object coverage when adding new VLANs.
  3. Test interface and zone identifiers against each target appliance model before site rollout.
  4. Check actual member inventory against every documented backup medium during failover rehearsals.

Explanation

Correct Answer

C:

Test interface and zone identifiers against each target appliance model before site rollout. This control reduces recurrence of the documented mechanism: Shared templates can contain stale interface references across hardware revisions. It creates a repeatable check around the needed response: Align the deployed zone and member references to the actual supported interface identifiers before pushing.

Incorrect Answers

A:

Inventory and test inherited policy routes before introducing SD-WAN at older branches. That safeguard addresses another potential failure: A new branch configures link monitoring but still sends Internet traffic through a legacy policy route bound to an obsolete gateway. It is not the most targeted recurring control for the described cause: Shared templates can contain stale interface references across hardware revisions.

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: Shared templates can contain stale interface references across hardware revisions.

D:

Check actual member inventory against every documented backup medium during failover rehearsals. That safeguard addresses another potential failure: A backup LTE interface is physically up but never added as an SD-WAN member, so WAN failure does not activate cellular continuity. It is not the most targeted recurring control for the described cause: Shared templates can contain stale interface references across hardware revisions.

Question 145

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

  1. Reorder the rule's preferred members to reflect the approved priority under equal-cost conditions.
  2. Replace the broad category match with the intended recognized application or application object.
  3. Include both eligible member IDs in the rule and apply the approved SLA target and cost settings.
  4. Add the supported user or group match condition to the finance steering policy while retaining network scope.

Explanation

Correct Answer

A:

Reorder the rule's preferred members to reflect the approved priority under equal-cost conditions. This is the most direct response to the stated incident: 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. The technical mechanism is: Equal-cost SLA selection may resolve using configured member preference order. Confirmation requires: The selected link matches the configured first eligible priority when cost and SLA results tie.

Incorrect Answers

B:

Replace the broad category match with the intended recognized application or application object. That could address a different issue in the same blueprint area: An administrator configures a rule matching application category Social Networking while the approved exception is only for a named conferencing application. It does not directly correct the given incident, whose decisive mechanism is: Equal-cost SLA selection may resolve using configured member preference order.

C:

Include both eligible member IDs in the rule and apply the approved SLA target and cost settings. That could address a different issue in the same blueprint area: 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. It does not directly correct the given incident, whose decisive mechanism is: Equal-cost SLA selection may resolve using configured member preference order.

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: Equal-cost SLA selection may resolve using configured member preference order.

Question 146

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

  1. The tested application hits its dedicated rule ID and selects the approved private link.
  2. The selected link matches the configured first eligible priority when cost and SLA results tie.
  3. When the cheap member fails SLA, the more expensive healthy link is selected.
  4. Backup throughput improves on the approved high-capacity link without disturbing voice prioritization.

Explanation

Correct Answer

B:

The selected link matches the configured first eligible priority when cost and SLA results tie. This evidence directly tests the intended corrective action: Reorder the rule's preferred members to reflect the approved priority under equal-cost conditions. It confirms the failure mechanism—Equal-cost SLA selection may resolve using configured member preference order.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Reorder the rule's preferred members to reflect the approved priority under equal-cost conditions.—worked.

C:

When the cheap member fails SLA, the more expensive healthy link is selected. This would verify resolution of a different case: 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. It does not show that the reported issue was fixed or that its intended action—Reorder the rule's preferred members to reflect the approved priority under equal-cost conditions.—worked.

D:

Backup throughput improves on the approved high-capacity link without disturbing voice prioritization. This would verify resolution of a different case: 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 does not show that the reported issue was fixed or that its intended action—Reorder the rule's preferred members to reflect the approved priority under equal-cost conditions.—worked.

Question 147

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

  1. Broad Internet-service categories can capture unrelated destinations.
  2. Inappropriate path distribution can conflict with applications bound to fixed egress identity.
  3. Equal-cost SLA selection may resolve using configured member preference order.
  4. An SD-WAN rule can choose an unapproved path if member eligibility is broader than the security intent.

Explanation

Correct Answer

C:

Equal-cost SLA selection may resolve using configured member preference order. This explains why the reported condition occurs: 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. The targeted correction is: Reorder the rule's preferred members to reflect the approved priority under equal-cost conditions.

Incorrect Answers

A:

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.

B:

Inappropriate path distribution can conflict with applications bound to fixed egress identity. This mechanism instead explains a separate problem: 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 current incident requires the more directly applicable cause stated by the correct option.

D:

An SD-WAN rule can choose an unapproved path if member eligibility is broader than the security intent. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

Question 148

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

  1. Test complete application session establishment and reclassification, not just SYN packets.
  2. Require representative destination match tests for every new service rule.
  3. Retire old member IDs from every dependent rule during carrier migration.
  4. Review tie-breaking and priority ordering when setting SD-WAN member costs.

Explanation

Correct Answer

D:

Review tie-breaking and priority ordering when setting SD-WAN member costs. This control reduces recurrence of the documented mechanism: Equal-cost SLA selection may resolve using configured member preference order. It creates a repeatable check around the needed response: Reorder the rule's preferred members to reflect the approved priority under equal-cost conditions.

Incorrect Answers

A:

Test complete application session establishment and reclassification, not just SYN packets. That safeguard addresses another potential failure: An application-based SD-WAN rule steers initial traffic through the wrong link before the application can be classified, confusing testers. It is not the most targeted recurring control for the described cause: Equal-cost SLA selection may resolve using configured member preference order.

B:

Require representative destination match tests for every new service rule. That safeguard addresses another potential failure: 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. It is not the most targeted recurring control for the described cause: Equal-cost SLA selection may resolve using configured member preference order.

C:

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: Equal-cost SLA selection may resolve using configured member preference order.

Question 149

During a production service incident, an administrator reports at a regional data center: A newly deployed FortiSASE tenant trusts a broad default administrative account even after named administrators receive individual credentials. What should the team change or investigate FIRST?

  1. Evaluate actual user-to-PoP latency and supported service-selection options before final assignment.
  2. Restrict or decommission the shared default account through supported admin identity controls and use individual audited roles.
  3. Roll back or narrow the profile change and perform a controlled pilot with explicit approved exceptions.
  4. Normalize identity group naming and map groups to approved, unambiguous service-policy references.

Explanation

Correct Answer

B:

Restrict or decommission the shared default account through supported admin identity controls and use individual audited roles. This is the most direct response to the stated incident: A newly deployed FortiSASE tenant trusts a broad default administrative account even after named administrators receive individual credentials. The technical mechanism is: Shared privileged identities weaken accountability even if basic tenant authentication works. Confirmation requires: Named admins sign in with appropriate privilege while unauthorized use of the shared credential is blocked.

Incorrect Answers

A:

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: Shared privileged identities weaken accountability even if basic tenant authentication works.

C:

Roll back or narrow the profile change and perform a controlled pilot with explicit approved exceptions. That could address a different issue in the same blueprint area: An operator applies a new global URL Filtering profile during business hours without a pilot, interrupting legitimate applications across the tenant. It does not directly correct the given incident, whose decisive mechanism is: Shared privileged identities weaken accountability even if basic tenant authentication works.

D:

Normalize identity group naming and map groups to approved, unambiguous service-policy references. That could address a different issue in the same blueprint area: A multi-site company creates an SASE administration configuration with duplicated names for user groups that have conflicting policy intent. It does not directly correct the given incident, whose decisive mechanism is: Shared privileged identities weaken accountability even if basic tenant authentication works.

Question 150

Following remediation at a regional data center, engineers revisit: A newly deployed FortiSASE tenant trusts a broad default administrative account even after named administrators receive individual credentials. Which observation would BEST prove the specific issue is resolved?

  1. A controlled employee session matches its intended policy while other users retain their approved behavior.
  2. Tests from each approved country resolve to the intended service and policy without affecting the other group.
  3. Named admins sign in with appropriate privilege while unauthorized use of the shared credential is blocked.
  4. Newly licensed user accounts enroll successfully while the license dashboard reflects accurate capacity.

Explanation

Correct Answer

C:

Named admins sign in with appropriate privilege while unauthorized use of the shared credential is blocked. This evidence directly tests the intended corrective action: Restrict or decommission the shared default account through supported admin identity controls and use individual audited roles. It confirms the failure mechanism—Shared privileged identities weaken accountability even if basic tenant authentication works.—has been addressed in the actual affected flow.

Incorrect Answers

A:

A controlled employee session matches its intended policy while other users retain their approved behavior. This would verify resolution of a different case: 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. It does not show that the reported issue was fixed or that its intended action—Restrict or decommission the shared default account through supported admin identity controls and use individual audited roles.—worked.

B:

Tests from each approved country resolve to the intended service and policy without affecting the other group. This would verify resolution of a different case: A company expects users in two countries to be assigned the same inspection region despite a requirement for country-specific enforcement policies. It does not show that the reported issue was fixed or that its intended action—Restrict or decommission the shared default account through supported admin identity controls and use individual audited roles.—worked.

D:

Newly licensed user accounts enroll successfully while the license dashboard reflects accurate capacity. This would verify resolution of a different case: A FortiSASE tenant's administrator sees a warning about insufficient user licensing but continues issuing enrollment invitations that fail at authentication. It does not show that the reported issue was fixed or that its intended action—Restrict or decommission the shared default account through supported admin identity controls and use individual audited roles.—worked.

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