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 61

Question 600

During a post-incident review at a logistics office, the original problem was: A FortiSASE report used for an audit exposes individual browsing URLs to a broad executive distribution although the approved report should contain aggregates only. Which preventive practice most directly addresses its cause?

  1. Classify report sensitivity and enforce audience-specific data minimization.
  2. Define active-user criteria and use them consistently in usage reporting.
  3. Require data source and inclusion criteria notes on every custom report.
  4. Align report retention and archive requirements with audit lookback obligations.

Explanation

Correct Answer

A:

Classify report sensitivity and enforce audience-specific data minimization. This control reduces recurrence of the documented mechanism: Detailed security logs can contain personal data inappropriate for broad summary sharing. It creates a repeatable check around the needed response: Use privacy-appropriate anonymization or aggregated reporting and restrict report distribution.

Incorrect Answers

B:

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: Detailed security logs can contain personal data inappropriate for broad summary sharing.

C:

Require data source and inclusion criteria notes on every custom report. That safeguard addresses another potential failure: An operator builds a custom report from a filtered set of denied sessions and presents it as total Internet traffic volume for management. It is not the most targeted recurring control for the described cause: Detailed security logs can contain personal data inappropriate for broad summary sharing.

D:

Align report retention and archive requirements with audit lookback obligations. That safeguard addresses another potential failure: 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. It is not the most targeted recurring control for the described cause: Detailed security logs can contain personal data inappropriate for broad summary sharing.

Question 601

A firewall operations team at a manufacturing plant encounters the following during a predeployment acceptance test: 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. Which action most directly restores the approved security outcome?

  1. Move the MPLS tunnel member to its appropriate private network SD-WAN zone and review policy references.
  2. Normalize the member association so each supported member belongs to the intended zone and remove conflicting mappings.
  3. Update the affected static route to the new correct zone and revalidate forwarding.
  4. Correct the supported far-end route or overlay advertisement for the missing branch subnet.

Explanation

Correct Answer

C:

Update the affected static route to the new correct zone and revalidate forwarding. This is the most direct response to the stated incident: 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. The technical mechanism is: Route next-hop zone references do not automatically follow every member migration. Confirmation requires: The private network prefix has an active route and test traffic follows the intended new member group.

Incorrect Answers

A:

Move the MPLS tunnel member to its appropriate private network SD-WAN zone and review policy references. That could address a different issue in the same blueprint area: 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 does not directly correct the given incident, whose decisive mechanism is: Route next-hop zone references do not automatically follow every member migration.

B:

Normalize the member association so each supported member belongs to the intended zone and remove conflicting mappings. That could address a different issue in the same blueprint area: A configuration template assigns one WAN member to multiple intended zones through duplicated site definitions, causing a conflict during managed deployment. It does not directly correct the given incident, whose decisive mechanism is: Route next-hop zone references do not automatically follow every member migration.

D:

Correct the supported far-end route or overlay advertisement for the missing branch subnet. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Route next-hop zone references do not automatically follow every member migration.

Question 602

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

  1. Only approved critical traffic uses the metered link under failover conditions.
  2. Configuration install succeeds and each member appears in one approved operational grouping.
  3. When fixed links fail, an authorized session traverses the cellular link with a valid return path.
  4. The private network prefix has an active route and test traffic follows the intended new member group.

Explanation

Correct Answer

D:

The private network prefix has an active route and test traffic follows the intended new member group. This evidence directly tests the intended corrective action: Update the affected static route to the new correct zone and revalidate forwarding. It confirms the failure mechanism—Route next-hop zone references do not automatically follow every member migration.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Only approved critical traffic uses the metered link under failover conditions. This would verify resolution of a different case: Two Internet uplinks are grouped into one zone but the branch needs separate policy treatment for metered mobile connectivity during outages. It does not show that the reported issue was fixed or that its intended action—Update the affected static route to the new correct zone and revalidate forwarding.—worked.

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—Update the affected static route to the new correct zone and revalidate forwarding.—worked.

C:

When fixed links fail, an authorized session traverses the cellular link with a valid return path. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Update the affected static route to the new correct zone and revalidate forwarding.—worked.

Question 603

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

  1. Route next-hop zone references do not automatically follow every member migration.
  2. Different access technologies expose distinct logical interfaces and gateway behaviors.
  3. One successful member cannot prove every zone member has a valid forwarding gateway.
  4. SD-WAN health checks depend on the member's valid routing and probe source context.

Explanation

Correct Answer

A:

Route next-hop zone references do not automatically follow every member migration. This explains why the reported condition occurs: 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. The targeted correction is: Update the affected static route to the new correct zone and revalidate forwarding.

Incorrect Answers

B:

Different access technologies expose distinct logical interfaces and gateway behaviors. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

C:

One successful member cannot prove every zone member has a valid forwarding gateway. This mechanism instead explains a separate problem: A branch moves its default route to the SD-WAN zone but removes the backup member's gateway, so the zone works only while the primary link is alive. 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 604

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

  1. Document metered paths and verify per-application allowed traffic before deployment.
  2. Reconcile zone routes whenever moving a member between SD-WAN groups.
  3. Confirm peer endpoints and cryptographic state before advertising overlay members healthy.
  4. Verify VRF and source-interface dependencies whenever using segmented WAN routing.

Explanation

Correct Answer

B:

Reconcile zone routes whenever moving a member between SD-WAN groups. This control reduces recurrence of the documented mechanism: Route next-hop zone references do not automatically follow every member migration. It creates a repeatable check around the needed response: Update the affected static route to the new correct zone and revalidate forwarding.

Incorrect Answers

A:

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: Route next-hop zone references do not automatically follow every member migration.

C:

Confirm peer endpoints and cryptographic state before advertising overlay members healthy. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Route next-hop zone references do not automatically follow every member migration.

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: Route next-hop zone references do not automatically follow every member migration.

Question 605

At a corporate headquarters, a security analyst is reviewing this failure during a planned policy migration: A source NAT policy translates a client to the primary ISP address even after SD-WAN routes traffic out through a backup provider, breaking return traffic. What is the MOST appropriate FIRST corrective step?

  1. Remove or update the stale more-specific route so the approved path has correct longest-prefix precedence.
  2. Add a narrowly scoped firewall permit for the partner application and correct SD-WAN destination zone.
  3. Add the correct route for the private app subnet toward the associated tunnel or zone.
  4. Configure supported egress-aware source NAT for both provider paths and verify the selected member.

Explanation

Correct Answer

D:

Configure supported egress-aware source NAT for both provider paths and verify the selected member. This is the most direct response to the stated incident: A source NAT policy translates a client to the primary ISP address even after SD-WAN routes traffic out through a backup provider, breaking return traffic. The technical mechanism is: SD-WAN route changes and source address translation must remain compatible across failover. Confirmation requires: External test services observe a valid address for each ISP and responses return successfully.

Incorrect Answers

A:

Remove or update the stale more-specific route so the approved path has correct longest-prefix precedence. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: SD-WAN route changes and source address translation must remain compatible across failover.

B:

Add a narrowly scoped firewall permit for the partner application and correct SD-WAN destination zone. That could address a different issue in the same blueprint area: 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. It does not directly correct the given incident, whose decisive mechanism is: SD-WAN route changes and source address translation must remain compatible across failover.

C:

Add the correct route for the private app subnet toward the associated tunnel or zone. That could address a different issue in the same blueprint area: A tunnel interface is a zone member but its route uses the remote gateway's public IP instead of the private destination prefix, leaving internal apps unrouteable. It does not directly correct the given incident, whose decisive mechanism is: SD-WAN route changes and source address translation must remain compatible across failover.

Question 606

During follow-up testing at a corporate headquarters, the original fault was: A source NAT policy translates a client to the primary ISP address even after SD-WAN routes traffic out through a backup provider, breaking return traffic. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. External test services observe a valid address for each ISP and responses return successfully.
  2. After subsequent FortiManager installs the route table retains the intended overlay prefix path.
  3. Syslog reaches the approved destination through its documented service path without altering user steering.
  4. The active route resolves to the healthy tunnel and the remote branch is reachable.

Explanation

Correct Answer

A:

External test services observe a valid address for each ISP and responses return successfully. This evidence directly tests the intended corrective action: Configure supported egress-aware source NAT for both provider paths and verify the selected member. It confirms the failure mechanism—SD-WAN route changes and source address translation must remain compatible across failover.—has been addressed in the actual affected flow.

Incorrect Answers

B:

After subsequent FortiManager installs the route table retains the intended overlay prefix path. This would verify resolution of a different case: A FortiGate has the correct SD-WAN zone route for corporate VPN but FortiManager installs a conflicting stale prefix route during configuration synchronization. It does not show that the reported issue was fixed or that its intended action—Configure supported egress-aware source NAT for both provider paths and verify the selected member.—worked.

C:

Syslog reaches the approved destination through its documented service path without altering user steering. This would verify resolution of a different case: 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. It does not show that the reported issue was fixed or that its intended action—Configure supported egress-aware source NAT for both provider paths and verify the selected member.—worked.

D:

The active route resolves to the healthy tunnel and the remote branch is reachable. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Configure supported egress-aware source NAT for both provider paths and verify the selected member.—worked.

Question 607

The incident investigation at a corporate headquarters records: A source NAT policy translates a client to the primary ISP address even after SD-WAN routes traffic out through a backup provider, breaking return traffic. Which mechanism provides the strongest explanation?

  1. Tunnel establishment is not proof that remote routing tables know the branch source network.
  2. SD-WAN route changes and source address translation must remain compatible across failover.
  3. A competing FIB route can redirect packets before expected SD-WAN forwarding decisions.
  4. Rule matching does not compensate for missing destination route state.

Explanation

Correct Answer

B:

SD-WAN route changes and source address translation must remain compatible across failover. This explains why the reported condition occurs: A source NAT policy translates a client to the primary ISP address even after SD-WAN routes traffic out through a backup provider, breaking return traffic. The targeted correction is: Configure supported egress-aware source NAT for both provider paths and verify the selected member.

Incorrect Answers

A:

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

C:

A competing FIB route can redirect packets before expected SD-WAN forwarding decisions. This mechanism instead explains a separate problem: A default route to the ISP remains preferred over the SD-WAN zone after migration, causing most traffic to bypass SD-WAN rules. The current incident requires the more directly applicable cause stated by the correct option.

D:

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.

Question 608

After a corrective change at a corporate headquarters, the team documents: A source NAT policy translates a client to the primary ISP address even after SD-WAN routes traffic out through a backup provider, breaking return traffic. Which repeatable control BEST prevents a recurrence?

  1. Require matched firewall rule plus route and SD-WAN rule evidence for application go-live.
  2. Compare FIB and BGP/OSPF candidates when troubleshooting overlay blackholes.
  3. Test egress NAT source identity under every supported route transition.
  4. Review destination prefix-to-zone mapping before enabling new overlays.

Explanation

Correct Answer

C:

Test egress NAT source identity under every supported route transition. This control reduces recurrence of the documented mechanism: SD-WAN route changes and source address translation must remain compatible across failover. It creates a repeatable check around the needed response: Configure supported egress-aware source NAT for both provider paths and verify the selected member.

Incorrect Answers

A:

Require matched firewall rule plus route and SD-WAN rule evidence for application go-live. That safeguard addresses another potential failure: 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. It is not the most targeted recurring control for the described cause: SD-WAN route changes and source address translation must remain compatible across failover.

B:

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: SD-WAN route changes and source address translation must remain compatible across failover.

D:

Review destination prefix-to-zone mapping before enabling new overlays. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: SD-WAN route changes and source address translation must remain compatible across failover.

Question 609

During a security audit at a distributed branch estate, analysts observe: A remote worker successfully authenticates to FortiSASE but a stale identity group cache keeps applying a former privileged access policy. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Refresh the supported identity/group mapping and confirm revocation of stale authorization.
  2. Deploy the authorized certificate chain to managed endpoints and investigate unsupported certificate identities.
  3. Coordinate signing certificate rollover with an overlap or scheduled trust update under the supported federation process.
  4. Install the approved PAC/manual proxy settings or supported agentless onboarding method for intended browsers.

Explanation

Correct Answer

A:

Refresh the supported identity/group mapping and confirm revocation of stale authorization. This is the most direct response to the stated incident: A remote worker successfully authenticates to FortiSASE but a stale identity group cache keeps applying a former privileged access policy. The technical mechanism is: Cached group identity can lag access changes even when authentication itself succeeds. Confirmation requires: A deprovisioned test account no longer matches the privileged policy while active users retain access.

Incorrect Answers

B:

Deploy the authorized certificate chain to managed endpoints and investigate unsupported certificate identities. That could address a different issue in the same blueprint area: A site lets users bypass required certificate trust warnings by manually accepting an unexpected FortiSASE proxy certificate on every device. It does not directly correct the given incident, whose decisive mechanism is: Cached group identity can lag access changes even when authentication itself succeeds.

C:

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: Cached group identity can lag access changes even when authentication itself succeeds.

D:

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: Cached group identity can lag access changes even when authentication itself succeeds.

Question 610

At a distributed branch estate, a test team is validating a change after this incident: A remote worker successfully authenticates to FortiSASE but a stale identity group cache keeps applying a former privileged access policy. What evidence most directly verifies the intended outcome?

  1. A clean installation enrolls to the correct tenant and establishes a protected connection.
  2. A deprovisioned test account no longer matches the privileged policy while active users retain access.
  3. The user can log in with only the minimum permitted applications available.
  4. Connection status shows the FortiSASE service and security traffic enters the expected PoP.

Explanation

Correct Answer

B:

A deprovisioned test account no longer matches the privileged policy while active users retain access. This evidence directly tests the intended corrective action: Refresh the supported identity/group mapping and confirm revocation of stale authorization. It confirms the failure mechanism—Cached group identity can lag access changes even when authentication itself succeeds.—has been addressed in the actual affected flow.

Incorrect Answers

A:

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—Refresh the supported identity/group mapping and confirm revocation of stale authorization.—worked.

C:

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—Refresh the supported identity/group mapping and confirm revocation of stale authorization.—worked.

D:

Connection status shows the FortiSASE service and security traffic enters the expected PoP. This would verify resolution of a different case: FortiClient is installed but its VPN connection uses a direct on-premises FortiGate tunnel instead of the intended FortiSASE service. It does not show that the reported issue was fixed or that its intended action—Refresh the supported identity/group mapping and confirm revocation of stale authorization.—worked.

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