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 19

Question 180

A trading firm needs latency-aware steering for its interactive remote desktop users. Suppose the team follows this shortcut instead: Prefer a high-throughput geostationary link for interactive calls solely because it advertises more Mbps. What is the most likely direct security or operational consequence?

  1. Private destinations become unreachable or traffic bypasses the intended encrypted overlay
  2. Secondary-link traffic fails before reaching the internet even though member selection succeeds
  3. Traffic locks to obsolete destinations and fails when the ISP or SaaS endpoint changes
  4. Voice and collaboration experience persistent delay while an alternative faster path exists

Answer & Explanations

Correct answer: D

A.

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 trading firm needs latency-aware steering for its interactive remote desktop users. The relevant consequence is: Voice and collaboration experience persistent delay while an alternative faster path exists. The control that prevents it is: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.

B.

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 trading firm needs latency-aware steering for its interactive remote desktop users. The relevant consequence is: Voice and collaboration experience persistent delay while an alternative faster path exists. The control that prevents it is: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.

C.

This failure concerns another scenario: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. In the stated case: A trading firm needs latency-aware steering for its interactive remote desktop users. The relevant consequence is: Voice and collaboration experience persistent delay while an alternative faster path exists. The control that prevents it is: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.

D.

Voice and collaboration experience persistent delay while an alternative faster path exists. This is the risk in the stated situation: A trading firm needs latency-aware steering for its interactive remote desktop users. The risky shortcut is: Prefer a high-throughput geostationary link for interactive calls solely because it advertises more Mbps. Prevent it by: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.

Question 181

A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. 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. Check interface link, gateway ARP, SD-WAN member status, health-check results, route selection and security policy in that order before changing service priorities
  3. Add eligible physical or tunnel WAN members to correctly named SD-WAN zones that match the organization network segmentation and security policy
  4. Register the correct SD-WAN member interface type and tunnel dependency before selecting an overlay or internet underlay in a service rule

Answer & Explanations

Correct answer: A

A.

Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member. The technical reason is: Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable. The stated condition is: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. Confirm the result by: Introduce bounded variable delay in a lab and confirm SLA breach, rule behavior and audio recovery.

B.

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 hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. The appropriate response is: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

C.

This action is appropriate in a different case: A hospital has separate private MPLS and public internet paths but a new member is added to the wrong zone. There, the reason is: 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. The current case is: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. The appropriate response is: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

D.

This action is appropriate in a different case: A regional bank uses IPsec overlays above two ISPs and one overlay loses its encryption association. There, the reason is: 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. The current case is: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. The appropriate response is: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

Question 182

A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. A Fortinet administrator recommends: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member. Which technical process explanation best justifies that recommendation?

  1. 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
  2. Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable
  3. 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
  4. Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route

Answer & Explanations

Correct answer: B

A.

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 hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. The mechanism relevant here is: Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable.

B.

Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable. That mechanism explains the decision: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member. In the reported situation: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. Confirmation requires: Introduce bounded variable delay in a lab and confirm SLA breach, rule behavior and audio recovery.

C.

This principle explains a different technical intervention: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency. It applies to: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. The actual case is: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. The mechanism relevant here is: Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable.

D.

This principle explains a different technical intervention: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy. It applies to: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. The actual case is: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. The mechanism relevant here is: Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable.

Question 183

A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. With both ISPs healthy verify the preferred member, then degrade it and inspect the approved alternative
  2. Send one business-critical and one bulk test flow and inspect path, measured SLA and intended cost preference
  3. Introduce bounded variable delay in a lab and confirm SLA breach, rule behavior and audio recovery
  4. Simulate authorized loss of the primary ISP and record both new connection success and established application behavior

Answer & Explanations

Correct answer: C

A.

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 hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. To assess it, check: Introduce bounded variable delay in a lab and confirm SLA breach, rule behavior and audio recovery.

B.

This observation would verify a different remedy: Record correct WAN transport costs or eligible member preferences and test cost-aware selection where supported by the configured strategy. That remedy applies to: A remote branch has metered 5G and unlimited DSL but backups unexpectedly prefer 5G. The present condition is: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. To assess it, check: Introduce bounded variable delay in a lab and confirm SLA breach, rule behavior and audio recovery.

C.

Introduce bounded variable delay in a lab and confirm SLA breach, rule behavior and audio recovery. This check directly tests: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member. The underlying behavior is: Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable. The case is: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP.

D.

This observation would verify a different remedy: Validate how new SD-WAN sessions use remaining healthy members and document the possible effect on existing stateful connections. That remedy applies to: A payment terminal loses its existing bank session when the primary member fails but new sessions work. The present condition is: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. To assess it, check: Introduce bounded variable delay in a lab and confirm SLA breach, rule behavior and audio recovery.

Question 184

A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. Which apparently convenient shortcut would most directly undermine the required control?

  1. Promise zero interruption for every existing VPN and payment session after introducing a second ISP
  2. Treat a 20 Mbps cellular path as equivalent to a 500 Mbps fiber service in a bulk transfer strategy
  3. Assume a cloned FortiGate appliance retains identical member mappings after interface hardware changes
  4. Evaluate only average RTT while ignoring rapidly varying packet arrival times for voice

Answer & Explanations

Correct answer: D

A.

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 hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. Here the unsafe shortcut is: Evaluate only average RTT while ignoring rapidly varying packet arrival times for voice. Use this response instead: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

B.

This proposed shortcut concerns a separate case: A logistics firm sends backups over fiber and cellular but the cellular path becomes overloaded. The risk in this question concerns: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. Here the unsafe shortcut is: Evaluate only average RTT while ignoring rapidly varying packet arrival times for voice. Use this response instead: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

C.

This proposed shortcut concerns a separate case: A branch firewall replacement has different WAN port numbering but retains the old template. The risk in this question concerns: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. Here the unsafe shortcut is: Evaluate only average RTT while ignoring rapidly varying packet arrival times for voice. Use this response instead: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

D.

Evaluate only average RTT while ignoring rapidly varying packet arrival times for voice. This shortcut is unsafe for: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. The resulting failure can be: Conference calls stutter despite an apparently normal average latency graph. The safer response is: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

Question 185

A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. 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. Conference calls stutter despite an apparently normal average latency graph
  2. One uplink cannot be used by the intended rule and failover stops working
  3. Normal transient packet drops trigger unnecessary path flapping
  4. Voice and collaboration experience persistent delay while an alternative faster path exists

Answer & Explanations

Correct answer: A

A.

Conference calls stutter despite an apparently normal average latency graph. This is the risk in the stated situation: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. 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.

B.

This failure concerns another scenario: A branch firewall replacement has different WAN port numbering but retains the old template. In the stated case: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. 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.

C.

This failure concerns another scenario: A call center's voice quality deteriorates when ISP loss rises despite a green interface LED. In the stated case: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. 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 satellite backup has more capacity but causes long voice delays compared with local fiber. In the stated case: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. 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 186

A customer support center needs to distinguish jitter problems from a simple throughput shortage. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Record correct WAN transport costs or eligible member preferences and test cost-aware selection where supported by the configured strategy
  2. Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member
  3. Validate how new SD-WAN sessions use remaining healthy members and document the possible effect on existing stateful connections
  4. Configure supported member bandwidth or traffic shaping expectations from actual ISP capacities before enabling load-sharing policies

Answer & Explanations

Correct answer: B

A.

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 customer support center needs to distinguish jitter problems from a simple throughput shortage. The appropriate response is: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

B.

Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member. The technical reason is: Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable. The stated condition is: A customer support center needs to distinguish jitter problems from a simple throughput shortage. Confirm the result by: Introduce bounded variable delay in a lab and confirm SLA breach, rule behavior and audio recovery.

C.

This action is appropriate in a different case: A payment terminal loses its existing bank session when the primary member fails but new sessions work. There, the reason is: 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. The current case is: A customer support center needs to distinguish jitter problems from a simple throughput shortage. The appropriate response is: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

D.

This action is appropriate in a different case: A logistics firm sends backups over fiber and cellular but the cellular path becomes overloaded. There, the reason is: 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. The current case is: A customer support center needs to distinguish jitter problems from a simple throughput shortage. The appropriate response is: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

Question 187

A customer support center needs to distinguish jitter problems from a simple throughput shortage. A Fortinet administrator recommends: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member. Which technical process explanation best justifies that recommendation?

  1. 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
  2. An interface reference that changed during provisioning can leave a logically valid SD-WAN rule pointing at the wrong member
  3. Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable
  4. Link loss measured through an active health check can indicate poor transport quality before the physical interface goes down

Answer & Explanations

Correct answer: C

A.

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 customer support center needs to distinguish jitter problems from a simple throughput shortage. The mechanism relevant here is: Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable.

B.

This principle explains a different technical intervention: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes. It applies to: A branch firewall replacement has different WAN port numbering but retains the old template. The actual case is: A customer support center needs to distinguish jitter problems from a simple throughput shortage. The mechanism relevant here is: Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable.

C.

Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable. That mechanism explains the decision: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member. In the reported situation: A customer support center needs to distinguish jitter problems from a simple throughput shortage. Confirmation requires: Introduce bounded variable delay in a lab and confirm SLA breach, rule behavior and audio recovery.

D.

This principle explains a different technical intervention: Define an SD-WAN performance SLA with justified packet loss tolerance and healthy probe targets for the critical application. It applies to: A call center's voice quality deteriorates when ISP loss rises despite a green interface LED. The actual case is: A customer support center needs to distinguish jitter problems from a simple throughput shortage. The mechanism relevant here is: Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable.

Question 188

A customer support center needs to distinguish jitter problems from a simple throughput shortage. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Inject controlled packet loss and verify member status crosses the threshold and restores at the expected point
  2. Increase test-link delay deliberately and inspect SLA status plus selected route for a VoIP trial call
  3. Compare probe response with actual protected application reachability using one permitted route and a second reference target
  4. Introduce bounded variable delay in a lab and confirm SLA breach, rule behavior and audio recovery

Answer & Explanations

Correct answer: D

A.

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 customer support center needs to distinguish jitter problems from a simple throughput shortage. To assess it, check: Introduce bounded variable delay in a lab and confirm SLA breach, rule behavior and audio recovery.

B.

This observation would verify a different remedy: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule. That remedy applies to: A satellite backup has more capacity but causes long voice delays compared with local fiber. The present condition is: A customer support center needs to distinguish jitter problems from a simple throughput shortage. To assess it, check: Introduce bounded variable delay in a lab and confirm SLA breach, rule behavior and audio recovery.

C.

This observation would verify a different remedy: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. That remedy applies to: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The present condition is: A customer support center needs to distinguish jitter problems from a simple throughput shortage. To assess it, check: Introduce bounded variable delay in a lab and confirm SLA breach, rule behavior and audio recovery.

D.

Introduce bounded variable delay in a lab and confirm SLA breach, rule behavior and audio recovery. This check directly tests: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member. The underlying behavior is: Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable. The case is: A customer support center needs to distinguish jitter problems from a simple throughput shortage.

Question 189

A customer support center needs to distinguish jitter problems from a simple throughput shortage. Which apparently convenient shortcut would most directly undermine the required control?

  1. Evaluate only average RTT while ignoring rapidly varying packet arrival times for voice
  2. Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service
  3. Disable a working backup circuit completely because it fails a strict voice SLA even though backups tolerate its latency
  4. Configure immediate route switching on any single lost probe across all branch members

Answer & Explanations

Correct answer: A

A.

Evaluate only average RTT while ignoring rapidly varying packet arrival times for voice. This shortcut is unsafe for: A customer support center needs to distinguish jitter problems from a simple throughput shortage. The resulting failure can be: Conference calls stutter despite an apparently normal average latency graph. The safer response is: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

B.

This proposed shortcut concerns a separate case: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The risk in this question concerns: A customer support center needs to distinguish jitter problems from a simple throughput shortage. Here the unsafe shortcut is: Evaluate only average RTT while ignoring rapidly varying packet arrival times for voice. Use this response instead: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

C.

This proposed shortcut concerns a separate case: An office has one slow LTE link suitable for email but unsuitable for voice. The risk in this question concerns: A customer support center needs to distinguish jitter problems from a simple throughput shortage. Here the unsafe shortcut is: Evaluate only average RTT while ignoring rapidly varying packet arrival times for voice. Use this response instead: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

D.

This proposed shortcut concerns a separate case: A clinic's WAN swaps every minute when one ping is delayed. The risk in this question concerns: A customer support center needs to distinguish jitter problems from a simple throughput shortage. Here the unsafe shortcut is: Evaluate only average RTT while ignoring rapidly varying packet arrival times for voice. Use this response instead: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.

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.

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