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 74

Question 730

An operations review at a university network has corrected: Remote users experience two different security postures because some are agent-based and others use browser-only SWG; an operator assumes both modes inspect nonweb traffic identically. Which observation specifically confirms success?

  1. Test web access appears in FortiSASE SWG logs and nonproxy direct browsing is appropriately restricted.
  2. Each tested OS uses a compatible approved onboarding mode with expected security restrictions.
  3. The local user receives only the allowed policy rather than unrestricted default access.
  4. Nonweb and web test cases show explicitly understood protection differences between agent and proxy cohorts.

Explanation

Correct Answer

D:

Nonweb and web test cases show explicitly understood protection differences between agent and proxy cohorts. This evidence directly tests the intended corrective action: Apply the approved security coverage rules for each connection mode and document which traffic types each mode protects. It confirms the failure mechanism—Agentless proxy scope is not automatically equivalent to full device-tunnel traffic coverage.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Test web access appears in FortiSASE SWG logs and nonproxy direct browsing is appropriately restricted. This would verify resolution of a different case: 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 show that the reported issue was fixed or that its intended action—Apply the approved security coverage rules for each connection mode and document which traffic types each mode protects.—worked.

B:

Each tested OS uses a compatible approved onboarding mode with expected security restrictions. This would verify resolution of a different case: An enterprise distributes FortiClient installation to Windows staff while Linux contractor devices are assumed supported under the identical profile without checking platform capabilities. It does not show that the reported issue was fixed or that its intended action—Apply the approved security coverage rules for each connection mode and document which traffic types each mode protects.—worked.

C:

The local user receives only the allowed policy rather than unrestricted default access. This would verify resolution of a different case: An administrator creates a local FortiSASE user but assumes LDAP group restrictions apply automatically although the account is not mapped to a corresponding local service group. It does not show that the reported issue was fixed or that its intended action—Apply the approved security coverage rules for each connection mode and document which traffic types each mode protects.—worked.

Question 731

At a university network, investigators observe: Remote users experience two different security postures because some are agent-based and others use browser-only SWG; an operator assumes both modes inspect nonweb traffic identically. Which underlying policy or system mechanism BEST explains this behavior?

  1. Agentless proxy scope is not automatically equivalent to full device-tunnel traffic coverage.
  2. A proxy account alone does not intercept browser traffic without the client directing sessions to it.
  3. Certificate validity checks can fail on an endpoint with incorrect system time.
  4. Agentless SWG and FortiClient agent-based onboarding are different access models.

Explanation

Correct Answer

A:

Agentless proxy scope is not automatically equivalent to full device-tunnel traffic coverage. This explains why the reported condition occurs: Remote users experience two different security postures because some are agent-based and others use browser-only SWG; an operator assumes both modes inspect nonweb traffic identically. The targeted correction is: Apply the approved security coverage rules for each connection mode and document which traffic types each mode protects.

Incorrect Answers

B:

A proxy account alone does not intercept browser traffic without the client directing sessions to it. This mechanism instead explains a separate problem: A team deploys an agentless SWG configuration but omits browser or system proxy settings, causing traffic to connect directly to Internet sites. The current incident requires the more directly applicable cause stated by the correct option.

C:

Certificate validity checks can fail on an endpoint with incorrect system time. This mechanism instead explains a separate problem: An employee's FortiClient connection repeatedly disconnects when the local system clock is wrong and the client rejects a valid service certificate. The current incident requires the more directly applicable cause stated by the correct option.

D:

Agentless SWG and FortiClient agent-based onboarding are different access models. This mechanism instead explains a separate problem: A company plans browser-only secure web gateway use for contractors but distributes an agent-based full-tunnel guide requiring managed endpoint enrollment. The current incident requires the more directly applicable cause stated by the correct option.

Question 732

An operations group at a university network resolved: Remote users experience two different security postures because some are agent-based and others use browser-only SWG; an operator assumes both modes inspect nonweb traffic identically. Which ongoing safeguard should become part of its change process?

  1. Test identity group claims and policy mapping together during SSO acceptance.
  2. Compare traffic-type coverage and user education across agent and agentless deployments.
  3. Distribute and rotate proxy certificates through controlled endpoint management.
  4. Maintain an approved endpoint OS and onboarding compatibility matrix.

Explanation

Correct Answer

B:

Compare traffic-type coverage and user education across agent and agentless deployments. This control reduces recurrence of the documented mechanism: Agentless proxy scope is not automatically equivalent to full device-tunnel traffic coverage. It creates a repeatable check around the needed response: Apply the approved security coverage rules for each connection mode and document which traffic types each mode protects.

Incorrect Answers

A:

Test identity group claims and policy mapping together during SSO acceptance. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Agentless proxy scope is not automatically equivalent to full device-tunnel traffic coverage.

C:

Distribute and rotate proxy certificates through controlled endpoint management. That safeguard addresses another potential failure: A site lets users bypass required certificate trust warnings by manually accepting an unexpected FortiSASE proxy certificate on every device. It is not the most targeted recurring control for the described cause: Agentless proxy scope is not automatically equivalent to full device-tunnel traffic coverage.

D:

Maintain an approved endpoint OS and onboarding compatibility matrix. That safeguard addresses another potential failure: An enterprise distributes FortiClient installation to Windows staff while Linux contractor devices are assumed supported under the identical profile without checking platform capabilities. It is not the most targeted recurring control for the described cause: Agentless proxy scope is not automatically equivalent to full device-tunnel traffic coverage.

Question 733

At a hospital campus, a security analyst is reviewing this failure during a planned policy migration: Voice calls fail during transient packet loss while FortiGate steers calls to the cheapest link because the SLA tracks only latency. What is the MOST appropriate FIRST corrective step?

  1. Set a valid supported probe source address or appropriate interface binding for that member.
  2. Calibrate the SLA threshold to an achievable business requirement and service geography.
  3. Use supported active health checks for pre-traffic baselining or observe passive measurements once eligible sessions exist.
  4. Add the approved packet-loss threshold to the voice performance SLA and apply it to the steering rule.

Explanation

Correct Answer

D:

Add the approved packet-loss threshold to the voice performance SLA and apply it to the steering rule. This is the most direct response to the stated incident: Voice calls fail during transient packet loss while FortiGate steers calls to the cheapest link because the SLA tracks only latency. The technical mechanism is: Latency alone does not characterize loss sensitivity of real-time voice traffic. Confirmation requires: Calls leave a member whose measured loss exceeds the threshold while a healthier option remains eligible.

Incorrect Answers

A:

Set a valid supported probe source address or appropriate interface binding for that member. That could address a different issue in the same blueprint area: The performance SLA reports high loss on a backup line because probes use a source address not routed by its provider. It does not directly correct the given incident, whose decisive mechanism is: Latency alone does not characterize loss sensitivity of real-time voice traffic.

B:

Calibrate the SLA threshold to an achievable business requirement and service geography. That could address a different issue in the same blueprint area: A performance SLA is configured with a 5-ms latency threshold despite a normal 40-ms regional WAN path, excluding all members under healthy conditions. It does not directly correct the given incident, whose decisive mechanism is: Latency alone does not characterize loss sensitivity of real-time voice traffic.

C:

Use supported active health checks for pre-traffic baselining or observe passive measurements once eligible sessions exist. That could address a different issue in the same blueprint area: Network staff assume passive WAN measurements will be available before any traffic is sent through a new link, causing an empty dashboard to be interpreted as a fault. It does not directly correct the given incident, whose decisive mechanism is: Latency alone does not characterize loss sensitivity of real-time voice traffic.

Question 734

During follow-up testing at a hospital campus, the original fault was: Voice calls fail during transient packet loss while FortiGate steers calls to the cheapest link because the SLA tracks only latency. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. Calls leave a member whose measured loss exceeds the threshold while a healthier option remains eligible.
  2. During a controlled borderline-quality test link status does not flap excessively, but major failures still trigger action.
  3. Health-check output lists both members with usable measurements and state changes.
  4. A direct-Internet test agrees with probe state and healthy DIA members become eligible.

Explanation

Correct Answer

A:

Calls leave a member whose measured loss exceeds the threshold while a healthier option remains eligible. This evidence directly tests the intended corrective action: Add the approved packet-loss threshold to the voice performance SLA and apply it to the steering rule. It confirms the failure mechanism—Latency alone does not characterize loss sensitivity of real-time voice traffic.—has been addressed in the actual affected flow.

Incorrect Answers

B:

During a controlled borderline-quality test link status does not flap excessively, but major failures still trigger action. This would verify resolution of a different case: A branch SLA oscillates between healthy and failed every few seconds because recovery thresholds are too sensitive near its jitter boundary. It does not show that the reported issue was fixed or that its intended action—Add the approved packet-loss threshold to the voice performance SLA and apply it to the steering rule.—worked.

C:

Health-check output lists both members with usable measurements and state changes. This would verify resolution of a different case: An engineer creates a performance SLA but does not associate the backup member with its health-check member list, leaving the backup unmonitored. It does not show that the reported issue was fixed or that its intended action—Add the approved packet-loss threshold to the voice performance SLA and apply it to the steering rule.—worked.

D:

A direct-Internet test agrees with probe state and healthy DIA members become eligible. This would verify resolution of a different case: A branch tests loss toward an internal DNS server reachable through a tunnel, so a public DIA member appears unhealthy despite reliable Internet service. It does not show that the reported issue was fixed or that its intended action—Add the approved packet-loss threshold to the voice performance SLA and apply it to the steering rule.—worked.

Question 735

The incident investigation at a hospital campus records: Voice calls fail during transient packet loss while FortiGate steers calls to the cheapest link because the SLA tracks only latency. Which mechanism provides the strongest explanation?

  1. Probe cadence and failure count control how quickly availability degradation is detected.
  2. Latency alone does not characterize loss sensitivity of real-time voice traffic.
  3. A blocked synthetic probe may cause false member failure separate from ordinary sessions.
  4. Performance SLA eligibility depends on which member interfaces are actually monitored.

Explanation

Correct Answer

B:

Latency alone does not characterize loss sensitivity of real-time voice traffic. This explains why the reported condition occurs: Voice calls fail during transient packet loss while FortiGate steers calls to the cheapest link because the SLA tracks only latency. The targeted correction is: Add the approved packet-loss threshold to the voice performance SLA and apply it to the steering rule.

Incorrect Answers

A:

Probe cadence and failure count control how quickly availability degradation is detected. This mechanism instead explains a separate problem: An SLA uses a probe interval too sparse to detect outages quickly enough for a monitored payment application. The current incident requires the more directly applicable cause stated by the correct option.

C:

A blocked synthetic probe may cause false member failure separate from ordinary sessions. This mechanism instead explains a separate problem: A branch's SLA probe targets are blocked by an upstream provider ACL, yet employees can reach normal applications without difficulty. The current incident requires the more directly applicable cause stated by the correct option.

D:

Performance SLA eligibility depends on which member interfaces are actually monitored. This mechanism instead explains a separate problem: An engineer creates a performance SLA but does not associate the backup member with its health-check member list, leaving the backup unmonitored. The current incident requires the more directly applicable cause stated by the correct option.

Question 736

After a corrective change at a hospital campus, the team documents: Voice calls fail during transient packet loss while FortiGate steers calls to the cheapest link because the SLA tracks only latency. Which repeatable control BEST prevents a recurrence?

  1. Create service-specific health-check targets for materially different WAN paths.
  2. Review SLA values using measured voice quality and contractual objectives.
  3. Monitor loss, latency and jitter against application requirements during call quality testing.
  4. Test no-member-meets-SLA conditions rather than assuming automatic dropping or universal failover.

Explanation

Correct Answer

C:

Monitor loss, latency and jitter against application requirements during call quality testing. This control reduces recurrence of the documented mechanism: Latency alone does not characterize loss sensitivity of real-time voice traffic. It creates a repeatable check around the needed response: Add the approved packet-loss threshold to the voice performance SLA and apply it to the steering rule.

Incorrect Answers

A:

Create service-specific health-check targets for materially different WAN paths. That safeguard addresses another potential failure: A site wants link status tracked separately for private data-center traffic and Internet browsing, but uses the same public Internet probe for both SLA decisions. It is not the most targeted recurring control for the described cause: Latency alone does not characterize loss sensitivity of real-time voice traffic.

B:

Review SLA values using measured voice quality and contractual objectives. That safeguard addresses another potential failure: A voice quality rule uses a jitter maximum far above business tolerance so choppy calls continue on a variable-delay ISP. It is not the most targeted recurring control for the described cause: Latency alone does not characterize loss sensitivity of real-time voice traffic.

D:

Test no-member-meets-SLA conditions rather than assuming automatic dropping or universal failover. That safeguard addresses another potential failure: An engineer configures SD-WAN latency monitoring but its rule selects a member that meets no required SLA due to an unreviewed fallback behavior. It is not the most targeted recurring control for the described cause: Latency alone does not characterize loss sensitivity of real-time voice traffic.

Question 737

During a security audit at a retail network, analysts observe: 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. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Restore the authorized zone default route and verify session processing.
  2. Remove or update the stale more-specific route so the approved path has correct longest-prefix precedence.
  3. Correct static route distance, priority or route target to prefer the approved SD-WAN zone.
  4. Install or advertise the correct reverse route in the remote routing domain.

Explanation

Correct Answer

A:

Restore the authorized zone default route and verify session processing. This is the most direct response to the stated incident: 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 technical mechanism is: Rule matching does not compensate for missing destination route state. Confirmation requires: Routing diagnostics show an eligible default path and the allowed application completes.

Incorrect Answers

B:

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: Rule matching does not compensate for missing destination route state.

C:

Correct static route distance, priority or route target to prefer the approved SD-WAN zone. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Rule matching does not compensate for missing destination route state.

D:

Install or advertise the correct reverse route in the remote routing domain. That could address a different issue in the same blueprint area: 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 directly correct the given incident, whose decisive mechanism is: Rule matching does not compensate for missing destination route state.

Question 738

At a retail network, a test team is validating a change after this incident: 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. 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. Routing diagnostics show an eligible default path and the allowed application completes.
  3. External test services observe a valid address for each ISP and responses return successfully.
  4. The active route resolves to the healthy tunnel and the remote branch is reachable.

Explanation

Correct Answer

B:

Routing diagnostics show an eligible default path and the allowed application completes. This evidence directly tests the intended corrective action: Restore the authorized zone default route and verify session processing. It confirms the failure mechanism—Rule matching does not compensate for missing destination route state.—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—Restore the authorized zone default route and verify session processing.—worked.

C:

External test services observe a valid address for each ISP and responses return successfully. This would verify resolution of a different case: 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. It does not show that the reported issue was fixed or that its intended action—Restore the authorized zone default route and verify session processing.—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—Restore the authorized zone default route and verify session processing.—worked.

Question 739

A Fortinet administrator at a retail network is assessing: 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. What is the most relevant root cause?

  1. SD-WAN route changes and source address translation must remain compatible across failover.
  2. Locally originated system traffic and forwarded sessions can use different routing decisions.
  3. Rule matching does not compensate for missing destination route state.
  4. Central route templates can override manually repaired local routes during later installs.

Explanation

Correct Answer

C:

Rule matching does not compensate for missing destination route state. This explains why the reported condition occurs: 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 targeted correction is: Restore the authorized zone default route and verify session processing.

Incorrect Answers

A:

SD-WAN route changes and source address translation must remain compatible across failover. This mechanism instead explains a separate problem: 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 current incident requires the more directly applicable cause stated by the correct option.

B:

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:

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 740

A risk review at a retail network focuses on preventing this issue again: 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. Which recurring control is most suitable?

  1. Document routing priorities for overlays with multiple learned next hops.
  2. Make permanent route corrections in the authoritative centralized configuration source.
  3. Require matched firewall rule plus route and SD-WAN rule evidence for application go-live.
  4. Add route-table verification to automated SD-WAN rule deployment pipelines.

Explanation

Correct Answer

D:

Add route-table verification to automated SD-WAN rule deployment pipelines. This control reduces recurrence of the documented mechanism: Rule matching does not compensate for missing destination route state. It creates a repeatable check around the needed response: Restore the authorized zone default route and verify session processing.

Incorrect Answers

A:

Document routing priorities for overlays with multiple learned next hops. That safeguard addresses another potential failure: 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 is not the most targeted recurring control for the described cause: Rule matching does not compensate for missing destination route state.

B:

Make permanent route corrections in the authoritative centralized configuration source. That safeguard addresses another potential failure: A FortiGate has the correct SD-WAN zone route for corporate VPN but FortiManager installs a conflicting stale prefix route during configuration synchronization. It is not the most targeted recurring control for the described cause: Rule matching does not compensate for missing destination route state.

C:

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: Rule matching does not compensate for missing destination route state.

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