Practice Exams:

Fortinet NSE5_SSE_AD-7.6 Dumps

EXAM: Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator
Verified By Experts
Premium Bundle
$49.99

NSE5_SSE_AD-7.6 Premium ETE File


  • Premium File 54 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet NSE5_SSE_AD-7.6 Practice Test 24

Question 230

A retailer has an unused latency monitor because the POS service rule references another SLA. Suppose the team follows this shortcut instead: Create a latency health check and assume all applications automatically honor it without binding a rule. What is the most likely direct security or operational consequence?

  1. Conference calls stutter despite an apparently normal average latency graph
  2. Poor paths remain selected for critical applications despite accurate SLA graphs
  3. The private overlay is marked unhealthy even while its business service remains reachable
  4. Bulk recovery transfers lose a usable path that could have served their requirements

Answer & Explanations

Correct answer: B

A.

This failure concerns another scenario: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. In the stated case: A retailer has an unused latency monitor because the POS service rule references another SLA. The relevant consequence is: Poor paths remain selected for critical applications despite accurate SLA graphs. The control that prevents it is: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds.

B.

Poor paths remain selected for critical applications despite accurate SLA graphs. This is the risk in the stated situation: A retailer has an unused latency monitor because the POS service rule references another SLA. The risky shortcut is: Create a latency health check and assume all applications automatically honor it without binding a rule. Prevent it by: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds.

C.

This failure concerns another scenario: A hospital's encrypted private circuit probes an unrelated public address and is marked down. In the stated case: A retailer has an unused latency monitor because the POS service rule references another SLA. The relevant consequence is: Poor paths remain selected for critical applications despite accurate SLA graphs. The control that prevents it is: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds.

D.

This failure concerns another scenario: An office has one slow LTE link suitable for email but unsuitable for voice. In the stated case: A retailer has an unused latency monitor because the POS service rule references another SLA. The relevant consequence is: Poor paths remain selected for critical applications despite accurate SLA graphs. The control that prevents it is: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds.

Question 231

A bank's primary ISP recovers but the service continues selecting a backup for new sessions. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Define an SD-WAN performance SLA with justified packet loss tolerance and healthy probe targets for the critical application
  2. Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule
  3. Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered
  4. Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member

Answer & Explanations

Correct answer: C

A.

This action is appropriate in a different case: A call center's voice quality deteriorates when ISP loss rises despite a green interface LED. There, the reason is: Link loss measured through an active health check can indicate poor transport quality before the physical interface goes down. The current case is: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The appropriate response is: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

B.

This action is appropriate in a different case: A satellite backup has more capacity but causes long voice delays compared with local fiber. There, the reason is: Latency measurements let a service rule reject a slow but reachable member; bandwidth by itself does not prove acceptable round-trip delay. The current case is: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The appropriate response is: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

C.

Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered. The technical reason is: Recovery may involve hold timers, strategy, member priority and new-session selection; healthy status does not imply existing sessions instantly migrate back. The stated condition is: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. Confirm the result by: Degrade and restore a pilot path while logging changes to SLA state, new-session member and transaction continuity.

D.

This action is appropriate in a different case: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. There, the reason is: Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable. The current case is: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The appropriate response is: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

Question 232

A bank's primary ISP recovers but the service continues selecting a backup for new sessions. A Fortinet administrator recommends: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered. Which technical process explanation best justifies that recommendation?

  1. Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable
  2. An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay
  3. An active but degraded circuit may continue carrying other approved traffic, while a truly dead path should not be selected for any required service
  4. Recovery may involve hold timers, strategy, member priority and new-session selection; healthy status does not imply existing sessions instantly migrate back

Answer & Explanations

Correct answer: D

A.

This principle explains a different technical intervention: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member. It applies to: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. The actual case is: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The mechanism relevant here is: Recovery may involve hold timers, strategy, member priority and new-session selection; healthy status does not imply existing sessions instantly migrate back.

B.

This principle explains a different technical intervention: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. It applies to: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The actual case is: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The mechanism relevant here is: Recovery may involve hold timers, strategy, member priority and new-session selection; healthy status does not imply existing sessions instantly migrate back.

C.

This principle explains a different technical intervention: Distinguish an unreachable SLA server or member-down condition from a reachable member that simply fails loss, latency or jitter objectives. It applies to: An office has one slow LTE link suitable for email but unsuitable for voice. The actual case is: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The mechanism relevant here is: Recovery may involve hold timers, strategy, member priority and new-session selection; healthy status does not imply existing sessions instantly migrate back.

D.

Recovery may involve hold timers, strategy, member priority and new-session selection; healthy status does not imply existing sessions instantly migrate back. That mechanism explains the decision: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered. In the reported situation: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. Confirmation requires: Degrade and restore a pilot path while logging changes to SLA state, new-session member and transaction continuity.

Question 233

A bank's primary ISP recovers but the service continues selecting a backup for new sessions. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Degrade and restore a pilot path while logging changes to SLA state, new-session member and transaction continuity
  2. Review FortiOS health-check status and two different application session paths under a controlled degradation
  3. Replay brief and sustained impairments and compare transition counts with the approved failover window
  4. Trigger a safe SLA breach and inspect both health-check state and actual matching SD-WAN service rule

Answer & Explanations

Correct answer: A

A.

Degrade and restore a pilot path while logging changes to SLA state, new-session member and transaction continuity. This check directly tests: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered. The underlying behavior is: Recovery may involve hold timers, strategy, member priority and new-session selection; healthy status does not imply existing sessions instantly migrate back. The case is: A bank's primary ISP recovers but the service continues selecting a backup for new sessions.

B.

This observation would verify a different remedy: Distinguish an unreachable SLA server or member-down condition from a reachable member that simply fails loss, latency or jitter objectives. That remedy applies to: An office has one slow LTE link suitable for email but unsuitable for voice. The present condition is: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. To assess it, check: Degrade and restore a pilot path while logging changes to SLA state, new-session member and transaction continuity.

C.

This observation would verify a different remedy: Set probe intervals, failure thresholds and recovery behavior to distinguish real link degradation from transient measurement noise. That remedy applies to: A clinic's WAN swaps every minute when one ping is delayed. The present condition is: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. To assess it, check: Degrade and restore a pilot path while logging changes to SLA state, new-session member and transaction continuity.

D.

This observation would verify a different remedy: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds. That remedy applies to: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. The present condition is: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. To assess it, check: Degrade and restore a pilot path while logging changes to SLA state, new-session member and transaction continuity.

Question 234

A bank's primary ISP recovers but the service continues selecting a backup for new sessions. Which apparently convenient shortcut would most directly undermine the required control?

  1. Create a latency health check and assume all applications automatically honor it without binding a rule
  2. Force all established sessions back to the preferred ISP the instant one good health check appears
  3. Backhaul every branch web flow through an unreachable headquarters tunnel merely because that was the former default route
  4. Declare all WAN paths healthy because the FortiGate interface counters show carrier detected

Answer & Explanations

Correct answer: B

A.

This proposed shortcut concerns a separate case: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. The risk in this question concerns: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. Here the unsafe shortcut is: Force all established sessions back to the preferred ISP the instant one good health check appears. Use this response instead: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

B.

Force all established sessions back to the preferred ISP the instant one good health check appears. This shortcut is unsafe for: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The resulting failure can be: Applications reset during an unstable restoration and path churn increases. The safer response is: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

C.

This proposed shortcut concerns a separate case: A retailer adds two local broadband links but keeps its branch SaaS sessions pinned to a failed data-center backhaul. The risk in this question concerns: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. Here the unsafe shortcut is: Force all established sessions back to the preferred ISP the instant one good health check appears. Use this response instead: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

D.

This proposed shortcut concerns a separate case: A logistics branch reports intermittent internet loss although both ISP ports show up. The risk in this question concerns: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. Here the unsafe shortcut is: Force all established sessions back to the preferred ISP the instant one good health check appears. Use this response instead: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

Question 235

A bank's primary ISP recovers but the service continues selecting a backup for new sessions. Suppose the team follows this shortcut instead: Force all established sessions back to the preferred ISP the instant one good health check appears. What is the most likely direct security or operational consequence?

  1. Traffic keeps using a blackholed upstream connection while dashboards appear green
  2. Duplicate networks and invalid gateways make branches unreachable or cause unpredictable traffic return
  3. Applications reset during an unstable restoration and path churn increases
  4. Sensitive business sessions leave the approved private path and fail access or compliance checks

Answer & Explanations

Correct answer: C

A.

This failure concerns another scenario: A logistics branch reports intermittent internet loss although both ISP ports show up. In the stated case: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The relevant consequence is: Applications reset during an unstable restoration and path churn increases. The control that prevents it is: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

B.

This failure concerns another scenario: A franchise duplicates the first store configuration and two stores unexpectedly advertise the same inside prefix. In the stated case: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The relevant consequence is: Applications reset during an unstable restoration and path churn increases. The control that prevents it is: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

C.

Applications reset during an unstable restoration and path churn increases. This is the risk in the stated situation: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The risky shortcut is: Force all established sessions back to the preferred ISP the instant one good health check appears. Prevent it by: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

D.

This failure concerns another scenario: A manufacturer connects field offices to private ERP over IPsec but needs ordinary web access on the local ISP. In the stated case: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The relevant consequence is: Applications reset during an unstable restoration and path churn increases. The control that prevents it is: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

Question 236

An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Set probe intervals, failure thresholds and recovery behavior to distinguish real link degradation from transient measurement noise
  2. Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds
  3. Implement direct internet access through a FortiGate SD-WAN zone with explicit underlay members, firewall policy, NAT and health checks
  4. Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered

Answer & Explanations

Correct answer: D

A.

This action is appropriate in a different case: A clinic's WAN swaps every minute when one ping is delayed. There, the reason is: Too-aggressive probes or thresholds can cause repeated SD-WAN path changes, while slow detection delays recovery after genuine failure. The current case is: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. The appropriate response is: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

B.

This action is appropriate in a different case: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. There, the reason is: A correctly configured health-check object does not change traffic steering unless the matching service uses its status under the chosen strategy. The current case is: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. The appropriate response is: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

C.

This action is appropriate in a different case: A retailer adds two local broadband links but keeps its branch SaaS sessions pinned to a failed data-center backhaul. There, the reason is: A direct internet access design keeps eligible branch traffic local while SD-WAN selects healthy internet members; defining the zone alone does not grant traffic or translate private addresses. The current case is: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. The appropriate response is: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

D.

Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered. The technical reason is: Recovery may involve hold timers, strategy, member priority and new-session selection; healthy status does not imply existing sessions instantly migrate back. The stated condition is: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. Confirm the result by: Degrade and restore a pilot path while logging changes to SLA state, new-session member and transaction continuity.

Question 237

An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. A Fortinet administrator recommends: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered. Which technical process explanation best justifies that recommendation?

  1. Recovery may involve hold timers, strategy, member priority and new-session selection; healthy status does not imply existing sessions instantly migrate back
  2. A direct internet access design keeps eligible branch traffic local while SD-WAN selects healthy internet members; defining the zone alone does not grant traffic or translate private addresses
  3. Member health and application path performance can differ from interface link state; an Ethernet up indicator alone cannot prove internet reachability or acceptable quality
  4. SD-WAN forwarding depends on valid routed underlay interfaces and correct address scope; duplicate subnets or stale routes can prevent return traffic even with acceptable link health

Answer & Explanations

Correct answer: A

A.

Recovery may involve hold timers, strategy, member priority and new-session selection; healthy status does not imply existing sessions instantly migrate back. That mechanism explains the decision: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered. In the reported situation: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. Confirmation requires: Degrade and restore a pilot path while logging changes to SLA state, new-session member and transaction continuity.

B.

This principle explains a different technical intervention: Implement direct internet access through a FortiGate SD-WAN zone with explicit underlay members, firewall policy, NAT and health checks. It applies to: A retailer adds two local broadband links but keeps its branch SaaS sessions pinned to a failed data-center backhaul. The actual case is: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. The mechanism relevant here is: Recovery may involve hold timers, strategy, member priority and new-session selection; healthy status does not imply existing sessions instantly migrate back.

C.

This principle explains a different technical intervention: Create a baseline of SD-WAN member status, aggregate traffic, packet loss and eligible route reachability before tuning steering rules. It applies to: A logistics branch reports intermittent internet loss although both ISP ports show up. The actual case is: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. The mechanism relevant here is: Recovery may involve hold timers, strategy, member priority and new-session selection; healthy status does not imply existing sessions instantly migrate back.

D.

This principle explains a different technical intervention: Inventory LAN subnets, overlapping WAN addresses, default routes and SD-WAN policy dependencies before enrolling a FortiGate in a new branch design. It applies to: A franchise duplicates the first store configuration and two stores unexpectedly advertise the same inside prefix. The actual case is: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. The mechanism relevant here is: Recovery may involve hold timers, strategy, member priority and new-session selection; healthy status does not imply existing sessions instantly migrate back.

Question 238

An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Validate a dry-run routing lookup and end-to-end return path for one client subnet on each ISP
  2. Degrade and restore a pilot path while logging changes to SLA state, new-session member and transaction continuity
  3. Test one public SaaS connection and one internal application connection and compare actual path, policy and encryption state
  4. Test two distinct applications and prove they select the intended member when both ISP routes remain reachable

Answer & Explanations

Correct answer: B

A.

This observation would verify a different remedy: Inventory LAN subnets, overlapping WAN addresses, default routes and SD-WAN policy dependencies before enrolling a FortiGate in a new branch design. That remedy applies to: A franchise duplicates the first store configuration and two stores unexpectedly advertise the same inside prefix. The present condition is: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. To assess it, check: Degrade and restore a pilot path while logging changes to SLA state, new-session member and transaction continuity.

B.

Degrade and restore a pilot path while logging changes to SLA state, new-session member and transaction continuity. This check directly tests: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered. The underlying behavior is: Recovery may involve hold timers, strategy, member priority and new-session selection; healthy status does not imply existing sessions instantly migrate back. The case is: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive.

C.

This observation would verify a different remedy: Define which branch destinations use secure overlay paths and which use local internet egress, then test scoped policies for both groups. That remedy applies to: A manufacturer connects field offices to private ERP over IPsec but needs ordinary web access on the local ISP. The present condition is: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. To assess it, check: Degrade and restore a pilot path while logging changes to SLA state, new-session member and transaction continuity.

D.

This observation would verify a different remedy: Add WAN interfaces as SD-WAN members in the intended zone and use eligible routes and SD-WAN services instead of pretending a pair of static defaults offers application-aware steering. That remedy applies to: A school uses two static internet routes but its classroom video app suffers during upstream loss. The present condition is: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. To assess it, check: Degrade and restore a pilot path while logging changes to SLA state, new-session member and transaction continuity.

Question 239

An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. Which apparently convenient shortcut would most directly undermine the required control?

  1. Add only equal-cost static default routes and claim latency-sensitive traffic will automatically move away from packet loss
  2. Treat a new SD-WAN rule as if it automatically creates an any-application firewall permit
  3. Force all established sessions back to the preferred ISP the instant one good health check appears
  4. Install a modified global SD-WAN template to every branch without validating local WAN interface references

Answer & Explanations

Correct answer: C

A.

This proposed shortcut concerns a separate case: A school uses two static internet routes but its classroom video app suffers during upstream loss. The risk in this question concerns: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. Here the unsafe shortcut is: Force all established sessions back to the preferred ISP the instant one good health check appears. Use this response instead: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

B.

This proposed shortcut concerns a separate case: An ecommerce branch sets the ideal SD-WAN service rule but its browser traffic still hits implicit deny. The risk in this question concerns: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. Here the unsafe shortcut is: Force all established sessions back to the preferred ISP the instant one good health check appears. Use this response instead: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

C.

Force all established sessions back to the preferred ISP the instant one good health check appears. This shortcut is unsafe for: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. The resulting failure can be: Applications reset during an unstable restoration and path churn increases. The safer response is: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

D.

This proposed shortcut concerns a separate case: An MSP updates one regional template but accidentally targets all customer FortiGates. The risk in this question concerns: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. Here the unsafe shortcut is: Force all established sessions back to the preferred ISP the instant one good health check appears. Use this response instead: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

Question 240

An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. Suppose the team follows this shortcut instead: Force all established sessions back to the preferred ISP the instant one good health check appears. What is the most likely direct security or operational consequence?

  1. Unrelated locations lose their internet paths when an incorrect shared value is deployed
  2. The underlying connectivity defect remains while unrelated applications are rerouted
  3. Guest connections gain an unexpected eligible transport or fail zone-specific security matching
  4. Applications reset during an unstable restoration and path churn increases

Answer & Explanations

Correct answer: D

A.

This failure concerns another scenario: An MSP updates one regional template but accidentally targets all customer FortiGates. In the stated case: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. The relevant consequence is: Applications reset during an unstable restoration and path churn increases. The control that prevents it is: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

B.

This failure concerns another scenario: A manufacturer cannot reach any destination through its new broadband circuit and assumes application steering is wrong. In the stated case: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. The relevant consequence is: Applications reset during an unstable restoration and path churn increases. The control that prevents it is: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

C.

This failure concerns another scenario: A hospital has separate private MPLS and public internet paths but a new member is added to the wrong zone. In the stated case: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. The relevant consequence is: Applications reset during an unstable restoration and path churn increases. The control that prevents it is: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

D.

Applications reset during an unstable restoration and path churn increases. This is the risk in the stated situation: An online retailer repeatedly flaps after restoration because its recovery threshold is too permissive. The risky shortcut is: Force all established sessions back to the preferred ISP the instant one good health check appears. Prevent it by: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered.

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