Pass Your LPI 102-500 Exam Easy!

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.

That observation checks A local application needs a dedicated group before administrators can assign its log readers. In this scenario it does not demonstrate Create an appropriate system account with useradd -r -s /usr/sbin/nologin svcname (path distro dependent).; the relevant evidence must establish getent passwd svcname shows the configured nologin shell and service runtime can use the UID.

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 an appropriate system account with useradd -r -s /usr/sbin/nologin svcname (path distro dependent).; the relevant evidence must establish getent passwd svcname shows the configured nologin shell and service runtime can use the UID.

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 Create an appropriate system account with useradd -r -s /usr/sbin/nologin svcname (path distro dependent).; the relevant evidence must establish getent passwd svcname shows the configured nologin shell and service runtime can use the UID.

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 A privileged interactive shell was assigned to the daemon account unnecessarily. The current requirement calls for a different check.

That symptom concerns A developer must be added to the supplementary docker group without losing current secondary groups. This concerns a separate requirement, not the one being tested. The relevant failure is A privileged interactive shell was assigned to the daemon account unnecessarily. The current requirement calls for a different check.

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 A privileged interactive shell was assigned to the daemon account unnecessarily. The current requirement calls for a different check.

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 A privileged interactive shell was assigned to the daemon account unnecessarily. and needs Set a valid nologin shell and tighten the service account's privileges.

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 privileged interactive shell was assigned to the daemon account unnecessarily. and needs Set a valid nologin shell and tighten the service account's privileges.

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 privileged interactive shell was assigned to the daemon account unnecessarily. and needs Set a valid nologin shell and tighten the service account's privileges.

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: Use usermod -s /bin/bash username for an installed permitted shell.

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 usermod -s /bin/bash username for an installed permitted shell.

Run getent passwd username. That operation is designed for the different case: An administrator needs to look up a user's account record using the configured NSS sources, not just local /etc/passwd. It does not perform the specific action required here: Use usermod -s /bin/bash username for an installed permitted shell.

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 Use usermod -s /bin/bash username for an installed permitted shell. 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 usermod -s /bin/bash username for an installed permitted shell. 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 Use usermod -s /bin/bash username for an installed permitted shell. satisfies the stated condition.

That observation checks A password policy requires local user passwords to expire after 90 days. In this scenario it does not demonstrate Use usermod -s /bin/bash username for an installed permitted shell.; the relevant evidence must establish getent passwd username reports /bin/bash and a fresh login opens the selected shell.

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 Use usermod -s /bin/bash username for an installed permitted shell.; the relevant evidence must establish getent passwd username reports /bin/bash and a fresh login opens the selected shell.

That observation checks A developer must be added to the supplementary docker group without losing current secondary groups. In this scenario it does not demonstrate Use usermod -s /bin/bash username for an installed permitted shell.; the relevant evidence must establish getent passwd username reports /bin/bash and a fresh login opens the selected shell.

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 The administrator changed the SHELL variable manually but login still launches the prior shell. The current requirement calls for a different check.

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 administrator changed the SHELL variable manually but login still launches the prior shell. The current requirement calls for a different check.

That symptom concerns An administrator needs to look up a user's account record using the configured NSS sources, not just local /etc/passwd. This concerns a separate requirement, not the one being tested. The relevant failure is The administrator changed the SHELL variable manually but login still launches the prior shell. The current requirement calls for a different check.

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 The administrator changed the SHELL variable manually but login still launches the prior shell. and needs Change the account's configured login shell with usermod -s.

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 The administrator changed the SHELL variable manually but login still launches the prior shell. and needs Change the account's configured login shell with usermod -s.

This fix is aimed at The policy was edited in an unrelated global file but the existing user's aging values did not change. and would be relevant if A password policy requires local user passwords to expire after 90 days. The incident instead states The administrator changed the SHELL variable manually but login still launches the prior shell. and needs Change the account's configured login shell with usermod -s.

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: Run id -gn username to display the account's primary group name.

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 id -gn username to display the account's primary group name.

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: Run id -gn username to display the account's primary group name.

This explains another Linux operation, namely Create the group with groupadd appreaders., where groupadd creates the group in the local group database so members and file ownership can refer to it. It does not explain why Run id -gn username to display the account's primary group name. 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 Run id -gn username to display the account's primary group name. 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 Run id -gn username to display the account's primary group name. satisfies the stated condition.