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 20

Question 190

A customer support center needs to distinguish jitter problems from a simple throughput shortage. Suppose the team follows this shortcut instead: Evaluate only average RTT while ignoring rapidly varying packet arrival times for voice. What is the most likely direct security or operational consequence?

  1. Brief congestion produces constant path changes and interruptive user sessions
  2. Conference calls stutter despite an apparently normal average latency graph
  3. Poor paths remain selected for critical applications despite accurate SLA graphs
  4. Applications reset during an unstable restoration and path churn increases

Answer & Explanations

Correct answer: B

A.

This failure concerns another scenario: A clinic's WAN swaps every minute when one ping is delayed. In the stated case: A customer support center needs to distinguish jitter problems from a simple throughput shortage. The relevant consequence is: Conference calls stutter despite an apparently normal average latency graph. The control that prevents it is: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

B.

Conference calls stutter despite an apparently normal average latency graph. This is the risk in the stated situation: A customer support center needs to distinguish jitter problems from a simple throughput shortage. The risky shortcut is: Evaluate only average RTT while ignoring rapidly varying packet arrival times for voice. Prevent it by: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

C.

This failure concerns another scenario: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. In the stated case: A customer support center needs to distinguish jitter problems from a simple throughput shortage. The relevant consequence is: Conference calls stutter despite an apparently normal average latency graph. The control that prevents it is: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

D.

This failure concerns another scenario: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. In the stated case: A customer support center needs to distinguish jitter problems from a simple throughput shortage. The relevant consequence is: Conference calls stutter despite an apparently normal average latency graph. The control that prevents it is: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

Question 191

A hospital's encrypted private circuit probes an unrelated public address and is marked down. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member
  2. Distinguish an unreachable SLA server or member-down condition from a reachable member that simply fails loss, latency or jitter objectives
  3. Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service
  4. Set probe intervals, failure thresholds and recovery behavior to distinguish real link degradation from transient measurement noise

Answer & Explanations

Correct answer: C

A.

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 hospital's encrypted private circuit probes an unrelated public address and is marked down. The appropriate response is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

B.

This action is appropriate in a different case: An office has one slow LTE link suitable for email but unsuitable for voice. There, the reason is: An active but degraded circuit may continue carrying other approved traffic, while a truly dead path should not be selected for any required service. The current case is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The appropriate response is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

C.

Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. The technical reason is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay. The stated condition is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. Confirm the result by: Compare probe response with actual protected application reachability using one permitted route and a second reference target.

D.

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: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The appropriate response is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

Question 192

A hospital's encrypted private circuit probes an unrelated public address and is marked down. A Fortinet administrator recommends: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. Which technical process explanation best justifies that recommendation?

  1. Too-aggressive probes or thresholds can cause repeated SD-WAN path changes, while slow detection delays recovery after genuine failure
  2. A correctly configured health-check object does not change traffic steering unless the matching service uses its status under the chosen strategy
  3. Recovery may involve hold timers, strategy, member priority and new-session selection; healthy status does not imply existing sessions instantly migrate back
  4. An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay

Answer & Explanations

Correct answer: D

A.

This principle explains a different technical intervention: Set probe intervals, failure thresholds and recovery behavior to distinguish real link degradation from transient measurement noise. It applies to: A clinic's WAN swaps every minute when one ping is delayed. The actual case is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The mechanism relevant here is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay.

B.

This principle explains a different technical intervention: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds. It applies to: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. The actual case is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The mechanism relevant here is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay.

C.

This principle explains a different technical intervention: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered. It applies to: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The actual case is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The mechanism relevant here is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay.

D.

An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay. That mechanism explains the decision: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. In the reported situation: A hospital's encrypted private circuit probes an unrelated public address and is marked down. Confirmation requires: Compare probe response with actual protected application reachability using one permitted route and a second reference target.

Question 193

A hospital's encrypted private circuit probes an unrelated public address and is marked down. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Compare probe response with actual protected application reachability using one permitted route and a second reference target
  2. Degrade and restore a pilot path while logging changes to SLA state, new-session member and transaction continuity
  3. Send approved client traffic through each permitted ISP and inspect the selected member, NAT tuple and firewall session
  4. Compare monitor results with a controlled synthetic browsing transaction and sampled session member IDs

Answer & Explanations

Correct answer: A

A.

Compare probe response with actual protected application reachability using one permitted route and a second reference target. This check directly tests: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. The underlying behavior is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay. The case is: A hospital's encrypted private circuit probes an unrelated public address and is marked down.

B.

This observation would verify a different remedy: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered. That remedy applies to: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The present condition is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. To assess it, check: Compare probe response with actual protected application reachability using one permitted route and a second reference target.

C.

This observation would verify a different remedy: Implement direct internet access through a FortiGate SD-WAN zone with explicit underlay members, firewall policy, NAT and health checks. That remedy applies to: A retailer adds two local broadband links but keeps its branch SaaS sessions pinned to a failed data-center backhaul. The present condition is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. To assess it, check: Compare probe response with actual protected application reachability using one permitted route and a second reference target.

D.

This observation would verify a different remedy: Create a baseline of SD-WAN member status, aggregate traffic, packet loss and eligible route reachability before tuning steering rules. That remedy applies to: A logistics branch reports intermittent internet loss although both ISP ports show up. The present condition is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. To assess it, check: Compare probe response with actual protected application reachability using one permitted route and a second reference target.

Question 194

A hospital's encrypted private circuit probes an unrelated public address and is marked down. Which apparently convenient shortcut would most directly undermine the required control?

  1. Declare all WAN paths healthy because the FortiGate interface counters show carrier detected
  2. Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service
  3. Copy headquarters interface addresses and gateway values directly to every newly provisioned branch
  4. Send regulated private service traffic directly to an untrusted public ISP because its latency is currently lowest

Answer & Explanations

Correct answer: B

A.

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 hospital's encrypted private circuit probes an unrelated public address and is marked down. Here the unsafe shortcut is: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. Use this response instead: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

B.

Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. This shortcut is unsafe for: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The resulting failure can be: The private overlay is marked unhealthy even while its business service remains reachable. The safer response is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

C.

This proposed shortcut concerns a separate case: A franchise duplicates the first store configuration and two stores unexpectedly advertise the same inside prefix. The risk in this question concerns: A hospital's encrypted private circuit probes an unrelated public address and is marked down. Here the unsafe shortcut is: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. Use this response instead: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

D.

This proposed shortcut concerns a separate case: A manufacturer connects field offices to private ERP over IPsec but needs ordinary web access on the local ISP. The risk in this question concerns: A hospital's encrypted private circuit probes an unrelated public address and is marked down. Here the unsafe shortcut is: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. Use this response instead: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

Question 195

A hospital's encrypted private circuit probes an unrelated public address and is marked down. Suppose the team follows this shortcut instead: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. What is the most likely direct security or operational consequence?

  1. Sensitive business sessions leave the approved private path and fail access or compliance checks
  2. Voice sessions remain on a poor-quality path despite another usable member
  3. The private overlay is marked unhealthy even while its business service remains reachable
  4. Sessions are steered toward a healthy interface but are denied or leave with unroutable source addresses

Answer & Explanations

Correct answer: C

A.

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 hospital's encrypted private circuit probes an unrelated public address and is marked down. The relevant consequence is: The private overlay is marked unhealthy even while its business service remains reachable. The control that prevents it is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

B.

This failure concerns another scenario: A school uses two static internet routes but its classroom video app suffers during upstream loss. In the stated case: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The relevant consequence is: The private overlay is marked unhealthy even while its business service remains reachable. The control that prevents it is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

C.

The private overlay is marked unhealthy even while its business service remains reachable. This is the risk in the stated situation: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The risky shortcut is: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. Prevent it by: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

D.

This failure concerns another scenario: An ecommerce branch sets the ideal SD-WAN service rule but its browser traffic still hits implicit deny. In the stated case: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The relevant consequence is: The private overlay is marked unhealthy even while its business service remains reachable. The control that prevents it is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

Question 196

A retailer has intermittent false failover because its chosen SLA target rate-limits probes. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Implement direct internet access through a FortiGate SD-WAN zone with explicit underlay members, firewall policy, NAT and health checks
  2. Create a baseline of SD-WAN member status, aggregate traffic, packet loss and eligible route reachability before tuning steering rules
  3. Inventory LAN subnets, overlapping WAN addresses, default routes and SD-WAN policy dependencies before enrolling a FortiGate in a new branch design
  4. Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service

Answer & Explanations

Correct answer: D

A.

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: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The appropriate response is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

B.

This action is appropriate in a different case: A logistics branch reports intermittent internet loss although both ISP ports show up. There, the reason is: Member health and application path performance can differ from interface link state; an Ethernet up indicator alone cannot prove internet reachability or acceptable quality. The current case is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The appropriate response is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

C.

This action is appropriate in a different case: A franchise duplicates the first store configuration and two stores unexpectedly advertise the same inside prefix. There, the reason is: 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. The current case is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The appropriate response is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

D.

Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. The technical reason is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay. The stated condition is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. Confirm the result by: Compare probe response with actual protected application reachability using one permitted route and a second reference target.

Question 197

A retailer has intermittent false failover because its chosen SLA target rate-limits probes. A Fortinet administrator recommends: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. Which technical process explanation best justifies that recommendation?

  1. An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay
  2. 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
  3. Secure private routes and direct internet routes serve different data destinations; a default internet egress rule is not evidence that private traffic traverses the intended protected overlay
  4. Two static routes can provide route preference, but SD-WAN adds member health, measured SLA and service rules to control which qualifying path handles a flow

Answer & Explanations

Correct answer: A

A.

An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay. That mechanism explains the decision: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. In the reported situation: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. Confirmation requires: Compare probe response with actual protected application reachability using one permitted route and a second reference target.

B.

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: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The mechanism relevant here is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay.

C.

This principle explains a different technical intervention: Define which branch destinations use secure overlay paths and which use local internet egress, then test scoped policies for both groups. It applies to: A manufacturer connects field offices to private ERP over IPsec but needs ordinary web access on the local ISP. The actual case is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The mechanism relevant here is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay.

D.

This principle explains a different technical intervention: 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. It applies to: A school uses two static internet routes but its classroom video app suffers during upstream loss. The actual case is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The mechanism relevant here is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay.

Question 198

A retailer has intermittent false failover because its chosen SLA target rate-limits probes. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Test two distinct applications and prove they select the intended member when both ISP routes remain reachable
  2. Compare probe response with actual protected application reachability using one permitted route and a second reference target
  3. Inspect one approved test flow for both SD-WAN rule result and firewall policy/NAT acceptance
  4. Compare two target branch effective configurations and confirm install status and a real WAN path test

Answer & Explanations

Correct answer: B

A.

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: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. To assess it, check: Compare probe response with actual protected application reachability using one permitted route and a second reference target.

B.

Compare probe response with actual protected application reachability using one permitted route and a second reference target. This check directly tests: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. The underlying behavior is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay. The case is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes.

C.

This observation would verify a different remedy: Create the required FortiGate security policy and source NAT for flows traversing the SD-WAN zone after defining membership and steering. That remedy applies to: An ecommerce branch sets the ideal SD-WAN service rule but its browser traffic still hits implicit deny. The present condition is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. To assess it, check: Compare probe response with actual protected application reachability using one permitted route and a second reference target.

D.

This observation would verify a different remedy: Use approved FortiManager templates and per-branch parameters to deploy FortiOS SD-WAN settings to the intended device groups with preview and rollback. That remedy applies to: An MSP updates one regional template but accidentally targets all customer FortiGates. The present condition is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. To assess it, check: Compare probe response with actual protected application reachability using one permitted route and a second reference target.

Question 199

A retailer has intermittent false failover because its chosen SLA target rate-limits probes. Which apparently convenient shortcut would most directly undermine the required control?

  1. Install a modified global SD-WAN template to every branch without validating local WAN interface references
  2. Raise every SD-WAN rule priority to fix an ISP handoff with no reachable gateway
  3. Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service
  4. Place a guest internet underlay into the protected private-WAN zone merely to make member selection simple

Answer & Explanations

Correct answer: C

A.

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: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. Here the unsafe shortcut is: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. Use this response instead: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

B.

This proposed shortcut concerns a separate case: A manufacturer cannot reach any destination through its new broadband circuit and assumes application steering is wrong. The risk in this question concerns: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. Here the unsafe shortcut is: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. Use this response instead: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

C.

Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. This shortcut is unsafe for: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The resulting failure can be: The private overlay is marked unhealthy even while its business service remains reachable. The safer response is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

D.

This proposed shortcut concerns a separate case: A hospital has separate private MPLS and public internet paths but a new member is added to the wrong zone. The risk in this question concerns: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. Here the unsafe shortcut is: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. Use this response instead: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

Question 200

A retailer has intermittent false failover because its chosen SLA target rate-limits probes. Suppose the team follows this shortcut instead: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. What is the most likely direct security or operational consequence?

  1. Guest connections gain an unexpected eligible transport or fail zone-specific security matching
  2. Private destinations become unreachable or traffic bypasses the intended encrypted overlay
  3. Secondary-link traffic fails before reaching the internet even though member selection succeeds
  4. The private overlay is marked unhealthy even while its business service remains reachable

Answer & Explanations

Correct answer: D

A.

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: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The relevant consequence is: The private overlay is marked unhealthy even while its business service remains reachable. The control that prevents it is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

B.

This failure concerns another scenario: A regional bank uses IPsec overlays above two ISPs and one overlay loses its encryption association. In the stated case: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The relevant consequence is: The private overlay is marked unhealthy even while its business service remains reachable. The control that prevents it is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

C.

This failure concerns another scenario: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. In the stated case: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The relevant consequence is: The private overlay is marked unhealthy even while its business service remains reachable. The control that prevents it is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

D.

The private overlay is marked unhealthy even while its business service remains reachable. This is the risk in the stated situation: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The risky shortcut is: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. Prevent it by: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.

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