Pass Your LPI 102-500 Exam Easy!

This explains another Linux operation, namely Run userdel -r oldsvc with the required permissions and backups., where userdel removes the account records and -r also removes its home and mail spool where supported. It does not explain why Lock the account password with passwd -l employee and separately assess other authentication paths. satisfies the stated condition.

This explains another Linux operation, namely Create an appropriate system account with useradd -r -s /usr/sbin/nologin svcname (path distro dependent)., where A system-account UID allocation and non-login shell reduce interactive access when no shell is needed. It does not explain why Lock the account password with passwd -l employee and separately assess other authentication paths. satisfies the stated condition.

This explains another Linux operation, namely Run getent passwd username., where getent queries the name service switch databases, including configured directory sources where available. It does not explain why Lock the account password with passwd -l employee and separately assess other authentication paths. satisfies the stated condition.

That observation checks A former service account must be deleted along with its local home directory after approved retention checks. In this scenario it does not demonstrate Lock the account password with passwd -l employee and separately assess other authentication paths.; the relevant evidence must establish Password authentication fails while the account and home directory remain for review.

That observation checks A new employee needs a local Linux login, a home directory and the configured default shell. In this scenario it does not demonstrate Lock the account password with passwd -l employee and separately assess other authentication paths.; the relevant evidence must establish Password authentication fails while the account and home directory remain for review.

That observation checks A local application needs a dedicated group before administrators can assign its log readers. In this scenario it does not demonstrate Lock the account password with passwd -l employee and separately assess other authentication paths.; the relevant evidence must establish Password authentication fails while the account and home directory remain for review.

That symptom concerns A password policy requires local user passwords to expire after 90 days. This concerns a separate requirement, not the one being tested. The relevant failure is SSH key login still succeeds despite a locked password hash. The current requirement calls for a different check.

That symptom concerns An account's interactive default shell must be changed without deleting or recreating the account. This concerns a separate requirement, not the one being tested. The relevant failure is SSH key login still succeeds despite a locked password hash. The current requirement calls for a different check.

That symptom concerns A daemon needs a low-privilege local system identity that normally should not be used for interactive login. This concerns a separate requirement, not the one being tested. The relevant failure is SSH key login still succeeds despite a locked password hash. The current requirement calls for a different check.

This fix is aimed at grep /etc/passwd misses a centrally managed account that can authenticate. and would be relevant if An administrator needs to look up a user's account record using the configured NSS sources, not just local /etc/passwd. The incident instead states SSH key login still succeeds despite a locked password hash. and needs Lock or disable additional authentication channels and expiry as required by policy.

This fix is aimed at A grep of supplementary memberships was mistaken for the account's primary group. and would be relevant if A technician wants to inspect which group is the primary group for a named account. The incident instead states SSH key login still succeeds despite a locked password hash. and needs Lock or disable additional authentication channels and expiry as required by policy.

This fix is aimed at The account disappears but the home remains because userdel ran without -r. and would be relevant if A former service account must be deleted along with its local home directory after approved retention checks. The incident instead states SSH key login still succeeds despite a locked password hash. and needs Lock or disable additional authentication channels and expiry as required by policy.

Create the account with useradd -m -s /bin/bash employee and set its password. That operation is designed for the different case: A new employee needs a local Linux login, a home directory and the configured default shell. It does not perform the specific action required here: Run userdel -r oldsvc with the required permissions and backups.

Use usermod -s /bin/bash username for an installed permitted shell. That operation is designed for the different case: An account's interactive default shell must be changed without deleting or recreating the account. It does not perform the specific action required here: Run userdel -r oldsvc with the required permissions and backups.

Use groupmod -n newgroup oldgroup. That operation is designed for the different case: The operations team renamed a local Unix group without changing its existing numeric GID. It does not perform the specific action required here: Run userdel -r oldsvc with the required permissions and backups.

This explains another Linux operation, namely Use usermod -aG docker developer., where The -a append modifier preserves the user's existing supplementary groups when -G changes membership. It does not explain why Run userdel -r oldsvc with the required permissions and backups. satisfies the stated condition.

This explains another Linux operation, namely Run getent passwd username., where getent queries the name service switch databases, including configured directory sources where available. It does not explain why Run userdel -r oldsvc with the required permissions and backups. satisfies the stated condition.

This explains another Linux operation, namely Use usermod -s /bin/bash username for an installed permitted shell., where usermod updates the shell field in the account database; the change applies to future login sessions. It does not explain why Run userdel -r oldsvc with the required permissions and backups. satisfies the stated condition.

That observation checks The operations team renamed a local Unix group without changing its existing numeric GID. In this scenario it does not demonstrate Run userdel -r oldsvc with the required permissions and backups.; the relevant evidence must establish getent passwd oldsvc returns no entry and the approved home path no longer exists.

That observation checks A technician wants to inspect which group is the primary group for a named account. In this scenario it does not demonstrate Run userdel -r oldsvc with the required permissions and backups.; the relevant evidence must establish getent passwd oldsvc returns no entry and the approved home path no longer exists.

That observation checks A new employee needs a local Linux login, a home directory and the configured default shell. In this scenario it does not demonstrate Run userdel -r oldsvc with the required permissions and backups.; the relevant evidence must establish getent passwd oldsvc returns no entry and the approved home path no longer exists.

That symptom concerns A password policy requires local user passwords to expire after 90 days. This concerns a separate requirement, not the one being tested. The relevant failure is The account disappears but the home remains because userdel ran without -r. The current requirement calls for a different check.

That symptom concerns A new employee needs a local Linux login, a home directory and the configured default shell. This concerns a separate requirement, not the one being tested. The relevant failure is The account disappears but the home remains because userdel ran without -r. The current requirement calls for a different check.

That symptom concerns A departing employee's interactive password login must be locked immediately while preserving account files for investigation. This concerns a separate requirement, not the one being tested. The relevant failure is The account disappears but the home remains because userdel ran without -r. The current requirement calls for a different check.

This fix is aimed at A grep of supplementary memberships was mistaken for the account's primary group. and would be relevant if A technician wants to inspect which group is the primary group for a named account. The incident instead states The account disappears but the home remains because userdel ran without -r. and needs Remove the approved residual home after ensuring it does not contain retained data.

This fix is aimed at grep /etc/passwd misses a centrally managed account that can authenticate. and would be relevant if An administrator needs to look up a user's account record using the configured NSS sources, not just local /etc/passwd. The incident instead states The account disappears but the home remains because userdel ran without -r. and needs Remove the approved residual home after ensuring it does not contain retained data.

This fix is aimed at The directory has group ownership set to a non-existent group name. and would be relevant if A local application needs a dedicated group before administrators can assign its log readers. The incident instead states The account disappears but the home remains because userdel ran without -r. and needs Remove the approved residual home after ensuring it does not contain retained data.

Create the group with groupadd appreaders. That operation is designed for the different case: A local application needs a dedicated group before administrators can assign its log readers. It does not perform the specific action required here: Set the maximum password age with chage -M 90 username.

Use groupmod -n newgroup oldgroup. That operation is designed for the different case: The operations team renamed a local Unix group without changing its existing numeric GID. It does not perform the specific action required here: Set the maximum password age with chage -M 90 username.

Run id -gn username to display the account's primary group name. That operation is designed for the different case: A technician wants to inspect which group is the primary group for a named account. It does not perform the specific action required here: Set the maximum password age with chage -M 90 username.

This explains another Linux operation, namely Use usermod -aG docker developer., where The -a append modifier preserves the user's existing supplementary groups when -G changes membership. It does not explain why Set the maximum password age with chage -M 90 username. satisfies the stated condition.

This explains another Linux operation, namely Run userdel -r oldsvc with the required permissions and backups., where userdel removes the account records and -r also removes its home and mail spool where supported. It does not explain why Set the maximum password age with chage -M 90 username. satisfies the stated condition.

This explains another Linux operation, namely Create the account with useradd -m -s /bin/bash employee and set its password., where useradd creates the account database entry, -m creates the initial home and -s selects the login shell. It does not explain why Set the maximum password age with chage -M 90 username. satisfies the stated condition.