Fortinet NSE5_SSE_AD-7.6 Dumps
Fortinet NSE5_SSE_AD-7.6 Practice Test 18
Question 170
A medical telehealth application needs path changes when upstream loss exceeds its approved service target. Suppose the team follows this shortcut instead: Use a universal zero-loss threshold based on a single quiet sample for every WAN circuit. What is the most likely direct security or operational consequence?
Answer & Explanations
Correct answer: B
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 medical telehealth application needs path changes when upstream loss exceeds its approved service target. The relevant consequence is: Normal transient packet drops trigger unnecessary path flapping. The control that prevents it is: Define an SD-WAN performance SLA with justified packet loss tolerance and healthy probe targets for the critical application.
Normal transient packet drops trigger unnecessary path flapping. This is the risk in the stated situation: A medical telehealth application needs path changes when upstream loss exceeds its approved service target. The risky shortcut is: Use a universal zero-loss threshold based on a single quiet sample for every WAN circuit. Prevent it by: Define an SD-WAN performance SLA with justified packet loss tolerance and healthy probe targets for the critical application.
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 medical telehealth application needs path changes when upstream loss exceeds its approved service target. The relevant consequence is: Normal transient packet drops trigger unnecessary path flapping. The control that prevents it is: Define an SD-WAN performance SLA with justified packet loss tolerance and healthy probe targets for the critical application.
This failure concerns another scenario: A retailer adds two local broadband links but keeps its branch SaaS sessions pinned to a failed data-center backhaul. In the stated case: A medical telehealth application needs path changes when upstream loss exceeds its approved service target. The relevant consequence is: Normal transient packet drops trigger unnecessary path flapping. The control that prevents it is: Define an SD-WAN performance SLA with justified packet loss tolerance and healthy probe targets for the critical application.
Question 171
A satellite backup has more capacity but causes long voice delays compared with local fiber. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?
Answer & Explanations
Correct answer: C
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 satellite backup has more capacity but causes long voice delays compared with local fiber. The appropriate response is: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.
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 satellite backup has more capacity but causes long voice delays compared with local fiber. The appropriate response is: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.
Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule. The technical reason is: Latency measurements let a service rule reject a slow but reachable member; bandwidth by itself does not prove acceptable round-trip delay. The stated condition is: A satellite backup has more capacity but causes long voice delays compared with local fiber. Confirm the result by: Increase test-link delay deliberately and inspect SLA status plus selected route for a VoIP trial call.
This action is appropriate in a different case: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. There, the reason is: A correctly configured health-check object does not change traffic steering unless the matching service uses its status under the chosen strategy. The current case is: A satellite backup has more capacity but causes long voice delays compared with local fiber. The appropriate response is: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.
Question 172
A satellite backup has more capacity but causes long voice delays compared with local fiber. A Fortinet administrator recommends: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule. Which technical process explanation best justifies that recommendation?
Answer & Explanations
Correct answer: D
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 satellite backup has more capacity but causes long voice delays compared with local fiber. The mechanism relevant here is: Latency measurements let a service rule reject a slow but reachable member; bandwidth by itself does not prove acceptable round-trip delay.
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 satellite backup has more capacity but causes long voice delays compared with local fiber. The mechanism relevant here is: Latency measurements let a service rule reject a slow but reachable member; bandwidth by itself does not prove acceptable round-trip delay.
This principle explains a different technical intervention: Implement direct internet access through a FortiGate SD-WAN zone with explicit underlay members, firewall policy, NAT and health checks. It applies to: A retailer adds two local broadband links but keeps its branch SaaS sessions pinned to a failed data-center backhaul. The actual case is: A satellite backup has more capacity but causes long voice delays compared with local fiber. The mechanism relevant here is: Latency measurements let a service rule reject a slow but reachable member; bandwidth by itself does not prove acceptable round-trip delay.
Latency measurements let a service rule reject a slow but reachable member; bandwidth by itself does not prove acceptable round-trip delay. That mechanism explains the decision: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule. In the reported situation: A satellite backup has more capacity but causes long voice delays compared with local fiber. Confirmation requires: Increase test-link delay deliberately and inspect SLA status plus selected route for a VoIP trial call.
Question 173
A satellite backup has more capacity but causes long voice delays compared with local fiber. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?
Answer & Explanations
Correct answer: A
Increase test-link delay deliberately and inspect SLA status plus selected route for a VoIP trial call. This check directly tests: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule. The underlying behavior is: Latency measurements let a service rule reject a slow but reachable member; bandwidth by itself does not prove acceptable round-trip delay. The case is: A satellite backup has more capacity but causes long voice delays compared with local fiber.
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 satellite backup has more capacity but causes long voice delays compared with local fiber. To assess it, check: Increase test-link delay deliberately and inspect SLA status plus selected route for a VoIP trial call.
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 satellite backup has more capacity but causes long voice delays compared with local fiber. To assess it, check: Increase test-link delay deliberately and inspect SLA status plus selected route for a VoIP trial call.
This observation would verify a different remedy: Inventory LAN subnets, overlapping WAN addresses, default routes and SD-WAN policy dependencies before enrolling a FortiGate in a new branch design. That remedy applies to: A franchise duplicates the first store configuration and two stores unexpectedly advertise the same inside prefix. The present condition is: A satellite backup has more capacity but causes long voice delays compared with local fiber. To assess it, check: Increase test-link delay deliberately and inspect SLA status plus selected route for a VoIP trial call.
Question 174
A satellite backup has more capacity but causes long voice delays compared with local fiber. Which apparently convenient shortcut would most directly undermine the required control?
Answer & Explanations
Correct answer: B
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 satellite backup has more capacity but causes long voice delays compared with local fiber. Here the unsafe shortcut is: Prefer a high-throughput geostationary link for interactive calls solely because it advertises more Mbps. Use this response instead: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.
Prefer a high-throughput geostationary link for interactive calls solely because it advertises more Mbps. This shortcut is unsafe for: A satellite backup has more capacity but causes long voice delays compared with local fiber. The resulting failure can be: Voice and collaboration experience persistent delay while an alternative faster path exists. The safer response is: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.
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 satellite backup has more capacity but causes long voice delays compared with local fiber. Here the unsafe shortcut is: Prefer a high-throughput geostationary link for interactive calls solely because it advertises more Mbps. Use this response instead: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.
This proposed shortcut concerns a separate case: A school uses two static internet routes but its classroom video app suffers during upstream loss. The risk in this question concerns: A satellite backup has more capacity but causes long voice delays compared with local fiber. Here the unsafe shortcut is: Prefer a high-throughput geostationary link for interactive calls solely because it advertises more Mbps. Use this response instead: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.
Question 175
A satellite backup has more capacity but causes long voice delays compared with local fiber. 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?
Answer & Explanations
Correct answer: C
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 satellite backup has more capacity but causes long voice delays compared with local fiber. 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.
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 satellite backup has more capacity but causes long voice delays compared with local fiber. 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.
Voice and collaboration experience persistent delay while an alternative faster path exists. This is the risk in the stated situation: A satellite backup has more capacity but causes long voice delays compared with local fiber. 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.
This failure concerns another scenario: An MSP updates one regional template but accidentally targets all customer FortiGates. In the stated case: A satellite backup has more capacity but causes long voice delays compared with local fiber. 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.
Question 176
A trading firm needs latency-aware steering for its interactive remote desktop users. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?
Answer & Explanations
Correct answer: D
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 trading firm needs latency-aware steering for its interactive remote desktop users. The appropriate response is: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.
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 trading firm needs latency-aware steering for its interactive remote desktop users. The appropriate response is: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.
This action is appropriate in a different case: A manufacturer connects field offices to private ERP over IPsec but needs ordinary web access on the local ISP. There, the reason is: 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. The current case is: A trading firm needs latency-aware steering for its interactive remote desktop users. The appropriate response is: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.
Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule. The technical reason is: Latency measurements let a service rule reject a slow but reachable member; bandwidth by itself does not prove acceptable round-trip delay. The stated condition is: A trading firm needs latency-aware steering for its interactive remote desktop users. Confirm the result by: Increase test-link delay deliberately and inspect SLA status plus selected route for a VoIP trial call.
Question 177
A trading firm needs latency-aware steering for its interactive remote desktop users. A Fortinet administrator recommends: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule. Which technical process explanation best justifies that recommendation?
Answer & Explanations
Correct answer: A
Latency measurements let a service rule reject a slow but reachable member; bandwidth by itself does not prove acceptable round-trip delay. That mechanism explains the decision: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule. In the reported situation: A trading firm needs latency-aware steering for its interactive remote desktop users. Confirmation requires: Increase test-link delay deliberately and inspect SLA status plus selected route for a VoIP trial call.
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 trading firm needs latency-aware steering for its interactive remote desktop users. The mechanism relevant here is: Latency measurements let a service rule reject a slow but reachable member; bandwidth by itself does not prove acceptable round-trip delay.
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 trading firm needs latency-aware steering for its interactive remote desktop users. The mechanism relevant here is: Latency measurements let a service rule reject a slow but reachable member; bandwidth by itself does not prove acceptable round-trip delay.
This principle explains a different technical intervention: Create the required FortiGate security policy and source NAT for flows traversing the SD-WAN zone after defining membership and steering. It applies to: An ecommerce branch sets the ideal SD-WAN service rule but its browser traffic still hits implicit deny. The actual case is: A trading firm needs latency-aware steering for its interactive remote desktop users. The mechanism relevant here is: Latency measurements let a service rule reject a slow but reachable member; bandwidth by itself does not prove acceptable round-trip delay.
Question 178
A trading firm needs latency-aware steering for its interactive remote desktop users. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?
Answer & Explanations
Correct answer: B
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 trading firm needs latency-aware steering for its interactive remote desktop users. To assess it, check: Increase test-link delay deliberately and inspect SLA status plus selected route for a VoIP trial call.
Increase test-link delay deliberately and inspect SLA status plus selected route for a VoIP trial call. This check directly tests: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule. The underlying behavior is: Latency measurements let a service rule reject a slow but reachable member; bandwidth by itself does not prove acceptable round-trip delay. The case is: A trading firm needs latency-aware steering for its interactive remote desktop users.
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 trading firm needs latency-aware steering for its interactive remote desktop users. To assess it, check: Increase test-link delay deliberately and inspect SLA status plus selected route for a VoIP trial call.
This observation would verify a different remedy: Check interface link, gateway ARP, SD-WAN member status, health-check results, route selection and security policy in that order before changing service priorities. That remedy applies to: A manufacturer cannot reach any destination through its new broadband circuit and assumes application steering is wrong. The present condition is: A trading firm needs latency-aware steering for its interactive remote desktop users. To assess it, check: Increase test-link delay deliberately and inspect SLA status plus selected route for a VoIP trial call.
Question 179
A trading firm needs latency-aware steering for its interactive remote desktop users. Which apparently convenient shortcut would most directly undermine the required control?
Answer & Explanations
Correct answer: C
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 trading firm needs latency-aware steering for its interactive remote desktop users. Here the unsafe shortcut is: Prefer a high-throughput geostationary link for interactive calls solely because it advertises more Mbps. Use this response instead: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.
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 trading firm needs latency-aware steering for its interactive remote desktop users. Here the unsafe shortcut is: Prefer a high-throughput geostationary link for interactive calls solely because it advertises more Mbps. Use this response instead: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.
Prefer a high-throughput geostationary link for interactive calls solely because it advertises more Mbps. This shortcut is unsafe for: A trading firm needs latency-aware steering for its interactive remote desktop users. The resulting failure can be: Voice and collaboration experience persistent delay while an alternative faster path exists. The safer response is: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.
This proposed shortcut concerns a separate case: A regional bank uses IPsec overlays above two ISPs and one overlay loses its encryption association. The risk in this question concerns: A trading firm needs latency-aware steering for its interactive remote desktop users. Here the unsafe shortcut is: Prefer a high-throughput geostationary link for interactive calls solely because it advertises more Mbps. Use this response instead: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule.
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?
Answer & Explanations
Correct answer: D
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.
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.
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.
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.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests
- Fortinet NSE5_SSE_AD-7.6 Practice Test 16 - 10 Questions (Last Reviewed 05-Nov-2026)
- Fortinet NSE5_SSE_AD-7.6 Practice Test 17 - 10 Questions (Last Reviewed 04-Nov-2026)
- Fortinet NSE5_SSE_AD-7.6 Practice Test 18 - 10 Questions (Last Reviewed 03-Nov-2026)
- Fortinet NSE5_SSE_AD-7.6 Practice Test 19 - 10 Questions (Last Reviewed 02-Nov-2026)
- Fortinet NSE5_SSE_AD-7.6 Practice Test 20 - 10 Questions (Last Reviewed 01-Nov-2026)