nerdexam
CompTIA

XK0-005 · Question #1491

A systems administrator is troubleshooting connectivity issues and trying to find out why a Linux server is not able to reach other servers on the same subnet it is connected to. When listing link…

The correct answer is D. The network interface cable is not connected to a switch. The most probable cause of the connectivity issue is that the network interface cable is not connected to a switch. This can be inferred from the output of the ip link list dev eth0 command, which shows that the network interface eth0 has the NO-CARRIER flag set. This flag…

Troubleshooting

Question

A systems administrator is troubleshooting connectivity issues and trying to find out why a Linux server is not able to reach other servers on the same subnet it is connected to. When listing link parameters, the following is presented: Based on the output above, which of following is the MOST probable cause of the issue?

Exhibit

XK0-005 question #1491 exhibit

Options

  • AThe address ac:00:11:22:33:cd is not a valid Ethernet address.
  • BThe Ethernet broadcast address should be ac:00:11:22:33:ff instead.
  • CThe network interface eth0 is using an old kernel module.
  • DThe network interface cable is not connected to a switch.

How the community answered

(23 responses)
  • A
    13% (3)
  • B
    4% (1)
  • C
    9% (2)
  • D
    74% (17)

Explanation

The most probable cause of the connectivity issue is that the network interface cable is not connected to a switch. This can be inferred from the output of the ip link list dev eth0 command, which shows that the network interface eth0 has the NO-CARRIER flag set. This flag indicates that there is no physical link detected on the interface, meaning that the cable is either unplugged

Topics

#Network troubleshooting#Physical layer#ip link command#Network interfaces

Community Discussion

No community discussion yet for this question.

Full XK0-005 Practice