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 69

Question 680

During a post-incident review at a regional data center, the original problem was: An operator builds a custom report from a filtered set of denied sessions and presents it as total Internet traffic volume for management. Which preventive practice most directly addresses its cause?

  1. Require data source and inclusion criteria notes on every custom report.
  2. Review custom report definitions after major SASE policy changes.
  3. Specify timestamps, timezone and cutoffs explicitly for cross-platform reports.
  4. Review report destinations and recipients at every operations staffing change.

Explanation

Correct Answer

A:

Require data source and inclusion criteria notes on every custom report. This control reduces recurrence of the documented mechanism: Action-filtered subsets cannot represent the full Internet traffic population without qualification. It creates a repeatable check around the needed response: Choose the correct traffic data set and clearly label whether blocked and allowed actions are included.

Incorrect Answers

B:

Review custom report definitions after major SASE policy changes. That safeguard addresses another potential failure: A scheduled report continues showing outdated policy category names after a FortiSASE rule restructuring, confusing auditors despite accurate event counts. It is not the most targeted recurring control for the described cause: Action-filtered subsets cannot represent the full Internet traffic population without qualification.

C:

Specify timestamps, timezone and cutoffs explicitly for cross-platform reports. That safeguard addresses another potential failure: An investigator generates a cloud report for a specific day but compares it with branch logs in another timezone, creating apparently inconsistent access counts. It is not the most targeted recurring control for the described cause: Action-filtered subsets cannot represent the full Internet traffic population without qualification.

D:

Review report destinations and recipients at every operations staffing change. That safeguard addresses another potential failure: A scheduled SOC summary is not delivered because its email recipient list still points to an abandoned security distribution mailbox. It is not the most targeted recurring control for the described cause: Action-filtered subsets cannot represent the full Internet traffic population without qualification.

Question 681

A firewall operations team at a university network encounters the following during a controlled failover drill: 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. Which action most directly restores the approved security outcome?

  1. Align the member's supported routing context and health-check source with the intended network path.
  2. Update the supported IPsec peer configuration and confirm the tunnel member can carry authenticated traffic.
  3. Correct the supported far-end route or overlay advertisement for the missing branch subnet.
  4. Add the IPsec tunnel interface as an appropriate overlay SD-WAN member and zone it correctly.

Explanation

Correct Answer

C:

Correct the supported far-end route or overlay advertisement for the missing branch subnet. This is the most direct response to the stated incident: 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 technical mechanism is: A healthy tunnel interface does not establish route symmetry to every internal subnet. Confirmation requires: Two-way packets reach the private application through the overlay without asymmetric return failure.

Incorrect Answers

A:

Align the member's supported routing context and health-check source with the intended network path. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: A healthy tunnel interface does not establish route symmetry to every internal subnet.

B:

Update the supported IPsec peer configuration and confirm the tunnel member can carry authenticated traffic. That could address a different issue in the same blueprint area: 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. It does not directly correct the given incident, whose decisive mechanism is: A healthy tunnel interface does not establish route symmetry to every internal subnet.

D:

Add the IPsec tunnel interface as an appropriate overlay SD-WAN member and zone it correctly. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: A healthy tunnel interface does not establish route symmetry to every internal subnet.

Question 682

An operations review at a university network has corrected: 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. Which observation specifically confirms success?

  1. Utilization during a controlled mixed-load test stays within the secondary link's approved share.
  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. Two-way packets reach the private application through the overlay without asymmetric return failure.

Explanation

Correct Answer

D:

Two-way packets reach the private application through the overlay without asymmetric return failure. This evidence directly tests the intended corrective action: Correct the supported far-end route or overlay advertisement for the missing branch subnet. It confirms the failure mechanism—A healthy tunnel interface does not establish route symmetry to every internal subnet.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Utilization during a controlled mixed-load test stays within the secondary link's approved share. This would verify resolution of a different case: A newly installed ISP link has a restricted bandwidth plan but its configured SD-WAN member weight causes bulk traffic to consume the entire link. It does not show that the reported issue was fixed or that its intended action—Correct the supported far-end route or overlay advertisement for the missing branch subnet.—worked.

B:

Private test traffic passes end-to-end through the established and monitored tunnel. This would verify resolution of a different case: 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. It does not show that the reported issue was fixed or that its intended action—Correct the supported far-end route or overlay advertisement for the missing branch subnet.—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—Correct the supported far-end route or overlay advertisement for the missing branch subnet.—worked.

Question 683

At a university network, investigators observe: 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. Which underlying policy or system mechanism BEST explains this behavior?

  1. A healthy tunnel interface does not establish route symmetry to every internal subnet.
  2. An invalid preferred member complicates path selection even when a working alternative exists.
  3. Default zone assignment may conflict with deliberate security segmentation.
  4. SD-WAN health checks depend on the member's valid routing and probe source context.

Explanation

Correct Answer

A:

A healthy tunnel interface does not establish route symmetry to every internal subnet. This explains why the reported condition occurs: 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 targeted correction is: Correct the supported far-end route or overlay advertisement for the missing branch subnet.

Incorrect Answers

B:

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:

Default zone assignment may conflict with deliberate security segmentation. This mechanism instead explains a separate problem: A new tunnel member is added under the default virtual-wan-link zone although the architecture requires region-specific security controls. The current incident requires the more directly applicable cause stated by the correct option.

D:

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.

Question 684

An operations group at a university network resolved: 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. Which ongoing safeguard should become part of its change process?

  1. Reconcile tunnel inventory and SD-WAN member membership after provisioning VPN overlays.
  2. Test representative subnet-to-subnet reachability with reverse-path inspection for every overlay.
  3. Review capacity and steering weights whenever a lower-speed member is introduced.
  4. Explicitly specify member zone instead of relying on defaults in site templates.

Explanation

Correct Answer

B:

Test representative subnet-to-subnet reachability with reverse-path inspection for every overlay. This control reduces recurrence of the documented mechanism: A healthy tunnel interface does not establish route symmetry to every internal subnet. It creates a repeatable check around the needed response: Correct the supported far-end route or overlay advertisement for the missing branch subnet.

Incorrect Answers

A:

Reconcile tunnel inventory and SD-WAN member membership after provisioning VPN overlays. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: A healthy tunnel interface does not establish route symmetry to every internal subnet.

C:

Review capacity and steering weights whenever a lower-speed member is introduced. That safeguard addresses another potential failure: A newly installed ISP link has a restricted bandwidth plan but its configured SD-WAN member weight causes bulk traffic to consume the entire link. It is not the most targeted recurring control for the described cause: A healthy tunnel interface does not establish route symmetry to every internal subnet.

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: A healthy tunnel interface does not establish route symmetry to every internal subnet.

Question 685

At a hospital campus, a security analyst is reviewing this failure during a configuration rollout: Traffic matching a local policy route is forced toward an outdated VPN tunnel instead of following the updated SD-WAN rule. What is the MOST appropriate FIRST corrective step?

  1. Adjust routing policy attributes or supported SD-WAN route preference according to the approved private-link design.
  2. Set the private subnet routes toward the approved private SD-WAN zone and verify firewall authorization.
  3. Add the correct private prefix route toward the approved SD-WAN overlay zone or tunnel.
  4. Remove or update the conflicting policy route and re-evaluate the real session lookup order.

Explanation

Correct Answer

D:

Remove or update the conflicting policy route and re-evaluate the real session lookup order. This is the most direct response to the stated incident: Traffic matching a local policy route is forced toward an outdated VPN tunnel instead of following the updated SD-WAN rule. The technical mechanism is: Policy routing can supersede expected steering under the platform's route decision order. Confirmation requires: A test client session follows the intended SD-WAN rule rather than the obsolete policy route.

Incorrect Answers

A:

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: Policy routing can supersede expected steering under the platform's route decision order.

B:

Set the private subnet routes toward the approved private SD-WAN zone and verify firewall authorization. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Policy routing can supersede expected steering under the platform's route decision order.

C:

Add the correct private prefix route toward the approved SD-WAN overlay zone or tunnel. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Policy routing can supersede expected steering under the platform's route decision order.

Question 686

During follow-up testing at a hospital campus, the original fault was: Traffic matching a local policy route is forced toward an outdated VPN tunnel instead of following the updated SD-WAN rule. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. A test client session follows the intended SD-WAN rule rather than the obsolete policy route.
  2. The regulated application consistently leaves through the allowed member while ordinary traffic may use both.
  3. The missing subnet appears in the routing information base and private sessions complete.
  4. Failure probes trigger the expected routing/member eligibility change and traffic uses an alternate path.

Explanation

Correct Answer

A:

A test client session follows the intended SD-WAN rule rather than the obsolete policy route. This evidence directly tests the intended corrective action: Remove or update the conflicting policy route and re-evaluate the real session lookup order. It confirms the failure mechanism—Policy routing can supersede expected steering under the platform's route decision order.—has been addressed in the actual affected flow.

Incorrect Answers

B:

The regulated application consistently leaves through the allowed member while ordinary traffic may use both. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Remove or update the conflicting policy route and re-evaluate the real session lookup order.—worked.

C:

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—Remove or update the conflicting policy route and re-evaluate the real session lookup order.—worked.

D:

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—Remove or update the conflicting policy route and re-evaluate the real session lookup order.—worked.

Question 687

The incident investigation at a hospital campus records: Traffic matching a local policy route is forced toward an outdated VPN tunnel instead of following the updated SD-WAN rule. Which mechanism provides the strongest explanation?

  1. Ordinary ECMP route eligibility alone does not encode per-application provider restrictions.
  2. Policy routing can supersede expected steering under the platform's route decision order.
  3. Locally originated system traffic and forwarded sessions can use different routing decisions.
  4. Overlay routing policy can suppress reachability even with healthy IPsec members.

Explanation

Correct Answer

B:

Policy routing can supersede expected steering under the platform's route decision order. This explains why the reported condition occurs: Traffic matching a local policy route is forced toward an outdated VPN tunnel instead of following the updated SD-WAN rule. The targeted correction is: Remove or update the conflicting policy route and re-evaluate the real session lookup order.

Incorrect Answers

A:

Ordinary ECMP route eligibility alone does not encode per-application provider restrictions. This mechanism instead explains a separate problem: 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 current incident requires the more directly applicable cause stated by the correct option.

C:

Locally originated system traffic and forwarded sessions can use different routing decisions. This mechanism instead explains a separate problem: A FortiGate sends firewall-originated syslog through a nonpreferred management route while user sessions correctly follow SD-WAN, leading staff to blame an SD-WAN rule. The current incident requires the more directly applicable cause stated by the correct option.

D:

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.

Question 688

After a corrective change at a hospital campus, the team documents: Traffic matching a local policy route is forced toward an outdated VPN tunnel instead of following the updated SD-WAN rule. Which repeatable control BEST prevents a recurrence?

  1. Reconcile private prefix reachability before enabling application-based path preference.
  2. Test failure-state route updates under controlled link outages.
  3. Inventory policy routes before changing SD-WAN service matching.
  4. Check routing table precedence when replacing legacy default routes.

Explanation

Correct Answer

C:

Inventory policy routes before changing SD-WAN service matching. This control reduces recurrence of the documented mechanism: Policy routing can supersede expected steering under the platform's route decision order. It creates a repeatable check around the needed response: Remove or update the conflicting policy route and re-evaluate the real session lookup order.

Incorrect Answers

A:

Reconcile private prefix reachability before enabling application-based path preference. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Policy routing can supersede expected steering under the platform's route decision order.

B:

Test failure-state route updates under controlled link outages. That safeguard addresses another potential failure: A preferred WAN becomes unhealthy and is withdrawn from service, but its route remains installed due to an incorrect health state-action setting. It is not the most targeted recurring control for the described cause: Policy routing can supersede expected steering under the platform's route decision order.

D:

Check routing table precedence when replacing legacy default routes. That safeguard addresses another potential failure: A default route to the ISP remains preferred over the SD-WAN zone after migration, causing most traffic to bypass SD-WAN rules. It is not the most targeted recurring control for the described cause: Policy routing can supersede expected steering under the platform's route decision order.

Question 689

During a quarterly compliance review at a retail network, analysts observe: An IdP migration removes a FortiSASE SAML signing certificate before the replacement has been accepted by the service provider. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Coordinate signing certificate rollover with an overlap or scheduled trust update under the supported federation process.
  2. Configure supported SAML group attributes and map them to FortiSASE policy groups.
  3. Deploy the correct approved FortiSASE connection profile and remove the obsolete client target.
  4. Restore device time synchronization and test the trusted FortiSASE certificate chain.

Explanation

Correct Answer

A:

Coordinate signing certificate rollover with an overlap or scheduled trust update under the supported federation process. This is the most direct response to the stated incident: An IdP migration removes a FortiSASE SAML signing certificate before the replacement has been accepted by the service provider. The technical mechanism is: Federation trust fails if the SP does not accept the IdP's active signing key. Confirmation requires: SAML assertions signed by the new key authenticate for pilot users and no unexpected outages occur.

Incorrect Answers

B:

Configure supported SAML group attributes and map them to FortiSASE policy groups. That could address a different issue in the same blueprint area: A FortiSASE SAML integration accepts users but places everyone into a default policy because role and group assertions are missing from the issued claim. It does not directly correct the given incident, whose decisive mechanism is: Federation trust fails if the SP does not accept the IdP's active signing key.

C:

Deploy the correct approved FortiSASE connection profile and remove the obsolete client target. That could address a different issue in the same blueprint area: FortiClient is installed but its VPN connection uses a direct on-premises FortiGate tunnel instead of the intended FortiSASE service. It does not directly correct the given incident, whose decisive mechanism is: Federation trust fails if the SP does not accept the IdP's active signing key.

D:

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: Federation trust fails if the SP does not accept the IdP's active signing key.

Question 690

At a retail network, a test team is validating a change after this incident: An IdP migration removes a FortiSASE SAML signing certificate before the replacement has been accepted by the service provider. What evidence most directly verifies the intended outcome?

  1. A user in the previously omitted OU is found and permitted according to group rules.
  2. SAML assertions signed by the new key authenticate for pilot users and no unexpected outages occur.
  3. A deprovisioned test account no longer matches the privileged policy while active users retain access.
  4. The user can log in with only the minimum permitted applications available.

Explanation

Correct Answer

B:

SAML assertions signed by the new key authenticate for pilot users and no unexpected outages occur. This evidence directly tests the intended corrective action: Coordinate signing certificate rollover with an overlap or scheduled trust update under the supported federation process. It confirms the failure mechanism—Federation trust fails if the SP does not accept the IdP's active signing key.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Coordinate signing certificate rollover with an overlap or scheduled trust update under the supported federation process.—worked.

C:

A deprovisioned test account no longer matches the privileged policy while active users retain access. This would verify resolution of a different case: A remote worker successfully authenticates to FortiSASE but a stale identity group cache keeps applying a former privileged access policy. It does not show that the reported issue was fixed or that its intended action—Coordinate signing certificate rollover with an overlap or scheduled trust update under the supported federation process.—worked.

D:

The user can log in with only the minimum permitted applications available. This would verify resolution of a different case: A user is enrolled into FortiSASE but attempts login before their account is assigned to an authorized access group. It does not show that the reported issue was fixed or that its intended action—Coordinate signing certificate rollover with an overlap or scheduled trust update under the supported federation process.—worked.

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