Practice Exams:

Fortinet FCP_FGT_AD-7.6 Dumps

EXAM: FCP - FortiGate 7.6 Administrator
Verified By Experts
Premium Bundle
$49.99

FCP_FGT_AD-7.6 Premium ETE File


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

Fortinet FCP_FGT_AD-7.6 Practice Test 48

Question 470

A design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the design firm deployment: Implement: Configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance. Verify: Withdraw the preferred private path in a lab and confirm packets to the protected prefix are discarded rather than sent through default WAN.
  2. For the design firm deployment: Implement: Configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic. Verify: Withdraw the preferred private path in a lab and confirm packets to the protected prefix are discarded rather than sent through default WAN.
  3. For the design firm deployment: Implement: Configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic. Verify: Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.
  4. For the design firm deployment: Implement: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. Verify: Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

Answer & Explanations

Correct answer: B

A.

This action and check address the alternate operation “For the design firm deployment: Implement: Configure a destination prefix with the correct reachable next hop, outgoing path and…” instead of the stated acceptance requirement. The matching action is to configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic. Its confirming test is to withdraw the preferred private path in a lab and confirm packets to the protected prefix are discarded rather than sent through default WAN.

B.

The situation is that a design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. Implement: Configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic. Verify: Withdraw the preferred private path in a lab and confirm packets to the protected prefix are discarded rather than sent through default WAN. This pairing is justified because a blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.

C.

This action and check address the alternate operation “For the design firm deployment: Implement: Configure a properly scoped blackhole route where failing over to the default internet…” instead of the stated acceptance requirement. The matching action is to configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic. Its confirming test is to withdraw the preferred private path in a lab and confirm packets to the protected prefix are discarded rather than sent through default WAN.

D.

The situation is that a design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. This action and check address the distinct objective “Measure SD-WAN member health with appropriate probes” instead of the stated acceptance requirement. The matching action is to configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic. Its confirming test is to withdraw the preferred private path in a lab and confirm packets to the protected prefix are discarded rather than sent through default WAN.

Question 471

A conference network has two equal-capacity private transport links to the same remote campus. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the conference network deployment: Configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic.
  2. For the conference network deployment: Configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance.
  3. For the conference network deployment: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix.
  4. For the conference network deployment: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths.

Answer & Explanations

Correct answer: C

A.

This option addresses the distinct objective “Use a deliberate blackhole route to avoid unintended fallback”, not the immediate requirement. A blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it. For the stated case, ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

B.

This option addresses the distinct objective “Install a static route with reachable next hop and intended distance”, not the immediate requirement. The routing table installs eligible routes according to reachability, prefix length and route selection attributes; a missing next-hop path can render a configured route unusable. For the stated case, ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

C.

Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. This resolves the issue because ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ. To verify, inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

D.

This option addresses the distinct objective “Measure SD-WAN member health with appropriate probes”, not the immediate requirement. Performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health. For the stated case, ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

Question 472

A conference network has two equal-capacity private transport links to the same remote campus. The engineer proposes this change: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the conference network deployment: The routing table installs eligible routes according to reachability, prefix length and route selection attributes; a missing next-hop path can render a configured route unusable.
  2. For the conference network deployment: Performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.
  3. For the conference network deployment: A blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.
  4. For the conference network deployment: ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

Answer & Explanations

Correct answer: D

A.

That statement explains the distinct objective “Install a static route with reachable next hop and intended distance” rather than the cause in this case. The deciding mechanism here is that ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

B.

That statement explains the distinct objective “Measure SD-WAN member health with appropriate probes” rather than the cause in this case. The deciding mechanism here is that ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

C.

That statement explains the distinct objective “Use a deliberate blackhole route to avoid unintended fallback” rather than the cause in this case. The deciding mechanism here is that ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

D.

ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ. It supports this action: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. To confirm, inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

Question 473

A conference network has two equal-capacity private transport links to the same remote campus. After implementing this change—Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix—which test best establishes that the intended outcome is actually working?

  1. For the conference network deployment: Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.
  2. For the conference network deployment: Inspect the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface.
  3. For the conference network deployment: Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.
  4. For the conference network deployment: Withdraw the preferred private path in a lab and confirm packets to the protected prefix are discarded rather than sent through default WAN.

Answer & Explanations

Correct answer: A

A.

Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions. This is the relevant test because ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

B.

This check would help evaluate the distinct objective “Install a static route with reachable next hop and intended distance”, but not the required result. For this case, inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

C.

This check would help evaluate the distinct objective “Measure SD-WAN member health with appropriate probes”, but not the required result. For this case, inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

D.

This check would help evaluate the distinct objective “Use a deliberate blackhole route to avoid unintended fallback”, but not the required result. For this case, inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

Question 474

A conference network has two equal-capacity private transport links to the same remote campus. Which proposed shortcut would most directly cause traffic pinned to an unintended path instead of an expected shared-cost set, and therefore must be avoided for this requirement?

  1. For the conference network deployment: Add a route using a gateway unreachable on any connected interface.
  2. For the conference network deployment: Assume routes with different administrative distances will automatically balance traffic equally.
  3. For the conference network deployment: Mark a WAN healthy based only on physical link-up while its end-to-end path drops application packets.
  4. For the conference network deployment: Rely on the public default route as a harmless replacement for every unavailable private network.

Answer & Explanations

Correct answer: B

A.

That shortcut would relate to the distinct objective “Install a static route with reachable next hop and intended distance”, rather than the specific configuration or use described. The unsafe step in this case is to assume routes with different administrative distances will automatically balance traffic equally.

B.

Assume routes with different administrative distances will automatically balance traffic equally. The proposed shortcut bypasses the needed control: ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ. The appropriate response is to check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix.

C.

That shortcut would relate to the distinct objective “Measure SD-WAN member health with appropriate probes”, rather than the specific configuration or use described. The unsafe step in this case is to assume routes with different administrative distances will automatically balance traffic equally.

D.

That shortcut would relate to the distinct objective “Use a deliberate blackhole route to avoid unintended fallback”, rather than the specific configuration or use described. The unsafe step in this case is to assume routes with different administrative distances will automatically balance traffic equally.

Question 475

A conference network has two equal-capacity private transport links to the same remote campus. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the conference network deployment: Implement: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Verify: Inspect the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface.
  2. For the conference network deployment: Implement: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. Verify: Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.
  3. For the conference network deployment: Implement: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Verify: Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.
  4. For the conference network deployment: Implement: Configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic. Verify: Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

Answer & Explanations

Correct answer: C

A.

This action and check address the alternate operation “For the conference network deployment: Implement: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost…” instead of the stated acceptance requirement. The matching action is to check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Its confirming test is to inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

B.

This action and check address the distinct objective “Measure SD-WAN member health with appropriate probes” instead of the stated acceptance requirement. The matching action is to check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Its confirming test is to inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

C.

Implement: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Verify: Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions. This pairing is justified because ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

D.

This action and check address the alternate operation “For the conference network deployment: Implement: Configure a properly scoped blackhole route where failing over to the default internet…” instead of the stated acceptance requirement. The matching action is to check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Its confirming test is to inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

Question 476

A supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the supplier wants deployment: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths.
  2. For the supplier wants deployment: Configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic.
  3. For the supplier wants deployment: Configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance.
  4. For the supplier wants deployment: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix.

Answer & Explanations

Correct answer: D

A.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. This option addresses the distinct objective “Measure SD-WAN member health with appropriate probes”, not the immediate requirement. Performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health. For the stated case, ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

B.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. This option addresses the distinct objective “Use a deliberate blackhole route to avoid unintended fallback”, not the immediate requirement. A blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it. For the stated case, ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

C.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. This option addresses the distinct objective “Install a static route with reachable next hop and intended distance”, not the immediate requirement. The routing table installs eligible routes according to reachability, prefix length and route selection attributes; a missing next-hop path can render a configured route unusable. For the stated case, ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

D.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. This resolves the issue because ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ. To verify, inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

Question 477

A supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. The engineer proposes this change: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the supplier wants deployment: ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.
  2. For the supplier wants deployment: Performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.
  3. For the supplier wants deployment: A blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.
  4. For the supplier wants deployment: The routing table installs eligible routes according to reachability, prefix length and route selection attributes; a missing next-hop path can render a configured route unusable.

Answer & Explanations

Correct answer: A

A.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ. It supports this action: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. To confirm, inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

B.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. That statement explains the distinct objective “Measure SD-WAN member health with appropriate probes” rather than the cause in this case. The deciding mechanism here is that ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

C.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. That statement explains the distinct objective “Use a deliberate blackhole route to avoid unintended fallback” rather than the cause in this case. The deciding mechanism here is that ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

D.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. That statement explains the distinct objective “Install a static route with reachable next hop and intended distance” rather than the cause in this case. The deciding mechanism here is that ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

Question 478

A supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. After implementing this change—Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix—which test best establishes that the intended outcome is actually working?

  1. For the supplier wants deployment: Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.
  2. For the supplier wants deployment: Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.
  3. For the supplier wants deployment: Withdraw the preferred private path in a lab and confirm packets to the protected prefix are discarded rather than sent through default WAN.
  4. For the supplier wants deployment: Inspect the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface.

Answer & Explanations

Correct answer: B

A.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. This check would help evaluate the distinct objective “Measure SD-WAN member health with appropriate probes”, but not the required result. For this case, inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

B.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions. This is the relevant test because ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

C.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. This check would help evaluate the distinct objective “Use a deliberate blackhole route to avoid unintended fallback”, but not the required result. For this case, inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

D.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. This check would help evaluate the distinct objective “Install a static route with reachable next hop and intended distance”, but not the required result. For this case, inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

Question 479

A supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. Which proposed shortcut would most directly cause traffic pinned to an unintended path instead of an expected shared-cost set, and therefore must be avoided for this requirement?

  1. For the supplier wants deployment: Mark a WAN healthy based only on physical link-up while its end-to-end path drops application packets.
  2. For the supplier wants deployment: Rely on the public default route as a harmless replacement for every unavailable private network.
  3. For the supplier wants deployment: Assume routes with different administrative distances will automatically balance traffic equally.
  4. For the supplier wants deployment: Add a route using a gateway unreachable on any connected interface.

Answer & Explanations

Correct answer: C

A.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. That shortcut would relate to the distinct objective “Measure SD-WAN member health with appropriate probes”, rather than the specific configuration or use described. The unsafe step in this case is to assume routes with different administrative distances will automatically balance traffic equally.

B.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. That shortcut would relate to the distinct objective “Use a deliberate blackhole route to avoid unintended fallback”, rather than the specific configuration or use described. The unsafe step in this case is to assume routes with different administrative distances will automatically balance traffic equally.

C.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. Assume routes with different administrative distances will automatically balance traffic equally. The proposed shortcut bypasses the needed control: ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ. The appropriate response is to check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix.

D.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. That shortcut would relate to the distinct objective “Install a static route with reachable next hop and intended distance”, rather than the specific configuration or use described. The unsafe step in this case is to assume routes with different administrative distances will automatically balance traffic equally.

Question 480

A supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the supplier wants deployment: Implement: Configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic. Verify: Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.
  2. For the supplier wants deployment: Implement: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Verify: Inspect the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface.
  3. For the supplier wants deployment: Implement: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. Verify: Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.
  4. For the supplier wants deployment: Implement: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Verify: Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

Answer & Explanations

Correct answer: D

A.

This action and check address the alternate operation “For the supplier wants deployment: Implement: Configure a properly scoped blackhole route where failing over to the default internet…” instead of the stated acceptance requirement. The matching action is to check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Its confirming test is to inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

B.

This action and check address the alternate operation “For the supplier wants deployment: Implement: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost…” instead of the stated acceptance requirement. The matching action is to check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Its confirming test is to inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

C.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. This action and check address the distinct objective “Measure SD-WAN member health with appropriate probes” instead of the stated acceptance requirement. The matching action is to check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Its confirming test is to inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

D.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. Implement: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Verify: Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions. This pairing is justified because ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

FCP - FortiGate 7.6 Administrator (FCP_FGT_AD-7.6) Practice Tests