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 47

Question 460

A manufacturer is adding a branch network over a dedicated router and must ensure the FortiGate next hop is reachable. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the manufacturer is deployment: Implement: Configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance. Verify: Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.
  2. For the manufacturer is 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 manufacturer is 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 the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface.
  4. For the manufacturer is deployment: Implement: Configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance. Verify: 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: D

A.

This action and check address the alternate operation “For the manufacturer is 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 destination prefix with the correct reachable next hop, outgoing path and administrative distance. Its confirming test is to inspect the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface.

B.

The situation is that a manufacturer is adding a branch network over a dedicated router and must ensure the FortiGate next hop is reachable. 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 destination prefix with the correct reachable next hop, outgoing path and administrative distance. Its confirming test is to inspect the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface.

C.

This action and check address the alternate operation “For the manufacturer is 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 destination prefix with the correct reachable next hop, outgoing path and administrative distance. Its confirming test is to inspect the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface.

D.

The situation is that a manufacturer is adding a branch network over a dedicated router and must ensure the FortiGate next hop is reachable. Implement: Configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance. Verify: Inspect the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface. This pairing is justified because 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.

Question 461

A hospital's back-office subnet must never attempt to reach patient records over the public internet if its private WAN fails. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the hospital's back-office subnet 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 hospital's back-office subnet deployment: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix.
  3. For the hospital's back-office subnet deployment: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths.
  4. For the hospital's back-office subnet deployment: Configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance.

Answer & Explanations

Correct answer: A

A.

Configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic. This resolves the issue because a blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it. To verify, withdraw the preferred private path in a lab and confirm packets to the protected prefix are discarded rather than sent through default WAN.

B.

This option addresses the distinct objective “Validate equal-cost routing candidates before enabling ECMP”, not the immediate requirement. ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ. For the stated case, 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 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, a blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.

D.

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, a blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.

Question 462

A hospital's back-office subnet must never attempt to reach patient records over the public internet if its private WAN fails. The engineer proposes this change: Configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the hospital's back-office subnet 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 hospital's back-office subnet deployment: A blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.
  3. For the hospital's back-office subnet 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.
  4. For the hospital's back-office subnet 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: B

A.

That statement explains the distinct objective “Validate equal-cost routing candidates before enabling ECMP” rather than the cause in this case. The deciding mechanism here is that a blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.

B.

A blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it. It supports this action: Configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic. To confirm, withdraw the preferred private path in a lab and confirm packets to the protected prefix are discarded rather than sent through default WAN.

C.

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 a blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.

D.

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 a blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.

Question 463

A hospital's back-office subnet must never attempt to reach patient records over the public internet if its private WAN fails. After implementing this change—Configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic—which test best establishes that the intended outcome is actually working?

  1. For the hospital's back-office subnet deployment: Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.
  2. For the hospital's back-office subnet deployment: Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.
  3. For the hospital's back-office subnet 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 hospital's back-office subnet 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: C

A.

This check would help evaluate the distinct objective “Validate equal-cost routing candidates before enabling ECMP”, but not the required result. For this case, withdraw the preferred private path in a lab and confirm packets to the protected prefix are discarded rather than sent through default WAN.

B.

This check would help evaluate the distinct objective “Measure SD-WAN member health with appropriate probes”, but not the required result. For this case, withdraw the preferred private path in a lab and confirm packets to the protected prefix are discarded rather than sent through default WAN.

C.

Withdraw the preferred private path in a lab and confirm packets to the protected prefix are discarded rather than sent through default WAN. This is the relevant test because a blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.

D.

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, withdraw the preferred private path in a lab and confirm packets to the protected prefix are discarded rather than sent through default WAN.

Question 464

A hospital's back-office subnet must never attempt to reach patient records over the public internet if its private WAN fails. Which proposed shortcut would most directly cause private-destination packets escaping toward an unintended default gateway, and therefore must be avoided for this requirement?

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

Answer & Explanations

Correct answer: D

A.

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 rely on the public default route as a harmless replacement for every unavailable private network.

B.

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 rely on the public default route as a harmless replacement for every unavailable private network.

C.

That shortcut would relate to the distinct objective “Validate equal-cost routing candidates before enabling ECMP”, rather than the specific configuration or use described. The unsafe step in this case is to rely on the public default route as a harmless replacement for every unavailable private network.

D.

Rely on the public default route as a harmless replacement for every unavailable private network. The proposed shortcut bypasses the needed control: A blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it. The appropriate response 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.

Question 465

A hospital's back-office subnet must never attempt to reach patient records over the public internet if its private WAN fails. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the hospital's back-office subnet 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.
  2. For the hospital's back-office subnet 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 hospital's back-office subnet 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.
  4. For the hospital's back-office subnet 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: A

A.

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.

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 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.

C.

This action and check address the alternate operation “For the hospital's back-office subnet deployment: Implement: Configure a destination prefix with the correct reachable next hop, outgoing path…” 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.

This action and check address the alternate operation “For the hospital's back-office subnet deployment: Implement: Configure a properly scoped blackhole route where failing over to the default…” 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 466

A design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the design firm deployment: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths.
  2. For the design firm 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 design firm deployment: Configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance.
  4. For the design firm 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: B

A.

The situation is that a design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. 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, a blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.

B.

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

C.

The situation is that a design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. 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, a blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.

D.

The situation is that a design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. This option addresses the distinct objective “Validate equal-cost routing candidates before enabling ECMP”, not the immediate requirement. ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ. For the stated case, a blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.

Question 467

A design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. The engineer proposes this change: Configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the design firm 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.
  2. For the design firm 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.
  3. For the design firm 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 design firm 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: C

A.

The situation is that a design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. 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 a blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.

B.

The situation is that a design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. 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 a blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.

C.

The situation is that a design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. A blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it. It supports this action: Configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic. To confirm, 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. That statement explains the distinct objective “Validate equal-cost routing candidates before enabling ECMP” rather than the cause in this case. The deciding mechanism here is that a blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.

Question 468

A design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. After implementing this change—Configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic—which test best establishes that the intended outcome is actually working?

  1. For the design firm deployment: 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 design firm deployment: Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.
  3. For the design firm deployment: Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.
  4. For the design firm 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: D

A.

The situation is that a design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. 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, 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. This check would help evaluate the distinct objective “Validate equal-cost routing candidates before enabling ECMP”, but not the required result. For this case, withdraw the preferred private path in a lab and confirm packets to the protected prefix are discarded rather than sent through default WAN.

C.

The situation is that a design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. This check would help evaluate the distinct objective “Measure SD-WAN member health with appropriate probes”, but not the required result. For this case, 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. Withdraw the preferred private path in a lab and confirm packets to the protected prefix are discarded rather than sent through default WAN. This is the relevant test because a blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it.

Question 469

A design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. Which proposed shortcut would most directly cause private-destination packets escaping toward an unintended default gateway, and therefore must be avoided for this requirement?

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

Answer & Explanations

Correct answer: A

A.

The situation is that a design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. Rely on the public default route as a harmless replacement for every unavailable private network. The proposed shortcut bypasses the needed control: A blackhole route can deliberately discard traffic for an unavailable private destination instead of allowing a less-specific default route to capture it. The appropriate response 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.

B.

The situation is that a design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. 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 rely on the public default route as a harmless replacement for every unavailable private network.

C.

The situation is that a design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. That shortcut would relate to the distinct objective “Validate equal-cost routing candidates before enabling ECMP”, rather than the specific configuration or use described. The unsafe step in this case is to rely on the public default route as a harmless replacement for every unavailable private network.

D.

The situation is that a design firm wants access to a confidential partner prefix dropped rather than redirected through an untrusted ISP. 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 rely on the public default route as a harmless replacement for every unavailable private network.

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.

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