Fortinet FCP_FGT_AD-7.6 Dumps
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?
Answer & Explanations
Correct answer: D
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.
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.
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.
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?
Answer & Explanations
Correct answer: 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.
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.
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.
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?
Answer & Explanations
Correct answer: B
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.
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.
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.
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?
Answer & Explanations
Correct answer: C
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.
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.
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.
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?
Answer & Explanations
Correct answer: D
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.
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.
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.
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?
Answer & Explanations
Correct answer: 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.
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.
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.
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?
Answer & Explanations
Correct answer: B
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.
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.
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.
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?
Answer & Explanations
Correct answer: C
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.
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.
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.
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?
Answer & Explanations
Correct answer: D
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.
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.
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.
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?
Answer & Explanations
Correct answer: 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.
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.
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.
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?
Answer & Explanations
Correct answer: B
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.
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.
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.
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
- Fortinet FCP_FGT_AD-7.6 Practice Test 45 - 10 Questions (Last Reviewed 08-Oct-2026)
- Fortinet FCP_FGT_AD-7.6 Practice Test 46 - 10 Questions (Last Reviewed 07-Oct-2026)
- Fortinet FCP_FGT_AD-7.6 Practice Test 47 - 10 Questions (Last Reviewed 06-Oct-2026)
- Fortinet FCP_FGT_AD-7.6 Practice Test 48 - 10 Questions (Last Reviewed 05-Oct-2026)
- Fortinet FCP_FGT_AD-7.6 Practice Test 49 - 10 Questions (Last Reviewed 04-Oct-2026)