Question 240
A Linux administrator evaluates: A third-party RPM reports an untrusted signing key and the team needs to authenticate the intended publisher. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A third-party RPM reports an untrusted signing key and the team needs to authenticate the intended publisher), the acceptance evidence is: A controlled package transaction resolves dependencies and reports trusted signatures with a healthy executable afterward. This verifies the action (Inspect package-manager dependency errors, installed versions and trusted signatures before repairing broken packages or excluding a conflict.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Forcing installation around dependency or GPG validation may leave incompatible libraries or install tampered artifacts.
The observed Linux condition is: A third-party RPM reports an untrusted signing key and the team needs to authenticate the intended publisher. The recommended direct administrative response is: Inspect package-manager dependency errors, installed versions and trusted signatures before repairing broken packages or excluding a conflict. The relevant failure or security risk is: Forcing installation around dependency or GPG validation may leave incompatible libraries or install tampered artifacts. Validate success with: A controlled package transaction resolves dependencies and reports trusted signatures with a healthy executable afterward.
Incorrect Answers
Process signals and targeted termination (2.3) would demonstrate or implement: The selected target exits cleanly, dependent services remain healthy, and journal or process inspection records the outcome. This choice can be useful for that problem, but it does not establish the Package dependency repair and integrity verification control being assessed here.
Persistent container data volumes (2.6) addresses another technical failure: Writing databases only inside a disposable container writable layer can lose data when the container is replaced. The required paired action and test concerns Package dependency repair and integrity verification; a passing result for this alternative could leave that requirement unresolved.
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 Package dependency repair and integrity verification; this alternative does not provide the matching intervention and separate acceptance evidence.