Difficulty: Medium
Correct Answer: 1 only
Explanation:
Introduction / Context:
At a small Internet edge, the minimal requirement for outbound Internet access is a default route on the gateway pointing toward the ISP's next hop. Internal routing protocols may be unnecessary if the site is a single LAN or if internal routers already default to the gateway. Understanding when a static default is sufficient avoids extra complexity.
Given Data / Assumptions:
Concept / Approach:
A default route (0.0.0.0/0) on the gateway is sufficient to forward unknown destinations to the ISP. As long as internal hosts know to reach the gateway for off-net traffic (via their default gateway or their own routing), no additional RIP configuration is required on the gateway to send traffic out. Lines 2 and 3 would start RIP and advertise/learn routes, but they are not strictly necessary to achieve outbound access. Line 4 is invalid RIP syntax; originating a default in RIP uses different commands (for example, default-information originate in other protocols, or ip default-network historically) and is not shown correctly here.
Step-by-Step Solution:
Verification / Alternative check:
From a host, ping/trace to an Internet address; on the gateway, show ip route should list the static default and show ip cef should resolve the next hop. If internal routing is needed, deploy it separately—but not strictly required by this question.
Why Other Options Are Wrong:
“3 only” (RIP network statement) does nothing alone for Internet access.
“1, 2 and 4” includes invalid line 4; starting RIP is unnecessary for simple outbound access.
“1 and 4” again includes an invalid command.
Common Pitfalls:
Assuming a routing protocol is mandatory at the edge; forgetting to configure NAT for private inside networks; misunderstanding that a default route by itself enables outbound traffic if return routing (via ISP) and NAT are in place.
Final Answer:
1 only
Discussion & Comments