Question 280
A Linux administrator evaluates: A persistent job container needs application state kept on host storage rather than baked into a reusable image. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: A persistent job container needs application state kept on host storage rather than baked into a reusable image. The recommended direct administrative response is: Mount a supported named volume or deliberately scoped bind mount for persistent container application data, then test recreation. The relevant failure or security risk is: Writing databases only inside a disposable container writable layer can lose data when the container is replaced. Validate success with: A newly created replacement container reads the expected previous data from the volume with correct access controls.
For the specific observation (A persistent job container needs application state kept on host storage rather than baked into a reusable image), the acceptance evidence is: A newly created replacement container reads the expected previous data from the volume with correct access controls. This verifies the action (Mount a supported named volume or deliberately scoped bind mount for persistent container application data, then test recreation.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Writing databases only inside a disposable container writable layer can lose data when the container is replaced.
Incorrect Answers
Local account creation with useradd and defaults (2.2) addresses another technical failure: An account with no intended home, wrong shell or duplicate UID can cause login failure or unexpected filesystem access. This choice can be useful for that problem, but it does not establish the Persistent container data volumes control being assessed here.
Distribution package manager and repository selection (2.4) would demonstrate or implement: The intended package version and signature/repository provenance are confirmed, and its service or executable starts successfully. This case instead tests Persistent container data volumes; the choice measures or changes another part of the system.
Systemd service start versus boot enablement (2.5) would demonstrate or implement: A service started manually may still be disabled at boot, and an enabled service need not be running yet. The paired-answer requirement concerns Persistent container data volumes; this alternative does not provide the matching intervention and separate acceptance evidence.