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 23

Question 220

A call center requires a stable failover algorithm that tolerates a few lost probes. Suppose the team follows this shortcut instead: Configure immediate route switching on any single lost probe across all branch members. What is the most likely direct security or operational consequence?

  1. The underlying connectivity defect remains while unrelated applications are rerouted
  2. Guest connections gain an unexpected eligible transport or fail zone-specific security matching
  3. Private destinations become unreachable or traffic bypasses the intended encrypted overlay
  4. Brief congestion produces constant path changes and interruptive user sessions

Answer & Explanations

Correct answer: D

A.

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: A call center requires a stable failover algorithm that tolerates a few lost probes. The relevant consequence is: Brief congestion produces constant path changes and interruptive user sessions. The control that prevents it is: Set probe intervals, failure thresholds and recovery behavior to distinguish real link degradation from transient measurement noise.

B.

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 call center requires a stable failover algorithm that tolerates a few lost probes. The relevant consequence is: Brief congestion produces constant path changes and interruptive user sessions. The control that prevents it is: Set probe intervals, failure thresholds and recovery behavior to distinguish real link degradation from transient measurement noise.

C.

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 call center requires a stable failover algorithm that tolerates a few lost probes. The relevant consequence is: Brief congestion produces constant path changes and interruptive user sessions. The control that prevents it is: Set probe intervals, failure thresholds and recovery behavior to distinguish real link degradation from transient measurement noise.

D.

Brief congestion produces constant path changes and interruptive user sessions. This is the risk in the stated situation: A call center requires a stable failover algorithm that tolerates a few lost probes. The risky shortcut is: Configure immediate route switching on any single lost probe across all branch members. Prevent it by: Set probe intervals, failure thresholds and recovery behavior to distinguish real link degradation from transient measurement noise.

Question 221

A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds
  2. Create the required FortiGate security policy and source NAT for flows traversing the SD-WAN zone after defining membership and steering
  3. Use approved FortiManager templates and per-branch parameters to deploy FortiOS SD-WAN settings to the intended device groups with preview and rollback
  4. Check interface link, gateway ARP, SD-WAN member status, health-check results, route selection and security policy in that order before changing service priorities

Answer & Explanations

Correct answer: A

A.

Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds. The technical 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 stated condition is: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. Confirm the result by: Trigger a safe SLA breach and inspect both health-check state and actual matching SD-WAN service rule.

B.

This action is appropriate in a different case: An ecommerce branch sets the ideal SD-WAN service rule but its browser traffic still hits implicit deny. There, the reason is: SD-WAN path selection and firewall session authorization are separate stages, so a correct member decision does not imply policy allows or NAT translates the traffic. The current case is: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. The appropriate response is: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds.

C.

This action is appropriate in a different case: An MSP updates one regional template but accidentally targets all customer FortiGates. There, the reason is: Centralized templates reduce drift, but device-specific interfaces, gateway addresses and overlay identities must resolve correctly before installation. The current case is: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. The appropriate response 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 action is appropriate in a different case: A manufacturer cannot reach any destination through its new broadband circuit and assumes application steering is wrong. There, the reason is: A broken next-hop adjacency, failed SLA target, missing route and firewall deny can look like the same user outage but require different remedies. The current case is: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. The appropriate response is: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds.

Question 222

A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. A Fortinet administrator recommends: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds. Which technical process explanation best justifies that recommendation?

  1. A broken next-hop adjacency, failed SLA target, missing route and firewall deny can look like the same user outage but require different remedies
  2. A correctly configured health-check object does not change traffic steering unless the matching service uses its status under the chosen strategy
  3. SD-WAN zones group eligible interfaces for forwarding and can be referenced by policy; assigning a member to the wrong zone changes security and route eligibility
  4. An IPsec tunnel can be an SD-WAN member only while its secure overlay and underlying route are usable; a physical interface being up does not prove tunnel reachability

Answer & Explanations

Correct answer: B

A.

This principle explains a different technical intervention: Check interface link, gateway ARP, SD-WAN member status, health-check results, route selection and security policy in that order before changing service priorities. It applies to: A manufacturer cannot reach any destination through its new broadband circuit and assumes application steering is wrong. The actual case is: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. The mechanism relevant here is: A correctly configured health-check object does not change traffic steering unless the matching service uses its status under the chosen strategy.

B.

A correctly configured health-check object does not change traffic steering unless the matching service uses its status under the chosen strategy. That mechanism explains the decision: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds. In the reported situation: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. Confirmation requires: Trigger a safe SLA breach and inspect both health-check state and actual matching SD-WAN service rule.

C.

This principle explains a different technical intervention: Add eligible physical or tunnel WAN members to correctly named SD-WAN zones that match the organization network segmentation and security policy. It applies to: A hospital has separate private MPLS and public internet paths but a new member is added to the wrong zone. The actual case is: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. The mechanism relevant here is: A correctly configured health-check object does not change traffic steering unless the matching service uses its status under the chosen strategy.

D.

This principle explains a different technical intervention: Register the correct SD-WAN member interface type and tunnel dependency before selecting an overlay or internet underlay in a service rule. It applies to: A regional bank uses IPsec overlays above two ISPs and one overlay loses its encryption association. The actual case is: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. The mechanism relevant here is: A correctly configured health-check object does not change traffic steering unless the matching service uses its status under the chosen strategy.

Question 223

A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Check tunnel negotiation and a private-address probe while monitoring underlay and overlay member statuses
  2. Inspect neighbor resolution and an authorized next-hop ping from the correct interface
  3. Trigger a safe SLA breach and inspect both health-check state and actual matching SD-WAN service rule
  4. With both ISPs healthy verify the preferred member, then degrade it and inspect the approved alternative

Answer & Explanations

Correct answer: C

A.

This observation would verify a different remedy: Register the correct SD-WAN member interface type and tunnel dependency before selecting an overlay or internet underlay in a service rule. That remedy applies to: A regional bank uses IPsec overlays above two ISPs and one overlay loses its encryption association. The present condition is: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. To assess it, check: Trigger a safe SLA breach and inspect both health-check state and actual matching SD-WAN service rule.

B.

This observation would verify a different remedy: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency. That remedy applies to: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. The present condition is: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. To assess it, check: Trigger a safe SLA breach and inspect both health-check state and actual matching SD-WAN service rule.

C.

Trigger a safe SLA breach and inspect both health-check state and actual matching SD-WAN service rule. This check directly tests: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds. The underlying behavior is: A correctly configured health-check object does not change traffic steering unless the matching service uses its status under the chosen strategy. The case is: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule.

D.

This observation would verify a different remedy: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy. That remedy applies to: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. The present condition is: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. To assess it, check: Trigger a safe SLA breach and inspect both health-check state and actual matching SD-WAN service rule.

Question 224

A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. Which apparently convenient shortcut would most directly undermine the required control?

  1. Install a static host route for every cloud application to force path preference without considering dynamic DNS or health
  2. Set metered backup as the preferred route for all file replication merely because its measured latency is low
  3. Promise zero interruption for every existing VPN and payment session after introducing a second ISP
  4. Create a latency health check and assume all applications automatically honor it without binding a rule

Answer & Explanations

Correct answer: D

A.

This proposed shortcut concerns a separate case: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. The risk in this question concerns: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. Here the unsafe shortcut is: Create a latency health check and assume all applications automatically honor it without binding a rule. Use this response instead: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds.

B.

This proposed shortcut concerns a separate case: A remote branch has metered 5G and unlimited DSL but backups unexpectedly prefer 5G. The risk in this question concerns: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. Here the unsafe shortcut is: Create a latency health check and assume all applications automatically honor it without binding a rule. Use this response instead: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds.

C.

This proposed shortcut concerns a separate case: A payment terminal loses its existing bank session when the primary member fails but new sessions work. The risk in this question concerns: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. Here the unsafe shortcut is: Create a latency health check and assume all applications automatically honor it without binding a rule. Use this response instead: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds.

D.

Create a latency health check and assume all applications automatically honor it without binding a rule. This shortcut is unsafe for: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. The resulting failure can be: Poor paths remain selected for critical applications despite accurate SLA graphs. The safer response is: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds.

Question 225

A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. 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. Poor paths remain selected for critical applications despite accurate SLA graphs
  2. Transaction sessions reset despite valid alternate connectivity
  3. The smaller link saturates and user sessions experience avoidable loss
  4. One uplink cannot be used by the intended rule and failover stops working

Answer & Explanations

Correct answer: A

A.

Poor paths remain selected for critical applications despite accurate SLA graphs. This is the risk in the stated situation: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. 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.

B.

This failure concerns another scenario: A payment terminal loses its existing bank session when the primary member fails but new sessions work. In the stated case: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. 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.

C.

This failure concerns another scenario: A logistics firm sends backups over fiber and cellular but the cellular path becomes overloaded. In the stated case: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. 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: A branch firewall replacement has different WAN port numbering but retains the old template. In the stated case: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. 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 226

A retailer has an unused latency monitor because the POS service rule references another SLA. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency
  2. Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds
  3. Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy
  4. Record correct WAN transport costs or eligible member preferences and test cost-aware selection where supported by the configured strategy

Answer & Explanations

Correct answer: B

A.

This action is appropriate in a different case: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. There, the reason is: FortiGate must resolve the actual next hop to transmit packets; a member object alone does not manufacture an ISP gateway or a working layer-two path. The current case is: A retailer has an unused latency monitor because the POS service rule references another SLA. The appropriate response is: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds.

B.

Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds. The technical 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 stated condition is: A retailer has an unused latency monitor because the POS service rule references another SLA. Confirm the result by: Trigger a safe SLA breach and inspect both health-check state and actual matching SD-WAN service rule.

C.

This action is appropriate in a different case: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. There, the reason is: Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route. The current case is: A retailer has an unused latency monitor because the POS service rule references another SLA. The appropriate response 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 action is appropriate in a different case: A remote branch has metered 5G and unlimited DSL but backups unexpectedly prefer 5G. There, the reason is: A low metered LTE cost is operationally different from a high-capacity flat-rate circuit; choosing the cheapest path without quality criteria may violate application SLAs. The current case is: A retailer has an unused latency monitor because the POS service rule references another SLA. The appropriate response is: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds.

Question 227

A retailer has an unused latency monitor because the POS service rule references another SLA. A Fortinet administrator recommends: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds. Which technical process explanation best justifies that recommendation?

  1. A low metered LTE cost is operationally different from a high-capacity flat-rate circuit; choosing the cheapest path without quality criteria may violate application SLAs
  2. A path change may alter source NAT and return routing; a backup member being healthy does not guarantee an established TCP session survives without reconnection
  3. A correctly configured health-check object does not change traffic steering unless the matching service uses its status under the chosen strategy
  4. An SD-WAN rule may spread traffic across eligible members while a narrow member saturates if actual upstream capacity is not represented in the design

Answer & Explanations

Correct answer: C

A.

This principle explains a different technical intervention: Record correct WAN transport costs or eligible member preferences and test cost-aware selection where supported by the configured strategy. It applies to: A remote branch has metered 5G and unlimited DSL but backups unexpectedly prefer 5G. The actual case is: A retailer has an unused latency monitor because the POS service rule references another SLA. The mechanism relevant here is: A correctly configured health-check object does not change traffic steering unless the matching service uses its status under the chosen strategy.

B.

This principle explains a different technical intervention: Validate how new SD-WAN sessions use remaining healthy members and document the possible effect on existing stateful connections. It applies to: A payment terminal loses its existing bank session when the primary member fails but new sessions work. The actual case is: A retailer has an unused latency monitor because the POS service rule references another SLA. The mechanism relevant here is: A correctly configured health-check object does not change traffic steering unless the matching service uses its status under the chosen strategy.

C.

A correctly configured health-check object does not change traffic steering unless the matching service uses its status under the chosen strategy. That mechanism explains the decision: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds. In the reported situation: A retailer has an unused latency monitor because the POS service rule references another SLA. Confirmation requires: Trigger a safe SLA breach and inspect both health-check state and actual matching SD-WAN service rule.

D.

This principle explains a different technical intervention: Configure supported member bandwidth or traffic shaping expectations from actual ISP capacities before enabling load-sharing policies. It applies to: A logistics firm sends backups over fiber and cellular but the cellular path becomes overloaded. The actual case is: A retailer has an unused latency monitor because the POS service rule references another SLA. The mechanism relevant here is: A correctly configured health-check object does not change traffic steering unless the matching service uses its status under the chosen strategy.

Question 228

A retailer has an unused latency monitor because the POS service rule references another SLA. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Run safe concurrent test traffic and compare member throughput, packet drops and observed shaping behavior
  2. Compare before-and-after member inventory, active sessions and test route output on the affected device
  3. Inject controlled packet loss and verify member status crosses the threshold and restores at the expected point
  4. Trigger a safe SLA breach and inspect both health-check state and actual matching SD-WAN service rule

Answer & Explanations

Correct answer: D

A.

This observation would verify a different remedy: Configure supported member bandwidth or traffic shaping expectations from actual ISP capacities before enabling load-sharing policies. That remedy applies to: A logistics firm sends backups over fiber and cellular but the cellular path becomes overloaded. The present condition is: A retailer has an unused latency monitor because the POS service rule references another SLA. To assess it, check: Trigger a safe SLA breach and inspect both health-check state and actual matching SD-WAN service rule.

B.

This observation would verify a different remedy: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes. That remedy applies to: A branch firewall replacement has different WAN port numbering but retains the old template. The present condition is: A retailer has an unused latency monitor because the POS service rule references another SLA. To assess it, check: Trigger a safe SLA breach and inspect both health-check state and actual matching SD-WAN service rule.

C.

This observation would verify a different remedy: Define an SD-WAN performance SLA with justified packet loss tolerance and healthy probe targets for the critical application. That remedy applies to: A call center's voice quality deteriorates when ISP loss rises despite a green interface LED. The present condition is: A retailer has an unused latency monitor because the POS service rule references another SLA. To assess it, check: Trigger a safe SLA breach and inspect both health-check state and actual matching SD-WAN service rule.

D.

Trigger a safe SLA breach and inspect both health-check state and actual matching SD-WAN service rule. This check directly tests: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds. The underlying behavior is: A correctly configured health-check object does not change traffic steering unless the matching service uses its status under the chosen strategy. The case is: A retailer has an unused latency monitor because the POS service rule references another SLA.

Question 229

A retailer has an unused latency monitor because the POS service rule references another SLA. 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. Use a universal zero-loss threshold based on a single quiet sample for every WAN circuit
  3. Prefer a high-throughput geostationary link for interactive calls solely because it advertises more Mbps
  4. Evaluate only average RTT while ignoring rapidly varying packet arrival times for voice

Answer & Explanations

Correct answer: A

A.

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

B.

This proposed shortcut concerns a separate case: A call center's voice quality deteriorates when ISP loss rises despite a green interface LED. The risk in this question concerns: A retailer has an unused latency monitor because the POS service rule references another SLA. Here the unsafe shortcut is: Create a latency health check and assume all applications automatically honor it without binding a rule. Use this response instead: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds.

C.

This proposed shortcut concerns a separate case: A satellite backup has more capacity but causes long voice delays compared with local fiber. The risk in this question concerns: A retailer has an unused latency monitor because the POS service rule references another SLA. Here the unsafe shortcut is: Create a latency health check and assume all applications automatically honor it without binding a rule. Use this response instead: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds.

D.

This proposed shortcut concerns a separate case: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. The risk in this question concerns: A retailer has an unused latency monitor because the POS service rule references another SLA. Here the unsafe shortcut is: Create a latency health check and assume all applications automatically honor it without binding a rule. Use this response instead: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds.

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.

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