Question 390
A systems administrator investigates this finding: A system begins booting but pauses before the root filesystem is available. What is the MOST directly supported cause?
Explanation
Correct Answer
An omitted storage module can make a valid root volume invisible during early boot. This explains the symptom rather than a coincidental service condition. Verification: The root filesystem mounts and init switches to the installed system.
Incorrect Answers
X-specific display assumptions do not always hold in a Wayland session. That can explain why a Linux workstation displays a Wayland session but an automation assumes an X11 server always exists, whereas the current evidence supports the initramfs must supply drivers and early root-device discovery before switching root.
The alternative describes the filesystem hierarchy separates configuration, variable service data and logs by conventional paths, which is relevant when an automation job writes service logs into the directory intended for changing application state. It does not explain this case because an omitted storage module can make a valid root volume invisible during early boot.
An accessible EFI entry cannot compensate for missing downstream boot artifacts. That can explain why a newly built Linux VM shows its firmware boot entry but not the installed kernel, whereas the current evidence supports the initramfs must supply drivers and early root-device discovery before switching root.





CompTIA Linux+ (XK0-006) Practice Tests