Question 250
A Linux administrator evaluates: A new systemd unit exists on disk but service state needs verification after it is enabled. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: A new systemd unit exists on disk but service state needs verification after it is enabled. The recommended direct administrative response is: Use systemctl start, enable, disable and status according to whether immediate activation or future boot persistence is required. The relevant failure or security risk is: A service started manually may still be disabled at boot, and an enabled service need not be running yet. Validate success with: systemctl is-active and is-enabled give the intended independent states before and after a controlled restart.
For the specific observation (A new systemd unit exists on disk but service state needs verification after it is enabled), the acceptance evidence is: systemctl is-active and is-enabled give the intended independent states before and after a controlled restart. This verifies the action (Use systemctl start, enable, disable and status according to whether immediate activation or future boot persistence is required.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: A service started manually may still be disabled at boot, and an enabled service need not be running yet.
Incorrect Answers
Find files by permissions and type without destructive action (2.1) addresses another technical failure: An unscoped recursive command can select unrelated system files or follow unexpected paths and damage permissions. The case states: A new systemd unit exists on disk but service state needs verification after it is enabled. The most direct paired action and test is: Use systemctl start, enable, disable and status according to whether immediate activation or future boot persistence is required.
Persistent container data volumes (2.6) would demonstrate or implement: A newly created replacement container reads the expected previous data from the volume with correct access controls. This case instead tests Systemd service start versus boot enablement; the choice measures or changes another part of the system.
Rootless Podman runtime and privilege boundaries (2.6) would demonstrate or implement: Launching every container as privileged root expands access to the host kernel and filesystem unnecessarily. The required paired action and test concerns Systemd service start versus boot enablement; a passing result for this alternative could leave that requirement unresolved.