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 63

Question 620

An operations group at a service-provider edge resolved: A compliance lead assumes the lack of an old web security event in a current report proves it never occurred, despite a shorter log retention period. Which ongoing safeguard should become part of its change process?

  1. Use report types aligned to the underlying control, not generic bandwidth summaries.
  2. Align report retention and archive requirements with audit lookback obligations.
  3. Include PoP and user-path dimensions in recurring SASE experience reports.
  4. Define active-user criteria and use them consistently in usage reporting.

Explanation

Correct Answer

B:

Align report retention and archive requirements with audit lookback obligations. This control reduces recurrence of the documented mechanism: Retention expiry can remove evidence from routine queries without proving an event absent. It creates a repeatable check around the needed response: Check the documented log-retention window and any authorized archive sources before drawing conclusions.

Incorrect Answers

A:

Use report types aligned to the underlying control, not generic bandwidth summaries. That safeguard addresses another potential failure: Managers request a list of users blocked by DLP policy, but the standard Internet traffic summary contains only successful requests. It is not the most targeted recurring control for the described cause: Retention expiry can remove evidence from routine queries without proving an event absent.

C:

Include PoP and user-path dimensions in recurring SASE experience reports. That safeguard addresses another potential failure: A branch performance dashboard claims a cloud PoP is at fault during slow browsing but includes no per-PoP user experience or latency segmentation. It is not the most targeted recurring control for the described cause: Retention expiry can remove evidence from routine queries without proving an event absent.

D:

Define active-user criteria and use them consistently in usage reporting. That safeguard addresses another potential failure: A quarterly SASE adoption report counts all provisioned users as active remote users even though many have never authenticated. It is not the most targeted recurring control for the described cause: Retention expiry can remove evidence from routine queries without proving an event absent.

Question 621

At a national SOC, a security analyst is reviewing this failure during a configuration rollout: A small branch lists a disconnected spare physical port as the highest-preference member and fails over repeatedly before landing on a working path. 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 that member's gateway to the address supplied by the new CPE and verify routing.
  3. Use the configured VLAN subinterface as the intended SD-WAN member rather than the parent physical port.
  4. Disable the unused member or correct its failover preference and health parameters.

Explanation

Correct Answer

D:

Disable the unused member or correct its failover preference and health parameters. This is the most direct response to the stated incident: 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 technical mechanism is: An invalid preferred member complicates path selection even when a working alternative exists. Confirmation requires: Steering diagnostics select healthy installed paths without oscillating through the spare port.

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: An invalid preferred member complicates path selection even when a working alternative exists.

B:

Update that member's gateway to the address supplied by the new CPE and verify routing. That could address a different issue in the same blueprint area: After replacing an ISP CPE, the old FortiGate member gateway remains configured and SLA probes fail despite the interface showing link up. It does not directly correct the given incident, whose decisive mechanism is: An invalid preferred member complicates path selection even when a working alternative exists.

C:

Use the configured VLAN subinterface as the intended SD-WAN member rather than the parent physical port. That could address a different issue in the same blueprint area: 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. It does not directly correct the given incident, whose decisive mechanism is: An invalid preferred member complicates path selection even when a working alternative exists.

Question 622

During follow-up testing at a national SOC, the original fault was: A small branch lists a disconnected spare physical port as the highest-preference member and fails over repeatedly before landing on a working path. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. Steering diagnostics select healthy installed paths without oscillating through the spare port.
  2. The private network prefix has an active route and test traffic follows the intended new member group.
  3. The tunnel appears in member status and approved private traffic can select it.
  4. Two-way packets reach the private application through the overlay without asymmetric return failure.

Explanation

Correct Answer

A:

Steering diagnostics select healthy installed paths without oscillating through the spare port. This evidence directly tests the intended corrective action: Disable the unused member or correct its failover preference and health parameters. It confirms the failure mechanism—An invalid preferred member complicates path selection even when a working alternative exists.—has been addressed in the actual affected flow.

Incorrect Answers

B:

The private network prefix has an active route and test traffic follows the intended new member group. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Disable the unused member or correct its failover preference and health parameters.—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—Disable the unused member or correct its failover preference and health parameters.—worked.

D:

Two-way packets reach the private application through the overlay without asymmetric return failure. This would verify resolution of a different case: 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. It does not show that the reported issue was fixed or that its intended action—Disable the unused member or correct its failover preference and health parameters.—worked.

Question 623

The incident investigation at a national SOC records: A small branch lists a disconnected spare physical port as the highest-preference member and fails over repeatedly before landing on a working path. Which mechanism provides the strongest explanation?

  1. Inconsistent member-to-zone declarations are not a valid substitute for separate routing groups.
  2. An invalid preferred member complicates path selection even when a working alternative exists.
  3. Physical carrier detection does not confirm a correct next-hop gateway.
  4. SD-WAN cannot steer into an overlay that is absent from eligible members.

Explanation

Correct Answer

B:

An invalid preferred member complicates path selection even when a working alternative exists. This explains why the reported condition occurs: 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 targeted correction is: Disable the unused member or correct its failover preference and health parameters.

Incorrect Answers

A:

Inconsistent member-to-zone declarations are not a valid substitute for separate routing groups. This mechanism instead explains a separate problem: A configuration template assigns one WAN member to multiple intended zones through duplicated site definitions, causing a conflict during managed deployment. The current incident requires the more directly applicable cause stated by the correct option.

C:

Physical carrier detection does not confirm a correct next-hop gateway. This mechanism instead explains a separate problem: After replacing an ISP CPE, the old FortiGate member gateway remains configured and SLA probes fail despite the interface showing link up. The current incident requires the more directly applicable cause stated by the correct option.

D:

SD-WAN cannot steer into an overlay that is absent from eligible members. This mechanism instead explains a separate problem: An IPsec overlay is present but its tunnel interface is not an SD-WAN member, so application rules cannot select the private WAN tunnel. The current incident requires the more directly applicable cause stated by the correct option.

Question 624

After a corrective change at a national SOC, the team documents: A small branch lists a disconnected spare physical port as the highest-preference member and fails over repeatedly before landing on a working path. Which repeatable control BEST prevents a recurrence?

  1. Inspect member-to-zone assignments during every underlay and overlay design review.
  2. Record circuit ID and interface mapping and test egress identity after cabling work.
  3. Remove or explicitly disable unprovisioned members from active configurations.
  4. Explicitly specify member zone instead of relying on defaults in site templates.

Explanation

Correct Answer

C:

Remove or explicitly disable unprovisioned members from active configurations. This control reduces recurrence of the documented mechanism: An invalid preferred member complicates path selection even when a working alternative exists. It creates a repeatable check around the needed response: Disable the unused member or correct its failover preference and health parameters.

Incorrect Answers

A:

Inspect member-to-zone assignments during every underlay and overlay design review. That safeguard addresses another potential failure: An engineer associates a backup MPLS tunnel with the Internet-DIA zone instead of the private overlay zone, exposing it to Internet traffic selection. It is not the most targeted recurring control for the described cause: An invalid preferred member complicates path selection even when a working alternative exists.

B:

Record circuit ID and interface mapping and test egress identity after cabling work. That safeguard addresses another potential failure: Two ISP circuits share similar port labels and an engineer reverses wan1 and wan2 member metadata, sending regulated traffic to the wrong provider. It is not the most targeted recurring control for the described cause: An invalid preferred member complicates path selection even when a working alternative exists.

D:

Explicitly specify member zone instead of relying on defaults in site templates. That safeguard addresses another potential failure: A new tunnel member is added under the default virtual-wan-link zone although the architecture requires region-specific security controls. It is not the most targeted recurring control for the described cause: An invalid preferred member complicates path selection even when a working alternative exists.

Question 625

During a quarterly compliance review at a financial services branch, analysts observe: An admin adds a route to an SD-WAN zone but leaves one member without its required gateway or health check, causing failover to an unusable next hop. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Correct the affected member route and gateway configuration and check its health before selection.
  2. Correct the approved prefix advertisement or route filter on the relevant BGP peers.
  3. Define the appropriate scoped SD-WAN service rule to enforce provider preference over equal-cost eligible routes.
  4. Adjust competing static and dynamic route preference so the valid overlay next hop is selected.

Explanation

Correct Answer

A:

Correct the affected member route and gateway configuration and check its health before selection. This is the most direct response to the stated incident: An admin adds a route to an SD-WAN zone but leaves one member without its required gateway or health check, causing failover to an unusable next hop. The technical mechanism is: Zone route existence does not guarantee that each candidate member has usable next-hop reachability. Confirmation requires: Failure of the first ISP sends sessions through the second member with successful return traffic.

Incorrect Answers

B:

Correct the approved prefix advertisement or route filter on the relevant BGP peers. That could address a different issue in the same blueprint area: A branch uses BGP to advertise overlay prefixes but a filtered remote office subnet is missing from received routes. It does not directly correct the given incident, whose decisive mechanism is: Zone route existence does not guarantee that each candidate member has usable next-hop reachability.

C:

Define the appropriate scoped SD-WAN service rule to enforce provider preference over equal-cost eligible routes. That could address a different issue in the same blueprint area: A device has two equal-cost underlay routes but an application must use one provider for compliance while SD-WAN service matching is absent. It does not directly correct the given incident, whose decisive mechanism is: Zone route existence does not guarantee that each candidate member has usable next-hop reachability.

D:

Adjust competing static and dynamic route preference so the valid overlay next hop is selected. That could address a different issue in the same blueprint area: A VPN overlay uses dynamic routing but an old static route for the same branch prefix takes precedence and sends traffic through an unreachable tunnel. It does not directly correct the given incident, whose decisive mechanism is: Zone route existence does not guarantee that each candidate member has usable next-hop reachability.

Question 626

At a financial services branch, a test team is validating a change after this incident: An admin adds a route to an SD-WAN zone but leaves one member without its required gateway or health check, causing failover to an unusable next hop. What evidence most directly verifies the intended outcome?

  1. A route lookup resolves the data-center prefix and a controlled session completes through the overlay.
  2. Failure of the first ISP sends sessions through the second member with successful return traffic.
  3. Failure probes trigger the expected routing/member eligibility change and traffic uses an alternate path.
  4. Route lookup for the specific host now uses the intended overlay path.

Explanation

Correct Answer

B:

Failure of the first ISP sends sessions through the second member with successful return traffic. This evidence directly tests the intended corrective action: Correct the affected member route and gateway configuration and check its health before selection. It confirms the failure mechanism—Zone route existence does not guarantee that each candidate member has usable next-hop reachability.—has been addressed in the actual affected flow.

Incorrect Answers

A:

A route lookup resolves the data-center prefix and a controlled session completes through the overlay. This would verify resolution of a different case: A branch firewall policy allows corporate traffic and an SD-WAN service is configured, but the route table lacks a prefix for the data-center network. It does not show that the reported issue was fixed or that its intended action—Correct the affected member route and gateway configuration and check its health before selection.—worked.

C:

Failure probes trigger the expected routing/member eligibility change and traffic uses an alternate path. This would verify resolution of a different case: A preferred WAN becomes unhealthy and is withdrawn from service, but its route remains installed due to an incorrect health state-action setting. It does not show that the reported issue was fixed or that its intended action—Correct the affected member route and gateway configuration and check its health before selection.—worked.

D:

Route lookup for the specific host now uses the intended overlay path. This would verify resolution of a different case: A new branch subnet has a longer specific static route pointing to an old MPLS path, overriding the intended broader overlay route. It does not show that the reported issue was fixed or that its intended action—Correct the affected member route and gateway configuration and check its health before selection.—worked.

Question 627

A Fortinet administrator at a financial services branch is assessing: An admin adds a route to an SD-WAN zone but leaves one member without its required gateway or health check, causing failover to an unusable next hop. What is the most relevant root cause?

  1. Rule matching does not compensate for missing destination route state.
  2. Overlay routing policy can suppress reachability even with healthy IPsec members.
  3. Zone route existence does not guarantee that each candidate member has usable next-hop reachability.
  4. Existing stateful sessions and NAT mappings may not transfer transparently between providers.

Explanation

Correct Answer

C:

Zone route existence does not guarantee that each candidate member has usable next-hop reachability. This explains why the reported condition occurs: An admin adds a route to an SD-WAN zone but leaves one member without its required gateway or health check, causing failover to an unusable next hop. The targeted correction is: Correct the affected member route and gateway configuration and check its health before selection.

Incorrect Answers

A:

Rule matching does not compensate for missing destination route state. This mechanism instead explains a separate problem: A FortiGate Internet flow matches an expected SD-WAN rule but outgoing packets have no policy-approved route because the zone default route was deleted by a script. The current incident requires the more directly applicable cause stated by the correct option.

B:

Overlay routing policy can suppress reachability even with healthy IPsec members. This mechanism instead explains a separate problem: A branch uses BGP to advertise overlay prefixes but a filtered remote office subnet is missing from received routes. The current incident requires the more directly applicable cause stated by the correct option.

D:

Existing stateful sessions and NAT mappings may not transfer transparently between providers. This mechanism instead explains a separate problem: An Internet route remains valid after wan1 failure but existing long-lived TCP sessions continue using the failed translated path and do not instantly recover. The current incident requires the more directly applicable cause stated by the correct option.

Question 628

A risk review at a financial services branch focuses on preventing this issue again: An admin adds a route to an SD-WAN zone but leaves one member without its required gateway or health check, causing failover to an unusable next hop. Which recurring control is most suitable?

  1. Test both new and established sessions during WAN failure acceptance criteria.
  2. Test advertised and accepted prefix lists across SD-WAN overlays after address expansion.
  3. Verify destination and reverse-path routing whenever moving internal VLANs.
  4. Validate all member gateways and live forwarding during individual link isolation tests.

Explanation

Correct Answer

D:

Validate all member gateways and live forwarding during individual link isolation tests. This control reduces recurrence of the documented mechanism: Zone route existence does not guarantee that each candidate member has usable next-hop reachability. It creates a repeatable check around the needed response: Correct the affected member route and gateway configuration and check its health before selection.

Incorrect Answers

A:

Test both new and established sessions during WAN failure acceptance criteria. That safeguard addresses another potential failure: An Internet route remains valid after wan1 failure but existing long-lived TCP sessions continue using the failed translated path and do not instantly recover. It is not the most targeted recurring control for the described cause: Zone route existence does not guarantee that each candidate member has usable next-hop reachability.

B:

Test advertised and accepted prefix lists across SD-WAN overlays after address expansion. That safeguard addresses another potential failure: A branch uses BGP to advertise overlay prefixes but a filtered remote office subnet is missing from received routes. It is not the most targeted recurring control for the described cause: Zone route existence does not guarantee that each candidate member has usable next-hop reachability.

C:

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: Zone route existence does not guarantee that each candidate member has usable next-hop reachability.

Question 629

During a production service incident, an administrator reports at a regional data center: FortiClient is installed but its VPN connection uses a direct on-premises FortiGate tunnel instead of the intended FortiSASE service. What should the team change or investigate FIRST?

  1. Refresh the supported identity/group mapping and confirm revocation of stale authorization.
  2. Deploy the correct approved FortiSASE connection profile and remove the obsolete client target.
  3. Correct the supported group-specific onboarding and region assignment while preserving identity and security controls.
  4. Coordinate signing certificate rollover with an overlap or scheduled trust update under the supported federation process.

Explanation

Correct Answer

B:

Deploy the correct approved FortiSASE connection profile and remove the obsolete client target. This is the most direct response to the stated incident: FortiClient is installed but its VPN connection uses a direct on-premises FortiGate tunnel instead of the intended FortiSASE service. The technical mechanism is: Installing FortiClient does not guarantee it targets the correct security service. Confirmation requires: Connection status shows the FortiSASE service and security traffic enters the expected PoP.

Incorrect Answers

A:

Refresh the supported identity/group mapping and confirm revocation of stale authorization. That could address a different issue in the same blueprint area: A remote worker successfully authenticates to FortiSASE but a stale identity group cache keeps applying a former privileged access policy. It does not directly correct the given incident, whose decisive mechanism is: Installing FortiClient does not guarantee it targets the correct security service.

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: Installing FortiClient does not guarantee it targets the correct security service.

D:

Coordinate signing certificate rollover with an overlap or scheduled trust update under the supported federation process. That could address a different issue in the same blueprint area: An IdP migration removes a FortiSASE SAML signing certificate before the replacement has been accepted by the service provider. It does not directly correct the given incident, whose decisive mechanism is: Installing FortiClient does not guarantee it targets the correct security service.

Question 630

Following remediation at a regional data center, engineers revisit: FortiClient is installed but its VPN connection uses a direct on-premises FortiGate tunnel instead of the intended FortiSASE service. Which observation would BEST prove the specific issue is resolved?

  1. Managed clients validate legitimate inspection certificates without unsafe click-through exceptions.
  2. A test user's RADIUS request succeeds with expected acceptance and group behavior.
  3. Connection status shows the FortiSASE service and security traffic enters the expected PoP.
  4. A user in the previously omitted OU is found and permitted according to group rules.

Explanation

Correct Answer

C:

Connection status shows the FortiSASE service and security traffic enters the expected PoP. This evidence directly tests the intended corrective action: Deploy the correct approved FortiSASE connection profile and remove the obsolete client target. It confirms the failure mechanism—Installing FortiClient does not guarantee it targets the correct security service.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Managed clients validate legitimate inspection certificates without unsafe click-through exceptions. This would verify resolution of a different case: A site lets users bypass required certificate trust warnings by manually accepting an unexpected FortiSASE proxy certificate on every device. It does not show that the reported issue was fixed or that its intended action—Deploy the correct approved FortiSASE connection profile and remove the obsolete client target.—worked.

B:

A test user's RADIUS request succeeds with expected acceptance and group behavior. This would verify resolution of a different case: A FortiSASE tenant uses RADIUS for user authentication but the RADIUS shared secret was changed on FortiAuthenticator only. It does not show that the reported issue was fixed or that its intended action—Deploy the correct approved FortiSASE connection profile and remove the obsolete client target.—worked.

D:

A user in the previously omitted OU is found and permitted according to group rules. This would verify resolution of a different case: A remote user enters a correct password but FortiSASE authentication against a central LDAP directory fails because the configured base DN excludes that organizational unit. It does not show that the reported issue was fixed or that its intended action—Deploy the correct approved FortiSASE connection profile and remove the obsolete client target.—worked.

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