Question 50
A Linux administrator evaluates: An administrator needs to verify a modified mount entry without risking a first test during production boot. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (An administrator needs to verify a modified mount entry without risking a first test during production boot), the acceptance evidence is: findmnt and mount output show the expected UUID at its intended path after a controlled reboot test. This verifies the action (Record the correct filesystem UUID and supported mount options in /etc/fstab and test the entry with mount before restarting the host.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Using a changing /dev/sdX name or wrong filesystem type can mount the wrong disk or drop the system into emergency mode.
The observed Linux condition is: An administrator needs to verify a modified mount entry without risking a first test during production boot. The recommended direct administrative response is: Record the correct filesystem UUID and supported mount options in /etc/fstab and test the entry with mount before restarting the host. The relevant failure or security risk is: Using a changing /dev/sdX name or wrong filesystem type can mount the wrong disk or drop the system into emergency mode. Validate success with: findmnt and mount output show the expected UUID at its intended path after a controlled reboot test.
Incorrect Answers
Hardware and device discovery (1.2) would demonstrate or implement: Guessing a driver without confirming the kernel-visible hardware can mask a disconnected device or wrong bus identity. This choice can be useful for that problem, but it does not establish the Persistent filesystem mounting by UUID control being assessed here.
Shell output redirection stdout stderr and append (1.5) would demonstrate or implement: A controlled command writes successes and errors to the separate expected logs with the intended retention behavior. The required paired action and test concerns Persistent filesystem mounting by UUID; a passing result for this alternative could leave that requirement unresolved.
Shell text processing pipelines (1.5) addresses another technical failure: Grepping an entire unfiltered log or using a wrong delimiter can silently miscount events or report unrelated fields. The paired-answer requirement concerns Persistent filesystem mounting by UUID; this alternative does not provide the matching intervention and separate acceptance evidence.