Question 270
A Linux administrator evaluates: A new Linux service should isolate container workloads under dedicated non-root identities rather than reuse host root. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A new Linux service should isolate container workloads under dedicated non-root identities rather than reuse host root), the acceptance evidence is: Container inspection identifies the intended rootless user and an authorization test confirms no unapproved host access. This verifies the action (Run suitable application containers with Podman as an unprivileged user and verify UID mappings, mounts and resource access.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Launching every container as privileged root expands access to the host kernel and filesystem unnecessarily.
The observed Linux condition is: A new Linux service should isolate container workloads under dedicated non-root identities rather than reuse host root. The recommended direct administrative response is: Run suitable application containers with Podman as an unprivileged user and verify UID mappings, mounts and resource access. The relevant failure or security risk is: Launching every container as privileged root expands access to the host kernel and filesystem unnecessarily. Validate success with: Container inspection identifies the intended rootless user and an authorization test confirms no unapproved host access.
Incorrect Answers
Groups and account expiration management (2.2) would demonstrate or implement: id and chage reports match the approved group and expiration policy, and a controlled login confirms the change. This case instead tests Rootless Podman runtime and privilege boundaries; the choice measures or changes another part of the system.
Distribution package manager and repository selection (2.4) would demonstrate or implement: Running the wrong distribution package tool or installing from an untrusted arbitrary repository can leave unresolved dependencies or compromised packages. The required paired action and test concerns Rootless Podman runtime and privilege boundaries; a passing result for this alternative could leave that requirement unresolved.
Process signals and targeted termination (2.3) addresses another technical failure: Sending SIGKILL to the wrong PID or terminating a parent indiscriminately can lose in-flight work and unrelated services. The paired-answer requirement concerns Rootless Podman runtime and privilege boundaries; this alternative does not provide the matching intervention and separate acceptance evidence.