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 46

Question 450

An online classroom service experiences periodic latency when a high-volume application hits an overly broad IPS sensor. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the online classroom service experiences deployment: Implement: Correlate IPS engine process load, inspected traffic and specific noisy signatures before revising the sensor's scope. Verify: Repeat the legitimate transaction and a safe negative control, ensuring the target signature exception is scoped and other IPS events persist.
  2. For the online classroom service experiences deployment: Implement: Correlate IPS engine process load, inspected traffic and specific noisy signatures before revising the sensor's scope. Verify: Measure CPU, IPS events and throughput during a reproducible representative workload after a targeted adjustment.
  3. For the online classroom service experiences deployment: Implement: Choose relevant IPS signatures and enforcement actions in a sensor attached to the correct traffic policy for the protected application. Verify: Run a benign lab signature test against a representative service and verify the specific IPS event action and policy ID.
  4. For the online classroom service experiences deployment: Implement: Check valid security subscription, update service access and installed IPS signature version before trusting protection claims. Verify: Measure CPU, IPS events and throughput during a reproducible representative workload after a targeted adjustment.

Answer & Explanations

Correct answer: B

A.

This action and check address the alternate operation “For the online classroom service experiences deployment: Implement: Correlate IPS engine process load, inspected traffic and specific noisy signatures…” instead of the stated acceptance requirement. The matching action is to correlate IPS engine process load, inspected traffic and specific noisy signatures before revising the sensor's scope. Its confirming test is to measure CPU, IPS events and throughput during a reproducible representative workload after a targeted adjustment.

B.

The situation is that an online classroom service experiences periodic latency when a high-volume application hits an overly broad IPS sensor. Implement: Correlate IPS engine process load, inspected traffic and specific noisy signatures before revising the sensor's scope. Verify: Measure CPU, IPS events and throughput during a reproducible representative workload after a targeted adjustment. This pairing is justified because high inspection load may reflect traffic volume, signature selection or engine behavior; broad removal of IPS trades performance for lost security.

C.

The situation is that an online classroom service experiences periodic latency when a high-volume application hits an overly broad IPS sensor. This action and check address the distinct objective “Apply an IPS sensor tuned to the protected service” instead of the stated acceptance requirement. The matching action is to correlate IPS engine process load, inspected traffic and specific noisy signatures before revising the sensor's scope. Its confirming test is to measure CPU, IPS events and throughput during a reproducible representative workload after a targeted adjustment.

D.

This action and check address the alternate operation “For the online classroom service experiences deployment: Implement: Check valid security subscription, update service access and installed IPS signature…” instead of the stated acceptance requirement. The matching action is to correlate IPS engine process load, inspected traffic and specific noisy signatures before revising the sensor's scope. Its confirming test is to measure CPU, IPS events and throughput during a reproducible representative workload after a targeted adjustment.

Question 451

A city finance annex gained a private WAN circuit and needs traffic to an accounting subnet routed through its new peer. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

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

Answer & Explanations

Correct answer: C

A.

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

B.

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

C.

Configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance. This resolves the issue 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. To verify, inspect the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface.

D.

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, 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 452

A city finance annex gained a private WAN circuit and needs traffic to an accounting subnet routed through its new peer. The engineer proposes this change: Configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the city finance annex 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 city finance annex 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 city finance annex deployment: ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.
  4. For the city finance annex 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: D

A.

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

B.

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

C.

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

D.

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. It supports this action: Configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance. To confirm, inspect the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface.

Question 453

A city finance annex gained a private WAN circuit and needs traffic to an accounting subnet routed through its new peer. After implementing this change—Configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance—which test best establishes that the intended outcome is actually working?

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

Answer & Explanations

Correct answer: A

A.

Inspect the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface. This is the relevant test 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.

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, 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 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 the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface.

D.

This check would help evaluate the distinct objective “Validate equal-cost routing candidates before enabling ECMP”, but not the required result. For this case, inspect the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface.

Question 454

A city finance annex gained a private WAN circuit and needs traffic to an accounting subnet routed through its new peer. Which proposed shortcut would most directly cause a configured but inactive path and packets failing to reach the remote subnet, and therefore must be avoided for this requirement?

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

Answer & Explanations

Correct answer: B

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 add a route using a gateway unreachable on any connected interface.

B.

Add a route using a gateway unreachable on any connected interface. The proposed shortcut bypasses the needed control: 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. The appropriate response is to configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance.

C.

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 add a route using a gateway unreachable on any connected interface.

D.

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 add a route using a gateway unreachable on any connected interface.

Question 455

A city finance annex gained a private WAN circuit and needs traffic to an accounting subnet routed through its new peer. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the city finance annex 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.
  2. For the city finance annex 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.
  3. For the city finance annex 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.
  4. For the city finance annex 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.

Answer & Explanations

Correct answer: C

A.

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.

B.

This action and check address the alternate operation “For the city finance annex 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 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.

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.

D.

This action and check address the alternate operation “For the city finance annex 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 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.

Question 456

A manufacturer is adding a branch network over a dedicated router and must ensure the FortiGate next hop is reachable. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

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

Answer & Explanations

Correct answer: D

A.

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

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

C.

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

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. Configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance. This resolves the issue 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. To verify, inspect the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface.

Question 457

A manufacturer is adding a branch network over a dedicated router and must ensure the FortiGate next hop is reachable. The engineer proposes this change: Configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the manufacturer is 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 manufacturer is 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 manufacturer is deployment: ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.
  4. For the manufacturer is 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.

Answer & Explanations

Correct answer: A

A.

The situation is that a manufacturer is adding a branch network over a dedicated router and must ensure the FortiGate next hop is reachable. 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. It supports this action: Configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance. To confirm, 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. 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 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.

C.

The situation is that a manufacturer is adding a branch network over a dedicated router and must ensure the FortiGate next hop is reachable. 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 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.

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

A manufacturer is adding a branch network over a dedicated router and must ensure the FortiGate next hop is reachable. After implementing this change—Configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance—which test best establishes that the intended outcome is actually working?

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

Answer & Explanations

Correct answer: B

A.

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 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 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. Inspect the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface. This is the relevant test 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.

C.

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 check would help evaluate the distinct objective “Validate equal-cost routing candidates before enabling ECMP”, but not the required result. For this case, 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. 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 the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface.

Question 459

A manufacturer is adding a branch network over a dedicated router and must ensure the FortiGate next hop is reachable. Which proposed shortcut would most directly cause a configured but inactive path and packets failing to reach the remote subnet, and therefore must be avoided for this requirement?

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

Answer & Explanations

Correct answer: C

A.

The situation is that a manufacturer is adding a branch network over a dedicated router and must ensure the FortiGate next hop is reachable. 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 add a route using a gateway unreachable on any connected 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. 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 add a route using a gateway unreachable on any connected interface.

C.

The situation is that a manufacturer is adding a branch network over a dedicated router and must ensure the FortiGate next hop is reachable. Add a route using a gateway unreachable on any connected interface. The proposed shortcut bypasses the needed control: 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. The appropriate response is to configure a destination prefix with the correct reachable next hop, outgoing path and administrative distance.

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. 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 add a route using a gateway unreachable on any connected interface.

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.

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