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 73

Question 720

After a corrective change at a national SOC, the team documents: A user activity report identifies only egress addresses and application names while investigators require an authorized account-level trace for a confirmed DLP event. Which repeatable control BEST prevents a recurrence?

  1. Classify report sensitivity and enforce audience-specific data minimization.
  2. Require data source and inclusion criteria notes on every custom report.
  3. Maintain approved user-attribution data sources and privacy access controls for incident reports.
  4. Review intended population and filter settings before sharing compliance reports.

Explanation

Correct Answer

C:

Maintain approved user-attribution data sources and privacy access controls for incident reports. This control reduces recurrence of the documented mechanism: An IP-aggregated report may be insufficient for per-identity security investigations. It creates a repeatable check around the needed response: Select a supported user-attributed report or correlate report records with permitted identity and DLP event fields.

Incorrect Answers

A:

Classify report sensitivity and enforce audience-specific data minimization. That safeguard addresses another potential failure: A FortiSASE report used for an audit exposes individual browsing URLs to a broad executive distribution although the approved report should contain aggregates only. It is not the most targeted recurring control for the described cause: An IP-aggregated report may be insufficient for per-identity security investigations.

B:

Require data source and inclusion criteria notes on every custom report. That safeguard addresses another potential failure: An operator builds a custom report from a filtered set of denied sessions and presents it as total Internet traffic volume for management. It is not the most targeted recurring control for the described cause: An IP-aggregated report may be insufficient for per-identity security investigations.

D:

Review intended population and filter settings before sharing compliance reports. That safeguard addresses another potential failure: A FortiSASE monthly report shows no events for one region because the analyst used the wrong user-group filter rather than the region's identity cohort. It is not the most targeted recurring control for the described cause: An IP-aggregated report may be insufficient for per-identity security investigations.

Question 721

During a quarterly compliance review at a financial services branch, analysts observe: A branch tests loss toward an internal DNS server reachable through a tunnel, so a public DIA member appears unhealthy despite reliable Internet service. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Select suitable stable external probe targets and the intended member list for the Internet SLA.
  2. Allow the approved health-check protocol or choose a reachable permitted target without broadening unrelated access.
  3. Add the approved packet-loss threshold to the voice performance SLA and apply it to the steering rule.
  4. Correct the jitter SLA target for the application and link it to the appropriate SD-WAN rule.

Explanation

Correct Answer

A:

Select suitable stable external probe targets and the intended member list for the Internet SLA. This is the most direct response to the stated incident: A branch tests loss toward an internal DNS server reachable through a tunnel, so a public DIA member appears unhealthy despite reliable Internet service. The technical mechanism is: A probe target reached through another path can misrepresent a member's real service health. Confirmation requires: A direct-Internet test agrees with probe state and healthy DIA members become eligible.

Incorrect Answers

B:

Allow the approved health-check protocol or choose a reachable permitted target without broadening unrelated access. That could address a different issue in the same blueprint area: A branch's SLA probe targets are blocked by an upstream provider ACL, yet employees can reach normal applications without difficulty. It does not directly correct the given incident, whose decisive mechanism is: A probe target reached through another path can misrepresent a member's real service health.

C:

Add the approved packet-loss threshold to the voice performance SLA and apply it to the steering rule. That could address a different issue in the same blueprint area: Voice calls fail during transient packet loss while FortiGate steers calls to the cheapest link because the SLA tracks only latency. It does not directly correct the given incident, whose decisive mechanism is: A probe target reached through another path can misrepresent a member's real service health.

D:

Correct the jitter SLA target for the application and link it to the appropriate SD-WAN rule. That could address a different issue in the same blueprint area: A voice quality rule uses a jitter maximum far above business tolerance so choppy calls continue on a variable-delay ISP. It does not directly correct the given incident, whose decisive mechanism is: A probe target reached through another path can misrepresent a member's real service health.

Question 722

At a financial services branch, a test team is validating a change after this incident: A branch tests loss toward an internal DNS server reachable through a tunnel, so a public DIA member appears unhealthy despite reliable Internet service. What evidence most directly verifies the intended outcome?

  1. When all tested members violate target, the observed fallback matches the documented continuity policy.
  2. A direct-Internet test agrees with probe state and healthy DIA members become eligible.
  3. A controlled upstream failure changes SLA health even while physical carrier stays up.
  4. A private overlay outage affects only private-path eligibility while healthy Internet DIA remains usable.

Explanation

Correct Answer

B:

A direct-Internet test agrees with probe state and healthy DIA members become eligible. This evidence directly tests the intended corrective action: Select suitable stable external probe targets and the intended member list for the Internet SLA. It confirms the failure mechanism—A probe target reached through another path can misrepresent a member's real service health.—has been addressed in the actual affected flow.

Incorrect Answers

A:

When all tested members violate target, the observed fallback matches the documented continuity policy. This would verify resolution of a different case: An engineer configures SD-WAN latency monitoring but its rule selects a member that meets no required SLA due to an unreviewed fallback behavior. It does not show that the reported issue was fixed or that its intended action—Select suitable stable external probe targets and the intended member list for the Internet SLA.—worked.

C:

A controlled upstream failure changes SLA health even while physical carrier stays up. This would verify resolution of a different case: An engineer measures only last-mile interface status to declare a partner API path healthy, overlooking repeated upstream packet drops. It does not show that the reported issue was fixed or that its intended action—Select suitable stable external probe targets and the intended member list for the Internet SLA.—worked.

D:

A private overlay outage affects only private-path eligibility while healthy Internet DIA remains usable. This would verify resolution of a different case: A site wants link status tracked separately for private data-center traffic and Internet browsing, but uses the same public Internet probe for both SLA decisions. It does not show that the reported issue was fixed or that its intended action—Select suitable stable external probe targets and the intended member list for the Internet SLA.—worked.

Question 723

A Fortinet administrator at a financial services branch is assessing: A branch tests loss toward an internal DNS server reachable through a tunnel, so a public DIA member appears unhealthy despite reliable Internet service. What is the most relevant root cause?

  1. Over-sensitive probe state transitions cause steering instability around normal variation.
  2. Layer 1 connectivity cannot reveal upstream reachability or path-quality failures.
  3. A probe target reached through another path can misrepresent a member's real service health.
  4. Performance SLA eligibility depends on which member interfaces are actually monitored.

Explanation

Correct Answer

C:

A probe target reached through another path can misrepresent a member's real service health. This explains why the reported condition occurs: A branch tests loss toward an internal DNS server reachable through a tunnel, so a public DIA member appears unhealthy despite reliable Internet service. The targeted correction is: Select suitable stable external probe targets and the intended member list for the Internet SLA.

Incorrect Answers

A:

Over-sensitive probe state transitions cause steering instability around normal variation. This mechanism instead explains a separate problem: A branch SLA oscillates between healthy and failed every few seconds because recovery thresholds are too sensitive near its jitter boundary. The current incident requires the more directly applicable cause stated by the correct option.

B:

Layer 1 connectivity cannot reveal upstream reachability or path-quality failures. This mechanism instead explains a separate problem: An engineer measures only last-mile interface status to declare a partner API path healthy, overlooking repeated upstream packet drops. The current incident requires the more directly applicable cause stated by the correct option.

D:

Performance SLA eligibility depends on which member interfaces are actually monitored. This mechanism instead explains a separate problem: An engineer creates a performance SLA but does not associate the backup member with its health-check member list, leaving the backup unmonitored. The current incident requires the more directly applicable cause stated by the correct option.

Question 724

A risk review at a financial services branch focuses on preventing this issue again: A branch tests loss toward an internal DNS server reachable through a tunnel, so a public DIA member appears unhealthy despite reliable Internet service. Which recurring control is most suitable?

  1. Verify probe source IP and provider return routes during link commissioning.
  2. Choose probe method and destination that reflect the service level being protected.
  3. Validate health-detection delay against payment transaction recovery objectives.
  4. Validate health-check destination and actual route path for each monitored service.

Explanation

Correct Answer

D:

Validate health-check destination and actual route path for each monitored service. This control reduces recurrence of the documented mechanism: A probe target reached through another path can misrepresent a member's real service health. It creates a repeatable check around the needed response: Select suitable stable external probe targets and the intended member list for the Internet SLA.

Incorrect Answers

A:

Verify probe source IP and provider return routes during link commissioning. That safeguard addresses another potential failure: The performance SLA reports high loss on a backup line because probes use a source address not routed by its provider. It is not the most targeted recurring control for the described cause: A probe target reached through another path can misrepresent a member's real service health.

B:

Choose probe method and destination that reflect the service level being protected. That safeguard addresses another potential failure: An SLA probes only TCP handshake reachability for a collaboration SaaS even though user complaints concern heavy application-layer response times. It is not the most targeted recurring control for the described cause: A probe target reached through another path can misrepresent a member's real service health.

C:

Validate health-detection delay against payment transaction recovery objectives. That safeguard addresses another potential failure: An SLA uses a probe interval too sparse to detect outages quickly enough for a monitored payment application. It is not the most targeted recurring control for the described cause: A probe target reached through another path can misrepresent a member's real service health.

Question 725

During a production service incident, an administrator reports at a regional data center: A device has two equal-cost underlay routes but an application must use one provider for compliance while SD-WAN service matching is absent. What should the team change or investigate FIRST?

  1. Add the correct route for the private app subnet toward the associated tunnel or zone.
  2. Define the appropriate scoped SD-WAN service rule to enforce provider preference over equal-cost eligible routes.
  3. Adjust routing policy attributes or supported SD-WAN route preference according to the approved private-link design.
  4. Restore the correct internal return route or interface association for the server subnet.

Explanation

Correct Answer

B:

Define the appropriate scoped SD-WAN service rule to enforce provider preference over equal-cost eligible routes. This is the most direct response to the stated incident: A device has two equal-cost underlay routes but an application must use one provider for compliance while SD-WAN service matching is absent. The technical mechanism is: Ordinary ECMP route eligibility alone does not encode per-application provider restrictions. Confirmation requires: The regulated application consistently leaves through the allowed member while ordinary traffic may use both.

Incorrect Answers

A:

Add the correct route for the private app subnet toward the associated tunnel or zone. That could address a different issue in the same blueprint area: A tunnel interface is a zone member but its route uses the remote gateway's public IP instead of the private destination prefix, leaving internal apps unrouteable. It does not directly correct the given incident, whose decisive mechanism is: Ordinary ECMP route eligibility alone does not encode per-application provider restrictions.

C:

Adjust routing policy attributes or supported SD-WAN route preference according to the approved private-link design. That could address a different issue in the same blueprint area: A BGP route to a private application is learned through both MPLS and Internet overlay with a preference that incorrectly favors the metered link. It does not directly correct the given incident, whose decisive mechanism is: Ordinary ECMP route eligibility alone does not encode per-application provider restrictions.

D:

Restore the correct internal return route or interface association for the server subnet. That could address a different issue in the same blueprint area: A FortiGate forwards web traffic via DIA but its route back to an internal server uses the wrong LAN interface after a segmentation project. It does not directly correct the given incident, whose decisive mechanism is: Ordinary ECMP route eligibility alone does not encode per-application provider restrictions.

Question 726

Following remediation at a regional data center, engineers revisit: A device has two equal-cost underlay routes but an application must use one provider for compliance while SD-WAN service matching is absent. Which observation would BEST prove the specific issue is resolved?

  1. Private addresses use the overlay while Internet destinations use direct access.
  2. The selected private prefix route and forwarding member follow the preferred non-metered path when healthy.
  3. The regulated application consistently leaves through the allowed member while ordinary traffic may use both.
  4. External test services observe a valid address for each ISP and responses return successfully.

Explanation

Correct Answer

C:

The regulated application consistently leaves through the allowed member while ordinary traffic may use both. This evidence directly tests the intended corrective action: Define the appropriate scoped SD-WAN service rule to enforce provider preference over equal-cost eligible routes. It confirms the failure mechanism—Ordinary ECMP route eligibility alone does not encode per-application provider restrictions.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Private addresses use the overlay while Internet destinations use direct access. This would verify resolution of a different case: A branch adds a second SD-WAN zone with private overlay members but the site's route to RFC1918 destinations still points to the DIA zone. It does not show that the reported issue was fixed or that its intended action—Define the appropriate scoped SD-WAN service rule to enforce provider preference over equal-cost eligible routes.—worked.

B:

The selected private prefix route and forwarding member follow the preferred non-metered path when healthy. This would verify resolution of a different case: A BGP route to a private application is learned through both MPLS and Internet overlay with a preference that incorrectly favors the metered link. It does not show that the reported issue was fixed or that its intended action—Define the appropriate scoped SD-WAN service rule to enforce provider preference over equal-cost eligible routes.—worked.

D:

External test services observe a valid address for each ISP and responses return successfully. This would verify resolution of a different case: A source NAT policy translates a client to the primary ISP address even after SD-WAN routes traffic out through a backup provider, breaking return traffic. It does not show that the reported issue was fixed or that its intended action—Define the appropriate scoped SD-WAN service rule to enforce provider preference over equal-cost eligible routes.—worked.

Question 727

During a production service incident, this condition is reported: A device has two equal-cost underlay routes but an application must use one provider for compliance while SD-WAN service matching is absent. Which technical explanation MOST directly accounts for the failure?

  1. Routing uses the configured interface and gateway combination, not the member's label alone.
  2. Longest-prefix routing can outweigh less-specific zone routes regardless of apparent preference.
  3. Tunnel establishment is not proof that remote routing tables know the branch source network.
  4. Ordinary ECMP route eligibility alone does not encode per-application provider restrictions.

Explanation

Correct Answer

D:

Ordinary ECMP route eligibility alone does not encode per-application provider restrictions. This explains why the reported condition occurs: A device has two equal-cost underlay routes but an application must use one provider for compliance while SD-WAN service matching is absent. The targeted correction is: Define the appropriate scoped SD-WAN service rule to enforce provider preference over equal-cost eligible routes.

Incorrect Answers

A:

Routing uses the configured interface and gateway combination, not the member's label alone. This mechanism instead explains a separate problem: An SD-WAN member has a static route to a provider gateway on the wrong interface, so probes work on another link but traffic drops when it is selected. The current incident requires the more directly applicable cause stated by the correct option.

B:

Longest-prefix routing can outweigh less-specific zone routes regardless of apparent preference. This mechanism instead explains a separate problem: A new branch subnet has a longer specific static route pointing to an old MPLS path, overriding the intended broader overlay route. The current incident requires the more directly applicable cause stated by the correct option.

C:

Tunnel establishment is not proof that remote routing tables know the branch source network. This mechanism instead explains a separate problem: An IPsec tunnel is up and part of an SD-WAN zone but remote servers cannot reply because their route to the branch subnet is absent. The current incident requires the more directly applicable cause stated by the correct option.

Question 728

During a post-incident review at a regional data center, the original problem was: A device has two equal-cost underlay routes but an application must use one provider for compliance while SD-WAN service matching is absent. Which preventive practice most directly addresses its cause?

  1. Audit application-level path constraints before enabling equal-cost WAN routing.
  2. Validate tunneled application prefixes separately from peer reachability.
  3. Document routing priorities for overlays with multiple learned next hops.
  4. Verify destination and reverse-path routing whenever moving internal VLANs.

Explanation

Correct Answer

A:

Audit application-level path constraints before enabling equal-cost WAN routing. This control reduces recurrence of the documented mechanism: Ordinary ECMP route eligibility alone does not encode per-application provider restrictions. It creates a repeatable check around the needed response: Define the appropriate scoped SD-WAN service rule to enforce provider preference over equal-cost eligible routes.

Incorrect Answers

B:

Validate tunneled application prefixes separately from peer reachability. That safeguard addresses another potential failure: A tunnel interface is a zone member but its route uses the remote gateway's public IP instead of the private destination prefix, leaving internal apps unrouteable. It is not the most targeted recurring control for the described cause: Ordinary ECMP route eligibility alone does not encode per-application provider restrictions.

C:

Document routing priorities for overlays with multiple learned next hops. That safeguard addresses another potential failure: A BGP route to a private application is learned through both MPLS and Internet overlay with a preference that incorrectly favors the metered link. It is not the most targeted recurring control for the described cause: Ordinary ECMP route eligibility alone does not encode per-application provider restrictions.

D:

Verify destination and reverse-path routing whenever moving internal VLANs. That safeguard addresses another potential failure: A FortiGate forwards web traffic via DIA but its route back to an internal server uses the wrong LAN interface after a segmentation project. It is not the most targeted recurring control for the described cause: Ordinary ECMP route eligibility alone does not encode per-application provider restrictions.

Question 729

A firewall operations team at a university network encounters the following during a predeployment acceptance test: Remote users experience two different security postures because some are agent-based and others use browser-only SWG; an operator assumes both modes inspect nonweb traffic identically. Which action most directly restores the approved security outcome?

  1. Use the supported agentless SWG proxy onboarding instructions for the contractor population.
  2. Restore device time synchronization and test the trusted FortiSASE certificate chain.
  3. Apply the approved security coverage rules for each connection mode and document which traffic types each mode protects.
  4. Synchronize the approved RADIUS client/server shared secret and test authentication exchanges.

Explanation

Correct Answer

C:

Apply the approved security coverage rules for each connection mode and document which traffic types each mode protects. This is the most direct response to the stated incident: Remote users experience two different security postures because some are agent-based and others use browser-only SWG; an operator assumes both modes inspect nonweb traffic identically. The technical mechanism is: Agentless proxy scope is not automatically equivalent to full device-tunnel traffic coverage. Confirmation requires: Nonweb and web test cases show explicitly understood protection differences between agent and proxy cohorts.

Incorrect Answers

A:

Use the supported agentless SWG proxy onboarding instructions for the contractor population. That could address a different issue in the same blueprint area: A company plans browser-only secure web gateway use for contractors but distributes an agent-based full-tunnel guide requiring managed endpoint enrollment. It does not directly correct the given incident, whose decisive mechanism is: Agentless proxy scope is not automatically equivalent to full device-tunnel traffic coverage.

B:

Restore device time synchronization and test the trusted FortiSASE certificate chain. That could address a different issue in the same blueprint area: An employee's FortiClient connection repeatedly disconnects when the local system clock is wrong and the client rejects a valid service certificate. It does not directly correct the given incident, whose decisive mechanism is: Agentless proxy scope is not automatically equivalent to full device-tunnel traffic coverage.

D:

Synchronize the approved RADIUS client/server shared secret and test authentication exchanges. That could address a different issue in the same blueprint area: A FortiSASE tenant uses RADIUS for user authentication but the RADIUS shared secret was changed on FortiAuthenticator only. It does not directly correct the given incident, whose decisive mechanism is: Agentless proxy scope is not automatically equivalent to full device-tunnel traffic coverage.

Question 730

An operations review at a university network has corrected: Remote users experience two different security postures because some are agent-based and others use browser-only SWG; an operator assumes both modes inspect nonweb traffic identically. Which observation specifically confirms success?

  1. Test web access appears in FortiSASE SWG logs and nonproxy direct browsing is appropriately restricted.
  2. Each tested OS uses a compatible approved onboarding mode with expected security restrictions.
  3. The local user receives only the allowed policy rather than unrestricted default access.
  4. Nonweb and web test cases show explicitly understood protection differences between agent and proxy cohorts.

Explanation

Correct Answer

D:

Nonweb and web test cases show explicitly understood protection differences between agent and proxy cohorts. This evidence directly tests the intended corrective action: Apply the approved security coverage rules for each connection mode and document which traffic types each mode protects. It confirms the failure mechanism—Agentless proxy scope is not automatically equivalent to full device-tunnel traffic coverage.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Test web access appears in FortiSASE SWG logs and nonproxy direct browsing is appropriately restricted. This would verify resolution of a different case: A team deploys an agentless SWG configuration but omits browser or system proxy settings, causing traffic to connect directly to Internet sites. It does not show that the reported issue was fixed or that its intended action—Apply the approved security coverage rules for each connection mode and document which traffic types each mode protects.—worked.

B:

Each tested OS uses a compatible approved onboarding mode with expected security restrictions. This would verify resolution of a different case: An enterprise distributes FortiClient installation to Windows staff while Linux contractor devices are assumed supported under the identical profile without checking platform capabilities. It does not show that the reported issue was fixed or that its intended action—Apply the approved security coverage rules for each connection mode and document which traffic types each mode protects.—worked.

C:

The local user receives only the allowed policy rather than unrestricted default access. This would verify resolution of a different case: An administrator creates a local FortiSASE user but assumes LDAP group restrictions apply automatically although the account is not mapped to a corresponding local service group. It does not show that the reported issue was fixed or that its intended action—Apply the approved security coverage rules for each connection mode and document which traffic types each mode protects.—worked.

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