Question 180
A production support team notices: A new server has an IP address but cannot reach an off-subnet destination. What is the MOST directly supported cause?
Explanation
Correct Answer
An interface address alone provides only directly connected route knowledge. This mechanism fits the stated evidence. Validate it by checking that ip route get selects the correct gateway for remote traffic.
Incorrect Answers
The alternative describes iPv6 has separate address and routing tables from IPv4, which is relevant when a Linux node loses IPv6 access because only an IPv4 default route exists. It does not explain this case because an interface address alone provides only directly connected route knowledge.
It would account for a firewall permits a service but the process binds only to 127.0.0.1, not the current evidence. For this incident, an interface address alone provides only directly connected route knowledge; the alternative mechanism leaves that distinction unexplained.
The wrong on-link route can ARP for destinations that should use a gateway. That can explain why a corporate subnet is /26 but the host was configured with /24, whereas the current evidence supports the kernel needs a correct default route to send traffic outside connected prefixes.





CompTIA Linux+ (XK0-006) Practice Tests