Question 590
A Linux administrator evaluates: A Linux alert reports a full filesystem but engineers must distinguish block exhaustion from inode exhaustion. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: A Linux alert reports a full filesystem but engineers must distinguish block exhaustion from inode exhaustion. The recommended direct administrative response is: Compare df -h and df -i, locate directories with excessive small-file creation and remediate safely according to retention policy. The relevant failure or security risk is: A filesystem can reject new files when its inode supply is exhausted even if many data blocks remain free. Validate success with: Inode utilization returns below the operational threshold and the application creates a new file successfully.
For the specific observation (A Linux alert reports a full filesystem but engineers must distinguish block exhaustion from inode exhaustion), the acceptance evidence is: Inode utilization returns below the operational threshold and the application creates a new file successfully. This verifies the action (Compare df -h and df -i, locate directories with excessive small-file creation and remediate safely according to retention policy.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: A filesystem can reject new files when its inode supply is exhausted even if many data blocks remain free.
Incorrect Answers
SSH key and certificate failure diagnosis (5.4) addresses another technical failure: Disabling strict host checks or accepting unknown certificates during an incident can mask a man-in-the-middle attack. This case instead tests Inode exhaustion versus free space; the choice measures or changes another part of the system.
Listener and firewall differentiation on Linux (5.3) would demonstrate or implement: The service listens on the intended interface and a permitted remote connection succeeds while an unapproved source remains blocked. The required paired action and test concerns Inode exhaustion versus free space; a passing result for this alternative could leave that requirement unresolved.
SELinux denial versus traditional permission fault (5.4) would demonstrate or implement: Turning SELinux off or using chmod 777 cannot reliably solve a labeling issue and can weaken host security. The paired-answer requirement concerns Inode exhaustion versus free space; this alternative does not provide the matching intervention and separate acceptance evidence.