Question 510
A user working at a Linux terminal reports: A security reviewer wants historical evidence of a previous interactive login and a junior technician checks only a current-process list. What should the learner do to satisfy the requirement?
Explanation
Correct Answer
Use last to review available login records, recognizing retention and logging limitations. This directly addresses the reported situation. Why it works: Login history is recorded separately from a snapshot of processes currently running. Acceptance evidence: A known prior login appears in the available history even after that session terminates.
Incorrect Answers
The proposed action focuses on a control governed by: Inspect account information through approved tools and recognize /etc/shadow as the protected password-hash database on typical systems. In this question the binding condition is: Use last to review available login records, recognizing retention and logging limitations. Applying “Use last to review available login records, recognizing retention and logging limitations” addresses that specific cause instead.
This option would change the part of the system described by: Use a separate normal user account for everyday work and elevate only specific approved commands when necessary. The reported behavior instead arises because use last to review available login records, recognizing retention and logging limitations. The direct remediation is “Use last to review available login records, recognizing retention and logging limitations”.
Use sudo for the one authorized administrative command rather than an unrestricted long-lived root session. That explains why “Use sudo for the one authorized administrative command rather than an unrestricted long-lived root session” is useful for its own dependency, but the present failure follows a different constraint: Use last to review available login records, recognizing retention and logging limitations. The targeted correction is “Use last to review available login records, recognizing retention and logging limitations”.