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 55

Question 540

An operations group at a university network resolved: Managers request a list of users blocked by DLP policy, but the standard Internet traffic summary contains only successful requests. Which ongoing safeguard should become part of its change process?

  1. Require data source and inclusion criteria notes on every custom report.
  2. Use report types aligned to the underlying control, not generic bandwidth summaries.
  3. Reconcile aggregate report totals to source logs during report template approval.
  4. Maintain approved user-attribution data sources and privacy access controls for incident reports.

Explanation

Correct Answer

B:

Use report types aligned to the underlying control, not generic bandwidth summaries. This control reduces recurrence of the documented mechanism: General successful-traffic summaries do not enumerate every security-policy block event. It creates a repeatable check around the needed response: Choose the suitable security-event or DLP-specific report with blocked-action filters.

Incorrect Answers

A:

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: General successful-traffic summaries do not enumerate every security-policy block event.

C:

Reconcile aggregate report totals to source logs during report template approval. That safeguard addresses another potential failure: A weekly report labels a user as the top bandwidth consumer but totals its sessions twice because overlapping traffic report categories were combined. It is not the most targeted recurring control for the described cause: General successful-traffic summaries do not enumerate every security-policy block event.

D:

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: General successful-traffic summaries do not enumerate every security-policy block event.

Question 541

At a hospital campus, a security analyst is reviewing this failure during a planned policy migration: 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. What is the MOST appropriate FIRST corrective step?

  1. Update the supported IPsec peer configuration and confirm the tunnel member can carry authenticated traffic.
  2. Update that member's gateway to the address supplied by the new CPE and verify routing.
  3. Configure the supported FortiExtender logical interface as an SD-WAN member with correct health and failover settings.
  4. Align the member's supported routing context and health-check source with the intended network path.

Explanation

Correct Answer

D:

Align the member's supported routing context and health-check source with the intended network path. This is the most direct response to the stated incident: 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 technical mechanism is: SD-WAN health checks depend on the member's valid routing and probe source context. Confirmation requires: Probe packets use the intended routing context and the member reports correct reachability.

Incorrect Answers

A:

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: SD-WAN health checks depend on the member's valid routing and probe source context.

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: SD-WAN health checks depend on the member's valid routing and probe source context.

C:

Configure the supported FortiExtender logical interface as an SD-WAN member with correct health and failover settings. That could address a different issue in the same blueprint area: The branch uses a cellular FortiExtender as a third path but engineers mistakenly treat the modem as a conventional Ethernet gateway without verifying supported interface details. It does not directly correct the given incident, whose decisive mechanism is: SD-WAN health checks depend on the member's valid routing and probe source context.

Question 542

During follow-up testing at a hospital campus, the original fault was: 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. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. Probe packets use the intended routing context and the member reports correct reachability.
  2. Private test traffic passes end-to-end through the established and monitored tunnel.
  3. Steering diagnostics select healthy installed paths without oscillating through the spare port.
  4. The private network prefix has an active route and test traffic follows the intended new member group.

Explanation

Correct Answer

A:

Probe packets use the intended routing context and the member reports correct reachability. This evidence directly tests the intended corrective action: Align the member's supported routing context and health-check source with the intended network path. It confirms the failure mechanism—SD-WAN health checks depend on the member's valid routing and probe source context.—has been addressed in the actual affected flow.

Incorrect Answers

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—Align the member's supported routing context and health-check source with the intended network path.—worked.

C:

Steering diagnostics select healthy installed paths without oscillating through the spare port. This would verify resolution of a different case: A small branch lists a disconnected spare physical port as the highest-preference member and fails over repeatedly before landing on a working path. It does not show that the reported issue was fixed or that its intended action—Align the member's supported routing context and health-check source with the intended network path.—worked.

D:

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—Align the member's supported routing context and health-check source with the intended network path.—worked.

Question 543

The incident investigation at a hospital campus records: 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. Which mechanism provides the strongest explanation?

  1. SD-WAN cannot steer into an overlay that is absent from eligible members.
  2. SD-WAN health checks depend on the member's valid routing and probe source context.
  3. Different access technologies expose distinct logical interfaces and gateway behaviors.
  4. Logical member identifiers must correspond to the actual provider circuits used in policy.

Explanation

Correct Answer

B:

SD-WAN health checks depend on the member's valid routing and probe source context. This explains why the reported condition occurs: 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 targeted correction is: Align the member's supported routing context and health-check source with the intended network path.

Incorrect Answers

A:

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.

C:

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.

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 544

After a corrective change at a hospital campus, the team documents: 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. Which repeatable control BEST prevents a recurrence?

  1. Document metered paths and verify per-application allowed traffic before deployment.
  2. Review capacity and steering weights whenever a lower-speed member is introduced.
  3. Verify VRF and source-interface dependencies whenever using segmented WAN routing.
  4. Test each member independently, not only the all-links-up zone state.

Explanation

Correct Answer

C:

Verify VRF and source-interface dependencies whenever using segmented WAN routing. This control reduces recurrence of the documented mechanism: SD-WAN health checks depend on the member's valid routing and probe source context. It creates a repeatable check around the needed response: Align the member's supported routing context and health-check source with the intended network path.

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: SD-WAN health checks depend on the member's valid routing and probe source context.

B:

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: SD-WAN health checks depend on the member's valid routing and probe source context.

D:

Test each member independently, not only the all-links-up zone state. That safeguard addresses another potential failure: 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. It is not the most targeted recurring control for the described cause: SD-WAN health checks depend on the member's valid routing and probe source context.

Question 545

During a security audit at a retail network, analysts observe: A branch uses BGP to advertise overlay prefixes but a filtered remote office subnet is missing from received routes. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Correct the approved prefix advertisement or route filter on the relevant BGP peers.
  2. Bind the intended gateway or route to the actual selected member interface as supported.
  3. Remove or update the conflicting policy route and re-evaluate the real session lookup order.
  4. Add a narrowly scoped firewall permit for the partner application and correct SD-WAN destination zone.

Explanation

Correct Answer

A:

Correct the approved prefix advertisement or route filter on the relevant BGP peers. This is the most direct response to the stated incident: A branch uses BGP to advertise overlay prefixes but a filtered remote office subnet is missing from received routes. The technical mechanism is: Overlay routing policy can suppress reachability even with healthy IPsec members. Confirmation requires: The missing subnet appears in the routing information base and private sessions complete.

Incorrect Answers

B:

Bind the intended gateway or route to the actual selected member interface as supported. That could address a different issue in the same blueprint area: An SD-WAN member has a static route to a provider gateway on the wrong interface, so probes work on another link but traffic drops when it is selected. It does not directly correct the given incident, whose decisive mechanism is: Overlay routing policy can suppress reachability even with healthy IPsec members.

C:

Remove or update the conflicting policy route and re-evaluate the real session lookup order. That could address a different issue in the same blueprint area: Traffic matching a local policy route is forced toward an outdated VPN tunnel instead of following the updated SD-WAN rule. It does not directly correct the given incident, whose decisive mechanism is: Overlay routing policy can suppress reachability even with healthy IPsec members.

D:

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: Overlay routing policy can suppress reachability even with healthy IPsec members.

Question 546

At a retail network, a test team is validating a change after this incident: A branch uses BGP to advertise overlay prefixes but a filtered remote office subnet is missing from received routes. 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. The missing subnet appears in the routing information base and private sessions complete.
  3. A bidirectional private test shows replies returning over the intended tunnel path.
  4. New Internet sessions use the SD-WAN zone and rule diagnostics show member selection.

Explanation

Correct Answer

B:

The missing subnet appears in the routing information base and private sessions complete. This evidence directly tests the intended corrective action: Correct the approved prefix advertisement or route filter on the relevant BGP peers. It confirms the failure mechanism—Overlay routing policy can suppress reachability even with healthy IPsec members.—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 approved prefix advertisement or route filter on the relevant BGP peers.—worked.

C:

A bidirectional private test shows replies returning over the intended tunnel path. This would verify resolution of a different case: 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. It does not show that the reported issue was fixed or that its intended action—Correct the approved prefix advertisement or route filter on the relevant BGP peers.—worked.

D:

New Internet sessions use the SD-WAN zone and rule diagnostics show member selection. This would verify resolution of a different case: A default route to the ISP remains preferred over the SD-WAN zone after migration, causing most traffic to bypass SD-WAN rules. It does not show that the reported issue was fixed or that its intended action—Correct the approved prefix advertisement or route filter on the relevant BGP peers.—worked.

Question 547

A Fortinet administrator at a retail network is assessing: A branch uses BGP to advertise overlay prefixes but a filtered remote office subnet is missing from received routes. What is the most relevant root cause?

  1. Existing stateful sessions and NAT mappings may not transfer transparently between providers.
  2. Route administrative distance and priority can make stale static entries override learned paths.
  3. Overlay routing policy can suppress reachability even with healthy IPsec members.
  4. Routing preference is determined by route-selection policies, not by the WAN link's price label.

Explanation

Correct Answer

C:

Overlay routing policy can suppress reachability even with healthy IPsec members. This explains why the reported condition occurs: A branch uses BGP to advertise overlay prefixes but a filtered remote office subnet is missing from received routes. The targeted correction is: Correct the approved prefix advertisement or route filter on the relevant BGP peers.

Incorrect Answers

A:

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.

B:

Route administrative distance and priority can make stale static entries override learned paths. This mechanism instead explains a separate problem: 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. The current incident requires the more directly applicable cause stated by the correct option.

D:

Routing preference is determined by route-selection policies, not by the WAN link's price label. This mechanism instead explains a separate problem: A BGP route to a private application is learned through both MPLS and Internet overlay with a preference that incorrectly favors the metered link. The current incident requires the more directly applicable cause stated by the correct option.

Question 548

A risk review at a retail network focuses on preventing this issue again: A branch uses BGP to advertise overlay prefixes but a filtered remote office subnet is missing from received routes. Which recurring control is most suitable?

  1. Validate all member gateways and live forwarding during individual link isolation tests.
  2. Review destination prefix-to-zone mapping before enabling new overlays.
  3. Document and test local-out route policy for DNS, NTP, telemetry, and syslog separately.
  4. Test advertised and accepted prefix lists across SD-WAN overlays after address expansion.

Explanation

Correct Answer

D:

Test advertised and accepted prefix lists across SD-WAN overlays after address expansion. This control reduces recurrence of the documented mechanism: Overlay routing policy can suppress reachability even with healthy IPsec members. It creates a repeatable check around the needed response: Correct the approved prefix advertisement or route filter on the relevant BGP peers.

Incorrect Answers

A:

Validate all member gateways and live forwarding during individual link isolation tests. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Overlay routing policy can suppress reachability even with healthy IPsec members.

B:

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: Overlay routing policy can suppress reachability even with healthy IPsec members.

C:

Document and test local-out route policy for DNS, NTP, telemetry, and syslog separately. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Overlay routing policy can suppress reachability even with healthy IPsec members.

Question 549

During an incident triage, an administrator reports at a logistics office: An employee's FortiClient connection repeatedly disconnects when the local system clock is wrong and the client rejects a valid service certificate. What should the team change or investigate FIRST?

  1. Refresh the supported identity/group mapping and confirm revocation of stale authorization.
  2. Restore device time synchronization and test the trusted FortiSASE certificate chain.
  3. Deploy the correct approved FortiSASE connection profile and remove the obsolete client target.
  4. Correct the approved agentless proxy SAML redirect and reply URLs at the application and identity provider.

Explanation

Correct Answer

B:

Restore device time synchronization and test the trusted FortiSASE certificate chain. This is the most direct response to the stated incident: An employee's FortiClient connection repeatedly disconnects when the local system clock is wrong and the client rejects a valid service certificate. The technical mechanism is: Certificate validity checks can fail on an endpoint with incorrect system time. Confirmation requires: The endpoint validates the service certificate and retains a stable authenticated connection.

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: Certificate validity checks can fail on an endpoint with incorrect system time.

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: Certificate validity checks can fail on an endpoint with incorrect system time.

D:

Correct the approved agentless proxy SAML redirect and reply URLs at the application and identity provider. That could address a different issue in the same blueprint area: A contractor's browser proxy authentication loops because SAML redirect URLs retain an old domain after a secure web gateway hostname change. It does not directly correct the given incident, whose decisive mechanism is: Certificate validity checks can fail on an endpoint with incorrect system time.

Question 550

Following remediation at a logistics office, engineers revisit: An employee's FortiClient connection repeatedly disconnects when the local system clock is wrong and the client rejects a valid service certificate. Which observation would BEST prove the specific issue is resolved?

  1. A test user's RADIUS request succeeds with expected acceptance and group behavior.
  2. Members of separate test groups match their intended access restrictions after SSO.
  3. The endpoint validates the service certificate and retains a stable authenticated connection.
  4. A clean installation enrolls to the correct tenant and establishes a protected connection.

Explanation

Correct Answer

C:

The endpoint validates the service certificate and retains a stable authenticated connection. This evidence directly tests the intended corrective action: Restore device time synchronization and test the trusted FortiSASE certificate chain. It confirms the failure mechanism—Certificate validity checks can fail on an endpoint with incorrect system time.—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—Restore device time synchronization and test the trusted FortiSASE certificate chain.—worked.

B:

Members of separate test groups match their intended access restrictions after SSO. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Restore device time synchronization and test the trusted FortiSASE certificate chain.—worked.

D:

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—Restore device time synchronization and test the trusted FortiSASE certificate chain.—worked.

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