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 39

Question 380

An operations group at a service-provider edge resolved: A remote user's FortiSASE log records many denied SSH connection attempts to Internet hosts but a rule-change request asks to permit all SSH to make alerts stop. Which ongoing safeguard should become part of its change process?

  1. Review configured IPS actions and resulting event disposition during alert triage.
  2. Review unusual denied connection bursts prior to allowing new protocols.
  3. Include CASB or SaaS-specific event sources in cloud data-exfiltration investigations.
  4. Retain user/device attribution and response fields for cloud malware detections.

Explanation

Correct Answer

B:

Review unusual denied connection bursts prior to allowing new protocols. This control reduces recurrence of the documented mechanism: Repeated policy denies can be threat indicators, not necessarily missing application requirements. It creates a repeatable check around the needed response: Assess the deny events' source, frequency, destination and user context before changing security policy.

Incorrect Answers

A:

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: Repeated policy denies can be threat indicators, not necessarily missing application requirements.

C:

Include CASB or SaaS-specific event sources in cloud data-exfiltration investigations. That safeguard addresses another potential failure: A suspicious SaaS upload is recorded in inline CASB logs, but investigators search only web filter events and miss it. It is not the most targeted recurring control for the described cause: Repeated policy denies can be threat indicators, not necessarily missing application requirements.

D:

Retain user/device attribution and response fields for cloud malware detections. That safeguard addresses another potential failure: An administrator sees antivirus detections in FortiSASE but lacks the affected user and device context to decide where containment is needed. It is not the most targeted recurring control for the described cause: Repeated policy denies can be threat indicators, not necessarily missing application requirements.

Question 381

At a national SOC, a security analyst is reviewing this failure during a planned policy migration: A WAN port with a tagged provider VLAN is added to SD-WAN as the physical untagged port, so no valid IP traffic reaches the carrier. What is the MOST appropriate FIRST corrective step?

  1. Create or select the region-approved SD-WAN zone and assign the tunnel member to it.
  2. Update the affected static route to the new correct zone and revalidate forwarding.
  3. Configure the supported FortiExtender logical interface as an SD-WAN member with correct health and failover settings.
  4. Use the configured VLAN subinterface as the intended SD-WAN member rather than the parent physical port.

Explanation

Correct Answer

D:

Use the configured VLAN subinterface as the intended SD-WAN member rather than the parent physical port. This is the most direct response to the stated incident: A WAN port with a tagged provider VLAN is added to SD-WAN as the physical untagged port, so no valid IP traffic reaches the carrier. The technical mechanism is: The SD-WAN member must reference the actual Layer 3 interface carrying the provider service. Confirmation requires: Health probes and test sessions leave with the approved VLAN tag and reach the ISP gateway.

Incorrect Answers

A:

Create or select the region-approved SD-WAN zone and assign the tunnel member to it. That could address a different issue in the same blueprint area: A new tunnel member is added under the default virtual-wan-link zone although the architecture requires region-specific security controls. It does not directly correct the given incident, whose decisive mechanism is: The SD-WAN member must reference the actual Layer 3 interface carrying the provider service.

B:

Update the affected static route to the new correct zone and revalidate forwarding. That could address a different issue in the same blueprint area: A fortigate WAN interface is moved between SD-WAN zones while a static route continues to point at its previous zone, leaving a private prefix unreachable. It does not directly correct the given incident, whose decisive mechanism is: The SD-WAN member must reference the actual Layer 3 interface carrying the provider service.

C:

Configure the supported FortiExtender logical interface as an SD-WAN member with correct health and failover settings. That could address a different issue in the same blueprint area: The branch uses a cellular FortiExtender as a third path but engineers mistakenly treat the modem as a conventional Ethernet gateway without verifying supported interface details. It does not directly correct the given incident, whose decisive mechanism is: The SD-WAN member must reference the actual Layer 3 interface carrying the provider service.

Question 382

During follow-up testing at a national SOC, the original fault was: A WAN port with a tagged provider VLAN is added to SD-WAN as the physical untagged port, so no valid IP traffic reaches the carrier. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. Health probes and test sessions leave with the approved VLAN tag and reach the ISP gateway.
  2. Configuration install succeeds and each member appears in one approved operational grouping.
  3. The tunnel appears in member status and approved private traffic can select it.
  4. Probe packets use the intended routing context and the member reports correct reachability.

Explanation

Correct Answer

A:

Health probes and test sessions leave with the approved VLAN tag and reach the ISP gateway. This evidence directly tests the intended corrective action: Use the configured VLAN subinterface as the intended SD-WAN member rather than the parent physical port. It confirms the failure mechanism—The SD-WAN member must reference the actual Layer 3 interface carrying the provider service.—has been addressed in the actual affected flow.

Incorrect Answers

B:

Configuration install succeeds and each member appears in one approved operational grouping. This would verify resolution of a different case: A configuration template assigns one WAN member to multiple intended zones through duplicated site definitions, causing a conflict during managed deployment. It does not show that the reported issue was fixed or that its intended action—Use the configured VLAN subinterface as the intended SD-WAN member rather than the parent physical port.—worked.

C:

The tunnel appears in member status and approved private traffic can select it. This would verify resolution of a different case: An IPsec overlay is present but its tunnel interface is not an SD-WAN member, so application rules cannot select the private WAN tunnel. It does not show that the reported issue was fixed or that its intended action—Use the configured VLAN subinterface as the intended SD-WAN member rather than the parent physical port.—worked.

D:

Probe packets use the intended routing context and the member reports correct reachability. This would verify resolution of a different case: An SD-WAN member's configured source interface is still associated with an old VRF and the health check is sent into a nonworking routing table. It does not show that the reported issue was fixed or that its intended action—Use the configured VLAN subinterface as the intended SD-WAN member rather than the parent physical port.—worked.

Question 383

The incident investigation at a national SOC records: A WAN port with a tagged provider VLAN is added to SD-WAN as the physical untagged port, so no valid IP traffic reaches the carrier. Which mechanism provides the strongest explanation?

  1. An invalid preferred member complicates path selection even when a working alternative exists.
  2. The SD-WAN member must reference the actual Layer 3 interface carrying the provider service.
  3. SD-WAN health checks depend on the member's valid routing and probe source context.
  4. A healthy tunnel interface does not establish route symmetry to every internal subnet.

Explanation

Correct Answer

B:

The SD-WAN member must reference the actual Layer 3 interface carrying the provider service. This explains why the reported condition occurs: A WAN port with a tagged provider VLAN is added to SD-WAN as the physical untagged port, so no valid IP traffic reaches the carrier. The targeted correction is: Use the configured VLAN subinterface as the intended SD-WAN member rather than the parent physical port.

Incorrect Answers

A:

An invalid preferred member complicates path selection even when a working alternative exists. This mechanism instead explains a separate problem: A small branch lists a disconnected spare physical port as the highest-preference member and fails over repeatedly before landing on a working path. The current incident requires the more directly applicable cause stated by the correct option.

C:

SD-WAN health checks depend on the member's valid routing and probe source context. This mechanism instead explains a separate problem: An SD-WAN member's configured source interface is still associated with an old VRF and the health check is sent into a nonworking routing table. The current incident requires the more directly applicable cause stated by the correct option.

D:

A healthy tunnel interface does not establish route symmetry to every internal subnet. This mechanism instead explains a separate problem: A FortiGate's overlay member health is green but its associated LAN subnet is not routed at the far end, producing one-way private application traffic. The current incident requires the more directly applicable cause stated by the correct option.

Question 384

After a corrective change at a national SOC, the team documents: A WAN port with a tagged provider VLAN is added to SD-WAN as the physical untagged port, so no valid IP traffic reaches the carrier. Which repeatable control BEST prevents a recurrence?

  1. Validate site template zone uniqueness and variable expansion before FortiManager install.
  2. Remove or explicitly disable unprovisioned members from active configurations.
  3. Check VLAN encapsulation and logical-interface selection during circuit acceptance.
  4. Verify VRF and source-interface dependencies whenever using segmented WAN routing.

Explanation

Correct Answer

C:

Check VLAN encapsulation and logical-interface selection during circuit acceptance. This control reduces recurrence of the documented mechanism: The SD-WAN member must reference the actual Layer 3 interface carrying the provider service. It creates a repeatable check around the needed response: Use the configured VLAN subinterface as the intended SD-WAN member rather than the parent physical port.

Incorrect Answers

A:

Validate site template zone uniqueness and variable expansion before FortiManager install. That safeguard addresses another potential failure: A configuration template assigns one WAN member to multiple intended zones through duplicated site definitions, causing a conflict during managed deployment. It is not the most targeted recurring control for the described cause: The SD-WAN member must reference the actual Layer 3 interface carrying the provider service.

B:

Remove or explicitly disable unprovisioned members from active configurations. That safeguard addresses another potential failure: A small branch lists a disconnected spare physical port as the highest-preference member and fails over repeatedly before landing on a working path. It is not the most targeted recurring control for the described cause: The SD-WAN member must reference the actual Layer 3 interface carrying the provider service.

D:

Verify VRF and source-interface dependencies whenever using segmented WAN routing. That safeguard addresses another potential failure: An SD-WAN member's configured source interface is still associated with an old VRF and the health check is sent into a nonworking routing table. It is not the most targeted recurring control for the described cause: The SD-WAN member must reference the actual Layer 3 interface carrying the provider service.

Question 385

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

  1. Use a suitable strategy and eligible link selection for bulk backups while retaining latency sensitivity for real-time apps.
  2. Re-enable the reviewed rule after resolving the fault and validate its actual match and member strategy.
  3. Select an appropriate fixed preferred member or session-persistent supported hash strategy for payment flows.
  4. Inspect the documented application learning and session steering stages, then align the fallback and app-based rule with the supported detection sequence.

Explanation

Correct Answer

A:

Use a suitable strategy and eligible link selection for bulk backups while retaining latency sensitivity for real-time apps. This is the most direct response to the stated incident: A link quality rule is configured to prefer the lowest measured latency but remote workers need consistent performance for large backups over a higher-capacity path. The technical mechanism is: The best path metric for latency-sensitive media may be inappropriate for bulk transfer applications. Confirmation requires: Backup throughput improves on the approved high-capacity link without disturbing voice prioritization.

Incorrect Answers

B:

Re-enable the reviewed rule after resolving the fault and validate its actual match and member strategy. That could address a different issue in the same blueprint area: A support team disables an SD-WAN service rule during troubleshooting and forgets the implicit rule now controls traffic, degrading latency. It does not directly correct the given incident, whose decisive mechanism is: The best path metric for latency-sensitive media may be inappropriate for bulk transfer applications.

C:

Select an appropriate fixed preferred member or session-persistent supported hash strategy for payment flows. That could address a different issue in the same blueprint area: 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 does not directly correct the given incident, whose decisive mechanism is: The best path metric for latency-sensitive media may be inappropriate for bulk transfer applications.

D:

Inspect the documented application learning and session steering stages, then align the fallback and app-based rule with the supported detection sequence. That could address a different issue in the same blueprint area: An application-based SD-WAN rule steers initial traffic through the wrong link before the application can be classified, confusing testers. It does not directly correct the given incident, whose decisive mechanism is: The best path metric for latency-sensitive media may be inappropriate for bulk transfer applications.

Question 386

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

  1. Normal traffic returns to the primary and failover still selects backup when appropriate.
  2. Backup throughput improves on the approved high-capacity link without disturbing voice prioritization.
  3. The tested application hits its dedicated rule ID and selects the approved private link.
  4. Only the target cloud service's sessions match the special forwarding rule.

Explanation

Correct Answer

B:

Backup throughput improves on the approved high-capacity link without disturbing voice prioritization. This evidence directly tests the intended corrective action: Use a suitable strategy and eligible link selection for bulk backups while retaining latency sensitivity for real-time apps. It confirms the failure mechanism—The best path metric for latency-sensitive media may be inappropriate for bulk transfer applications.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Normal traffic returns to the primary and failover still selects backup when appropriate. This would verify resolution of a different case: 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. It does not show that the reported issue was fixed or that its intended action—Use a suitable strategy and eligible link selection for bulk backups while retaining latency sensitivity for real-time apps.—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—Use a suitable strategy and eligible link selection for bulk backups while retaining latency sensitivity for real-time apps.—worked.

D:

Only the target cloud service's sessions match the special forwarding rule. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Use a suitable strategy and eligible link selection for bulk backups while retaining latency sensitivity for real-time apps.—worked.

Question 387

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

  1. The Best Quality strategy compares configured metrics, not an inferred universal quality score.
  2. Rules with stale member references cannot select removed circuits as intended.
  3. The best path metric for latency-sensitive media may be inappropriate for bulk transfer applications.
  4. Mis-scoped source matching in ordered rules creates unexpected path selection.

Explanation

Correct Answer

C:

The best path metric for latency-sensitive media may be inappropriate for bulk transfer applications. This explains why the reported condition occurs: A link quality rule is configured to prefer the lowest measured latency but remote workers need consistent performance for large backups over a higher-capacity path. The targeted correction is: Use a suitable strategy and eligible link selection for bulk backups while retaining latency sensitivity for real-time apps.

Incorrect Answers

A:

The Best Quality strategy compares configured metrics, not an inferred universal quality score. This mechanism instead explains a separate problem: An operator selects Best Quality but leaves the metric on latency when the business application is mainly disrupted by packet loss. The current incident requires the more directly applicable cause stated by the correct option.

B:

Rules with stale member references cannot select removed circuits as intended. This mechanism instead explains a separate problem: An SD-WAN rule uses a manual preferred member that's no longer provisioned after carrier cutover; otherwise healthy links are ignored. The current incident requires the more directly applicable cause stated by the correct option.

D:

Mis-scoped source matching in ordered rules creates unexpected path selection. This mechanism instead explains a separate problem: A high-priority rule for guest Internet traffic mistakenly matches the corporate workstation source segment and sends trusted users over a limited guest ISP. The current incident requires the more directly applicable cause stated by the correct option.

Question 388

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

  1. Record temporary rule-disable actions and require postincident restoration checks.
  2. Retire old member IDs from every dependent rule during carrier migration.
  3. Test rule selection, route lookup and firewall policy together for each service.
  4. Map application class to correct quality or capacity decision policy.

Explanation

Correct Answer

D:

Map application class to correct quality or capacity decision policy. This control reduces recurrence of the documented mechanism: The best path metric for latency-sensitive media may be inappropriate for bulk transfer applications. It creates a repeatable check around the needed response: Use a suitable strategy and eligible link selection for bulk backups while retaining latency sensitivity for real-time apps.

Incorrect Answers

A:

Record temporary rule-disable actions and require postincident restoration checks. That safeguard addresses another potential failure: A support team disables an SD-WAN service rule during troubleshooting and forgets the implicit rule now controls traffic, degrading latency. It is not the most targeted recurring control for the described cause: The best path metric for latency-sensitive media may be inappropriate for bulk transfer applications.

B:

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: The best path metric for latency-sensitive media may be inappropriate for bulk transfer applications.

C:

Test rule selection, route lookup and firewall policy together for each service. That safeguard addresses another potential failure: A transaction flow is directed to a preferred member despite no matching route for its destination through that member, producing packet drops. It is not the most targeted recurring control for the described cause: The best path metric for latency-sensitive media may be inappropriate for bulk transfer applications.

Question 389

During an incident triage, an administrator reports at a regional data center: A company plans browser-only secure web gateway use for contractors but distributes an agent-based full-tunnel guide requiring managed endpoint enrollment. What should the team change or investigate FIRST?

  1. Install the approved PAC/manual proxy settings or supported agentless onboarding method for intended browsers.
  2. Use the supported agentless SWG proxy onboarding instructions for the contractor population.
  3. Correct the supported group-specific onboarding and region assignment while preserving identity and security controls.
  4. Update the approved SAML trust, entity ID and assertion configuration on both FortiSASE and IdP.

Explanation

Correct Answer

B:

Use the supported agentless SWG proxy onboarding instructions for the contractor population. This is the most direct response to the stated incident: A company plans browser-only secure web gateway use for contractors but distributes an agent-based full-tunnel guide requiring managed endpoint enrollment. The technical mechanism is: Agentless SWG and FortiClient agent-based onboarding are different access models. Confirmation requires: A browser-only test reaches approved web destinations through the intended proxy without a managed VPN agent.

Incorrect Answers

A:

Install the approved PAC/manual proxy settings or supported agentless onboarding method for intended browsers. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Agentless SWG and FortiClient agent-based onboarding are different access models.

C:

Correct the supported group-specific onboarding and region assignment while preserving identity and security controls. That could address a different issue in the same blueprint area: An endpoint registers successfully but the FortiClient service profile applies to the wrong geographic user group, routing employees through a distant PoP. It does not directly correct the given incident, whose decisive mechanism is: Agentless SWG and FortiClient agent-based onboarding are different access models.

D:

Update the approved SAML trust, entity ID and assertion configuration on both FortiSASE and IdP. That could address a different issue in the same blueprint area: Users are assigned to a FortiSASE SAML login profile but the identity provider does not trust the current service provider entity ID. It does not directly correct the given incident, whose decisive mechanism is: Agentless SWG and FortiClient agent-based onboarding are different access models.

Question 390

Following remediation at a regional data center, engineers revisit: A company plans browser-only secure web gateway use for contractors but distributes an agent-based full-tunnel guide requiring managed endpoint enrollment. Which observation would BEST prove the specific issue is resolved?

  1. Each tested OS uses a compatible approved onboarding mode with expected security restrictions.
  2. A clean installation enrolls to the correct tenant and establishes a protected connection.
  3. A browser-only test reaches approved web destinations through the intended proxy without a managed VPN agent.
  4. Browser-only sign-in completes without redirect loops and the protected web session is logged.

Explanation

Correct Answer

C:

A browser-only test reaches approved web destinations through the intended proxy without a managed VPN agent. This evidence directly tests the intended corrective action: Use the supported agentless SWG proxy onboarding instructions for the contractor population. It confirms the failure mechanism—Agentless SWG and FortiClient agent-based onboarding are different access models.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Use the supported agentless SWG proxy onboarding instructions for the contractor population.—worked.

B:

A clean installation enrolls to the correct tenant and establishes a protected connection. This would verify resolution of a different case: A corporate FortiClient enrollment profile specifies an obsolete FortiSASE service endpoint after a regional service migration, and new clients cannot connect. It does not show that the reported issue was fixed or that its intended action—Use the supported agentless SWG proxy onboarding instructions for the contractor population.—worked.

D:

Browser-only sign-in completes without redirect loops and the protected web session is logged. This would verify resolution of a different case: A contractor's browser proxy authentication loops because SAML redirect URLs retain an old domain after a secure web gateway hostname change. It does not show that the reported issue was fixed or that its intended action—Use the supported agentless SWG proxy onboarding instructions for the contractor population.—worked.

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