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 16

Question 150

A campus wants proportionate usage of two unequal WAN circuits without harming voice. Suppose the team follows this shortcut instead: Treat a 20 Mbps cellular path as equivalent to a 500 Mbps fiber service in a bulk transfer strategy. What is the most likely direct security or operational consequence?

  1. One uplink cannot be used by the intended rule and failover stops working
  2. The smaller link saturates and user sessions experience avoidable loss
  3. Branch users lose SaaS connectivity even though their local ISP is working
  4. Traffic keeps using a blackholed upstream connection while dashboards appear green

Answer & Explanations

Correct answer: B

A.

This failure concerns another scenario: A branch firewall replacement has different WAN port numbering but retains the old template. In the stated case: A campus wants proportionate usage of two unequal WAN circuits without harming voice. The relevant consequence is: The smaller link saturates and user sessions experience avoidable loss. The control that prevents it is: Configure supported member bandwidth or traffic shaping expectations from actual ISP capacities before enabling load-sharing policies.

B.

The smaller link saturates and user sessions experience avoidable loss. This is the risk in the stated situation: A campus wants proportionate usage of two unequal WAN circuits without harming voice. The risky shortcut is: Treat a 20 Mbps cellular path as equivalent to a 500 Mbps fiber service in a bulk transfer strategy. Prevent it by: Configure supported member bandwidth or traffic shaping expectations from actual ISP capacities before enabling load-sharing policies.

C.

This failure concerns another scenario: A retailer adds two local broadband links but keeps its branch SaaS sessions pinned to a failed data-center backhaul. In the stated case: A campus wants proportionate usage of two unequal WAN circuits without harming voice. The relevant consequence is: The smaller link saturates and user sessions experience avoidable loss. The control that prevents it is: Configure supported member bandwidth or traffic shaping expectations from actual ISP capacities before enabling load-sharing policies.

D.

This failure concerns another scenario: A logistics branch reports intermittent internet loss although both ISP ports show up. In the stated case: A campus wants proportionate usage of two unequal WAN circuits without harming voice. The relevant consequence is: The smaller link saturates and user sessions experience avoidable loss. The control that prevents it is: Configure supported member bandwidth or traffic shaping expectations from actual ISP capacities before enabling load-sharing policies.

Question 151

A branch firewall replacement has different WAN port numbering but retains the old template. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Record correct WAN transport costs or eligible member preferences and test cost-aware selection where supported by the configured strategy
  2. Validate how new SD-WAN sessions use remaining healthy members and document the possible effect on existing stateful connections
  3. Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes
  4. Configure supported member bandwidth or traffic shaping expectations from actual ISP capacities before enabling load-sharing policies

Answer & Explanations

Correct answer: C

A.

This action is appropriate in a different case: A remote branch has metered 5G and unlimited DSL but backups unexpectedly prefer 5G. There, the reason is: 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. The current case is: A branch firewall replacement has different WAN port numbering but retains the old template. The appropriate response is: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

B.

This action is appropriate in a different case: A payment terminal loses its existing bank session when the primary member fails but new sessions work. There, the reason is: 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. The current case is: A branch firewall replacement has different WAN port numbering but retains the old template. The appropriate response is: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

C.

Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes. The technical reason is: An interface reference that changed during provisioning can leave a logically valid SD-WAN rule pointing at the wrong member. The stated condition is: A branch firewall replacement has different WAN port numbering but retains the old template. Confirm the result by: Compare before-and-after member inventory, active sessions and test route output on the affected device.

D.

This action is appropriate in a different case: A logistics firm sends backups over fiber and cellular but the cellular path becomes overloaded. There, the reason is: An SD-WAN rule may spread traffic across eligible members while a narrow member saturates if actual upstream capacity is not represented in the design. The current case is: A branch firewall replacement has different WAN port numbering but retains the old template. The appropriate response is: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

Question 152

A branch firewall replacement has different WAN port numbering but retains the old template. A Fortinet administrator recommends: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes. Which technical process explanation best justifies that recommendation?

  1. An SD-WAN rule may spread traffic across eligible members while a narrow member saturates if actual upstream capacity is not represented in the design
  2. 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
  3. Member health and application path performance can differ from interface link state; an Ethernet up indicator alone cannot prove internet reachability or acceptable quality
  4. An interface reference that changed during provisioning can leave a logically valid SD-WAN rule pointing at the wrong member

Answer & Explanations

Correct answer: D

A.

This principle explains a different technical intervention: Configure supported member bandwidth or traffic shaping expectations from actual ISP capacities before enabling load-sharing policies. It applies to: A logistics firm sends backups over fiber and cellular but the cellular path becomes overloaded. The actual case is: A branch firewall replacement has different WAN port numbering but retains the old template. The mechanism relevant here is: An interface reference that changed during provisioning can leave a logically valid SD-WAN rule pointing at the wrong member.

B.

This principle explains a different technical intervention: Implement direct internet access through a FortiGate SD-WAN zone with explicit underlay members, firewall policy, NAT and health checks. It applies to: A retailer adds two local broadband links but keeps its branch SaaS sessions pinned to a failed data-center backhaul. The actual case is: A branch firewall replacement has different WAN port numbering but retains the old template. The mechanism relevant here is: An interface reference that changed during provisioning can leave a logically valid SD-WAN rule pointing at the wrong member.

C.

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 branch firewall replacement has different WAN port numbering but retains the old template. The mechanism relevant here is: An interface reference that changed during provisioning can leave a logically valid SD-WAN rule pointing at the wrong member.

D.

An interface reference that changed during provisioning can leave a logically valid SD-WAN rule pointing at the wrong member. That mechanism explains the decision: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes. In the reported situation: A branch firewall replacement has different WAN port numbering but retains the old template. Confirmation requires: Compare before-and-after member inventory, active sessions and test route output on the affected device.

Question 153

A branch firewall replacement has different WAN port numbering but retains the old template. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Compare before-and-after member inventory, active sessions and test route output on the affected device
  2. Compare monitor results with a controlled synthetic browsing transaction and sampled session member IDs
  3. Validate a dry-run routing lookup and end-to-end return path for one client subnet on each ISP
  4. Test one public SaaS connection and one internal application connection and compare actual path, policy and encryption state

Answer & Explanations

Correct answer: A

A.

Compare before-and-after member inventory, active sessions and test route output on the affected device. This check directly tests: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes. The underlying behavior is: An interface reference that changed during provisioning can leave a logically valid SD-WAN rule pointing at the wrong member. The case is: A branch firewall replacement has different WAN port numbering but retains the old template.

B.

This observation would verify a different remedy: Create a baseline of SD-WAN member status, aggregate traffic, packet loss and eligible route reachability before tuning steering rules. That remedy applies to: A logistics branch reports intermittent internet loss although both ISP ports show up. The present condition is: A branch firewall replacement has different WAN port numbering but retains the old template. To assess it, check: Compare before-and-after member inventory, active sessions and test route output on the affected device.

C.

This observation would verify a different remedy: Inventory LAN subnets, overlapping WAN addresses, default routes and SD-WAN policy dependencies before enrolling a FortiGate in a new branch design. That remedy applies to: A franchise duplicates the first store configuration and two stores unexpectedly advertise the same inside prefix. The present condition is: A branch firewall replacement has different WAN port numbering but retains the old template. To assess it, check: Compare before-and-after member inventory, active sessions and test route output on the affected device.

D.

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 branch firewall replacement has different WAN port numbering but retains the old template. To assess it, check: Compare before-and-after member inventory, active sessions and test route output on the affected device.

Question 154

A branch firewall replacement has different WAN port numbering but retains the old template. Which apparently convenient shortcut would most directly undermine the required control?

  1. Send regulated private service traffic directly to an untrusted public ISP because its latency is currently lowest
  2. Assume a cloned FortiGate appliance retains identical member mappings after interface hardware changes
  3. Add only equal-cost static default routes and claim latency-sensitive traffic will automatically move away from packet loss
  4. Treat a new SD-WAN rule as if it automatically creates an any-application firewall permit

Answer & Explanations

Correct answer: B

A.

This proposed shortcut concerns a separate case: A manufacturer connects field offices to private ERP over IPsec but needs ordinary web access on the local ISP. The risk in this question concerns: A branch firewall replacement has different WAN port numbering but retains the old template. Here the unsafe shortcut is: Assume a cloned FortiGate appliance retains identical member mappings after interface hardware changes. Use this response instead: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

B.

Assume a cloned FortiGate appliance retains identical member mappings after interface hardware changes. This shortcut is unsafe for: A branch firewall replacement has different WAN port numbering but retains the old template. The resulting failure can be: One uplink cannot be used by the intended rule and failover stops working. The safer response is: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

C.

This proposed shortcut concerns a separate case: A school uses two static internet routes but its classroom video app suffers during upstream loss. The risk in this question concerns: A branch firewall replacement has different WAN port numbering but retains the old template. Here the unsafe shortcut is: Assume a cloned FortiGate appliance retains identical member mappings after interface hardware changes. Use this response instead: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

D.

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 branch firewall replacement has different WAN port numbering but retains the old template. Here the unsafe shortcut is: Assume a cloned FortiGate appliance retains identical member mappings after interface hardware changes. Use this response instead: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

Question 155

A branch firewall replacement has different WAN port numbering but retains the old template. Suppose the team follows this shortcut instead: Assume a cloned FortiGate appliance retains identical member mappings after interface hardware changes. What is the most likely direct security or operational consequence?

  1. Sessions are steered toward a healthy interface but are denied or leave with unroutable source addresses
  2. Unrelated locations lose their internet paths when an incorrect shared value is deployed
  3. One uplink cannot be used by the intended rule and failover stops working
  4. The underlying connectivity defect remains while unrelated applications are rerouted

Answer & Explanations

Correct answer: C

A.

This failure concerns another scenario: An ecommerce branch sets the ideal SD-WAN service rule but its browser traffic still hits implicit deny. In the stated case: A branch firewall replacement has different WAN port numbering but retains the old template. The relevant consequence is: One uplink cannot be used by the intended rule and failover stops working. The control that prevents it is: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

B.

This failure concerns another scenario: An MSP updates one regional template but accidentally targets all customer FortiGates. In the stated case: A branch firewall replacement has different WAN port numbering but retains the old template. The relevant consequence is: One uplink cannot be used by the intended rule and failover stops working. The control that prevents it is: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

C.

One uplink cannot be used by the intended rule and failover stops working. This is the risk in the stated situation: A branch firewall replacement has different WAN port numbering but retains the old template. The risky shortcut is: Assume a cloned FortiGate appliance retains identical member mappings after interface hardware changes. Prevent it by: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

D.

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 branch firewall replacement has different WAN port numbering but retains the old template. The relevant consequence is: One uplink cannot be used by the intended rule and failover stops working. The control that prevents it is: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

Question 156

A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. Which FortiSASE or Secure SD-WAN configuration or operating process best addresses the situation?

  1. Inventory LAN subnets, overlapping WAN addresses, default routes and SD-WAN policy dependencies before enrolling a FortiGate in a new branch design
  2. Define which branch destinations use secure overlay paths and which use local internet egress, then test scoped policies for both groups
  3. 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
  4. Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes

Answer & Explanations

Correct answer: D

A.

This action is appropriate in a different case: A franchise duplicates the first store configuration and two stores unexpectedly advertise the same inside prefix. There, the reason is: 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. The current case is: A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. The appropriate response is: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

B.

This action is appropriate in a different case: A manufacturer connects field offices to private ERP over IPsec but needs ordinary web access on the local ISP. There, the reason is: 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. The current case is: A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. The appropriate response is: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

C.

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 regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. The appropriate response is: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

D.

Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes. The technical reason is: An interface reference that changed during provisioning can leave a logically valid SD-WAN rule pointing at the wrong member. The stated condition is: A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. Confirm the result by: Compare before-and-after member inventory, active sessions and test route output on the affected device.

Question 157

A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. A Fortinet administrator recommends: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes. Which technical process explanation best justifies that recommendation?

  1. An interface reference that changed during provisioning can leave a logically valid SD-WAN rule pointing at the wrong member
  2. 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
  3. 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
  4. Centralized templates reduce drift, but device-specific interfaces, gateway addresses and overlay identities must resolve correctly before installation

Answer & Explanations

Correct answer: A

A.

An interface reference that changed during provisioning can leave a logically valid SD-WAN rule pointing at the wrong member. That mechanism explains the decision: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes. In the reported situation: A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. Confirmation requires: Compare before-and-after member inventory, active sessions and test route output on the affected device.

B.

This principle explains a different technical intervention: 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. It applies to: A school uses two static internet routes but its classroom video app suffers during upstream loss. The actual case is: A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. The mechanism relevant here is: An interface reference that changed during provisioning can leave a logically valid SD-WAN rule pointing at the wrong member.

C.

This principle explains a different technical intervention: Create the required FortiGate security policy and source NAT for flows traversing the SD-WAN zone after defining membership and steering. It applies to: An ecommerce branch sets the ideal SD-WAN service rule but its browser traffic still hits implicit deny. The actual case is: A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. The mechanism relevant here is: An interface reference that changed during provisioning can leave a logically valid SD-WAN rule pointing at the wrong member.

D.

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 regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. The mechanism relevant here is: An interface reference that changed during provisioning can leave a logically valid SD-WAN rule pointing at the wrong member.

Question 158

A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Compare two target branch effective configurations and confirm install status and a real WAN path test
  2. Compare before-and-after member inventory, active sessions and test route output on the affected device
  3. Reproduce one failed test connection and record the first failing layer and its corrected counter or log
  4. Inject controlled packet loss and verify member status crosses the threshold and restores at the expected point

Answer & Explanations

Correct answer: B

A.

This observation would verify a different remedy: Use approved FortiManager templates and per-branch parameters to deploy FortiOS SD-WAN settings to the intended device groups with preview and rollback. That remedy applies to: An MSP updates one regional template but accidentally targets all customer FortiGates. The present condition is: A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. To assess it, check: Compare before-and-after member inventory, active sessions and test route output on the affected device.

B.

Compare before-and-after member inventory, active sessions and test route output on the affected device. This check directly tests: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes. The underlying behavior is: An interface reference that changed during provisioning can leave a logically valid SD-WAN rule pointing at the wrong member. The case is: A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct.

C.

This observation would verify a different remedy: Check interface link, gateway ARP, SD-WAN member status, health-check results, route selection and security policy in that order before changing service priorities. That remedy applies to: A manufacturer cannot reach any destination through its new broadband circuit and assumes application steering is wrong. The present condition is: A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. To assess it, check: Compare before-and-after member inventory, active sessions and test route output on the affected device.

D.

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 regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. To assess it, check: Compare before-and-after member inventory, active sessions and test route output on the affected device.

Question 159

A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. Which apparently convenient shortcut would most directly undermine the required control?

  1. Use a universal zero-loss threshold based on a single quiet sample for every WAN circuit
  2. Prefer a high-throughput geostationary link for interactive calls solely because it advertises more Mbps
  3. Assume a cloned FortiGate appliance retains identical member mappings after interface hardware changes
  4. Evaluate only average RTT while ignoring rapidly varying packet arrival times for voice

Answer & Explanations

Correct answer: C

A.

This proposed shortcut concerns a separate case: A call center's voice quality deteriorates when ISP loss rises despite a green interface LED. The risk in this question concerns: A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. Here the unsafe shortcut is: Assume a cloned FortiGate appliance retains identical member mappings after interface hardware changes. Use this response instead: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

B.

This proposed shortcut concerns a separate case: A satellite backup has more capacity but causes long voice delays compared with local fiber. The risk in this question concerns: A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. Here the unsafe shortcut is: Assume a cloned FortiGate appliance retains identical member mappings after interface hardware changes. Use this response instead: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

C.

Assume a cloned FortiGate appliance retains identical member mappings after interface hardware changes. This shortcut is unsafe for: A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. The resulting failure can be: One uplink cannot be used by the intended rule and failover stops working. The safer response is: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

D.

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 regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. Here the unsafe shortcut is: Assume a cloned FortiGate appliance retains identical member mappings after interface hardware changes. Use this response instead: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

Question 160

A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. Suppose the team follows this shortcut instead: Assume a cloned FortiGate appliance retains identical member mappings after interface hardware changes. What is the most likely direct security or operational consequence?

  1. Conference calls stutter despite an apparently normal average latency graph
  2. The private overlay is marked unhealthy even while its business service remains reachable
  3. Bulk recovery transfers lose a usable path that could have served their requirements
  4. One uplink cannot be used by the intended rule and failover stops working

Answer & Explanations

Correct answer: D

A.

This failure concerns another scenario: A hospital's Wi-Fi calling backhaul suffers unstable delay on an overloaded ISP. In the stated case: A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. The relevant consequence is: One uplink cannot be used by the intended rule and failover stops working. The control that prevents it is: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

B.

This failure concerns another scenario: A hospital's encrypted private circuit probes an unrelated public address and is marked down. In the stated case: A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. The relevant consequence is: One uplink cannot be used by the intended rule and failover stops working. The control that prevents it is: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

C.

This failure concerns another scenario: An office has one slow LTE link suitable for email but unsuitable for voice. In the stated case: A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. The relevant consequence is: One uplink cannot be used by the intended rule and failover stops working. The control that prevents it is: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

D.

One uplink cannot be used by the intended rule and failover stops working. This is the risk in the stated situation: A regional office changes its ISP handoff and needs to prove the member and zone mapping remain correct. The risky shortcut is: Assume a cloned FortiGate appliance retains identical member mappings after interface hardware changes. Prevent it by: Inspect each member's interface, gateway, zone, allowed SLA probes and policy references after controlled device upgrades or template changes.

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