Fortinet NSE5_SSE_AD-7.6 Dumps
Fortinet NSE5_SSE_AD-7.6 Practice Test 20
Question 190
A customer support center needs to distinguish jitter problems from a simple throughput shortage. Suppose the team follows this shortcut instead: Evaluate only average RTT while ignoring rapidly varying packet arrival times for voice. What is the most likely direct security or operational consequence?
Answer & Explanations
Correct answer: B
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.
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.
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.
This failure concerns another scenario: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. In the stated case: A customer support center needs to distinguish jitter problems from a simple throughput shortage. The relevant consequence is: Conference calls stutter despite an apparently normal average latency graph. The control that prevents it is: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member.
Question 191
A hospital's encrypted private circuit probes an unrelated public address and is marked down. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?
Answer & Explanations
Correct answer: C
This action is appropriate in a different case: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. There, the reason is: Variation in packet delay damages interactive audio even when average latency and link-up state are acceptable. The current case is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The appropriate response is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
This action is appropriate in a different case: An office has one slow LTE link suitable for email but unsuitable for voice. There, the reason is: An active but degraded circuit may continue carrying other approved traffic, while a truly dead path should not be selected for any required service. The current case is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The appropriate response is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. The technical reason is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay. The stated condition is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. Confirm the result by: Compare probe response with actual protected application reachability using one permitted route and a second reference target.
This action is appropriate in a different case: A clinic's WAN swaps every minute when one ping is delayed. There, the reason is: Too-aggressive probes or thresholds can cause repeated SD-WAN path changes, while slow detection delays recovery after genuine failure. The current case is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The appropriate response is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
Question 192
A hospital's encrypted private circuit probes an unrelated public address and is marked down. A Fortinet administrator recommends: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. Which technical process explanation best justifies that recommendation?
Answer & Explanations
Correct answer: D
This principle explains a different technical intervention: Set probe intervals, failure thresholds and recovery behavior to distinguish real link degradation from transient measurement noise. It applies to: A clinic's WAN swaps every minute when one ping is delayed. The actual case is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The mechanism relevant here is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay.
This principle explains a different technical intervention: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds. It applies to: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. The actual case is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The mechanism relevant here is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay.
This principle explains a different technical intervention: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered. It applies to: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The actual case is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The mechanism relevant here is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay.
An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay. That mechanism explains the decision: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. In the reported situation: A hospital's encrypted private circuit probes an unrelated public address and is marked down. Confirmation requires: Compare probe response with actual protected application reachability using one permitted route and a second reference target.
Question 193
A hospital's encrypted private circuit probes an unrelated public address and is marked down. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?
Answer & Explanations
Correct answer: A
Compare probe response with actual protected application reachability using one permitted route and a second reference target. This check directly tests: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. The underlying behavior is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay. The case is: A hospital's encrypted private circuit probes an unrelated public address and is marked down.
This observation would verify a different remedy: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered. That remedy applies to: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The present condition is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. To assess it, check: Compare probe response with actual protected application reachability using one permitted route and a second reference target.
This observation would verify a different remedy: Implement direct internet access through a FortiGate SD-WAN zone with explicit underlay members, firewall policy, NAT and health checks. That remedy applies to: A retailer adds two local broadband links but keeps its branch SaaS sessions pinned to a failed data-center backhaul. The present condition is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. To assess it, check: Compare probe response with actual protected application reachability using one permitted route and a second reference target.
This observation would verify a different remedy: Create a baseline of SD-WAN member status, aggregate traffic, packet loss and eligible route reachability before tuning steering rules. That remedy applies to: A logistics branch reports intermittent internet loss although both ISP ports show up. The present condition is: A hospital's encrypted private circuit probes an unrelated public address and is marked down. To assess it, check: Compare probe response with actual protected application reachability using one permitted route and a second reference target.
Question 194
A hospital's encrypted private circuit probes an unrelated public address and is marked down. Which apparently convenient shortcut would most directly undermine the required control?
Answer & Explanations
Correct answer: B
This proposed shortcut concerns a separate case: A logistics branch reports intermittent internet loss although both ISP ports show up. The risk in this question concerns: A hospital's encrypted private circuit probes an unrelated public address and is marked down. Here the unsafe shortcut is: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. Use this response instead: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. This shortcut is unsafe for: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The resulting failure can be: The private overlay is marked unhealthy even while its business service remains reachable. The safer response is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
This proposed shortcut concerns a separate case: A franchise duplicates the first store configuration and two stores unexpectedly advertise the same inside prefix. The risk in this question concerns: A hospital's encrypted private circuit probes an unrelated public address and is marked down. Here the unsafe shortcut is: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. Use this response instead: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
This proposed shortcut concerns a separate case: A manufacturer connects field offices to private ERP over IPsec but needs ordinary web access on the local ISP. The risk in this question concerns: A hospital's encrypted private circuit probes an unrelated public address and is marked down. Here the unsafe shortcut is: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. Use this response instead: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
Question 195
A hospital's encrypted private circuit probes an unrelated public address and is marked down. Suppose the team follows this shortcut instead: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. What is the most likely direct security or operational consequence?
Answer & Explanations
Correct answer: C
This failure concerns another scenario: A manufacturer connects field offices to private ERP over IPsec but needs ordinary web access on the local ISP. In the stated case: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The relevant consequence is: The private overlay is marked unhealthy even while its business service remains reachable. The control that prevents it is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
This failure concerns another scenario: A school uses two static internet routes but its classroom video app suffers during upstream loss. In the stated case: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The relevant consequence is: The private overlay is marked unhealthy even while its business service remains reachable. The control that prevents it is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
The private overlay is marked unhealthy even while its business service remains reachable. This is the risk in the stated situation: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The risky shortcut is: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. Prevent it by: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
This failure concerns another scenario: An ecommerce branch sets the ideal SD-WAN service rule but its browser traffic still hits implicit deny. In the stated case: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The relevant consequence is: The private overlay is marked unhealthy even while its business service remains reachable. The control that prevents it is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
Question 196
A retailer has intermittent false failover because its chosen SLA target rate-limits probes. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?
Answer & Explanations
Correct answer: D
This action is appropriate in a different case: A retailer adds two local broadband links but keeps its branch SaaS sessions pinned to a failed data-center backhaul. There, the reason is: A direct internet access design keeps eligible branch traffic local while SD-WAN selects healthy internet members; defining the zone alone does not grant traffic or translate private addresses. The current case is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The appropriate response is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
This action is appropriate in a different case: A logistics branch reports intermittent internet loss although both ISP ports show up. There, the reason is: Member health and application path performance can differ from interface link state; an Ethernet up indicator alone cannot prove internet reachability or acceptable quality. The current case is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The appropriate response is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
This action is appropriate in a different case: A franchise duplicates the first store configuration and two stores unexpectedly advertise the same inside prefix. There, the reason is: SD-WAN forwarding depends on valid routed underlay interfaces and correct address scope; duplicate subnets or stale routes can prevent return traffic even with acceptable link health. The current case is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The appropriate response is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. The technical reason is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay. The stated condition is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. Confirm the result by: Compare probe response with actual protected application reachability using one permitted route and a second reference target.
Question 197
A retailer has intermittent false failover because its chosen SLA target rate-limits probes. A Fortinet administrator recommends: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. Which technical process explanation best justifies that recommendation?
Answer & Explanations
Correct answer: A
An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay. That mechanism explains the decision: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. In the reported situation: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. Confirmation requires: Compare probe response with actual protected application reachability using one permitted route and a second reference target.
This principle explains a different technical intervention: Inventory LAN subnets, overlapping WAN addresses, default routes and SD-WAN policy dependencies before enrolling a FortiGate in a new branch design. It applies to: A franchise duplicates the first store configuration and two stores unexpectedly advertise the same inside prefix. The actual case is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The mechanism relevant here is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay.
This principle explains a different technical intervention: Define which branch destinations use secure overlay paths and which use local internet egress, then test scoped policies for both groups. It applies to: A manufacturer connects field offices to private ERP over IPsec but needs ordinary web access on the local ISP. The actual case is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The mechanism relevant here is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay.
This principle explains a different technical intervention: Add WAN interfaces as SD-WAN members in the intended zone and use eligible routes and SD-WAN services instead of pretending a pair of static defaults offers application-aware steering. It applies to: A school uses two static internet routes but its classroom video app suffers during upstream loss. The actual case is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The mechanism relevant here is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay.
Question 198
A retailer has intermittent false failover because its chosen SLA target rate-limits probes. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?
Answer & Explanations
Correct answer: B
This observation would verify a different remedy: Add WAN interfaces as SD-WAN members in the intended zone and use eligible routes and SD-WAN services instead of pretending a pair of static defaults offers application-aware steering. That remedy applies to: A school uses two static internet routes but its classroom video app suffers during upstream loss. The present condition is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. To assess it, check: Compare probe response with actual protected application reachability using one permitted route and a second reference target.
Compare probe response with actual protected application reachability using one permitted route and a second reference target. This check directly tests: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service. The underlying behavior is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay. The case is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes.
This observation would verify a different remedy: Create the required FortiGate security policy and source NAT for flows traversing the SD-WAN zone after defining membership and steering. That remedy applies to: An ecommerce branch sets the ideal SD-WAN service rule but its browser traffic still hits implicit deny. The present condition is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. To assess it, check: Compare probe response with actual protected application reachability using one permitted route and a second reference target.
This observation would verify a different remedy: Use approved FortiManager templates and per-branch parameters to deploy FortiOS SD-WAN settings to the intended device groups with preview and rollback. That remedy applies to: An MSP updates one regional template but accidentally targets all customer FortiGates. The present condition is: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. To assess it, check: Compare probe response with actual protected application reachability using one permitted route and a second reference target.
Question 199
A retailer has intermittent false failover because its chosen SLA target rate-limits probes. Which apparently convenient shortcut would most directly undermine the required control?
Answer & Explanations
Correct answer: C
This proposed shortcut concerns a separate case: An MSP updates one regional template but accidentally targets all customer FortiGates. The risk in this question concerns: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. Here the unsafe shortcut is: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. Use this response instead: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
This proposed shortcut concerns a separate case: A manufacturer cannot reach any destination through its new broadband circuit and assumes application steering is wrong. The risk in this question concerns: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. Here the unsafe shortcut is: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. Use this response instead: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. This shortcut is unsafe for: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The resulting failure can be: The private overlay is marked unhealthy even while its business service remains reachable. The safer response is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
This proposed shortcut concerns a separate case: A hospital has separate private MPLS and public internet paths but a new member is added to the wrong zone. The risk in this question concerns: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. Here the unsafe shortcut is: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. Use this response instead: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
Question 200
A retailer has intermittent false failover because its chosen SLA target rate-limits probes. Suppose the team follows this shortcut instead: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. What is the most likely direct security or operational consequence?
Answer & Explanations
Correct answer: D
This failure concerns another scenario: A hospital has separate private MPLS and public internet paths but a new member is added to the wrong zone. In the stated case: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The relevant consequence is: The private overlay is marked unhealthy even while its business service remains reachable. The control that prevents it is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
This failure concerns another scenario: A regional bank uses IPsec overlays above two ISPs and one overlay loses its encryption association. In the stated case: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The relevant consequence is: The private overlay is marked unhealthy even while its business service remains reachable. The control that prevents it is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
This failure concerns another scenario: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. In the stated case: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The relevant consequence is: The private overlay is marked unhealthy even while its business service remains reachable. The control that prevents it is: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
The private overlay is marked unhealthy even while its business service remains reachable. This is the risk in the stated situation: A retailer has intermittent false failover because its chosen SLA target rate-limits probes. The risky shortcut is: Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service. Prevent it by: Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests
- 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)
- Fortinet NSE5_SSE_AD-7.6 Practice Test 21 - 10 Questions (Last Reviewed 31-Oct-2026)
- Fortinet NSE5_SSE_AD-7.6 Practice Test 22 - 10 Questions (Last Reviewed 30-Oct-2026)