Question 200
A Linux administrator evaluates: A quarterly audit requires the password expiry and last-change fields for a selected local account. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A quarterly audit requires the password expiry and last-change fields for a selected local account), the acceptance evidence is: id and chage reports match the approved group and expiration policy, and a controlled login confirms the change. This verifies the action (Update supplementary groups, account locks or expiry using usermod, passwd and chage, then verify effective membership and aging settings.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Overwriting rather than appending supplementary groups or neglecting account expiry can remove authorized access or leave stale logins.
The observed Linux condition is: A quarterly audit requires the password expiry and last-change fields for a selected local account. The recommended direct administrative response is: Update supplementary groups, account locks or expiry using usermod, passwd and chage, then verify effective membership and aging settings. The relevant failure or security risk is: Overwriting rather than appending supplementary groups or neglecting account expiry can remove authorized access or leave stale logins. Validate success with: id and chage reports match the approved group and expiration policy, and a controlled login confirms the change.
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 Groups and account expiration management control being assessed here.
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. This case instead tests Groups and account expiration management; the choice measures or changes another part of the system.
Recurring and one-time job scheduling (2.3) would demonstrate or implement: A job defined in the wrong user crontab or scheduled at an incorrect time may never run when required. The required paired action and test concerns Groups and account expiration management; a passing result for this alternative could leave that requirement unresolved.