Question 40
A Linux administrator evaluates: A hardware inventory task must distinguish a kernel-recognized NIC from an unconnected switch port. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: A hardware inventory task must distinguish a kernel-recognized NIC from an unconnected switch port. The recommended direct administrative response is: Correlate lspci, lsusb, lscpu, lsblk, dmesg and relevant /sys device information to identify Linux hardware before modifying drivers. The relevant failure or security risk is: Guessing a driver without confirming the kernel-visible hardware can mask a disconnected device or wrong bus identity. Validate success with: Hardware inventory and kernel events agree on the expected device and its reported bus, capacity or driver.
For the specific observation (A hardware inventory task must distinguish a kernel-recognized NIC from an unconnected switch port), the acceptance evidence is: Hardware inventory and kernel events agree on the expected device and its reported bus, capacity or driver. This verifies the action (Correlate lspci, lsusb, lscpu, lsblk, dmesg and relevant /sys device information to identify Linux hardware before modifying drivers.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Guessing a driver without confirming the kernel-visible hardware can mask a disconnected device or wrong bus identity.
Incorrect Answers
Shell text processing pipelines (1.5) would demonstrate or implement: The pipeline returns the expected test rows and field values on representative input, leaving source data unchanged. This choice can be useful for that problem, but it does not establish the Hardware and device discovery control being assessed here.
Shell output redirection stdout stderr and append (1.5) would demonstrate or implement: Confusing 2> with > or using overwrite when append is required can lose evidence or hide errors. This case instead tests Hardware and device discovery; the choice measures or changes another part of the system.
GRUB kernel boot parameter recovery (1.1) addresses another technical failure: An incorrect kernel or root filesystem parameter can stop the host before its normal init process starts. The required paired action and test concerns Hardware and device discovery; a passing result for this alternative could leave that requirement unresolved.