Question 660
A support team has applied its planned fix for this issue: An application on Linux reports no space even though a user only sees a small Documents folder. Which remaining risk should still be communicated?
Explanation
Correct Answer
Removing logs without retention review may erase incident evidence. This risk remains relevant after responding to: An application on Linux reports no space even though a user only sees a small Documents folder. The appropriate action is: Clear or relocate verified safe data based on the full filesystem analysis. It follows from: df reports filesystem-level available space while du measures directory-level consumption. Verify the immediate fix through: The target mount has sufficient free space and the application writes successfully. This is why closing the ticket should not imply all related risks have disappeared.
Incorrect Answers
Installing unsigned third-party repositories can undermine supply-chain trust. It does not establish Removing logs without retention review may erase incident evidence; the scenario instead depends on Removing logs without retention review may erase incident evidence.
World-writable or world-executable settings may create avoidable risk. The requirement instead turns on Removing logs without retention review may erase incident evidence, not this separate capability.
Editing a generated resolv.conf directly may be overwritten automatically. This is different from the required Removing logs without retention review may erase incident evidence result.