Question 170
A Linux administrator evaluates: A symlink inside an application tree becomes broken after its referenced file is moved. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: A symlink inside an application tree becomes broken after its referenced file is moved. The recommended direct administrative response is: Choose ln for a hard link or ln -s for a symbolic link based on filesystem boundaries and desired target behavior, then inspect inode and link properties. The relevant failure or security risk is: A hard link cannot span filesystem boundaries; a symlink can become dangling after the named target is removed. Validate success with: stat and readlink show the intended link type and a controlled target change behaves as expected.
For the specific observation (A symlink inside an application tree becomes broken after its referenced file is moved), the acceptance evidence is: stat and readlink show the intended link type and a controlled target change behaves as expected. This verifies the action (Choose ln for a hard link or ln -s for a symbolic link based on filesystem boundaries and desired target behavior, then inspect inode and link properties.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: A hard link cannot span filesystem boundaries; a symlink can become dangling after the named target is removed.
Incorrect Answers
Package dependency repair and integrity verification (2.4) would demonstrate or implement: Forcing installation around dependency or GPG validation may leave incompatible libraries or install tampered artifacts. This choice can be useful for that problem, but it does not establish the Linux symbolic versus hard links control being assessed here.
Systemd service start versus boot enablement (2.5) addresses another technical failure: A service started manually may still be disabled at boot, and an enabled service need not be running yet. This case instead tests Linux symbolic versus hard links; the choice measures or changes another part of the system.
Recurring and one-time job scheduling (2.3) would demonstrate or implement: A controlled schedule invocation records the intended user, environment, timestamp and job result. The paired-answer requirement concerns Linux symbolic versus hard links; this alternative does not provide the matching intervention and separate acceptance evidence.