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 12

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.

Question 111

A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes
  2. Implement direct internet access through a FortiGate SD-WAN zone with explicit underlay members, firewall policy, NAT and health checks
  3. Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy
  4. Create a baseline of SD-WAN member status, aggregate traffic, packet loss and eligible route reachability before tuning steering rules

Answer & Explanations

Correct answer: C

A.

This action is appropriate in a different case: A branch firewall replacement has different WAN port numbering but retains the old template. There, the reason is: An interface reference that changed during provisioning can leave a logically valid SD-WAN rule pointing at the wrong member. The current case is: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. The appropriate response is: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

B.

This action is appropriate in a different case: A retailer adds two local broadband links but keeps its branch SaaS sessions pinned to a failed data-center backhaul. There, the reason is: A direct internet access design keeps eligible branch traffic local while SD-WAN selects healthy internet members; defining the zone alone does not grant traffic or translate private addresses. The current case is: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. The appropriate response is: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

C.

Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy. The technical reason is: Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route. The stated condition is: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. Confirm the result by: With both ISPs healthy verify the preferred member, then degrade it and inspect the approved alternative.

D.

This action is appropriate in a different case: A logistics branch reports intermittent internet loss although both ISP ports show up. There, the reason is: Member health and application path performance can differ from interface link state; an Ethernet up indicator alone cannot prove internet reachability or acceptable quality. The current case is: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. The appropriate response is: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

Question 112

A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. A Fortinet administrator recommends: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy. Which technical process explanation best justifies that recommendation?

  1. Member health and application path performance can differ from interface link state; an Ethernet up indicator alone cannot prove internet reachability or acceptable quality
  2. SD-WAN forwarding depends on valid routed underlay interfaces and correct address scope; duplicate subnets or stale routes can prevent return traffic even with acceptable link health
  3. Secure private routes and direct internet routes serve different data destinations; a default internet egress rule is not evidence that private traffic traverses the intended protected overlay
  4. Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route

Answer & Explanations

Correct answer: D

A.

This principle explains a different technical intervention: Create a baseline of SD-WAN member status, aggregate traffic, packet loss and eligible route reachability before tuning steering rules. It applies to: A logistics branch reports intermittent internet loss although both ISP ports show up. The actual case is: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. The mechanism relevant here is: Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route.

B.

This principle explains a different technical intervention: Inventory LAN subnets, overlapping WAN addresses, default routes and SD-WAN policy dependencies before enrolling a FortiGate in a new branch design. It applies to: A franchise duplicates the first store configuration and two stores unexpectedly advertise the same inside prefix. The actual case is: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. The mechanism relevant here is: Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route.

C.

This principle explains a different technical intervention: Define which branch destinations use secure overlay paths and which use local internet egress, then test scoped policies for both groups. It applies to: A manufacturer connects field offices to private ERP over IPsec but needs ordinary web access on the local ISP. The actual case is: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. The mechanism relevant here is: Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route.

D.

Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route. That mechanism explains the decision: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy. In the reported situation: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. Confirmation requires: With both ISPs healthy verify the preferred member, then degrade it and inspect the approved alternative.

Question 113

A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. With both ISPs healthy verify the preferred member, then degrade it and inspect the approved alternative
  2. Test one public SaaS connection and one internal application connection and compare actual path, policy and encryption state
  3. Test two distinct applications and prove they select the intended member when both ISP routes remain reachable
  4. Inspect one approved test flow for both SD-WAN rule result and firewall policy/NAT acceptance

Answer & Explanations

Correct answer: A

A.

With both ISPs healthy verify the preferred member, then degrade it and inspect the approved alternative. This check directly tests: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy. The underlying behavior is: Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route. The case is: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target.

B.

This observation would verify a different remedy: Define which branch destinations use secure overlay paths and which use local internet egress, then test scoped policies for both groups. That remedy applies to: A manufacturer connects field offices to private ERP over IPsec but needs ordinary web access on the local ISP. The present condition is: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. To assess it, check: With both ISPs healthy verify the preferred member, then degrade it and inspect the approved alternative.

C.

This observation would verify a different remedy: Add WAN interfaces as SD-WAN members in the intended zone and use eligible routes and SD-WAN services instead of pretending a pair of static defaults offers application-aware steering. That remedy applies to: A school uses two static internet routes but its classroom video app suffers during upstream loss. The present condition is: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. To assess it, check: With both ISPs healthy verify the preferred member, then degrade it and inspect the approved alternative.

D.

This observation would verify a different remedy: Create the required FortiGate security policy and source NAT for flows traversing the SD-WAN zone after defining membership and steering. That remedy applies to: An ecommerce branch sets the ideal SD-WAN service rule but its browser traffic still hits implicit deny. The present condition is: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. To assess it, check: With both ISPs healthy verify the preferred member, then degrade it and inspect the approved alternative.

Question 114

A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. Which apparently convenient shortcut would most directly undermine the required control?

  1. Treat a new SD-WAN rule as if it automatically creates an any-application firewall permit
  2. Install a static host route for every cloud application to force path preference without considering dynamic DNS or health
  3. Install a modified global SD-WAN template to every branch without validating local WAN interface references
  4. Raise every SD-WAN rule priority to fix an ISP handoff with no reachable gateway

Answer & Explanations

Correct answer: B

A.

This proposed shortcut concerns a separate case: An ecommerce branch sets the ideal SD-WAN service rule but its browser traffic still hits implicit deny. The risk in this question concerns: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. Here the unsafe shortcut is: Install a static host route for every cloud application to force path preference without considering dynamic DNS or health. Use this response instead: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

B.

Install a static host route for every cloud application to force path preference without considering dynamic DNS or health. This shortcut is unsafe for: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. The resulting failure can be: Traffic locks to obsolete destinations and fails when the ISP or SaaS endpoint changes. The safer response is: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

C.

This proposed shortcut concerns a separate case: An MSP updates one regional template but accidentally targets all customer FortiGates. The risk in this question concerns: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. Here the unsafe shortcut is: Install a static host route for every cloud application to force path preference without considering dynamic DNS or health. Use this response instead: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

D.

This proposed shortcut concerns a separate case: A manufacturer cannot reach any destination through its new broadband circuit and assumes application steering is wrong. The risk in this question concerns: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. Here the unsafe shortcut is: Install a static host route for every cloud application to force path preference without considering dynamic DNS or health. Use this response instead: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

Question 115

A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. Suppose the team follows this shortcut instead: Install a static host route for every cloud application to force path preference without considering dynamic DNS or health. What is the most likely direct security or operational consequence?

  1. The underlying connectivity defect remains while unrelated applications are rerouted
  2. Normal transient packet drops trigger unnecessary path flapping
  3. Traffic locks to obsolete destinations and fails when the ISP or SaaS endpoint changes
  4. Voice and collaboration experience persistent delay while an alternative faster path exists

Answer & Explanations

Correct answer: C

A.

This failure concerns another scenario: A manufacturer cannot reach any destination through its new broadband circuit and assumes application steering is wrong. In the stated case: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. The relevant consequence is: Traffic locks to obsolete destinations and fails when the ISP or SaaS endpoint changes. The control that prevents it is: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

B.

This failure concerns another scenario: A call center's voice quality deteriorates when ISP loss rises despite a green interface LED. In the stated case: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. The relevant consequence is: Traffic locks to obsolete destinations and fails when the ISP or SaaS endpoint changes. The control that prevents it is: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

C.

Traffic locks to obsolete destinations and fails when the ISP or SaaS endpoint changes. This is the risk in the stated situation: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. The risky shortcut is: Install a static host route for every cloud application to force path preference without considering dynamic DNS or health. Prevent it by: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

D.

This failure concerns another scenario: A satellite backup has more capacity but causes long voice delays compared with local fiber. In the stated case: A clinic wants fiber preferred for clinical SaaS and LTE used only when health falls below target. The relevant consequence is: Traffic locks to obsolete destinations and fails when the ISP or SaaS endpoint changes. The control that prevents it is: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

Question 116

A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Add WAN interfaces as SD-WAN members in the intended zone and use eligible routes and SD-WAN services instead of pretending a pair of static defaults offers application-aware steering
  2. Create the required FortiGate security policy and source NAT for flows traversing the SD-WAN zone after defining membership and steering
  3. Use approved FortiManager templates and per-branch parameters to deploy FortiOS SD-WAN settings to the intended device groups with preview and rollback
  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: D

A.

This action is appropriate in a different case: A school uses two static internet routes but its classroom video app suffers during upstream loss. There, the reason is: Two static routes can provide route preference, but SD-WAN adds member health, measured SLA and service rules to control which qualifying path handles a flow. The current case is: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. The appropriate response is: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

B.

This action is appropriate in a different case: An ecommerce branch sets the ideal SD-WAN service rule but its browser traffic still hits implicit deny. There, the reason is: SD-WAN path selection and firewall session authorization are separate stages, so a correct member decision does not imply policy allows or NAT translates the traffic. The current case is: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. The appropriate response is: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

C.

This action is appropriate in a different case: An MSP updates one regional template but accidentally targets all customer FortiGates. There, the reason is: Centralized templates reduce drift, but device-specific interfaces, gateway addresses and overlay identities must resolve correctly before installation. The current case is: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. The appropriate response is: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

D.

Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy. The technical reason is: Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route. The stated condition is: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. Confirm the result by: With both ISPs healthy verify the preferred member, then degrade it and inspect the approved alternative.

Question 117

A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. A Fortinet administrator recommends: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy. 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. Centralized templates reduce drift, but device-specific interfaces, gateway addresses and overlay identities must resolve correctly before installation
  3. A broken next-hop adjacency, failed SLA target, missing route and firewall deny can look like the same user outage but require different remedies
  4. Link loss measured through an active health check can indicate poor transport quality before the physical interface goes down

Answer & Explanations

Correct answer: A

A.

Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route. That mechanism explains the decision: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy. In the reported situation: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. Confirmation requires: With both ISPs healthy verify the preferred member, then degrade it and inspect the approved alternative.

B.

This principle explains a different technical intervention: Use approved FortiManager templates and per-branch parameters to deploy FortiOS SD-WAN settings to the intended device groups with preview and rollback. It applies to: An MSP updates one regional template but accidentally targets all customer FortiGates. The actual case is: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. The mechanism relevant here is: Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route.

C.

This principle explains a different technical intervention: Check interface link, gateway ARP, SD-WAN member status, health-check results, route selection and security policy in that order before changing service priorities. It applies to: A manufacturer cannot reach any destination through its new broadband circuit and assumes application steering is wrong. The actual case is: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. The mechanism relevant here is: Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route.

D.

This principle explains a different technical intervention: Define an SD-WAN performance SLA with justified packet loss tolerance and healthy probe targets for the critical application. It applies to: A call center's voice quality deteriorates when ISP loss rises despite a green interface LED. The actual case is: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. The mechanism relevant here is: Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route.

Question 118

A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Inject controlled packet loss and verify member status crosses the threshold and restores at the expected point
  2. With both ISPs healthy verify the preferred member, then degrade it and inspect the approved alternative
  3. Increase test-link delay deliberately and inspect SLA status plus selected route for a VoIP trial call
  4. Introduce bounded variable delay in a lab and confirm SLA breach, rule behavior and audio recovery

Answer & Explanations

Correct answer: B

A.

This observation would verify a different remedy: Define an SD-WAN performance SLA with justified packet loss tolerance and healthy probe targets for the critical application. That remedy applies to: A call center's voice quality deteriorates when ISP loss rises despite a green interface LED. The present condition is: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. To assess it, check: With both ISPs healthy verify the preferred member, then degrade it and inspect the approved alternative.

B.

With both ISPs healthy verify the preferred member, then degrade it and inspect the approved alternative. This check directly tests: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy. The underlying behavior is: Member priority expresses preference among eligible paths; a higher priority alone should not override a failed SLA or unavailable route. The case is: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service.

C.

This observation would verify a different remedy: Set latency targets and destination probes appropriate for delay-sensitive services, then associate the SLA with the intended SD-WAN rule. That remedy applies to: A satellite backup has more capacity but causes long voice delays compared with local fiber. The present condition is: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. To assess it, check: With both ISPs healthy verify the preferred member, then degrade it and inspect the approved alternative.

D.

This observation would verify a different remedy: Use performance SLA jitter thresholds to decide whether a real-time application should stay on an eligible member. That remedy applies to: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. The present condition is: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. To assess it, check: With both ISPs healthy verify the preferred member, then degrade it and inspect the approved alternative.

Question 119

A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. Which apparently convenient shortcut would most directly undermine the required control?

  1. Evaluate only average RTT while ignoring rapidly varying packet arrival times for voice
  2. Use a public DNS host that blocks ICMP as the sole health target for a private MPLS service
  3. Install a static host route for every cloud application to force path preference without considering dynamic DNS or health
  4. Disable a working backup circuit completely because it fails a strict voice SLA even though backups tolerate its latency

Answer & Explanations

Correct answer: C

A.

This proposed shortcut concerns a separate case: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. The risk in this question concerns: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. Here the unsafe shortcut is: Install a static host route for every cloud application to force path preference without considering dynamic DNS or health. Use this response instead: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

B.

This proposed shortcut concerns a separate case: A hospital's encrypted private circuit probes an unrelated public address and is marked down. The risk in this question concerns: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. Here the unsafe shortcut is: Install a static host route for every cloud application to force path preference without considering dynamic DNS or health. Use this response instead: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

C.

Install a static host route for every cloud application to force path preference without considering dynamic DNS or health. This shortcut is unsafe for: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. The resulting failure can be: Traffic locks to obsolete destinations and fails when the ISP or SaaS endpoint changes. The safer response is: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

D.

This proposed shortcut concerns a separate case: An office has one slow LTE link suitable for email but unsuitable for voice. The risk in this question concerns: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. Here the unsafe shortcut is: Install a static host route for every cloud application to force path preference without considering dynamic DNS or health. Use this response instead: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

Question 120

A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. Suppose the team follows this shortcut instead: Install a static host route for every cloud application to force path preference without considering dynamic DNS or health. What is the most likely direct security or operational consequence?

  1. Bulk recovery transfers lose a usable path that could have served their requirements
  2. Brief congestion produces constant path changes and interruptive user sessions
  3. Poor paths remain selected for critical applications despite accurate SLA graphs
  4. Traffic locks to obsolete destinations and fails when the ISP or SaaS endpoint changes

Answer & Explanations

Correct answer: D

A.

This failure concerns another scenario: An office has one slow LTE link suitable for email but unsuitable for voice. In the stated case: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. The relevant consequence is: Traffic locks to obsolete destinations and fails when the ISP or SaaS endpoint changes. The control that prevents it is: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

B.

This failure concerns another scenario: A clinic's WAN swaps every minute when one ping is delayed. In the stated case: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. The relevant consequence is: Traffic locks to obsolete destinations and fails when the ISP or SaaS endpoint changes. The control that prevents it is: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

C.

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 wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. The relevant consequence is: Traffic locks to obsolete destinations and fails when the ISP or SaaS endpoint changes. The control that prevents it is: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

D.

Traffic locks to obsolete destinations and fails when the ISP or SaaS endpoint changes. This is the risk in the stated situation: A wholesaler's backup ISP receives excessive traffic because link priorities were never set for its default service. The risky shortcut is: Install a static host route for every cloud application to force path preference without considering dynamic DNS or health. Prevent it by: Set supported SD-WAN member priority and service behavior according to intended preference and measured health without replacing security policy.

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