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 35

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.

Question 341

A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior
  2. Monitor matched SD-WAN service IDs, member changes and performance statistics for a targeted transaction after policy rollout
  3. Configure the applicable FortiOS route toward an SD-WAN zone and verify the forwarding table supports eligible internet members
  4. Install or learn appropriate protected destination routes through approved IPsec or private SD-WAN members separately from the internet default

Answer & Explanations

Correct answer: A

A.

Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior. The technical reason is: Route lookup establishes reachable destination context while steering policies may direct eligible traffic; policy routes or mismatched priorities can alter the expected decision. The stated condition is: A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. Confirm the result by: Use authorized diagnostics to identify which routing or service policy selects each of two test traffic classes.

B.

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 retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. The appropriate response is: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

C.

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 retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. The appropriate response is: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

D.

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 retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. The appropriate response is: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

Question 342

A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. A Fortinet administrator recommends: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior. Which technical process explanation best justifies that recommendation?

  1. Specific private subnet routes must remain reachable through intended overlay; an internet default route is not an acceptable substitute for protected enterprise prefixes
  2. Route lookup establishes reachable destination context while steering policies may direct eligible traffic; policy routes or mismatched priorities can alter the expected decision
  3. Dynamic routing distributes site reachability as topology changes, but an incorrect neighbor or route-map can advertise private destinations to the wrong transport
  4. Routing protocol and static route preference decide route installation, while SD-WAN service strategy determines eligible member selection after matching

Answer & Explanations

Correct answer: B

A.

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 retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. The mechanism relevant here is: Route lookup establishes reachable destination context while steering policies may direct eligible traffic; policy routes or mismatched priorities can alter the expected decision.

B.

Route lookup establishes reachable destination context while steering policies may direct eligible traffic; policy routes or mismatched priorities can alter the expected decision. That mechanism explains the decision: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior. In the reported situation: A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. Confirmation requires: Use authorized diagnostics to identify which routing or service policy selects each of two test traffic classes.

C.

This principle explains a different technical intervention: Use approved BGP route advertisements and learned private prefixes on the intended SD-WAN overlay, validating next-hop and route preference. It applies to: A chain retailer uses BGP over IPsec overlays and needs new store prefixes learned without manual static entries. The actual case is: A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. The mechanism relevant here is: Route lookup establishes reachable destination context while steering policies may direct eligible traffic; policy routes or mismatched priorities can alter the expected decision.

D.

This principle explains a different technical intervention: Set route administrative distance and priority appropriate to available static or learned paths without confusing them with SD-WAN SLA preference. It applies to: A factory has duplicate defaults from DHCP and BGP with unexpected route preference. The actual case is: A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. The mechanism relevant here is: Route lookup establishes reachable destination context while steering policies may direct eligible traffic; policy routes or mismatched priorities can alter the expected decision.

Question 343

A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Inspect a controlled route change and observe both route table state and actual service member selection
  2. Disable a test private tunnel and confirm affected private traffic drops locally while public web continues
  3. Use authorized diagnostics to identify which routing or service policy selects each of two test traffic classes
  4. Record original and translated tuples on each WAN during a pilot failover and verify end-to-end transaction completion

Answer & Explanations

Correct answer: C

A.

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 retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. To assess it, check: Use authorized diagnostics to identify which routing or service policy selects each of two test traffic classes.

B.

This observation would verify a different remedy: Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback. That remedy applies to: A bank wants site-private destinations denied locally during total VPN loss instead of exiting broadband. The present condition is: A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. To assess it, check: Use authorized diagnostics to identify which routing or service policy selects each of two test traffic classes.

C.

Use authorized diagnostics to identify which routing or service policy selects each of two test traffic classes. This check directly tests: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior. The underlying behavior is: Route lookup establishes reachable destination context while steering policies may direct eligible traffic; policy routes or mismatched priorities can alter the expected decision. The case is: A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active.

D.

This observation would verify a different remedy: Validate source NAT, route symmetry and remote peer responses after WAN member changes, especially where applications retain state. That remedy applies to: A payment provider only permits the original source IP and rejects flows during ISP failover. The present condition is: A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. To assess it, check: Use authorized diagnostics to identify which routing or service policy selects each of two test traffic classes.

Question 344

A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. Which apparently convenient shortcut would most directly undermine the required control?

  1. Treat successful gateway pings as proof that every existing stateful application will survive path switch
  2. Insert an any-source any-destination rule above the protected payroll-specific routing exception
  3. Pin mission-critical video to a single member without health validation merely because it is normally fastest
  4. Add competing policy routes without checking whether they bypass the desired SD-WAN rule

Answer & Explanations

Correct answer: D

A.

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 retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. Here the unsafe shortcut is: Add competing policy routes without checking whether they bypass the desired SD-WAN rule. Use this response instead: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

B.

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 retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. Here the unsafe shortcut is: Add competing policy routes without checking whether they bypass the desired SD-WAN rule. Use this response instead: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

C.

This proposed shortcut concerns a separate case: A hospital's telemedicine sessions remain on high-loss broadband because the rule ignores health SLA. The risk in this question concerns: A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. Here the unsafe shortcut is: Add competing policy routes without checking whether they bypass the desired SD-WAN rule. Use this response instead: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

D.

Add competing policy routes without checking whether they bypass the desired SD-WAN rule. This shortcut is unsafe for: A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. The resulting failure can be: Sessions follow an unintended interface despite accurate SLA and service configurations. The safer response is: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

Question 345

A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. Suppose the team follows this shortcut instead: Add competing policy routes without checking whether they bypass the desired SD-WAN rule. What is the most likely direct security or operational consequence?

  1. Sessions follow an unintended interface despite accurate SLA and service configurations
  2. Call quality collapses when that circuit degrades while a healthier circuit remains eligible
  3. Unrelated users consume the restricted WAN or bypass approved internet handling
  4. Unrelated encrypted applications inherit the special path and violate bandwidth or trust design

Answer & Explanations

Correct answer: A

A.

Sessions follow an unintended interface despite accurate SLA and service configurations. This is the risk in the stated situation: A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. The risky shortcut is: Add competing policy routes without checking whether they bypass the desired SD-WAN rule. Prevent it by: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

B.

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 retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. The relevant consequence is: Sessions follow an unintended interface despite accurate SLA and service configurations. The control that prevents it is: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

C.

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 retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. The relevant consequence is: Sessions follow an unintended interface despite accurate SLA and service configurations. The control that prevents it is: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

D.

This failure concerns another scenario: A retailer wants checkout transactions preferred without steering every HTTPS download to expensive MPLS. In the stated case: A retailer's VoIP service ignores its SD-WAN SLA after an older policy route remains active. The relevant consequence is: Sessions follow an unintended interface despite accurate SLA and service configurations. The control that prevents it is: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

Question 346

An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Configure justified blackhole routes for specified protected destinations when no secure overlay path exists, and test against undesired internet fallback
  2. Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior
  3. Validate source NAT, route symmetry and remote peer responses after WAN member changes, especially where applications retain state
  4. Order application-specific SD-WAN service rules before general internet defaults and confirm the first qualifying match

Answer & Explanations

Correct answer: B

A.

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: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. The appropriate response is: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

B.

Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior. The technical reason is: Route lookup establishes reachable destination context while steering policies may direct eligible traffic; policy routes or mismatched priorities can alter the expected decision. The stated condition is: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. Confirm the result by: Use authorized diagnostics to identify which routing or service policy selects each of two test traffic classes.

C.

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: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. The appropriate response is: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

D.

This action is appropriate in a different case: A bank's private finance rule never matches because a generic internet SD-WAN rule is higher in the list. There, the reason is: 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. The current case is: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. The appropriate response is: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

Question 347

An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. A Fortinet administrator recommends: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior. Which technical process explanation best justifies that recommendation?

  1. 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
  2. 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
  3. Route lookup establishes reachable destination context while steering policies may direct eligible traffic; policy routes or mismatched priorities can alter the expected decision
  4. Source and destination selectors can route only authorized traffic over a preferred member while other flows retain their own service routing

Answer & Explanations

Correct answer: C

A.

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: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. The mechanism relevant here is: Route lookup establishes reachable destination context while steering policies may direct eligible traffic; policy routes or mismatched priorities can alter the expected decision.

B.

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: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. The mechanism relevant here is: Route lookup establishes reachable destination context while steering policies may direct eligible traffic; policy routes or mismatched priorities can alter the expected decision.

C.

Route lookup establishes reachable destination context while steering policies may direct eligible traffic; policy routes or mismatched priorities can alter the expected decision. That mechanism explains the decision: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior. In the reported situation: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. Confirmation requires: Use authorized diagnostics to identify which routing or service policy selects each of two test traffic classes.

D.

This principle explains a different technical intervention: Match distinct user subnets or known remote destinations in a narrow service rule rather than relying on a shared catchall. It applies to: A hospital needs its radiology systems on a private WAN while guest devices use DIA. The actual case is: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. The mechanism relevant here is: Route lookup establishes reachable destination context while steering policies may direct eligible traffic; policy routes or mismatched priorities can alter the expected decision.

Question 348

An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Trace one authorized source and one excluded source to the same destination and confirm only the intended flow matches the exception
  2. Send a legitimate target app and an unrelated flow on its shared port and compare rule and member outcomes
  3. Generate a controlled bulk workload and compare member session counts, utilization and application quality
  4. Use authorized diagnostics to identify which routing or service policy selects each of two test traffic classes

Answer & Explanations

Correct answer: D

A.

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: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. To assess it, check: Use authorized diagnostics to identify which routing or service policy selects each of two test traffic classes.

B.

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: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. To assess it, check: Use authorized diagnostics to identify which routing or service policy selects each of two test traffic classes.

C.

This observation would verify a different remedy: Configure an eligible load-balancing rule with appropriate member weights or supported cost preferences for bulk traffic. That remedy applies to: A logistics firm uses unequal internet circuits and wants balanced nightly offsite copies. The present condition is: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. To assess it, check: Use authorized diagnostics to identify which routing or service policy selects each of two test traffic classes.

D.

Use authorized diagnostics to identify which routing or service policy selects each of two test traffic classes. This check directly tests: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior. The underlying behavior is: Route lookup establishes reachable destination context while steering policies may direct eligible traffic; policy routes or mismatched priorities can alter the expected decision. The case is: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups.

Question 349

An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. Which apparently convenient shortcut would most directly undermine the required control?

  1. Add competing policy routes without checking whether they bypass the desired SD-WAN rule
  2. Distribute large backups evenly across a gigabit fiber and a low-bandwidth metered LTE circuit
  3. Use the lowest measured latency WAN for a bank integration that requires a preapproved fixed source IP
  4. Delete a low-hit disaster recovery service rule after one quiet weekend

Answer & Explanations

Correct answer: A

A.

Add competing policy routes without checking whether they bypass the desired SD-WAN rule. This shortcut is unsafe for: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. The resulting failure can be: Sessions follow an unintended interface despite accurate SLA and service configurations. The safer response is: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

B.

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: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. Here the unsafe shortcut is: Add competing policy routes without checking whether they bypass the desired SD-WAN rule. Use this response instead: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

C.

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: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. Here the unsafe shortcut is: Add competing policy routes without checking whether they bypass the desired SD-WAN rule. Use this response instead: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

D.

This proposed shortcut concerns a separate case: A bank wants to remove an apparently idle secondary SD-WAN service used only during annual disaster tests. The risk in this question concerns: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. Here the unsafe shortcut is: Add competing policy routes without checking whether they bypass the desired SD-WAN rule. Use this response instead: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

Question 350

An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. Suppose the team follows this shortcut instead: Add competing policy routes without checking whether they bypass the desired SD-WAN rule. What is the most likely direct security or operational consequence?

  1. Recovery flows fail when the alternate operating mode is invoked
  2. Sessions follow an unintended interface despite accurate SLA and service configurations
  3. The user remains blocked because no allowed security policy matches the actual session
  4. The application continues using the prior member while change records falsely report completion

Answer & Explanations

Correct answer: B

A.

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: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. The relevant consequence is: Sessions follow an unintended interface despite accurate SLA and service configurations. The control that prevents it is: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

B.

Sessions follow an unintended interface despite accurate SLA and service configurations. This is the risk in the stated situation: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. The risky shortcut is: Add competing policy routes without checking whether they bypass the desired SD-WAN rule. Prevent it by: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

C.

This failure concerns another scenario: A hospital confirms its patient portal selects the correct WAN yet access is still denied. In the stated case: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. The relevant consequence is: Sessions follow an unintended interface despite accurate SLA and service configurations. The control that prevents it is: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

D.

This failure concerns another scenario: A call center changes a voice service rule but cannot show that any call selected the new ISP. In the stated case: An engineering team needs to explain why identical destinations take different egress paths for two LAN groups. The relevant consequence is: Sessions follow an unintended interface despite accurate SLA and service configurations. The control that prevents it is: Compare regular route table, SD-WAN service decisions and FortiOS policy routes before changing a production forwarding behavior.

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