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 57

Question 560

After a corrective change at a corporate headquarters, the team documents: A scheduled SOC summary is not delivered because its email recipient list still points to an abandoned security distribution mailbox. Which repeatable control BEST prevents a recurrence?

  1. Use report types aligned to the underlying control, not generic bandwidth summaries.
  2. Maintain approved user-attribution data sources and privacy access controls for incident reports.
  3. Review report destinations and recipients at every operations staffing change.
  4. Include PoP and user-path dimensions in recurring SASE experience reports.

Explanation

Correct Answer

C:

Review report destinations and recipients at every operations staffing change. This control reduces recurrence of the documented mechanism: Report generation and delivery routing are separate operational dependencies. It creates a repeatable check around the needed response: Update the report distribution profile with the approved current recipient addresses and delivery settings.

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: Report generation and delivery routing are separate operational dependencies.

B:

Maintain approved user-attribution data sources and privacy access controls for incident reports. That safeguard addresses another potential failure: A user activity report identifies only egress addresses and application names while investigators require an authorized account-level trace for a confirmed DLP event. It is not the most targeted recurring control for the described cause: Report generation and delivery routing are separate operational dependencies.

D:

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: Report generation and delivery routing are separate operational dependencies.

Question 561

During a quarterly compliance review at a distributed branch estate, analysts observe: A branch's overlay tunnel is administratively up but points to a remote peer address that changed during cloud migration, so private-app sessions time out. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Update the supported IPsec peer configuration and confirm the tunnel member can carry authenticated traffic.
  2. Remove or migrate the dependent SD-WAN member and associated route or rule references before deleting the interface.
  3. Update that member's gateway to the address supplied by the new CPE and verify routing.
  4. Create or select the region-approved SD-WAN zone and assign the tunnel member to it.

Explanation

Correct Answer

A:

Update the supported IPsec peer configuration and confirm the tunnel member can carry authenticated traffic. This is the most direct response to the stated incident: A branch's overlay tunnel is administratively up but points to a remote peer address that changed during cloud migration, so private-app sessions time out. The technical mechanism is: Membership does not guarantee an IPsec overlay's far-end peer is reachable or authenticated. Confirmation requires: Private test traffic passes end-to-end through the established and monitored tunnel.

Incorrect Answers

B:

Remove or migrate the dependent SD-WAN member and associated route or rule references before deleting the interface. That could address a different issue in the same blueprint area: An administrator deletes a physical WAN interface that is still referenced by an active SD-WAN member, resulting in blocked change validation. It does not directly correct the given incident, whose decisive mechanism is: Membership does not guarantee an IPsec overlay's far-end peer is reachable or authenticated.

C:

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: Membership does not guarantee an IPsec overlay's far-end peer is reachable or authenticated.

D:

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: Membership does not guarantee an IPsec overlay's far-end peer is reachable or authenticated.

Question 562

At a distributed branch estate, a test team is validating a change after this incident: A branch's overlay tunnel is administratively up but points to a remote peer address that changed during cloud migration, so private-app sessions time out. What evidence most directly verifies the intended outcome?

  1. The tunnel appears in member status and approved private traffic can select it.
  2. Private test traffic passes end-to-end through the established and monitored tunnel.
  3. Configuration install succeeds and each member appears in one approved operational grouping.
  4. Member health recovers and eligible sessions traverse the replaced ISP link.

Explanation

Correct Answer

B:

Private test traffic passes end-to-end through the established and monitored tunnel. This evidence directly tests the intended corrective action: Update the supported IPsec peer configuration and confirm the tunnel member can carry authenticated traffic. It confirms the failure mechanism—Membership does not guarantee an IPsec overlay's far-end peer is reachable or authenticated.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Update the supported IPsec peer configuration and confirm the tunnel member can carry authenticated traffic.—worked.

C:

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—Update the supported IPsec peer configuration and confirm the tunnel member can carry authenticated traffic.—worked.

D:

Member health recovers and eligible sessions traverse the replaced ISP link. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Update the supported IPsec peer configuration and confirm the tunnel member can carry authenticated traffic.—worked.

Question 563

A Fortinet administrator at a distributed branch estate is assessing: A branch's overlay tunnel is administratively up but points to a remote peer address that changed during cloud migration, so private-app sessions time out. What is the most relevant root cause?

  1. An invalid preferred member complicates path selection even when a working alternative exists.
  2. Inconsistent member-to-zone declarations are not a valid substitute for separate routing groups.
  3. Membership does not guarantee an IPsec overlay's far-end peer is reachable or authenticated.
  4. Logical member identifiers must correspond to the actual provider circuits used in policy.

Explanation

Correct Answer

C:

Membership does not guarantee an IPsec overlay's far-end peer is reachable or authenticated. This explains why the reported condition occurs: A branch's overlay tunnel is administratively up but points to a remote peer address that changed during cloud migration, so private-app sessions time out. The targeted correction is: Update the supported IPsec peer configuration and confirm the tunnel member can carry authenticated traffic.

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.

B:

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.

D:

Logical member identifiers must correspond to the actual provider circuits used in policy. This mechanism instead explains a separate problem: Two ISP circuits share similar port labels and an engineer reverses wan1 and wan2 member metadata, sending regulated traffic to the wrong provider. The current incident requires the more directly applicable cause stated by the correct option.

Question 564

A risk review at a distributed branch estate focuses on preventing this issue again: A branch's overlay tunnel is administratively up but points to a remote peer address that changed during cloud migration, so private-app sessions time out. Which recurring control is most suitable?

  1. Inspect member-to-zone assignments during every underlay and overlay design review.
  2. Document metered paths and verify per-application allowed traffic before deployment.
  3. Check VLAN encapsulation and logical-interface selection during circuit acceptance.
  4. Confirm peer endpoints and cryptographic state before advertising overlay members healthy.

Explanation

Correct Answer

D:

Confirm peer endpoints and cryptographic state before advertising overlay members healthy. This control reduces recurrence of the documented mechanism: Membership does not guarantee an IPsec overlay's far-end peer is reachable or authenticated. It creates a repeatable check around the needed response: Update the supported IPsec peer configuration and confirm the tunnel member can carry authenticated traffic.

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: Membership does not guarantee an IPsec overlay's far-end peer is reachable or authenticated.

B:

Document metered paths and verify per-application allowed traffic before deployment. That safeguard addresses another potential failure: Two Internet uplinks are grouped into one zone but the branch needs separate policy treatment for metered mobile connectivity during outages. It is not the most targeted recurring control for the described cause: Membership does not guarantee an IPsec overlay's far-end peer is reachable or authenticated.

C:

Check VLAN encapsulation and logical-interface selection during circuit acceptance. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Membership does not guarantee an IPsec overlay's far-end peer is reachable or authenticated.

Question 565

During a production service incident, an administrator reports at a research campus: An engineer confuses SD-WAN rules with firewall security policies and creates only an SD-WAN service for a new partner app, which remains denied. What should the team change or investigate FIRST?

  1. Correct the affected member route and gateway configuration and check its health before selection.
  2. Add a narrowly scoped firewall permit for the partner application and correct SD-WAN destination zone.
  3. Configure supported SLA member state or route-removal behavior to match documented failover policy.
  4. Adjust competing static and dynamic route preference so the valid overlay next hop is selected.

Explanation

Correct Answer

B:

Add a narrowly scoped firewall permit for the partner application and correct SD-WAN destination zone. This is the most direct response to the stated incident: An engineer confuses SD-WAN rules with firewall security policies and creates only an SD-WAN service for a new partner app, which remains denied. The technical mechanism is: Path steering determines link use; firewall policy separately authorizes traffic. Confirmation requires: Logs show both the intended Security policy permit and the expected SD-WAN path selection.

Incorrect Answers

A:

Correct the affected member route and gateway configuration and check its health before selection. That could address a different issue in the same blueprint area: 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. It does not directly correct the given incident, whose decisive mechanism is: Path steering determines link use; firewall policy separately authorizes traffic.

C:

Configure supported SLA member state or route-removal behavior to match documented failover policy. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Path steering determines link use; firewall policy separately authorizes traffic.

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: Path steering determines link use; firewall policy separately authorizes traffic.

Question 566

Following remediation at a research campus, engineers revisit: An engineer confuses SD-WAN rules with firewall security policies and creates only an SD-WAN service for a new partner app, which remains denied. Which observation would BEST prove the specific issue is resolved?

  1. Private addresses use the overlay while Internet destinations use direct access.
  2. Packet captures show forward and return traffic traversing the intended approved overlay.
  3. Logs show both the intended Security policy permit and the expected SD-WAN path selection.
  4. The missing subnet appears in the routing information base and private sessions complete.

Explanation

Correct Answer

C:

Logs show both the intended Security policy permit and the expected SD-WAN path selection. This evidence directly tests the intended corrective action: Add a narrowly scoped firewall permit for the partner application and correct SD-WAN destination zone. It confirms the failure mechanism—Path steering determines link use; firewall policy separately authorizes traffic.—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—Add a narrowly scoped firewall permit for the partner application and correct SD-WAN destination zone.—worked.

B:

Packet captures show forward and return traffic traversing the intended approved overlay. This would verify resolution of a different case: A new IPsec tunnel is added as an SD-WAN member yet the remote LAN gateway replies through a third-party cloud path because route advertisement is asymmetric. It does not show that the reported issue was fixed or that its intended action—Add a narrowly scoped firewall permit for the partner application and correct SD-WAN destination zone.—worked.

D:

The missing subnet appears in the routing information base and private sessions complete. This would verify resolution of a different case: A branch uses BGP to advertise overlay prefixes but a filtered remote office subnet is missing from received routes. It does not show that the reported issue was fixed or that its intended action—Add a narrowly scoped firewall permit for the partner application and correct SD-WAN destination zone.—worked.

Question 567

During a production service incident, this condition is reported: An engineer confuses SD-WAN rules with firewall security policies and creates only an SD-WAN service for a new partner app, which remains denied. Which technical explanation MOST directly accounts for the failure?

  1. Zone route existence does not guarantee that each candidate member has usable next-hop reachability.
  2. Overlay routing policy can suppress reachability even with healthy IPsec members.
  3. Central route templates can override manually repaired local routes during later installs.
  4. Path steering determines link use; firewall policy separately authorizes traffic.

Explanation

Correct Answer

D:

Path steering determines link use; firewall policy separately authorizes traffic. This explains why the reported condition occurs: An engineer confuses SD-WAN rules with firewall security policies and creates only an SD-WAN service for a new partner app, which remains denied. The targeted correction is: Add a narrowly scoped firewall permit for the partner application and correct SD-WAN destination zone.

Incorrect Answers

A:

Zone route existence does not guarantee that each candidate member has usable next-hop reachability. This mechanism instead explains a separate problem: 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 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.

C:

Central route templates can override manually repaired local routes during later installs. This mechanism instead explains a separate problem: A FortiGate has the correct SD-WAN zone route for corporate VPN but FortiManager installs a conflicting stale prefix route during configuration synchronization. The current incident requires the more directly applicable cause stated by the correct option.

Question 568

During a post-incident review at a research campus, the original problem was: An engineer confuses SD-WAN rules with firewall security policies and creates only an SD-WAN service for a new partner app, which remains denied. Which preventive practice most directly addresses its cause?

  1. Require matched firewall rule plus route and SD-WAN rule evidence for application go-live.
  2. Inventory policy routes before changing SD-WAN service matching.
  3. Verify destination and reverse-path routing whenever moving internal VLANs.
  4. Compare FIB and BGP/OSPF candidates when troubleshooting overlay blackholes.

Explanation

Correct Answer

A:

Require matched firewall rule plus route and SD-WAN rule evidence for application go-live. This control reduces recurrence of the documented mechanism: Path steering determines link use; firewall policy separately authorizes traffic. It creates a repeatable check around the needed response: Add a narrowly scoped firewall permit for the partner application and correct SD-WAN destination zone.

Incorrect Answers

B:

Inventory policy routes before changing SD-WAN service matching. That safeguard addresses another potential failure: Traffic matching a local policy route is forced toward an outdated VPN tunnel instead of following the updated SD-WAN rule. It is not the most targeted recurring control for the described cause: Path steering determines link use; firewall policy separately authorizes traffic.

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: Path steering determines link use; firewall policy separately authorizes traffic.

D:

Compare FIB and BGP/OSPF candidates when troubleshooting overlay blackholes. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Path steering determines link use; firewall policy separately authorizes traffic.

Question 569

A firewall operations team at a service-provider edge encounters the following during a predeployment acceptance test: A team deploys an agentless SWG configuration but omits browser or system proxy settings, causing traffic to connect directly to Internet sites. Which action most directly restores the approved security outcome?

  1. Coordinate signing certificate rollover with an overlap or scheduled trust update under the supported federation process.
  2. Deploy and register the compatible FortiClient agent using the approved enrollment process.
  3. Install the approved PAC/manual proxy settings or supported agentless onboarding method for intended browsers.
  4. Update the approved FortiClient registration or connection profile to the current service endpoint.

Explanation

Correct Answer

C:

Install the approved PAC/manual proxy settings or supported agentless onboarding method for intended browsers. This is the most direct response to the stated incident: A team deploys an agentless SWG configuration but omits browser or system proxy settings, causing traffic to connect directly to Internet sites. The technical mechanism is: A proxy account alone does not intercept browser traffic without the client directing sessions to it. Confirmation requires: Test web access appears in FortiSASE SWG logs and nonproxy direct browsing is appropriately restricted.

Incorrect Answers

A:

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: A proxy account alone does not intercept browser traffic without the client directing sessions to it.

B:

Deploy and register the compatible FortiClient agent using the approved enrollment process. That could address a different issue in the same blueprint area: Remote employees are instructed to use FortiSASE agent-based protection but no FortiClient installation or managed registration has been completed. It does not directly correct the given incident, whose decisive mechanism is: A proxy account alone does not intercept browser traffic without the client directing sessions to it.

D:

Update the approved FortiClient registration or connection profile to the current service endpoint. That could address a different issue in the same blueprint area: A corporate FortiClient enrollment profile specifies an obsolete FortiSASE service endpoint after a regional service migration, and new clients cannot connect. It does not directly correct the given incident, whose decisive mechanism is: A proxy account alone does not intercept browser traffic without the client directing sessions to it.

Question 570

An operations review at a service-provider edge has corrected: A team deploys an agentless SWG configuration but omits browser or system proxy settings, causing traffic to connect directly to Internet sites. Which observation specifically confirms success?

  1. A test user's RADIUS request succeeds with expected acceptance and group behavior.
  2. A browser-only test reaches approved web destinations through the intended proxy without a managed VPN agent.
  3. SAML assertions signed by the new key authenticate for pilot users and no unexpected outages occur.
  4. Test web access appears in FortiSASE SWG logs and nonproxy direct browsing is appropriately restricted.

Explanation

Correct Answer

D:

Test web access appears in FortiSASE SWG logs and nonproxy direct browsing is appropriately restricted. This evidence directly tests the intended corrective action: Install the approved PAC/manual proxy settings or supported agentless onboarding method for intended browsers. It confirms the failure mechanism—A proxy account alone does not intercept browser traffic without the client directing sessions to it.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Install the approved PAC/manual proxy settings or supported agentless onboarding method for intended browsers.—worked.

B:

A browser-only test reaches approved web destinations through the intended proxy without a managed VPN agent. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Install the approved PAC/manual proxy settings or supported agentless onboarding method for intended browsers.—worked.

C:

SAML assertions signed by the new key authenticate for pilot users and no unexpected outages occur. This would verify resolution of a different case: An IdP migration removes a FortiSASE SAML signing certificate before the replacement has been accepted by the service provider. It does not show that the reported issue was fixed or that its intended action—Install the approved PAC/manual proxy settings or supported agentless onboarding method for intended browsers.—worked.

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