A technician is trying to determine the reason why a Linux server is not communicating on a network. The returned network configuration is as follows: eth0: flags=4163<UP…

Question

Options

• AThe server is configured to use DHCP on a network that has multiple scope options
• BThe server is configured to use DHCP, but the DHCP server is sending an incorrect subnet mask
• CThe server is configured to use DHCP on a network that does not have a DHCP server
• DThe server is configured to use DHCP, but the DHCP server is sending an incorrect MTU setting

• A
  7% (3)
• B
  2% (1)
• C
  78% (32)
• D
  12% (5)

Explanation

The IP address 127.0.0.1 is the loopback address, not a valid network address. When a Linux system is configured for DHCP but receives no response from a DHCP server, it may fall back to the loopback address or fail to obtain any usable IP - resulting in no network communication. This is the classic symptom of a missing or unreachable DHCP server. If a DHCP server existed but sent an incorrect subnet mask (B), the server would still receive a routable IP, just with routing issues. An incorrect MTU (D) would cause fragmentation problems, not a loopback address assignment. Multiple DHCP scope options (A) would still result in a valid IP being assigned.

No community discussion yet for this question.