Pass Your LPI 102-500 Exam Easy!

This fix is aimed at Slow Keys is enabled but shortcuts still require simultaneous modifier presses. and would be relevant if An operator with limited dexterity cannot hold modifier keys while typing keyboard shortcuts. The incident instead states The high-contrast theme improves color separation but does not speak control labels. and needs Activate and configure the screen reader and appropriate speech output.

This fix is aimed at Changing display resolution shrinks usable space and still does not provide the required per-user magnification control. and would be relevant if A low-vision operator needs text and UI elements enlarged without requiring others to increase the system-wide resolution. The incident instead states The high-contrast theme improves color separation but does not speak control labels. and needs Activate and configure the screen reader and appropriate speech output.

This fix is aimed at The inventory labels RDP as the installed graphical desktop environment. and would be relevant if An administrator needs to recognize the difference between GNOME and KDE Plasma on managed Linux desktops. The incident instead states The high-contrast theme improves color separation but does not speak control labels. and needs Activate and configure the screen reader and appropriate speech output.

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: Create the account with useradd -m -s /bin/bash employee and set its password.

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 account with useradd -m -s /bin/bash employee and set its password.

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 account with useradd -m -s /bin/bash employee and set its password.

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 account with useradd -m -s /bin/bash employee and set its password. 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 Create the account with useradd -m -s /bin/bash employee and set its password. satisfies the stated condition.

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 Create the account with useradd -m -s /bin/bash employee and set its password. satisfies the stated condition.

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 the account with useradd -m -s /bin/bash employee and set its password.; the relevant evidence must establish getent passwd employee shows the home and /bin/bash, and the home contains approved skeleton files.

That observation checks The operations team renamed a local Unix group without changing its existing numeric GID. In this scenario it does not demonstrate Create the account with useradd -m -s /bin/bash employee and set its password.; the relevant evidence must establish getent passwd employee shows the home and /bin/bash, and the home contains approved skeleton files.

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 account with useradd -m -s /bin/bash employee and set its password.; the relevant evidence must establish getent passwd employee shows the home and /bin/bash, and the home contains approved skeleton files.

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 account exists in passwd but has no home directory because -m was omitted. and needs Create the home with correct ownership or recreate the account through a home-creating workflow.

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 exists in passwd but has no home directory because -m was omitted. and needs Create the home with correct ownership or recreate the account through a home-creating workflow.

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 account exists in passwd but has no home directory because -m was omitted. and needs Create the home with correct ownership or recreate the account through a home-creating workflow.

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: Use usermod -aG docker developer.

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: Use usermod -aG docker developer.

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 -aG docker developer.

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 Use usermod -aG docker developer. 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 Use usermod -aG docker developer. 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 Use usermod -aG docker developer. satisfies the stated condition.

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 usermod -aG docker developer.; the relevant evidence must establish id developer shows docker and the user's previous supplementary group memberships.

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 Use usermod -aG docker developer.; the relevant evidence must establish id developer shows docker and the user's previous supplementary group memberships.

That observation checks A password policy requires local user passwords to expire after 90 days. In this scenario it does not demonstrate Use usermod -aG docker developer.; the relevant evidence must establish id developer shows docker and the user's previous supplementary group memberships.

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 A plain usermod -G docker developer replaced the entire supplementary group list. and needs Use usermod -aG and confirm all intended memberships with id or groups.

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 A plain usermod -G docker developer replaced the entire supplementary group list. and needs Use usermod -aG and confirm all intended memberships with id or groups.

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 A plain usermod -G docker developer replaced the entire supplementary group list. and needs Use usermod -aG and confirm all intended memberships with id or groups.

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: Lock the account password with passwd -l employee and separately assess other authentication paths.

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: Lock the account password with passwd -l employee and separately assess other authentication paths.

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: Lock the account password with passwd -l employee and separately assess other authentication paths.

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.