Question 570
A Linux administrator evaluates: A rescue console has access to the previous boot journal and the operator needs the exact failing mount unit. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A rescue console has access to the previous boot journal and the operator needs the exact failing mount unit), the acceptance evidence is: A controlled restart reaches the intended target, and the previous boot error is absent from the new journal. This verifies the action (Use the bootloader, emergency-mode logs and journalctl -b or prior-boot records to isolate a failed startup dependency before a controlled correction.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Blindly reinstalling the kernel or disabling essential units can destroy the evidence and leave the actual root-device fault unresolved.
The observed Linux condition is: A rescue console has access to the previous boot journal and the operator needs the exact failing mount unit. The recommended direct administrative response is: Use the bootloader, emergency-mode logs and journalctl -b or prior-boot records to isolate a failed startup dependency before a controlled correction. The relevant failure or security risk is: Blindly reinstalling the kernel or disabling essential units can destroy the evidence and leave the actual root-device fault unresolved. Validate success with: A controlled restart reaches the intended target, and the previous boot error is absent from the new journal.
Incorrect Answers
SLO-based monitoring and actionable alert thresholds (5.1) would demonstrate or implement: A controlled service degradation crosses the documented threshold and produces an actionable alert with the relevant host and timestamp. This choice can be useful for that problem, but it does not establish the Linux boot failure recovery using journal and GRUB evidence control being assessed here.
Disk IO wait and throughput bottleneck diagnosis (5.5) addresses another technical failure: Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device. This case instead tests Linux boot failure recovery using journal and GRUB evidence; the choice measures or changes another part of the system.
MTU and path fragmentation troubleshooting (5.3) would demonstrate or implement: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass. The required paired action and test concerns Linux boot failure recovery using journal and GRUB evidence; a passing result for this alternative could leave that requirement unresolved.