Question 20
A Linux administrator evaluates: A backup plan needs to distinguish home directories, static configuration and variable service data. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: A backup plan needs to distinguish home directories, static configuration and variable service data. The recommended direct administrative response is: Locate system-specific configuration, transient runtime data, device nodes, user homes and variable application data under their appropriate FHS paths. The relevant failure or security risk is: Placing persistent configuration or operational logs under temporary paths can cause data loss or a broken service on reboot. Validate success with: Inspection shows persistent settings in /etc and expected service state or logs in appropriate paths such as /var or /run.
For the specific observation (A backup plan needs to distinguish home directories, static configuration and variable service data), the acceptance evidence is: Inspection shows persistent settings in /etc and expected service state or logs in appropriate paths such as /var or /run. This verifies the action (Locate system-specific configuration, transient runtime data, device nodes, user homes and variable application data under their appropriate FHS paths.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Placing persistent configuration or operational logs under temporary paths can cause data loss or a broken service on reboot.
Incorrect Answers
Persistent network configuration with nmcli (1.4) would demonstrate or implement: Changing an ephemeral interface address without saving its connection profile can remove remote access at restart. This case instead tests Filesystem Hierarchy Standard paths; the choice measures or changes another part of the system.
Route and socket inspection with IP and ss (1.4) would demonstrate or implement: The route lookup selects the intended next hop and ss shows the service listening on the required address and port. The required paired action and test concerns Filesystem Hierarchy Standard paths; a passing result for this alternative could leave that requirement unresolved.
DNS resolver diagnosis with dig and hosts precedence (1.4) addresses another technical failure: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched. The paired-answer requirement concerns Filesystem Hierarchy Standard paths; this alternative does not provide the matching intervention and separate acceptance evidence.