Question 690
A Linux administrator evaluates: An operations team must identify whether a memory leak or normal page cache is responsible for a rising used-memory graph. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (An operations team must identify whether a memory leak or normal page cache is responsible for a rising used-memory graph), the acceptance evidence is: Memory and swap metrics return within tested thresholds and the protected service survives sustained representative load. This verifies the action (Inspect free, vmstat, /proc/meminfo and kernel OOM events to distinguish reclaimable cache, active swapping and actual memory exhaustion.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Treating file cache as unavailable RAM or blindly disabling swap can obscure the application responsible for OOM kills.
The observed Linux condition is: An operations team must identify whether a memory leak or normal page cache is responsible for a rising used-memory graph. The recommended direct administrative response is: Inspect free, vmstat, /proc/meminfo and kernel OOM events to distinguish reclaimable cache, active swapping and actual memory exhaustion. The relevant failure or security risk is: Treating file cache as unavailable RAM or blindly disabling swap can obscure the application responsible for OOM kills. Validate success with: Memory and swap metrics return within tested thresholds and the protected service survives sustained representative load.
Incorrect Answers
Inode exhaustion versus free space (5.2) would demonstrate or implement: A filesystem can reject new files when its inode supply is exhausted even if many data blocks remain free. This case instead tests Memory pressure OOM killer and swapping; the choice measures or changes another part of the system.
SLO-based monitoring and actionable alert thresholds (5.1) addresses another technical failure: An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach. The required paired action and test concerns Memory pressure OOM killer and swapping; a passing result for this alternative could leave that requirement unresolved.
ACL mask and directory traversal permission failures (5.4) would demonstrate or implement: An authorized process reaches the intended path, while unrelated users still fail read or execute tests. The paired-answer requirement concerns Memory pressure OOM killer and swapping; this alternative does not provide the matching intervention and separate acceptance evidence.