Pass Your LPI 102-500 Exam Easy!

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.

That observation checks A local application needs a dedicated group before administrators can assign its log readers. In this scenario it does not demonstrate Set the maximum password age with chage -M 90 username.; the relevant evidence must establish chage -l username shows the maximum password age set to 90 days.

That observation checks A daemon needs a low-privilege local system identity that normally should not be used for interactive login. In this scenario it does not demonstrate Set the maximum password age with chage -M 90 username.; the relevant evidence must establish chage -l username shows the maximum password age set to 90 days.

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 Set the maximum password age with chage -M 90 username.; the relevant evidence must establish chage -l username shows the maximum password age set to 90 days.

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 policy was edited in an unrelated global file but the existing user's aging values did not change. 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 policy was edited in an unrelated global file but the existing user's aging values did not change. 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 The policy was edited in an unrelated global file but the existing user's aging values did not change. The current requirement calls for a different check.

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 policy was edited in an unrelated global file but the existing user's aging values did not change. and needs Apply chage to the target account and confirm the shadow aging fields.

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 The policy was edited in an unrelated global file but the existing user's aging values did not change. and needs Apply chage to the target account and confirm the shadow aging fields.

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 policy was edited in an unrelated global file but the existing user's aging values did not change. and needs Apply chage to the target account and confirm the shadow aging fields.

Set the maximum password age with chage -M 90 username. That operation is designed for the different case: A password policy requires local user passwords to expire after 90 days. It does not perform the specific action required here: Run getent passwd username.

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 getent passwd 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: Run getent passwd username.

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 getent passwd username. 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 Run getent passwd username. 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 Run getent passwd username. 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 Run getent passwd username.; the relevant evidence must establish A centrally managed user absent from /etc/passwd can still be resolved by getent passwd.

That observation checks A local application needs a dedicated group before administrators can assign its log readers. In this scenario it does not demonstrate Run getent passwd username.; the relevant evidence must establish A centrally managed user absent from /etc/passwd can still be resolved by getent passwd.

That observation checks An administrator needs to identify which file stores local password hashes rather than account names and shell paths. In this scenario it does not demonstrate Run getent passwd username.; the relevant evidence must establish A centrally managed user absent from /etc/passwd can still be resolved by getent passwd.

That symptom concerns A technician wants to inspect which group is the primary group for a named account. This concerns a separate requirement, not the one being tested. The relevant failure is grep /etc/passwd misses a centrally managed account that can authenticate. 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 grep /etc/passwd misses a centrally managed account that can authenticate. 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 grep /etc/passwd misses a centrally managed account that can authenticate. The current requirement calls for a different check.

This fix is aimed at The account exists in passwd but has no home directory because -m was omitted. and would be relevant if A new employee needs a local Linux login, a home directory and the configured default shell. The incident instead states grep /etc/passwd misses a centrally managed account that can authenticate. and needs Query the NSS database through getent and verify name-service configuration.

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 grep /etc/passwd misses a centrally managed account that can authenticate. and needs Query the NSS database through getent and verify name-service configuration.

This fix is aimed at A new group was created with a different GID, leaving files owned by the original group ID. and would be relevant if The operations team renamed a local Unix group without changing its existing numeric GID. The incident instead states grep /etc/passwd misses a centrally managed account that can authenticate. and needs Query the NSS database through getent and verify name-service configuration.

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 the group with groupadd appreaders.

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: Create the group with groupadd appreaders.

Lock the account password with passwd -l employee and separately assess other authentication paths. That operation is designed for the different case: A departing employee's interactive password login must be locked immediately while preserving account files for investigation. It does not perform the specific action required here: Create the group with groupadd appreaders.

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.