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 Create the group with groupadd appreaders. satisfies the stated condition.

This explains another Linux operation, namely Lock the account password with passwd -l employee and separately assess other authentication paths., where passwd -l prefixes the stored password hash with an invalid marker; it does not by itself disable SSH public-key or other authentication. It does not explain why Create the group with groupadd appreaders. satisfies the stated condition.

This explains another Linux operation, namely Set the maximum password age with chage -M 90 username., where chage modifies password-aging policy stored with the account in the shadow database. It does not explain why Create the group with groupadd appreaders. satisfies the stated condition.

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 Create the group with groupadd appreaders.; the relevant evidence must establish getent group appreaders returns the new group entry with its expected name.

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 Create the group with groupadd appreaders.; the relevant evidence must establish getent group appreaders returns the new group entry with its expected name.

That observation checks An account's interactive default shell must be changed without deleting or recreating the account. In this scenario it does not demonstrate Create the group with groupadd appreaders.; the relevant evidence must establish getent group appreaders returns the new group entry with its expected name.

That symptom concerns An administrator needs to identify which file stores local password hashes rather than account names and shell paths. This concerns a separate requirement, not the one being tested. The relevant failure is The directory has group ownership set to a non-existent group name. 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 The directory has group ownership set to a non-existent group name. 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 directory has group ownership set to a non-existent group name. The current requirement calls for a different check.

This fix is aimed at A privileged interactive shell was assigned to the daemon account unnecessarily. and would be relevant if A daemon needs a low-privilege local system identity that normally should not be used for interactive login. The incident instead states The directory has group ownership set to a non-existent group name. and needs Create the correct group first, then assign ownership and intended membership.

This fix is aimed at SSH key login still succeeds despite a locked password hash. and would be relevant if A departing employee's interactive password login must be locked immediately while preserving account files for investigation. The incident instead states The directory has group ownership set to a non-existent group name. and needs Create the correct group first, then assign ownership and intended membership.

This fix is aimed at The administrator changed the SHELL variable manually but login still launches the prior shell. and would be relevant if An account's interactive default shell must be changed without deleting or recreating the account. The incident instead states The directory has group ownership set to a non-existent group name. and needs Create the correct group first, then assign ownership and intended membership.

Run userdel -r oldsvc with the required permissions and backups. That operation is designed for the different case: A former service account must be deleted along with its local home directory after approved retention checks. It does not perform the specific action required here: Use groupmod -n newgroup oldgroup.

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: Use groupmod -n newgroup oldgroup.

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: Use groupmod -n newgroup oldgroup.

This explains another Linux operation, namely Inspect the protected /etc/shadow database under appropriate privileges., where /etc/shadow stores password hash and aging fields, separate from the world-readable account metadata in /etc/passwd. It does not explain why Use groupmod -n newgroup oldgroup. satisfies the stated condition.

This explains another Linux operation, namely Run id -gn username to display the account's primary group name., where id retrieves the user's UID/GID identity details from system account sources; the primary GID is not merely a supplementary group entry. It does not explain why Use groupmod -n newgroup oldgroup. 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 Use groupmod -n newgroup oldgroup. satisfies the stated condition.

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 Use groupmod -n newgroup oldgroup.; the relevant evidence must establish getent group newgroup reports the original GID and the old name is no longer found.

That observation checks An administrator needs to look up a user's account record using the configured NSS sources, not just local /etc/passwd. In this scenario it does not demonstrate Use groupmod -n newgroup oldgroup.; the relevant evidence must establish getent group newgroup reports the original GID and the old name is no longer found.

That observation checks A departing employee's interactive password login must be locked immediately while preserving account files for investigation. In this scenario it does not demonstrate Use groupmod -n newgroup oldgroup.; the relevant evidence must establish getent group newgroup reports the original GID and the old name is no longer found.

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 A new group was created with a different GID, leaving files owned by the original group ID. The current requirement calls for a different check.

That symptom concerns A former service account must be deleted along with its local home directory after approved retention checks. This concerns a separate requirement, not the one being tested. The relevant failure is A new group was created with a different GID, leaving files owned by the original group ID. The current requirement calls for a different check.

That symptom concerns A local application needs a dedicated group before administrators can assign its log readers. This concerns a separate requirement, not the one being tested. The relevant failure is A new group was created with a different GID, leaving files owned by the original group ID. The current requirement calls for a different check.

This fix is aimed at The administrator changed the SHELL variable manually but login still launches the prior shell. and would be relevant if An account's interactive default shell must be changed without deleting or recreating the account. The incident instead states A new group was created with a different GID, leaving files owned by the original group ID. and needs Rename the existing group with groupmod rather than creating an unrelated GID.

This fix is aimed at A plain usermod -G docker developer replaced the entire supplementary group list. and would be relevant if A developer must be added to the supplementary docker group without losing current secondary groups. The incident instead states A new group was created with a different GID, leaving files owned by the original group ID. and needs Rename the existing group with groupmod rather than creating an unrelated GID.

This fix is aimed at Passwords were treated as hashes in /etc/passwd even though its password field is a placeholder. and would be relevant if An administrator needs to identify which file stores local password hashes rather than account names and shell paths. The incident instead states A new group was created with a different GID, leaving files owned by the original group ID. and needs Rename the existing group with groupmod rather than creating an unrelated GID.

Inspect the protected /etc/shadow database under appropriate privileges. That operation is designed for the different case: An administrator needs to identify which file stores local password hashes rather than account names and shell paths. It does not perform the specific action required here: Create an appropriate system account with useradd -r -s /usr/sbin/nologin svcname (path distro dependent).

Use usermod -aG docker developer. That operation is designed for the different case: A developer must be added to the supplementary docker group without losing current secondary groups. It does not perform the specific action required here: Create an appropriate system account with useradd -r -s /usr/sbin/nologin svcname (path distro dependent).

Run userdel -r oldsvc with the required permissions and backups. That operation is designed for the different case: A former service account must be deleted along with its local home directory after approved retention checks. It does not perform the specific action required here: Create an appropriate system account with useradd -r -s /usr/sbin/nologin svcname (path distro dependent).

This explains another Linux operation, namely Run id -gn username to display the account's primary group name., where id retrieves the user's UID/GID identity details from system account sources; the primary GID is not merely a supplementary group entry. It does not explain why Create an appropriate system account with useradd -r -s /usr/sbin/nologin svcname (path distro dependent). satisfies the stated condition.

This explains another Linux operation, namely Inspect the protected /etc/shadow database under appropriate privileges., where /etc/shadow stores password hash and aging fields, separate from the world-readable account metadata in /etc/passwd. It does not explain why Create an appropriate system account with useradd -r -s /usr/sbin/nologin svcname (path distro dependent). satisfies the stated condition.

This explains another Linux operation, namely Use groupmod -n newgroup oldgroup., where The -n option changes the group name while retaining its numeric group identifier. It does not explain why Create an appropriate system account with useradd -r -s /usr/sbin/nologin svcname (path distro dependent). satisfies the stated condition.