200-301 Question 318
Single answerA network engineer configured a static route on a router using the command 'ip route 192.168.10.0 255.255.255.0 10.0.0.1'. After deploying the configuration, users on the 192.168.20.0/24 subnet report they are unable to reach the 192.168.10.0/24 subnet. What could be the most likely cause of this issue?
- A
The next-hop IP address 10.0.0.1 is unreachable from the router.
- B
The configured static route is missing the administrative distance value.
- C
The subnet mask for the static route is incorrect.
- D
The 192.168.20.0/24 subnet does not have a route back to 192.168.10.0/24.
Show answer and explanation
Correct answer: A
Explanation
The static route points to a next-hop address (10.0.0.1). If this next-hop address is unreachable from the router, the route will not be functional, and traffic will not reach the 192.168.10.0/24 network. The issue must be resolved by ensuring the next-hop IP address is reachable.
- A. Correct.
If the next-hop IP address (10.0.0.1) is unreachable, the static route will not work, and packets destined for 192.168.10.0/24 will be dropped.
- B. Incorrect.
A static route does not require an administrative distance to function. The default administrative distance for static routes is 1, which is sufficient for this configuration.
- C. Incorrect.
The subnet mask 255.255.255.0 is correct for the 192.168.10.0/24 network. Changing the subnet mask would not resolve the issue.
- D. Incorrect.
While a return route is necessary for bidirectional communication, this would not prevent users from 192.168.20.0/24 from initially sending packets to 192.168.10.0/24. The issue lies with the static route configuration.