Question 440
An instructor presents the following real-world Linux situation: An administrator finds a disk called /dev/sdb but cannot understand why a separate /sys tree contains hardware information. Which observation would BEST verify that the problem was resolved?
Explanation
Correct Answer
A device has an accessible /dev entry while relevant attributes can be inspected beneath /sys. This is specific evidence for the stated requirement. The explanation is: Linux presents device-access nodes and sysfs metadata through different virtual filesystem interfaces. The required action is: Use /dev for device nodes and /sys for exposed kernel device and driver attributes.
Incorrect Answers
The alternative measures an outcome associated with: Procfs represents kernel and process information and is not a general-purpose persistent document store. It does not verify the stated failure. Here linux presents device-access nodes and sysfs metadata through different virtual filesystem interfaces. Confirm “A device has an accessible /dev entry while relevant attributes can be inspected beneath /sys”.
“The application log is found at its configured path and survives an ordinary user-session logout” tests the technical condition: The /var hierarchy includes variable system data such as logs, whereas /tmp is primarily for temporary files. The current control has another acceptance boundary: Linux presents device-access nodes and sysfs metadata through different virtual filesystem interfaces. Its direct evidence is “A device has an accessible /dev entry while relevant attributes can be inspected beneath /sys”.
This test can succeed without resolving the cause described here. It addresses: Top displays changing runtime measurements, and a CPU-utilization sample is distinct from total process lifetime. The relevant causal dependency is: Linux presents device-access nodes and sysfs metadata through different virtual filesystem interfaces. The required validation is “A device has an accessible /dev entry while relevant attributes can be inspected beneath /sys”.