On router R1, users in the 192.168.10.0/24 LAN must reach a file server on a remote network via next-hop WAN address 209.165.200.226. Which static route on R1 will allow these file requests to reach the server?

Introduction / Context:
Static routes are manually configured paths that tell a router how to reach remote networks when dynamic routing is not used or when specific paths are preferred. In many small office scenarios, a default route is configured on the edge router to send all non-local traffic toward an upstream service provider or another router that knows the rest of the network topology.

Given Data / Assumptions:

• Local LAN: 192.168.10.0 with mask 255.255.255.0.
• Router R1 connects this LAN to a WAN link with next-hop IP 209.165.200.226.
• The file server is located on a remote network reachable beyond that next hop.
• We must choose one static route command on R1 that permits users to reach the remote server.

Concept / Approach:
When the exact remote network address is not specified or multiple external networks must be reachable, a default route is often configured. In Cisco IOS, a default route is written as ip route 0.0.0.0 0.0.0.0 next-hop, which means that any destination not found in the more specific routes will be forwarded to the specified next-hop address. Here, the upstream next-hop toward the file server is 209.165.200.226, so the default route must point to that address rather than an interface or an internal IP.

Step-by-Step Solution:
1. The LAN 192.168.10.0/24 is directly connected, so R1 already knows this network.2. Remote networks, including the one containing Server 1, are reached through the WAN next hop 209.165.200.226.3. Configure a default route so that any unknown destination is forwarded to 209.165.200.226.4. The correct Cisco IOS syntax is ip route 0.0.0.0 0.0.0.0 209.165.200.226.5. This route will send all non-local traffic from the 192.168.10.0/24 LAN to the remote file server through the next hop.

Verification / Alternative check:
After configuration, you can verify the route with show ip route on R1. The default route should appear with a 0.0.0.0/0 entry pointing to 209.165.200.226. A ping or traceroute from a LAN host to the server address can further confirm end-to-end connectivity, provided that return routes exist on the remote side.

Why Other Options Are Wrong:
Option A points the default route to an outgoing interface only; while this can work in some setups, the question specifically highlights the next-hop IP, and relying solely on an interface can cause issues with multipoint networks. Option C defines a static route for network 209.165.200.0 with the next hop inside the LAN, which is not valid and does not point to the WAN. Option D incorrectly states that 192.168.10.0 is reached via 209.165.100.250, which conflicts with the fact that 192.168.10.0 is directly connected and should not point to a remote next hop.

Common Pitfalls:
Students often forget that default routes must use 0.0.0.0 0.0.0.0 as the destination and mask. Another pitfall is pointing a route to the wrong next-hop IP or to an address that is not directly reachable, which results in routing loops or dropped packets. Always verify that the next hop is on a directly connected network of the router where the static route is configured.

Final Answer:
ip route 0.0.0.0 0.0.0.0 209.165.200.226