Question 520
A production support team notices: A password policy was edited in PAM but existing sessions remain authenticated. Which technical explanation BEST accounts for it?
Explanation
Correct Answer
Editing PAM configuration does not retroactively reauthenticate running sessions. This explains the symptom rather than a coincidental service condition. Verification: A new login enforces the intended policy.
Incorrect Answers
An effective UID alone may not identify the original accountable user. That can explain why a service account's actions are absent from audit logs after a privilege escalation, whereas the current evidence supports pAM evaluates authentication/account/session steps when a supported application invokes the stack.
The alternative describes pAM account management can deny users after successful identity verification, which is relevant when an SSH daemon is reachable but a group of directory users is denied due to account restrictions. It does not explain this case because editing PAM configuration does not retroactively reauthenticate running sessions.
A successful realm join does not ensure libc can resolve every domain UID. That can explain why a machine joined a domain but NSS name lookup fails for its users, whereas the current evidence supports pAM evaluates authentication/account/session steps when a supported application invokes the stack.





CompTIA Linux+ (XK0-006) Practice Tests