NSE4 · Question #25
Examine the exhibit; then answer the question below. The Vancouver FortiGate initially had the following information in its routing table: S 172.20.0.0/16 [10/0] via 172.21.1.2, port2 C…
The correct answer is B. The 'gateway' IP address is NOT in the same subnet as the IP address of port1. The new static route isn't appearing because its configured gateway IP address is not directly reachable through the specified egress interface, preventing the FortiGate from activating the route.
Question
Examine the exhibit; then answer the question below. The Vancouver FortiGate initially had the following information in its routing table:
S 172.20.0.0/16 [10/0] via 172.21.1.2, port2 C 172.21.0.0/16 is directly connected, port2 C 172.11.11.0/24 is directly connected, port1 Afterwards, the following static route was added:
config router static edit 6 set dst 172.20.1.0 255.255.255.0 set pririoty 0 set device port1 set gateway 172.11.12.1 next end Since this change, the new static route is NOT showing up in the routing table. Given the information provided, which of the following describes the cause of this problem?
Exhibit
Options
- AThe subnet 172.20.1.0/24 is overlapped with the subnet of one static route that is already in the
- BThe 'gateway' IP address is NOT in the same subnet as the IP address of port1.
- CThe priority is 0, which means that the route will remain inactive.
- DThe static route configuration is missing the distance setting.
How the community answered
(37 responses)- A3% (1)
- B81% (30)
- C5% (2)
- D11% (4)
Why each option
The new static route isn't appearing because its configured gateway IP address is not directly reachable through the specified egress interface, preventing the FortiGate from activating the route.
A more specific route (172.20.1.0/24) would normally be preferred over a less specific one (172.20.0.0/16) if both are valid, so overlap itself doesn't prevent installation.
For a static route to be active and installed in the routing table, its specified gateway IP address (172.11.12.1) must be directly reachable via a connected network on the configured egress device (port1), but port1 is connected to 172.11.11.0/24, not 172.11.12.0/24.
A priority of 0 is a valid and highly preferred setting for a static route, making it more likely to be selected if the gateway is reachable, not inactive.
If the distance setting is missing for a static route, it defaults to 10, which does not prevent the route from being installed if all other conditions, like gateway reachability, are met.
Concept tested: FortiGate static route gateway reachability
Source: https://docs.fortinet.com/document/fortigate/7.4.0/admin-guides/714088/routing
Topics
Community Discussion
No community discussion yet for this question.