Fortinet NSE5_SSE_AD-7.6 Dumps
Fortinet NSE5_SSE_AD-7.6 Practice Test 39
Question 380
A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. Suppose the team follows this shortcut instead: Lower an unrelated backup route distance until it overrides all specific private paths just to improve internet performance. What is the most likely direct security or operational consequence?
Answer & Explanations
Correct answer: D
This failure concerns another scenario: A branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. In the stated case: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. The relevant consequence is: Critical internal destinations use an unsuitable backup route and stop responding. The control that prevents it is: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
This failure concerns another scenario: A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. In the stated case: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. The relevant consequence is: Critical internal destinations use an unsuitable backup route and stop responding. The control that prevents it is: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
This failure concerns another scenario: A multinational updates branch SD-WAN routes and its private billing subnet stops responding. In the stated case: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. The relevant consequence is: Critical internal destinations use an unsuitable backup route and stop responding. The control that prevents it is: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
Critical internal destinations use an unsuitable backup route and stop responding. This is the risk in the stated situation: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. The risky shortcut is: Lower an unrelated backup route distance until it overrides all specific private paths just to improve internet performance. Prevent it by: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
Question 381
A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?
Answer & Explanations
Correct answer: A
Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback. The technical reason is: A blackhole for known private prefixes can prevent accidental leakage if the protected route disappears; it should never override a healthy more specific route. The stated condition is: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. Confirm the result by: Disable a test private tunnel and confirm affected private traffic drops locally while public web continues.
This action is appropriate in a different case: A hospital confirms its patient portal selects the correct WAN yet access is still denied. There, the reason is: SD-WAN rules select a path for matched sessions, whereas firewall policy decides access and NAT supplies routable addresses. The current case is: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. The appropriate response is: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
This action is appropriate in a different case: A call center changes a voice service rule but cannot show that any call selected the new ISP. There, the reason is: A rule that exists in configuration is not evidence that an observed flow matches it, especially when policy precedence or application identification differs. The current case is: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. The appropriate response is: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
This action is appropriate in a different case: A branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. There, the reason is: A service rule cannot forward a flow if routing lacks a usable egress path; the presence of two ISP interfaces does not create a functioning default route automatically. The current case is: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. The appropriate response is: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
Question 382
A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. A Fortinet administrator recommends: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback. Which technical process explanation best justifies that recommendation?
Answer & Explanations
Correct answer: B
This principle explains a different technical intervention: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members. It applies to: A branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. The actual case is: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. The mechanism relevant here is: A blackhole for known private prefixes can prevent accidental leakage if the protected route disappears; it should never override a healthy more specific route.
A blackhole for known private prefixes can prevent accidental leakage if the protected route disappears; it should never override a healthy more specific route. That mechanism explains the decision: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback. In the reported situation: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. Confirmation requires: Disable a test private tunnel and confirm affected private traffic drops locally while public web continues.
This principle explains a different technical intervention: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior. It applies to: A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. The actual case is: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. The mechanism relevant here is: A blackhole for known private prefixes can prevent accidental leakage if the protected route disappears; it should never override a healthy more specific route.
This principle explains a different technical intervention: Install or learn appropriate protected destination routes through approved IPsec or private SD-WAN members separately from the internet default. It applies to: A multinational updates branch SD-WAN routes and its private billing subnet stops responding. The actual case is: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. The mechanism relevant here is: A blackhole for known private prefixes can prevent accidental leakage if the protected route disappears; it should never override a healthy more specific route.
Question 383
A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?
Answer & Explanations
Correct answer: C
This observation would verify a different remedy: Install or learn appropriate protected destination routes through approved IPsec or private SD-WAN members separately from the internet default. That remedy applies to: A multinational updates branch SD-WAN routes and its private billing subnet stops responding. The present condition is: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. To assess it, check: Disable a test private tunnel and confirm affected private traffic drops locally while public web continues.
This observation would verify a different remedy: Use approved BGP route advertisements and learned private prefixes on the intended SD-WAN overlay, validating next-hop and route preference. That remedy applies to: A chain retailer uses BGP over IPsec overlays and needs new store prefixes learned without manual static entries. The present condition is: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. To assess it, check: Disable a test private tunnel and confirm affected private traffic drops locally while public web continues.
Disable a test private tunnel and confirm affected private traffic drops locally while public web continues. This check directly tests: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback. The underlying behavior is: A blackhole for known private prefixes can prevent accidental leakage if the protected route disappears; it should never override a healthy more specific route. The case is: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband.
This observation would verify a different remedy: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference. That remedy applies to: A factory has duplicate defaults from DHCP and BGP with unexpected route preference. The present condition is: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. To assess it, check: Disable a test private tunnel and confirm affected private traffic drops locally while public web continues.
Question 384
A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. Which apparently convenient shortcut would most directly undermine the required control?
Answer & Explanations
Correct answer: D
This proposed shortcut concerns a separate case: A factory has duplicate defaults from DHCP and BGP with unexpected route preference. The risk in this question concerns: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. Here the unsafe shortcut is: Send protected RFC1918 traffic through ordinary public internet as a fallback whenever a tunnel fails. Use this response instead: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
This proposed shortcut concerns a separate case: A payment provider only permits the original source IP and rejects flows during ISP failover. The risk in this question concerns: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. Here the unsafe shortcut is: Send protected RFC1918 traffic through ordinary public internet as a fallback whenever a tunnel fails. Use this response instead: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
This proposed shortcut concerns a separate case: A bank's private finance rule never matches because a generic internet SD-WAN rule is higher in the list. The risk in this question concerns: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. Here the unsafe shortcut is: Send protected RFC1918 traffic through ordinary public internet as a fallback whenever a tunnel fails. Use this response instead: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
Send protected RFC1918 traffic through ordinary public internet as a fallback whenever a tunnel fails. This shortcut is unsafe for: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. The resulting failure can be: Private flows leak into an external transport and fail or expose inappropriate metadata. The safer response is: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
Question 385
A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. Suppose the team follows this shortcut instead: Send protected RFC1918 traffic through ordinary public internet as a fallback whenever a tunnel fails. What is the most likely direct security or operational consequence?
Answer & Explanations
Correct answer: A
Private flows leak into an external transport and fail or expose inappropriate metadata. This is the risk in the stated situation: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. The risky shortcut is: Send protected RFC1918 traffic through ordinary public internet as a fallback whenever a tunnel fails. Prevent it by: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
This failure concerns another scenario: A bank's private finance rule never matches because a generic internet SD-WAN rule is higher in the list. In the stated case: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. The relevant consequence is: Private flows leak into an external transport and fail or expose inappropriate metadata. The control that prevents it is: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
This failure concerns another scenario: A hospital's telemedicine sessions remain on high-loss broadband because the rule ignores health SLA. In the stated case: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. The relevant consequence is: Private flows leak into an external transport and fail or expose inappropriate metadata. The control that prevents it is: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
This failure concerns another scenario: A hospital needs its radiology systems on a private WAN while guest devices use DIA. In the stated case: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. The relevant consequence is: Private flows leak into an external transport and fail or expose inappropriate metadata. The control that prevents it is: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
Question 386
A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?
Answer & Explanations
Correct answer: B
This action is appropriate in a different case: A chain retailer uses BGP over IPsec overlays and needs new store prefixes learned without manual static entries. There, the reason is: Dynamic routing distributes site reachability as topology changes, but an incorrect neighbor or route-map can advertise private destinations to the wrong transport. The current case is: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. The appropriate response is: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback. The technical reason is: A blackhole for known private prefixes can prevent accidental leakage if the protected route disappears; it should never override a healthy more specific route. The stated condition is: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. Confirm the result by: Disable a test private tunnel and confirm affected private traffic drops locally while public web continues.
This action is appropriate in a different case: A factory has duplicate defaults from DHCP and BGP with unexpected route preference. There, the reason is: Routing protocol and static route preference decide route installation, while SD-WAN service strategy determines eligible member selection after matching. The current case is: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. The appropriate response is: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
This action is appropriate in a different case: A payment provider only permits the original source IP and rejects flows during ISP failover. There, the reason is: SD-WAN new-session routing can select a backup egress while return traffic follows stale NAT or external allowlist state, causing asymmetric or rejected sessions. The current case is: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. The appropriate response is: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
Question 387
A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. A Fortinet administrator recommends: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback. Which technical process explanation best justifies that recommendation?
Answer & Explanations
Correct answer: C
This principle explains a different technical intervention: Validate source NAT, route symmetry and remote peer responses after WAN member changes, especially where applications retain state. It applies to: A payment provider only permits the original source IP and rejects flows during ISP failover. The actual case is: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. The mechanism relevant here is: A blackhole for known private prefixes can prevent accidental leakage if the protected route disappears; it should never override a healthy more specific route.
This principle explains a different technical intervention: Order application-specific SD-WAN service rules before general internet defaults and confirm the first qualifying match. It applies to: A bank's private finance rule never matches because a generic internet SD-WAN rule is higher in the list. The actual case is: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. The mechanism relevant here is: A blackhole for known private prefixes can prevent accidental leakage if the protected route disappears; it should never override a healthy more specific route.
A blackhole for known private prefixes can prevent accidental leakage if the protected route disappears; it should never override a healthy more specific route. That mechanism explains the decision: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback. In the reported situation: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. Confirmation requires: Disable a test private tunnel and confirm affected private traffic drops locally while public web continues.
This principle explains a different technical intervention: Configure the appropriate SLA-oriented SD-WAN service selection method with explicit eligible members and thresholds. It applies to: A hospital's telemedicine sessions remain on high-loss broadband because the rule ignores health SLA. The actual case is: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. The mechanism relevant here is: A blackhole for known private prefixes can prevent accidental leakage if the protected route disappears; it should never override a healthy more specific route.
Question 388
A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?
Answer & Explanations
Correct answer: D
This observation would verify a different remedy: Configure the appropriate SLA-oriented SD-WAN service selection method with explicit eligible members and thresholds. That remedy applies to: A hospital's telemedicine sessions remain on high-loss broadband because the rule ignores health SLA. The present condition is: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. To assess it, check: Disable a test private tunnel and confirm affected private traffic drops locally while public web continues.
This observation would verify a different remedy: Match distinct user subnets or known remote destinations in a narrow service rule rather than relying on a shared catchall. That remedy applies to: A hospital needs its radiology systems on a private WAN while guest devices use DIA. The present condition is: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. To assess it, check: Disable a test private tunnel and confirm affected private traffic drops locally while public web continues.
This observation would verify a different remedy: Identify traffic with supported application control or application groups when building SD-WAN service rules and validate classification. That remedy applies to: A retailer wants checkout transactions preferred without steering every HTTPS download to expensive MPLS. The present condition is: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. To assess it, check: Disable a test private tunnel and confirm affected private traffic drops locally while public web continues.
Disable a test private tunnel and confirm affected private traffic drops locally while public web continues. This check directly tests: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback. The underlying behavior is: A blackhole for known private prefixes can prevent accidental leakage if the protected route disappears; it should never override a healthy more specific route. The case is: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery.
Question 389
A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. Which apparently convenient shortcut would most directly undermine the required control?
Answer & Explanations
Correct answer: A
Send protected RFC1918 traffic through ordinary public internet as a fallback whenever a tunnel fails. This shortcut is unsafe for: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. The resulting failure can be: Private flows leak into an external transport and fail or expose inappropriate metadata. The safer response is: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
This proposed shortcut concerns a separate case: A retailer wants checkout transactions preferred without steering every HTTPS download to expensive MPLS. The risk in this question concerns: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. Here the unsafe shortcut is: Send protected RFC1918 traffic through ordinary public internet as a fallback whenever a tunnel fails. Use this response instead: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
This proposed shortcut concerns a separate case: A logistics firm uses unequal internet circuits and wants balanced nightly offsite copies. The risk in this question concerns: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. Here the unsafe shortcut is: Send protected RFC1918 traffic through ordinary public internet as a fallback whenever a tunnel fails. Use this response instead: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
This proposed shortcut concerns a separate case: A hospital claims one partner API requires a dedicated authorized public source address. The risk in this question concerns: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. Here the unsafe shortcut is: Send protected RFC1918 traffic through ordinary public internet as a fallback whenever a tunnel fails. Use this response instead: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
Question 390
A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. Suppose the team follows this shortcut instead: Send protected RFC1918 traffic through ordinary public internet as a fallback whenever a tunnel fails. What is the most likely direct security or operational consequence?
Answer & Explanations
Correct answer: B
This failure concerns another scenario: A hospital claims one partner API requires a dedicated authorized public source address. In the stated case: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. The relevant consequence is: Private flows leak into an external transport and fail or expose inappropriate metadata. The control that prevents it is: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
Private flows leak into an external transport and fail or expose inappropriate metadata. This is the risk in the stated situation: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. The risky shortcut is: Send protected RFC1918 traffic through ordinary public internet as a fallback whenever a tunnel fails. Prevent it by: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
This failure concerns another scenario: A bank wants to remove an apparently idle secondary SD-WAN service used only during annual disaster tests. In the stated case: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. The relevant consequence is: Private flows leak into an external transport and fail or expose inappropriate metadata. The control that prevents it is: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
This failure concerns another scenario: A hospital confirms its patient portal selects the correct WAN yet access is still denied. In the stated case: A manufacturer fears routing private plant controller traffic into public DIA after SD-WAN recovery. The relevant consequence is: Private flows leak into an external transport and fail or expose inappropriate metadata. The control that prevents it is: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback.
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 37 - 10 Questions (Last Reviewed 15-Oct-2026)
- Fortinet NSE5_SSE_AD-7.6 Practice Test 38 - 10 Questions (Last Reviewed 14-Oct-2026)
- Fortinet NSE5_SSE_AD-7.6 Practice Test 39 - 10 Questions (Last Reviewed 13-Oct-2026)
- Fortinet NSE5_SSE_AD-7.6 Practice Test 40 - 10 Questions (Last Reviewed 12-Oct-2026)
- Fortinet NSE5_SSE_AD-7.6 Practice Test 41 - 10 Questions (Last Reviewed 11-Oct-2026)