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 11

Question 100

A factory adds a physical fiber uplink and mistakenly treats it as the ready-to-use private VPN member. Suppose the team follows this shortcut instead: Steer protected application traffic directly onto an internet physical port after its IPsec tunnel disconnects. What is the most likely direct security or operational consequence?

  1. Brief congestion produces constant path changes and interruptive user sessions
  2. Poor paths remain selected for critical applications despite accurate SLA graphs
  3. Applications reset during an unstable restoration and path churn increases
  4. Private destinations become unreachable or traffic bypasses the intended encrypted overlay

Answer & Explanations

Correct answer: D

A.

This failure concerns another scenario: A clinic's WAN swaps every minute when one ping is delayed. In the stated case: A factory adds a physical fiber uplink and mistakenly treats it as the ready-to-use private VPN member. The relevant consequence is: Private destinations become unreachable or traffic bypasses the intended encrypted overlay. The control that prevents it is: Register the correct SD-WAN member interface type and tunnel dependency before selecting an overlay or internet underlay in a service rule.

B.

This failure concerns another scenario: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. In the stated case: A factory adds a physical fiber uplink and mistakenly treats it as the ready-to-use private VPN member. The relevant consequence is: Private destinations become unreachable or traffic bypasses the intended encrypted overlay. The control that prevents it is: Register the correct SD-WAN member interface type and tunnel dependency before selecting an overlay or internet underlay in a service rule.

C.

This failure concerns another scenario: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. In the stated case: A factory adds a physical fiber uplink and mistakenly treats it as the ready-to-use private VPN member. The relevant consequence is: Private destinations become unreachable or traffic bypasses the intended encrypted overlay. The control that prevents it is: Register the correct SD-WAN member interface type and tunnel dependency before selecting an overlay or internet underlay in a service rule.

D.

Private destinations become unreachable or traffic bypasses the intended encrypted overlay. This is the risk in the stated situation: A factory adds a physical fiber uplink and mistakenly treats it as the ready-to-use private VPN member. The risky shortcut is: Steer protected application traffic directly onto an internet physical port after its IPsec tunnel disconnects. Prevent it by: Register the correct SD-WAN member interface type and tunnel dependency before selecting an overlay or internet underlay in a service rule.

Question 101

A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency
  2. Configure SD-WAN probes to stable reachable targets that reflect the actual destination path and avoid reliance on a single unsuitable public service
  3. Distinguish an unreachable SLA server or member-down condition from a reachable member that simply fails loss, latency or jitter objectives
  4. Set probe intervals, failure thresholds and recovery behavior to distinguish real link degradation from transient measurement noise

Answer & Explanations

Correct answer: A

A.

Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency. The technical reason is: FortiGate must resolve the actual next hop to transmit packets; a member object alone does not manufacture an ISP gateway or a working layer-two path. The stated condition is: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. Confirm the result by: Inspect neighbor resolution and an authorized next-hop ping from the correct interface.

B.

This action is appropriate in a different case: A hospital's encrypted private circuit probes an unrelated public address and is marked down. There, the reason is: An SLA probe tests its specific source and target path; a failed arbitrary public ICMP host can falsely condemn a working private overlay. The current case is: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. The appropriate response is: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

C.

This action is appropriate in a different case: An office has one slow LTE link suitable for email but unsuitable for voice. There, the reason is: An active but degraded circuit may continue carrying other approved traffic, while a truly dead path should not be selected for any required service. The current case is: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. The appropriate response is: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

D.

This action is appropriate in a different case: A clinic's WAN swaps every minute when one ping is delayed. There, the reason is: Too-aggressive probes or thresholds can cause repeated SD-WAN path changes, while slow detection delays recovery after genuine failure. The current case is: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. The appropriate response is: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

Question 102

A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. A Fortinet administrator recommends: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency. Which technical process explanation best justifies that recommendation?

  1. Too-aggressive probes or thresholds can cause repeated SD-WAN path changes, while slow detection delays recovery after genuine failure
  2. FortiGate must resolve the actual next hop to transmit packets; a member object alone does not manufacture an ISP gateway or a working layer-two path
  3. A correctly configured health-check object does not change traffic steering unless the matching service uses its status under the chosen strategy
  4. Recovery may involve hold timers, strategy, member priority and new-session selection; healthy status does not imply existing sessions instantly migrate back

Answer & Explanations

Correct answer: B

A.

This principle explains a different technical intervention: Set probe intervals, failure thresholds and recovery behavior to distinguish real link degradation from transient measurement noise. It applies to: A clinic's WAN swaps every minute when one ping is delayed. The actual case is: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. The mechanism relevant here is: FortiGate must resolve the actual next hop to transmit packets; a member object alone does not manufacture an ISP gateway or a working layer-two path.

B.

FortiGate must resolve the actual next hop to transmit packets; a member object alone does not manufacture an ISP gateway or a working layer-two path. That mechanism explains the decision: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency. In the reported situation: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. Confirmation requires: Inspect neighbor resolution and an authorized next-hop ping from the correct interface.

C.

This principle explains a different technical intervention: Verify that the SD-WAN service rule actually references the intended performance SLA and eligible member group before relying on measured thresholds. It applies to: A branch creates a jitter SLA yet its VoIP traffic still follows the old generic rule. The actual case is: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. The mechanism relevant here is: FortiGate must resolve the actual next hop to transmit packets; a member object alone does not manufacture an ISP gateway or a working layer-two path.

D.

This principle explains a different technical intervention: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered. It applies to: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The actual case is: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. The mechanism relevant here is: FortiGate must resolve the actual next hop to transmit packets; a member object alone does not manufacture an ISP gateway or a working layer-two path.

Question 103

A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Degrade and restore a pilot path while logging changes to SLA state, new-session member and transaction continuity
  2. Verify a test session exits only interfaces in the intended zone and that an excluded backup stays outside its policy
  3. Inspect neighbor resolution and an authorized next-hop ping from the correct interface
  4. Check tunnel negotiation and a private-address probe while monitoring underlay and overlay member statuses

Answer & Explanations

Correct answer: C

A.

This observation would verify a different remedy: Validate when and whether an SD-WAN service returns to a previously preferred path after monitored health has recovered. That remedy applies to: A bank's primary ISP recovers but the service continues selecting a backup for new sessions. The present condition is: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. To assess it, check: Inspect neighbor resolution and an authorized next-hop ping from the correct interface.

B.

This observation would verify a different remedy: Add eligible physical or tunnel WAN members to correctly named SD-WAN zones that match the organization network segmentation and security policy. That remedy applies to: A hospital has separate private MPLS and public internet paths but a new member is added to the wrong zone. The present condition is: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. To assess it, check: Inspect neighbor resolution and an authorized next-hop ping from the correct interface.

C.

Inspect neighbor resolution and an authorized next-hop ping from the correct interface. This check directly tests: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency. The underlying behavior is: FortiGate must resolve the actual next hop to transmit packets; a member object alone does not manufacture an ISP gateway or a working layer-two path. The case is: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop.

D.

This observation would verify a different remedy: Register the correct SD-WAN member interface type and tunnel dependency before selecting an overlay or internet underlay in a service rule. That remedy applies to: A regional bank uses IPsec overlays above two ISPs and one overlay loses its encryption association. The present condition is: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. To assess it, check: Inspect neighbor resolution and an authorized next-hop ping from the correct interface.

Question 104

A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. Which apparently convenient shortcut would most directly undermine the required control?

  1. Steer protected application traffic directly onto an internet physical port after its IPsec tunnel disconnects
  2. Install a static host route for every cloud application to force path preference without considering dynamic DNS or health
  3. Set metered backup as the preferred route for all file replication merely because its measured latency is low
  4. Reuse the primary ISP gateway address for a second independent provider

Answer & Explanations

Correct answer: D

A.

This proposed shortcut concerns a separate case: A regional bank uses IPsec overlays above two ISPs and one overlay loses its encryption association. The risk in this question concerns: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. Here the unsafe shortcut is: Reuse the primary ISP gateway address for a second independent provider. Use this response instead: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

B.

This proposed shortcut concerns a separate case: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. The risk in this question concerns: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. Here the unsafe shortcut is: Reuse the primary ISP gateway address for a second independent provider. Use this response instead: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

C.

This proposed shortcut concerns a separate case: A remote branch has metered 5G and unlimited DSL but backups unexpectedly prefer 5G. The risk in this question concerns: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. Here the unsafe shortcut is: Reuse the primary ISP gateway address for a second independent provider. Use this response instead: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

D.

Reuse the primary ISP gateway address for a second independent provider. This shortcut is unsafe for: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. The resulting failure can be: Secondary-link traffic fails before reaching the internet even though member selection succeeds. The safer response is: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

Question 105

A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. Suppose the team follows this shortcut instead: Reuse the primary ISP gateway address for a second independent provider. What is the most likely direct security or operational consequence?

  1. Secondary-link traffic fails before reaching the internet even though member selection succeeds
  2. Cellular charges surge and a congested backup path degrades important traffic
  3. Transaction sessions reset despite valid alternate connectivity
  4. The smaller link saturates and user sessions experience avoidable loss

Answer & Explanations

Correct answer: A

A.

Secondary-link traffic fails before reaching the internet even though member selection succeeds. This is the risk in the stated situation: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. The risky shortcut is: Reuse the primary ISP gateway address for a second independent provider. Prevent it by: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

B.

This failure concerns another scenario: A remote branch has metered 5G and unlimited DSL but backups unexpectedly prefer 5G. In the stated case: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. The relevant consequence is: Secondary-link traffic fails before reaching the internet even though member selection succeeds. The control that prevents it is: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

C.

This failure concerns another scenario: A payment terminal loses its existing bank session when the primary member fails but new sessions work. In the stated case: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. The relevant consequence is: Secondary-link traffic fails before reaching the internet even though member selection succeeds. The control that prevents it is: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

D.

This failure concerns another scenario: A logistics firm sends backups over fiber and cellular but the cellular path becomes overloaded. In the stated case: A retailer's second ISP has a different gateway but both SD-WAN member records use the same next-hop. The relevant consequence is: Secondary-link traffic fails before reaching the internet even though member selection succeeds. The control that prevents it is: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

Question 106

A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Add eligible physical or tunnel WAN members to correctly named SD-WAN zones that match the organization network segmentation and security policy
  2. Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency
  3. Register the correct SD-WAN member interface type and tunnel dependency before selecting an overlay or internet underlay in a service rule
  4. Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy

Answer & Explanations

Correct answer: B

A.

This action is appropriate in a different case: A hospital has separate private MPLS and public internet paths but a new member is added to the wrong zone. There, the reason is: SD-WAN zones group eligible interfaces for forwarding and can be referenced by policy; assigning a member to the wrong zone changes security and route eligibility. The current case is: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. The appropriate response is: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

B.

Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency. The technical reason is: FortiGate must resolve the actual next hop to transmit packets; a member object alone does not manufacture an ISP gateway or a working layer-two path. The stated condition is: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. Confirm the result by: Inspect neighbor resolution and an authorized next-hop ping from the correct interface.

C.

This action is appropriate in a different case: A regional bank uses IPsec overlays above two ISPs and one overlay loses its encryption association. There, the reason is: An IPsec tunnel can be an SD-WAN member only while its secure overlay and underlying route are usable; a physical interface being up does not prove tunnel reachability. The current case is: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. The appropriate response is: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

D.

This action is appropriate in a different case: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. There, the reason is: Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route. The current case is: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. The appropriate response is: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

Question 107

A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. A Fortinet administrator recommends: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency. Which technical process explanation best justifies that recommendation?

  1. Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route
  2. A low metered LTE cost is operationally different from a high-capacity flat-rate circuit; choosing the cheapest path without quality criteria may violate application SLAs
  3. FortiGate must resolve the actual next hop to transmit packets; a member object alone does not manufacture an ISP gateway or a working layer-two path
  4. A path change may alter source NAT and return routing; a backup member being healthy does not guarantee an established TCP session survives without reconnection

Answer & Explanations

Correct answer: C

A.

This principle explains a different technical intervention: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy. It applies to: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. The actual case is: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. The mechanism relevant here is: FortiGate must resolve the actual next hop to transmit packets; a member object alone does not manufacture an ISP gateway or a working layer-two path.

B.

This principle explains a different technical intervention: Record correct WAN transport costs or eligible member preferences and test cost-aware selection where supported by the configured strategy. It applies to: A remote branch has metered 5G and unlimited DSL but backups unexpectedly prefer 5G. The actual case is: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. The mechanism relevant here is: FortiGate must resolve the actual next hop to transmit packets; a member object alone does not manufacture an ISP gateway or a working layer-two path.

C.

FortiGate must resolve the actual next hop to transmit packets; a member object alone does not manufacture an ISP gateway or a working layer-two path. That mechanism explains the decision: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency. In the reported situation: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. Confirmation requires: Inspect neighbor resolution and an authorized next-hop ping from the correct interface.

D.

This principle explains a different technical intervention: Validate how new SD-WAN sessions use remaining healthy members and document the possible effect on existing stateful connections. It applies to: A payment terminal loses its existing bank session when the primary member fails but new sessions work. The actual case is: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. The mechanism relevant here is: FortiGate must resolve the actual next hop to transmit packets; a member object alone does not manufacture an ISP gateway or a working layer-two path.

Question 108

A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Simulate authorized loss of the primary ISP and record both new connection success and established application behavior
  2. Run safe concurrent test traffic and compare member throughput, packet drops and observed shaping behavior
  3. Compare before-and-after member inventory, active sessions and test route output on the affected device
  4. Inspect neighbor resolution and an authorized next-hop ping from the correct interface

Answer & Explanations

Correct answer: D

A.

This observation would verify a different remedy: Validate how new SD-WAN sessions use remaining healthy members and document the possible effect on existing stateful connections. That remedy applies to: A payment terminal loses its existing bank session when the primary member fails but new sessions work. The present condition is: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. To assess it, check: Inspect neighbor resolution and an authorized next-hop ping from the correct interface.

B.

This observation would verify a different remedy: Configure supported member bandwidth or traffic shaping expectations from actual ISP capacities before enabling load-sharing policies. That remedy applies to: A logistics firm sends backups over fiber and cellular but the cellular path becomes overloaded. The present condition is: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. To assess it, check: Inspect neighbor resolution and an authorized next-hop ping from the correct interface.

C.

This observation would verify a different remedy: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes. That remedy applies to: A branch firewall replacement has different WAN port numbering but retains the old template. The present condition is: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. To assess it, check: Inspect neighbor resolution and an authorized next-hop ping from the correct interface.

D.

Inspect neighbor resolution and an authorized next-hop ping from the correct interface. This check directly tests: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency. The underlying behavior is: FortiGate must resolve the actual next hop to transmit packets; a member object alone does not manufacture an ISP gateway or a working layer-two path. The case is: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway.

Question 109

A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. Which apparently convenient shortcut would most directly undermine the required control?

  1. Reuse the primary ISP gateway address for a second independent provider
  2. Assume a cloned FortiGate appliance retains identical member mappings after interface hardware changes
  3. Backhaul every branch web flow through an unreachable headquarters tunnel merely because that was the former default route
  4. Declare all WAN paths healthy because the FortiGate interface counters show carrier detected

Answer & Explanations

Correct answer: A

A.

Reuse the primary ISP gateway address for a second independent provider. This shortcut is unsafe for: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. The resulting failure can be: Secondary-link traffic fails before reaching the internet even though member selection succeeds. The safer response is: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

B.

This proposed shortcut concerns a separate case: A branch firewall replacement has different WAN port numbering but retains the old template. The risk in this question concerns: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. Here the unsafe shortcut is: Reuse the primary ISP gateway address for a second independent provider. Use this response instead: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

C.

This proposed shortcut concerns a separate case: A retailer adds two local broadband links but keeps its branch SaaS sessions pinned to a failed data-center backhaul. The risk in this question concerns: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. Here the unsafe shortcut is: Reuse the primary ISP gateway address for a second independent provider. Use this response instead: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

D.

This proposed shortcut concerns a separate case: A logistics branch reports intermittent internet loss although both ISP ports show up. The risk in this question concerns: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. Here the unsafe shortcut is: Reuse the primary ISP gateway address for a second independent provider. Use this response instead: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

Question 110

A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. Suppose the team follows this shortcut instead: Reuse the primary ISP gateway address for a second independent provider. What is the most likely direct security or operational consequence?

  1. Traffic keeps using a blackholed upstream connection while dashboards appear green
  2. Secondary-link traffic fails before reaching the internet even though member selection succeeds
  3. Duplicate networks and invalid gateways make branches unreachable or cause unpredictable traffic return
  4. Sensitive business sessions leave the approved private path and fail access or compliance checks

Answer & Explanations

Correct answer: B

A.

This failure concerns another scenario: A logistics branch reports intermittent internet loss although both ISP ports show up. In the stated case: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. The relevant consequence is: Secondary-link traffic fails before reaching the internet even though member selection succeeds. The control that prevents it is: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

B.

Secondary-link traffic fails before reaching the internet even though member selection succeeds. This is the risk in the stated situation: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. The risky shortcut is: Reuse the primary ISP gateway address for a second independent provider. Prevent it by: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

C.

This failure concerns another scenario: A franchise duplicates the first store configuration and two stores unexpectedly advertise the same inside prefix. In the stated case: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. The relevant consequence is: Secondary-link traffic fails before reaching the internet even though member selection succeeds. The control that prevents it is: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

D.

This failure concerns another scenario: A manufacturer connects field offices to private ERP over IPsec but needs ordinary web access on the local ISP. In the stated case: A rural branch migrates a WAN circuit to DHCP and still retains a hard-coded obsolete gateway. The relevant consequence is: Secondary-link traffic fails before reaching the internet even though member selection succeeds. The control that prevents it is: Configure each SD-WAN member with its correct upstream gateway or supported dynamic gateway information and check routing adjacency.

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