Fortinet NSE5_SSE_AD-7.6 Dumps
Fortinet NSE5_SSE_AD-7.6 Practice Test 38
Question 370
A data center receives a wrong default route from a branch peer and must stop unintended advertisement. Suppose the team follows this shortcut instead: Advertise all internal network prefixes indiscriminately to every public ISP peer. What is the most likely direct security or operational consequence?
Answer & Explanations
Correct answer: B
This failure concerns another scenario: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. In the stated case: A data center receives a wrong default route from a branch peer and must stop unintended advertisement. The relevant consequence is: Sensitive or unroutable private destinations are announced outside the trusted enterprise and routing becomes unstable. The control that prevents it is: Use approved BGP route advertisements and learned private prefixes on the intended SD-WAN overlay, validating next-hop and route preference.
Sensitive or unroutable private destinations are announced outside the trusted enterprise and routing becomes unstable. This is the risk in the stated situation: A data center receives a wrong default route from a branch peer and must stop unintended advertisement. The risky shortcut is: Advertise all internal network prefixes indiscriminately to every public ISP peer. Prevent it by: Use approved BGP route advertisements and learned private prefixes on the intended SD-WAN overlay, validating next-hop and route preference.
This failure concerns another scenario: A payment provider only permits the original source IP and rejects flows during ISP failover. In the stated case: A data center receives a wrong default route from a branch peer and must stop unintended advertisement. The relevant consequence is: Sensitive or unroutable private destinations are announced outside the trusted enterprise and routing becomes unstable. The control that prevents it is: Use approved BGP route advertisements and learned private prefixes on the intended SD-WAN overlay, validating next-hop and route preference.
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 data center receives a wrong default route from a branch peer and must stop unintended advertisement. The relevant consequence is: Sensitive or unroutable private destinations are announced outside the trusted enterprise and routing becomes unstable. The control that prevents it is: Use approved BGP route advertisements and learned private prefixes on the intended SD-WAN overlay, validating next-hop and route preference.
Question 371
A factory has duplicate defaults from DHCP and BGP with unexpected route preference. 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 multinational updates branch SD-WAN routes and its private billing subnet stops responding. There, the reason is: Specific private subnet routes must remain reachable through intended overlay; an internet default route is not an acceptable substitute for protected enterprise prefixes. The current case is: A factory has duplicate defaults from DHCP and BGP with unexpected route preference. The appropriate response is: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
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 factory has duplicate defaults from DHCP and BGP with unexpected route preference. The appropriate response is: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference. The technical reason is: Routing protocol and static route preference decide route installation, while SD-WAN service strategy determines eligible member selection after matching. The stated condition is: A factory has duplicate defaults from DHCP and BGP with unexpected route preference. Confirm the result by: Inspect a controlled route change and observe both route table state and actual service member selection.
This action is appropriate in a different case: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. There, the 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 current case is: A factory has duplicate defaults from DHCP and BGP with unexpected route preference. The appropriate response is: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
Question 372
A factory has duplicate defaults from DHCP and BGP with unexpected route preference. A Fortinet administrator recommends: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference. Which technical process explanation best justifies that recommendation?
Answer & Explanations
Correct answer: D
This principle explains a different technical intervention: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback. It applies to: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. The actual case is: A factory has duplicate defaults from DHCP and BGP with unexpected route preference. The mechanism relevant here is: Routing protocol and static route preference decide route installation, while SD-WAN service strategy determines eligible member selection after matching.
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 factory has duplicate defaults from DHCP and BGP with unexpected route preference. The mechanism relevant here is: Routing protocol and static route preference decide route installation, while SD-WAN service strategy determines eligible member selection after matching.
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 factory has duplicate defaults from DHCP and BGP with unexpected route preference. The mechanism relevant here is: Routing protocol and static route preference decide route installation, while SD-WAN service strategy determines eligible member selection after matching.
Routing protocol and static route preference decide route installation, while SD-WAN service strategy determines eligible member selection after matching. That mechanism explains the decision: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference. In the reported situation: A factory has duplicate defaults from DHCP and BGP with unexpected route preference. Confirmation requires: Inspect a controlled route change and observe both route table state and actual service member selection.
Question 373
A factory has duplicate defaults from DHCP and BGP with unexpected route preference. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?
Answer & Explanations
Correct answer: A
Inspect a controlled route change and observe both route table state and actual service member selection. This check directly tests: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference. The underlying behavior is: Routing protocol and static route preference decide route installation, while SD-WAN service strategy determines eligible member selection after matching. The case is: A factory has duplicate defaults from DHCP and BGP with unexpected route preference.
This observation would verify a different remedy: Order application-specific SD-WAN service rules before general internet defaults and confirm the first qualifying match. That remedy applies to: A bank's private finance rule never matches because a generic internet SD-WAN rule is higher in the list. The present condition is: A factory has duplicate defaults from DHCP and BGP with unexpected route preference. To assess it, check: Inspect a controlled route change and observe both route table state and actual service member selection.
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 factory has duplicate defaults from DHCP and BGP with unexpected route preference. To assess it, check: Inspect a controlled route change and observe both route table state and actual service member selection.
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 factory has duplicate defaults from DHCP and BGP with unexpected route preference. To assess it, check: Inspect a controlled route change and observe both route table state and actual service member selection.
Question 374
A factory has duplicate defaults from DHCP and BGP with unexpected route preference. Which apparently convenient shortcut would most directly undermine the required control?
Answer & Explanations
Correct answer: B
This proposed shortcut concerns a separate case: A hospital needs its radiology systems on a private WAN while guest devices use DIA. The risk in this question concerns: A factory has duplicate defaults from DHCP and BGP with unexpected route preference. Here the unsafe shortcut is: Lower an unrelated backup route distance until it overrides all specific private paths just to improve internet performance. Use this response instead: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
Lower an unrelated backup route distance until it overrides all specific private paths just to improve internet performance. This shortcut is unsafe for: A factory has duplicate defaults from DHCP and BGP with unexpected route preference. The resulting failure can be: Critical internal destinations use an unsuitable backup route and stop responding. The safer response is: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
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 factory has duplicate defaults from DHCP and BGP with unexpected route preference. Here the unsafe shortcut is: Lower an unrelated backup route distance until it overrides all specific private paths just to improve internet performance. Use this response instead: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
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 factory has duplicate defaults from DHCP and BGP with unexpected route preference. Here the unsafe shortcut is: Lower an unrelated backup route distance until it overrides all specific private paths just to improve internet performance. Use this response instead: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
Question 375
A factory has duplicate defaults from DHCP and BGP with unexpected route preference. 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: C
This failure concerns another scenario: A logistics firm uses unequal internet circuits and wants balanced nightly offsite copies. In the stated case: A factory has duplicate defaults from DHCP and BGP with unexpected route preference. 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 hospital claims one partner API requires a dedicated authorized public source address. In the stated case: A factory has duplicate defaults from DHCP and BGP with unexpected route preference. 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 factory has duplicate defaults from DHCP and BGP with unexpected route preference. 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.
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 factory has duplicate defaults from DHCP and BGP with unexpected route preference. 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.
Question 376
A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. 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 hospital's telemedicine sessions remain on high-loss broadband because the rule ignores health SLA. There, the reason is: A service strategy that considers SLA membership can choose a healthy qualified path rather than simply using a fixed interface regardless of latency or loss. The current case is: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. The appropriate response is: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
This action is appropriate in a different case: A hospital needs its radiology systems on a private WAN while guest devices use DIA. There, the reason is: Source and destination selectors can route only authorized traffic over a preferred member while other flows retain their own service routing. The current case is: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. The appropriate response is: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
This action is appropriate in a different case: A retailer wants checkout transactions preferred without steering every HTTPS download to expensive MPLS. There, the reason is: An application-based routing intent may rely on deep packet or session identification, so port number alone can group unrelated business applications. The current case is: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. The appropriate response is: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference. The technical reason is: Routing protocol and static route preference decide route installation, while SD-WAN service strategy determines eligible member selection after matching. The stated condition is: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. Confirm the result by: Inspect a controlled route change and observe both route table state and actual service member selection.
Question 377
A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. A Fortinet administrator recommends: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference. Which technical process explanation best justifies that recommendation?
Answer & Explanations
Correct answer: A
Routing protocol and static route preference decide route installation, while SD-WAN service strategy determines eligible member selection after matching. That mechanism explains the decision: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference. In the reported situation: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. Confirmation requires: Inspect a controlled route change and observe both route table state and actual service member selection.
This principle explains a different technical intervention: Identify traffic with supported application control or application groups when building SD-WAN service rules and validate classification. It applies to: A retailer wants checkout transactions preferred without steering every HTTPS download to expensive MPLS. The actual case is: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. The mechanism relevant here is: Routing protocol and static route preference decide route installation, while SD-WAN service strategy determines eligible member selection after matching.
This principle explains a different technical intervention: Configure an eligible load-balancing rule with appropriate member weights or supported cost preferences for bulk traffic. It applies to: A logistics firm uses unequal internet circuits and wants balanced nightly offsite copies. The actual case is: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. The mechanism relevant here is: Routing protocol and static route preference decide route installation, while SD-WAN service strategy determines eligible member selection after matching.
This principle explains a different technical intervention: Use a scoped manual or priority-based SD-WAN service rule when a contractual endpoint must use an approved egress provider. It applies to: A hospital claims one partner API requires a dedicated authorized public source address. The actual case is: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. The mechanism relevant here is: Routing protocol and static route preference decide route installation, while SD-WAN service strategy determines eligible member selection after matching.
Question 378
A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. 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: Use a scoped manual or priority-based SD-WAN service rule when a contractual endpoint must use an approved egress provider. That remedy applies to: A hospital claims one partner API requires a dedicated authorized public source address. The present condition is: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. To assess it, check: Inspect a controlled route change and observe both route table state and actual service member selection.
Inspect a controlled route change and observe both route table state and actual service member selection. This check directly tests: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference. The underlying behavior is: Routing protocol and static route preference decide route installation, while SD-WAN service strategy determines eligible member selection after matching. The case is: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default.
This observation would verify a different remedy: Audit SD-WAN service order, match counts and real session outcomes before removing or refactoring broad rules. That remedy applies to: A bank wants to remove an apparently idle secondary SD-WAN service used only during annual disaster tests. The present condition is: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. To assess it, check: Inspect a controlled route change and observe both route table state and actual service member selection.
This observation would verify a different remedy: Inspect the SD-WAN service match independently from firewall policy, route resolution and NAT to explain why a steered connection is denied. That remedy applies to: A hospital confirms its patient portal selects the correct WAN yet access is still denied. The present condition is: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. To assess it, check: Inspect a controlled route change and observe both route table state and actual service member selection.
Question 379
A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. Which apparently convenient shortcut would most directly undermine the required control?
Answer & Explanations
Correct answer: C
This proposed shortcut concerns a separate case: A hospital confirms its patient portal selects the correct WAN yet access is still denied. The risk in this question concerns: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. Here the unsafe shortcut is: Lower an unrelated backup route distance until it overrides all specific private paths just to improve internet performance. Use this response instead: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
This proposed shortcut concerns a separate case: A call center changes a voice service rule but cannot show that any call selected the new ISP. The risk in this question concerns: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. Here the unsafe shortcut is: Lower an unrelated backup route distance until it overrides all specific private paths just to improve internet performance. Use this response instead: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
Lower an unrelated backup route distance until it overrides all specific private paths just to improve internet performance. This shortcut is unsafe for: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. The resulting failure can be: Critical internal destinations use an unsuitable backup route and stop responding. The safer response is: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
This proposed shortcut concerns a separate case: A branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. The risk in this question concerns: A hospital's preferred internet SLA is healthy but its private tunnel routes are incorrectly replaced by a static default. Here the unsafe shortcut is: Lower an unrelated backup route distance until it overrides all specific private paths just to improve internet performance. Use this response instead: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference.
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.
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 36 - 10 Questions (Last Reviewed 16-Oct-2026)
- 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)