Question 210
A Linux administrator evaluates: A developer assumes kill -9 is always the safest first response to a long-running process. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A developer assumes kill -9 is always the safest first response to a long-running process), the acceptance evidence is: The selected target exits cleanly, dependent services remain healthy, and journal or process inspection records the outcome. This verifies the action (Identify the correct process tree with ps, pstree or pgrep, request a graceful SIGTERM where suitable, and escalate only when warranted.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Sending SIGKILL to the wrong PID or terminating a parent indiscriminately can lose in-flight work and unrelated services.
The observed Linux condition is: A developer assumes kill -9 is always the safest first response to a long-running process. The recommended direct administrative response is: Identify the correct process tree with ps, pstree or pgrep, request a graceful SIGTERM where suitable, and escalate only when warranted. The relevant failure or security risk is: Sending SIGKILL to the wrong PID or terminating a parent indiscriminately can lose in-flight work and unrelated services. Validate success with: The selected target exits cleanly, dependent services remain healthy, and journal or process inspection records the outcome.
Incorrect Answers
Package dependency repair and integrity verification (2.4) addresses another technical failure: Forcing installation around dependency or GPG validation may leave incompatible libraries or install tampered artifacts. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: The selected target exits cleanly, dependent services remain healthy, and journal or process inspection records the outcome.
Rootless Podman runtime and privilege boundaries (2.6) would demonstrate or implement: Container inspection identifies the intended rootless user and an authorization test confirms no unapproved host access. This choice can be useful for that problem, but it does not establish the Process signals and targeted termination control being assessed here.
Local account creation with useradd and defaults (2.2) would demonstrate or implement: An account with no intended home, wrong shell or duplicate UID can cause login failure or unexpected filesystem access. The paired-answer requirement concerns Process signals and targeted termination; this alternative does not provide the matching intervention and separate acceptance evidence.