Practice Exams:

Fortinet NSE5_SSE_AD-7.6 Dumps

EXAM: Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator
Verified By Experts
Premium Bundle
$49.99

NSE5_SSE_AD-7.6 Premium ETE File


  • Premium File 54 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet NSE5_SSE_AD-7.6 Practice Test 34

Question 330

A clinic wants an auditable record that its dedicated video route was actually used after installation. Suppose the team follows this shortcut instead: Declare a deployment successful solely because the SD-WAN service object was saved. What is the most likely direct security or operational consequence?

  1. The partner rejects traffic from the unrecognized public address despite the circuit being healthy
  2. The application continues using the prior member while change records falsely report completion
  3. Recovery flows fail when the alternate operating mode is invoked
  4. The user remains blocked because no allowed security policy matches the actual session

Answer & Explanations

Correct answer: B

A.

This failure concerns another scenario: A hospital claims one partner API requires a dedicated authorized public source address. In the stated case: A clinic wants an auditable record that its dedicated video route was actually used after installation. The relevant consequence is: The application continues using the prior member while change records falsely report completion. The control that prevents it is: Monitor matched SD-WAN service IDs, member changes and performance statistics for a targeted transaction after policy rollout.

B.

The application continues using the prior member while change records falsely report completion. This is the risk in the stated situation: A clinic wants an auditable record that its dedicated video route was actually used after installation. The risky shortcut is: Declare a deployment successful solely because the SD-WAN service object was saved. Prevent it by: Monitor matched SD-WAN service IDs, member changes and performance statistics for a targeted transaction after policy rollout.

C.

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 clinic wants an auditable record that its dedicated video route was actually used after installation. The relevant consequence is: The application continues using the prior member while change records falsely report completion. The control that prevents it is: Monitor matched SD-WAN service IDs, member changes and performance statistics for a targeted transaction after policy rollout.

D.

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 clinic wants an auditable record that its dedicated video route was actually used after installation. The relevant consequence is: The application continues using the prior member while change records falsely report completion. The control that prevents it is: Monitor matched SD-WAN service IDs, member changes and performance statistics for a targeted transaction after policy rollout.

Question 331

A branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference
  2. Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback
  3. Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members
  4. Validate source NAT, route symmetry and remote peer responses after WAN member changes, especially where applications retain state

Answer & Explanations

Correct answer: C

A.

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 branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. The appropriate response is: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

B.

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 branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. The appropriate response is: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

C.

Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members. The technical 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 stated condition is: A branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. Confirm the result by: Inspect a route lookup and send controlled internet traffic via both available WAN members.

D.

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 branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. The appropriate response is: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

Question 332

A branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. A Fortinet administrator recommends: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members. Which technical process explanation best justifies that recommendation?

  1. 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
  2. FortiOS evaluates configured SD-WAN service rules in order; a broad matching rule can prevent a lower precise service from selecting its intended WAN member
  3. 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
  4. 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

Answer & Explanations

Correct answer: D

A.

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 branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. The mechanism relevant here 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.

B.

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 branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. The mechanism relevant here 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.

C.

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 branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. The mechanism relevant here 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.

D.

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. That mechanism explains the decision: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members. In the reported situation: A branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. Confirmation requires: Inspect a route lookup and send controlled internet traffic via both available WAN members.

Question 333

A branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Inspect a route lookup and send controlled internet traffic via both available WAN members
  2. Test two WANs under equal and degraded quality and record the member chosen for new application sessions
  3. Trace one authorized source and one excluded source to the same destination and confirm only the intended flow matches the exception
  4. Send a legitimate target app and an unrelated flow on its shared port and compare rule and member outcomes

Answer & Explanations

Correct answer: A

A.

Inspect a route lookup and send controlled internet traffic via both available WAN members. This check directly tests: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members. The underlying behavior 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 case is: A branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table.

B.

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 branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. To assess it, check: Inspect a route lookup and send controlled internet traffic via both available WAN members.

C.

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 branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. To assess it, check: Inspect a route lookup and send controlled internet traffic via both available WAN members.

D.

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 branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. To assess it, check: Inspect a route lookup and send controlled internet traffic via both available WAN members.

Question 334

A branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. Which apparently convenient shortcut would most directly undermine the required control?

  1. Treat all TCP 443 traffic as the same SaaS application and send it to a privileged private carrier
  2. Remove all default routing on the assumption that adding an SD-WAN zone creates every necessary route
  3. Distribute large backups evenly across a gigabit fiber and a low-bandwidth metered LTE circuit
  4. Use the lowest measured latency WAN for a bank integration that requires a preapproved fixed source IP

Answer & Explanations

Correct answer: B

A.

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 branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. Here the unsafe shortcut is: Remove all default routing on the assumption that adding an SD-WAN zone creates every necessary route. Use this response instead: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

B.

Remove all default routing on the assumption that adding an SD-WAN zone creates every necessary route. This shortcut is unsafe for: A branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. The resulting failure can be: Users lose ordinary internet connectivity even though WAN member health reports good. The safer response is: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

C.

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 branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. Here the unsafe shortcut is: Remove all default routing on the assumption that adding an SD-WAN zone creates every necessary route. Use this response instead: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

D.

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 branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. Here the unsafe shortcut is: Remove all default routing on the assumption that adding an SD-WAN zone creates every necessary route. Use this response instead: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

Question 335

A branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. Suppose the team follows this shortcut instead: Remove all default routing on the assumption that adding an SD-WAN zone creates every necessary route. What is the most likely direct security or operational consequence?

  1. The partner rejects traffic from the unrecognized public address despite the circuit being healthy
  2. Recovery flows fail when the alternate operating mode is invoked
  3. Users lose ordinary internet connectivity even though WAN member health reports good
  4. The user remains blocked because no allowed security policy matches the actual session

Answer & Explanations

Correct answer: C

A.

This failure concerns another scenario: A hospital claims one partner API requires a dedicated authorized public source address. In the stated case: A branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. The relevant consequence is: Users lose ordinary internet connectivity even though WAN member health reports good. The control that prevents it is: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

B.

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 branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. The relevant consequence is: Users lose ordinary internet connectivity even though WAN member health reports good. The control that prevents it is: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

C.

Users lose ordinary internet connectivity even though WAN member health reports good. This is the risk in the stated situation: A branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. The risky shortcut is: Remove all default routing on the assumption that adding an SD-WAN zone creates every necessary route. Prevent it by: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

D.

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 branch adds both ISPs to an SD-WAN zone but has no valid internet route in its forwarding table. The relevant consequence is: Users lose ordinary internet connectivity even though WAN member health reports good. The control that prevents it is: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

Question 336

A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Match distinct user subnets or known remote destinations in a narrow service rule rather than relying on a shared catchall
  2. Identify traffic with supported application control or application groups when building SD-WAN service rules and validate classification
  3. Configure an eligible load-balancing rule with appropriate member weights or supported cost preferences for bulk traffic
  4. Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members

Answer & Explanations

Correct answer: D

A.

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 factory migrates static per-interface defaults to a zone-based design and must validate the route exists. The appropriate response is: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

B.

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 factory migrates static per-interface defaults to a zone-based design and must validate the route exists. The appropriate response is: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

C.

This action is appropriate in a different case: A logistics firm uses unequal internet circuits and wants balanced nightly offsite copies. There, the reason is: Equal distribution does not mean equal throughput on WANs with different capacities and a load-balancing strategy affects new flow placement. The current case is: A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. The appropriate response is: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

D.

Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members. The technical 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 stated condition is: A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. Confirm the result by: Inspect a route lookup and send controlled internet traffic via both available WAN members.

Question 337

A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. A Fortinet administrator recommends: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members. Which technical process explanation best justifies that recommendation?

  1. 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
  2. Equal distribution does not mean equal throughput on WANs with different capacities and a load-balancing strategy affects new flow placement
  3. Some business requirements mandate a specific egress identity or carrier even when another WAN measures lower latency; rule choice must honor compliance and health
  4. A lower rule with zero hits can be shadowed or used only infrequently; a short observation period is not proof it is unnecessary

Answer & Explanations

Correct answer: A

A.

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. That mechanism explains the decision: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members. In the reported situation: A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. Confirmation requires: Inspect a route lookup and send controlled internet traffic via both available WAN members.

B.

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 factory migrates static per-interface defaults to a zone-based design and must validate the route exists. The mechanism relevant here 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.

C.

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 factory migrates static per-interface defaults to a zone-based design and must validate the route exists. The mechanism relevant here 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.

D.

This principle explains a different technical intervention: Audit SD-WAN service order, match counts and real session outcomes before removing or refactoring broad rules. It applies to: A bank wants to remove an apparently idle secondary SD-WAN service used only during annual disaster tests. The actual case is: A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. The mechanism relevant here 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.

Question 338

A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Test the documented special application while reviewing first-match service counters and rollback readiness
  2. Inspect a route lookup and send controlled internet traffic via both available WAN members
  3. Trace a safe test five-tuple through service decision, firewall action, selected member and translated source
  4. Capture an authorized before-and-after session sample with the exact rule and member shown in FortiOS diagnostics

Answer & Explanations

Correct answer: B

A.

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 factory migrates static per-interface defaults to a zone-based design and must validate the route exists. To assess it, check: Inspect a route lookup and send controlled internet traffic via both available WAN members.

B.

Inspect a route lookup and send controlled internet traffic via both available WAN members. This check directly tests: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members. The underlying behavior 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 case is: A factory migrates static per-interface defaults to a zone-based design and must validate the route exists.

C.

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 factory migrates static per-interface defaults to a zone-based design and must validate the route exists. To assess it, check: Inspect a route lookup and send controlled internet traffic via both available WAN members.

D.

This observation would verify a different remedy: Monitor matched SD-WAN service IDs, member changes and performance statistics for a targeted transaction after policy rollout. That remedy applies to: A call center changes a voice service rule but cannot show that any call selected the new ISP. The present condition is: A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. To assess it, check: Inspect a route lookup and send controlled internet traffic via both available WAN members.

Question 339

A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. Which apparently convenient shortcut would most directly undermine the required control?

  1. Declare a deployment successful solely because the SD-WAN service object was saved
  2. Add competing policy routes without checking whether they bypass the desired SD-WAN rule
  3. Remove all default routing on the assumption that adding an SD-WAN zone creates every necessary route
  4. Delete all private prefix routes when enabling a new internet SD-WAN default

Answer & Explanations

Correct answer: C

A.

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 factory migrates static per-interface defaults to a zone-based design and must validate the route exists. Here the unsafe shortcut is: Remove all default routing on the assumption that adding an SD-WAN zone creates every necessary route. Use this response instead: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

B.

This proposed shortcut concerns a separate case: A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. The risk in this question concerns: A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. Here the unsafe shortcut is: Remove all default routing on the assumption that adding an SD-WAN zone creates every necessary route. Use this response instead: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

C.

Remove all default routing on the assumption that adding an SD-WAN zone creates every necessary route. This shortcut is unsafe for: A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. The resulting failure can be: Users lose ordinary internet connectivity even though WAN member health reports good. The safer response is: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

D.

This proposed shortcut concerns a separate case: A multinational updates branch SD-WAN routes and its private billing subnet stops responding. The risk in this question concerns: A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. Here the unsafe shortcut is: Remove all default routing on the assumption that adding an SD-WAN zone creates every necessary route. Use this response instead: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

Question 340

A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. Suppose the team follows this shortcut instead: Remove all default routing on the assumption that adding an SD-WAN zone creates every necessary route. What is the most likely direct security or operational consequence?

  1. Private ERP traffic leaks toward an unusable public path or times out
  2. Sensitive or unroutable private destinations are announced outside the trusted enterprise and routing becomes unstable
  3. Critical internal destinations use an unsuitable backup route and stop responding
  4. Users lose ordinary internet connectivity even though WAN member health reports good

Answer & Explanations

Correct answer: D

A.

This failure concerns another scenario: A multinational updates branch SD-WAN routes and its private billing subnet stops responding. In the stated case: A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. The relevant consequence is: Users lose ordinary internet connectivity even though WAN member health reports good. The control that prevents it is: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

B.

This failure concerns another scenario: A chain retailer uses BGP over IPsec overlays and needs new store prefixes learned without manual static entries. In the stated case: A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. The relevant consequence is: Users lose ordinary internet connectivity even though WAN member health reports good. The control that prevents it is: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

C.

This failure concerns another scenario: A factory has duplicate defaults from DHCP and BGP with unexpected route preference. In the stated case: A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. The relevant consequence is: Users lose ordinary internet connectivity even though WAN member health reports good. The control that prevents it is: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

D.

Users lose ordinary internet connectivity even though WAN member health reports good. This is the risk in the stated situation: A factory migrates static per-interface defaults to a zone-based design and must validate the route exists. The risky shortcut is: Remove all default routing on the assumption that adding an SD-WAN zone creates every necessary route. Prevent it by: Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members.

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