How should I use these User and Group Management practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

Can I practise just User and Group Management questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the User and Group Management domain.

LFCS · topic practice

User and Group Management practice questions

Practise Linux Foundation Certified System Administrator LFCS User and Group Management practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Reviewed byJohnson Ajibi· MSc IT Security

20 questionsDomain: User and Group Management

Practice 10 questions Browse domain →

What the exam tests

What to know about User and Group Management

User and Group Management questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Watch out for

Common User and Group Management exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

User and Group Management questions

20 questions · select your answer, then reveal the explanation

Question 1mediummultiple choice

Read the full User and Group Management explanation →

A developer was removed from the 'developers' group but still needs to run commands that require membership in that group. The user has logged out and back in, but the issue persists. What is the most likely cause?

Trap 1: The user's primary group is different from the 'developers' group.

Primary group mismatch does not prevent supplementary group access after re-login.

Trap 2: The user is using 'newgrp developers' but is no longer a member.

Using 'newgrp' without being a member will fail, but the issue is that the user hasn't refreshed their session properly.

Trap 3: The 'id' command shows the old group because the user's shell is…

'id' reads from kernel; after re-login, it should show updated groups.

Study all User and Group Management common traps →

A
The user did not explicitly start a new login shell after group removal.
Group membership changes require a new login session; logging out and back in should suffice, but if the user only logged out of the desktop and the session manager cached credentials, it might not refresh. The most likely cause is that the user's current shell environment still has cached group membership from the previous session.
B
The user's primary group is different from the 'developers' group.
Why wrong: Primary group mismatch does not prevent supplementary group access after re-login.
C
The user is using 'newgrp developers' but is no longer a member.
Why wrong: Using 'newgrp' without being a member will fail, but the issue is that the user hasn't refreshed their session properly.
D
The 'id' command shows the old group because the user's shell is still running.
Why wrong: 'id' reads from kernel; after re-login, it should show updated groups.

Full breakdown with real-world context →

Question 2easymultiple choice

Read the full User and Group Management explanation →

A system administrator needs to create a user 'john' with a home directory in /data/users and an expiry date of 2025-12-31. Which command accomplishes this?

Trap 1: useradd -d /data/users -c 2025-12-31 john

-c sets the GECOS comment, not expiry.

Trap 2: adduser --home /data/users --expiredate 2025-12-31 john

adduser is distribution-specific and interactive; not the standard command.

Trap 3: useradd -m -e 2025-12-31 john

-m creates the home directory in /home/john by default, not /data/users.

Study all User and Group Management common traps →

A
useradd -d /data/users -c 2025-12-31 john
Why wrong: -c sets the GECOS comment, not expiry.
B
adduser --home /data/users --expiredate 2025-12-31 john
Why wrong: adduser is distribution-specific and interactive; not the standard command.
C
useradd -d /data/users -e 2025-12-31 john
Correctly sets home directory and expiry.
D
useradd -m -e 2025-12-31 john
Why wrong: -m creates the home directory in /home/john by default, not /data/users.

Full breakdown with real-world context →

Question 3hardmultiple choice

Read the full User and Group Management explanation →

An administrator needs to set up a shared directory /project for the group 'projectteam' (GID 5000). All members of the group should be able to create and delete files, but only the file owner can modify their own files. The directory should also ensure that new files inherit the group ownership. Which set of commands achieves this?

Trap 1: chown root:projectteam /project; chmod 2775 /project; setfacl -m…

Default ACL not set, so new files may not inherit group permissions.

Trap 2: chown root:projectteam /project; chmod 2775 /project

Sticky bit (1) prevents deletion of others' files, which is not desired.

Trap 3: chown root:projectteam /project; chmod 1770 /project; setfacl -m…

Sticky bit (1) prevents deletion; mask not inherited.

Study all User and Group Management common traps →

A
chown root:projectteam /project; chmod 2775 /project; setfacl -m g:projectteam:rwx /project
Why wrong: Default ACL not set, so new files may not inherit group permissions.
B
chown root:projectteam /project; chmod 2770 /project; setfacl -d -m o::--- /project
SGID (2) inherits group; 770 gives group rwx; default ACL denies others.
C
chown root:projectteam /project; chmod 2775 /project
Why wrong: Sticky bit (1) prevents deletion of others' files, which is not desired.
D
chown root:projectteam /project; chmod 1770 /project; setfacl -m m::rwx /project
Why wrong: Sticky bit (1) prevents deletion; mask not inherited.

Full breakdown with real-world context →

Question 4easymultiple choice

Read the full User and Group Management explanation →

A user 'alice' is unable to log in via SSH. The administrator checks /etc/shadow and sees 'alice:!:19234:0:99999:7:::'. What does the '!' in the password field indicate?

Trap 1: The password must be changed at next login.

That is indicated by the last change field set to 0.

Trap 2: The account is disabled.

Disabled accounts often have '!!' or '*'.

Trap 3: The password is expired.

Expired passwords are shown by a '!' at the start of the hash.

Study all User and Group Management common traps →

A
The password must be changed at next login.
Why wrong: That is indicated by the last change field set to 0.
B
The account is disabled.
Why wrong: Disabled accounts often have '!!' or '*'.
C
The account is locked.
'!' is a common indicator of a locked account in /etc/shadow.
D
The password is expired.
Why wrong: Expired passwords are shown by a '!' at the start of the hash.

Full breakdown with real-world context →

Question 5hardmultiple choice

Read the full User and Group Management explanation →

An administrator wants to enforce that users in the 'contractors' group must change their password every 30 days, with a warning 7 days before expiry. Which command should be used?

Trap 1: groupmod -p 30 contractors

groupmod does not have -p for password policy.

Trap 2: passwd -x 30 -w 7 contractors

passwd -x sets max days but requires a username, not a group; also -w sets warning.

Trap 3: usermod -e 30 contractors

-e sets account expiry date, not password policy.

Study all User and Group Management common traps →

A
groupmod -p 30 contractors
Why wrong: groupmod does not have -p for password policy.
B
passwd -x 30 -w 7 contractors
Why wrong: passwd -x sets max days but requires a username, not a group; also -w sets warning.
C
usermod -e 30 contractors
Why wrong: -e sets account expiry date, not password policy.
D
chage -M 30 -W 7 contractors
chage modifies password aging for a user; but the question says 'users in the group', so you would need to apply to each user. However, among the options, this is the closest correct command for a user.

Full breakdown with real-world context →

Question 6mediummulti select

Read the full User and Group Management explanation →

Which TWO commands can be used to list all users currently logged into the system?

Trap 1: last

Shows last logins, not current.

Trap 2: users

Also lists logged-in users, but we need exactly two; who and w are more common.

Trap 3: id

Displays user identity, not logged-in status.

Study all User and Group Management common traps →

A
w
Shows who is logged in and what they are doing.
B
last
Why wrong: Shows last logins, not current.
C
users
Why wrong: Also lists logged-in users, but we need exactly two; who and w are more common.
D
id
Why wrong: Displays user identity, not logged-in status.
E
who
Lists currently logged-in users.

Full breakdown with real-world context →

Question 7hardmulti select

Read the full User and Group Management explanation →

Which THREE files are directly related to user and group management in a Linux system? (Select three.)

Trap 1: /etc/sudoers

Controls sudo access, not user/group management.

Trap 2: /etc/login.defs

Contains default values for user account creation, but not direct user/group data.

Study all User and Group Management common traps →

A
/etc/sudoers
Why wrong: Controls sudo access, not user/group management.
B
/etc/login.defs
Why wrong: Contains default values for user account creation, but not direct user/group data.
C
/etc/group
Contains group definitions.
D
/etc/passwd
Contains user account information.
E
/etc/shadow
Contains encrypted passwords and aging info.

Full breakdown with real-world context →

Question 8hardmultiple choice

Read the full User and Group Management explanation →

You are the Linux administrator for a medium-sized company that uses a centralized authentication system (LDAP) for user accounts, but local files (/etc/passwd, /etc/shadow, /etc/group) are also used for a few service accounts. The server is running RHEL 8. A new employee, 'jane', needs to be added to the local system for a temporary project. You create the user with 'useradd jane' and set a password with 'passwd jane'. However, when jane tries to log in via SSH using her password, she receives 'Permission denied, please try again.' The SSH server is configured to allow password authentication. Other users (both LDAP and local) can log in successfully. You verify that the password was set correctly and that the account is not locked. What is the most likely cause and solution?

Trap 1: Configure the SSH daemon to allow password authentication for local…

The SSH server already allows password authentication.

Trap 2: Unlock the account using passwd -u jane

The account is not locked according to the administrator's verification.

Trap 3: Remove the password expiry for jane using chage -E -1 jane

Password expiry would cause a warning, not immediate denial.

Study all User and Group Management common traps →

A
Configure the SSH daemon to allow password authentication for local users
Why wrong: The SSH server already allows password authentication.
B
Change jane's login shell to /bin/bash using usermod -s /bin/bash jane
If the user's shell is set to /sbin/nologin or a non-existent shell, SSH will reject authentication despite correct password.
C
Unlock the account using passwd -u jane
Why wrong: The account is not locked according to the administrator's verification.
D
Remove the password expiry for jane using chage -E -1 jane
Why wrong: Password expiry would cause a warning, not immediate denial.

Full breakdown with real-world context →

Question 9mediummultiple choice

Read the full User and Group Management explanation →

A system administrator needs to ensure that all users in the 'developers' group have read and write access to a shared project directory /project/data, but new files created in that directory should belong to the 'developers' group automatically. Which command sequence achieves this goal?

Trap 1: setfacl -m g:developers:rwx /project/data && chmod 2775…

ACL grants access but without SGID, new files will inherit the creating user's primary group, not developers.

Trap 2: chown root:developers /project/data && chmod u+s /project/data

chmod u+s sets setuid bit (user), not SGID; new files will inherit the owner's primary group, not developers group.

Trap 3: chmod g+s /project/data && chown root:developers /project/data

Order matters: chmod g+s first on a directory owned by root:root will set SGID, but then chown changes group to developers but may clear SGID on some systems; also new files still inherit primary group without proper group ownership set first.

Study all User and Group Management common traps →

A
setfacl -m g:developers:rwx /project/data && chmod 2775 /project/data
Why wrong: ACL grants access but without SGID, new files will inherit the creating user's primary group, not developers.
B
chown root:developers /project/data && chmod u+s /project/data
Why wrong: chmod u+s sets setuid bit (user), not SGID; new files will inherit the owner's primary group, not developers group.
C
chmod g+s /project/data && chown root:developers /project/data
Why wrong: Order matters: chmod g+s first on a directory owned by root:root will set SGID, but then chown changes group to developers but may clear SGID on some systems; also new files still inherit primary group without proper group ownership set first.
D
chown :developers /project/data && chmod g+s /project/data
chown :developers sets the group to developers; chmod g+s sets the SGID bit so new files inherit the group.

Full breakdown with real-world context →

Question 10hardmultiple choice

Read the full User and Group Management explanation →

A user 'alice' cannot log in via SSH. The administrator checks /etc/passwd and sees: alice:x:1002:1002::/home/alice:/sbin/nologin. Which command should be used to allow alice to log in with a bash shell?

Trap 1: usermod -d /home/alice alice

-d changes the home directory, not the shell. The shell is still /sbin/nologin.

Trap 2: usermod -u 1002 alice

-u changes the UID, which is already 1002. Does not affect shell.

Trap 3: useradd -m -s /bin/bash alice

useradd creates a new user; alice already exists. This would fail or create a duplicate.

Study all User and Group Management common traps →

A
usermod -d /home/alice alice
Why wrong: -d changes the home directory, not the shell. The shell is still /sbin/nologin.
B
usermod -u 1002 alice
Why wrong: -u changes the UID, which is already 1002. Does not affect shell.
C
usermod -s /bin/bash alice
usermod -s changes the login shell to /bin/bash, allowing interactive login.
D
useradd -m -s /bin/bash alice
Why wrong: useradd creates a new user; alice already exists. This would fail or create a duplicate.

Full breakdown with real-world context →

Question 11easymultiple choice

Read the full User and Group Management explanation →

An administrator wants to add user 'bob' to the supplementary group 'docker' without removing bob from any existing groups. Which command accomplishes this?

Trap 1: usermod -g docker bob

-g changes the primary group, not supplementary.

Trap 2: usermod -G docker bob

-G without -a replaces all supplementary groups with only docker, removing bob from any other groups.

Trap 3: usermod -G docker bob

Same as B; no -a flag.

Study all User and Group Management common traps →

A
usermod -g docker bob
Why wrong: -g changes the primary group, not supplementary.
B
usermod -aG docker bob
-aG appends docker to the list of supplementary groups.
C
usermod -G docker bob
Why wrong: -G without -a replaces all supplementary groups with only docker, removing bob from any other groups.
D
usermod -G docker bob
Why wrong: Same as B; no -a flag.

Full breakdown with real-world context →

Question 12hardmultiple choice

Read the full User and Group Management explanation →

A security policy requires that user 'svc_backup' have a password that never expires. Additionally, the account should be locked after 90 days of inactivity. Which set of commands achieves this?

Trap 1: chage -W 7 -I 90 svc_backup

-W sets warning days before password expiration; does not affect max days or inactivity.

Trap 2: chage -E 2025-01-01 -I 90 svc_backup

-E sets an absolute account expiration date, not password inactivity lock.

Trap 3: chage -M 90 -I 90 svc_backup

-M 90 sets maximum password age to 90 days, forcing password change; administrator wants password never to expire.

Study all User and Group Management common traps →

A
chage -W 7 -I 90 svc_backup
Why wrong: -W sets warning days before password expiration; does not affect max days or inactivity.
B
chage -E 2025-01-01 -I 90 svc_backup
Why wrong: -E sets an absolute account expiration date, not password inactivity lock.
C
chage -M 99999 -I 90 svc_backup
-M 99999 effectively disables password expiration; -I 90 locks account after 90 days of inactivity.
D
chage -M 90 -I 90 svc_backup
Why wrong: -M 90 sets maximum password age to 90 days, forcing password change; administrator wants password never to expire.

Full breakdown with real-world context →

Question 13mediummulti select

Read the full User and Group Management explanation →

Which TWO commands can be used to display the groups to which the current user belongs? (Select exactly two.)

Trap 1: cat /etc/group

Lists all groups, not just those of the current user.

Trap 2: groupmems -l

groupmems lists members of a group, not groups of a user.

Trap 3: getent group

Lists all groups from configured sources.

Study all User and Group Management common traps →

A
cat /etc/group
Why wrong: Lists all groups, not just those of the current user.
B
groupmems -l
Why wrong: groupmems lists members of a group, not groups of a user.
C
id
Displays user identity including group memberships.
D
getent group
Why wrong: Lists all groups from configured sources.
E
groups
Displays the groups of the current user.

Full breakdown with real-world context →

Question 14hardmultiple choice

Read the full User and Group Management explanation →

You are managing a multi-user Linux server used by a development team. The server has a shared directory /data/projects where each project has a subdirectory owned by a project lead. The requirement is that all members of the 'devteam' group need to be able to create files in any project subdirectory, but only the project lead (owner) should be able to delete files. Currently, members of devteam are unable to create files in /data/projects. You check permissions: /data/projects has drwxrwxr-x root:devteam. Each project subdirectory, e.g., /data/projects/proj1, has drwx------ lead1:devteam. The lead1 user is in devteam. What is the most likely reason that devteam members cannot create files in proj1, and what is the correct solution?

Trap 1: The devteam group does not include all members; add each user to…

The group membership is not the issue; the directory permissions are too restrictive.

Trap 2: The parent directory /data/projects lacks execute permission for…

The parent directory already has rwx for group; execute is present (x in rwx).

Trap 3: The sticky bit is not set; set the sticky bit on proj1 to allow…

Sticky bit does not affect ability to create files; it affects deletion of files. The immediate issue is no write access.

Study all User and Group Management common traps →

A
The devteam group does not include all members; add each user to the devteam group.
Why wrong: The group membership is not the issue; the directory permissions are too restrictive.
B
The parent directory /data/projects lacks execute permission for devteam; add execute permission to /data/projects.
Why wrong: The parent directory already has rwx for group; execute is present (x in rwx).
C
The sticky bit is not set; set the sticky bit on proj1 to allow only owners to delete files.
Why wrong: Sticky bit does not affect ability to create files; it affects deletion of files. The immediate issue is no write access.
D
The proj1 directory lacks group write and execute permissions; use chmod g+rwx proj1 and chmod g+s proj1 to allow group members to create files and ensure new files inherit group.
drwx------ means only owner has access; adding group rwx gives devteam access; SGID ensures new files belong to devteam.

Full breakdown with real-world context →

Question 15easymulti select

Read the full User and Group Management explanation →

An administrator needs to grant a user named 'john' the ability to switch to any other user without a password. Which TWO of the following steps are required to achieve this?

Trap 1: Set the suid bit on /bin/su.

Incorrect: The suid bit is already set on su; it does not bypass the password prompt.

Trap 2: Run 'usermod -L john'.

Incorrect: This locks the account, preventing any login.

Trap 3: Add 'john' to the 'root' group.

Incorrect: Being in the root group does not grant passwordless su.

Study all User and Group Management common traps →

A
Add 'john' to the 'wheel' group and configure /etc/pam.d/su to use pam_wheel.so with the 'trust' option.
Correct: This allows members of the wheel group to su without a password if pam_wheel.so is configured.
B
Add a sudo rule: 'john ALL=(ALL) NOPASSWD: ALL' to /etc/sudoers.
Correct: This allows 'john' to run any command as any user without a password via sudo.
C
Set the suid bit on /bin/su.
Why wrong: Incorrect: The suid bit is already set on su; it does not bypass the password prompt.
D
Run 'usermod -L john'.
Why wrong: Incorrect: This locks the account, preventing any login.
E
Add 'john' to the 'root' group.
Why wrong: Incorrect: Being in the root group does not grant passwordless su.

Full breakdown with real-world context →

Question 16hardmultiple choice

Read the full User and Group Management explanation →

A user named 'charlie' has just been added to the 'devops' group. However, when 'charlie' runs 'sudo -l', no sudo entries are shown. What is the most likely cause?

Exhibit

Refer to the exhibit.

$ sudo cat /etc/group | grep devops
devops:x:3001:alice,bob
$ sudo cat /etc/sudoers.d/devops
%devops ALL=(ALL) /usr/bin/systemctl
$ ls -l /usr/bin/systemctl
-rwxr-xr-x 1 root root 100000 Jan  1 12:00 /usr/bin/systemctl
$ sudo -l -U alice
User alice may run the following commands on this host:
    (ALL) /usr/bin/systemctl
$ sudo -l -U bob
User bob may run the following commands on this host:
    (ALL) /usr/bin/systemctl

Trap 1: 'charlie' is not listed by name in the sudoers file.

Membership in the devops group is sufficient; the sudoers rule uses %devops.

Trap 2: 'charlie' is also a member of another group that restricts sudo.

No evidence of restriction; the group devops grants the privilege.

Trap 3: The systemctl command is not executable by 'charlie'.

The command has execute permissions for all (chmod 755).

Study all User and Group Management common traps →

A
'charlie' is not listed by name in the sudoers file.
Why wrong: Membership in the devops group is sufficient; the sudoers rule uses %devops.
B
'charlie' must log out and log back in for the group change to take effect.
Correct: Group changes require a new login session to be recognized by PAM and sudo.
C
'charlie' is also a member of another group that restricts sudo.
Why wrong: No evidence of restriction; the group devops grants the privilege.
D
The systemctl command is not executable by 'charlie'.
Why wrong: The command has execute permissions for all (chmod 755).
E
The sudoers file has a syntax error.
Why wrong: No, sudo -l works for alice and bob, so syntax is fine.

Full breakdown with real-world context →

Question 17mediummultiple choice

Read the full User and Group Management explanation →

Scenario: You are managing a Linux server that hosts a web application. The application runs under the user 'webapp' and the group 'webgroup'. Recently, a new intern 'john' (username 'john') needs to be able to view and modify files in /var/www/html, which is owned by root:webgroup with permissions 775. John is currently a member of the group 'staff', but not 'webgroup'. The security policy requires that John must be able to edit files without using sudo, and his primary group must remain 'staff'. Which of the following actions should you take to meet the requirements?

Trap 1: Change the group ownership of /var/www/html to 'staff' and set the…

Incorrect: This would grant access to all staff members, which is too permissive.

Trap 2: Change John's primary group to 'webgroup' with 'usermod -g webgroup…

Incorrect: This changes his primary group, which may affect file creation in other directories.

Trap 3: Set the setgid bit on /var/www/html with 'chmod g+s /var/www/html'.

Incorrect: The setgid bit only affects new files; John still needs group membership to access existing files.

Study all User and Group Management common traps →

A
Add John to the 'webgroup' supplementary group with 'usermod -a -G webgroup john'.
Correct: John gains the group permissions of webgroup, allowing read/write access to the directory, while his primary group remains 'staff'.
B
Change the group ownership of /var/www/html to 'staff' and set the setgid bit.
Why wrong: Incorrect: This would grant access to all staff members, which is too permissive.
C
Change John's primary group to 'webgroup' with 'usermod -g webgroup john'.
Why wrong: Incorrect: This changes his primary group, which may affect file creation in other directories.
D
Set the setgid bit on /var/www/html with 'chmod g+s /var/www/html'.
Why wrong: Incorrect: The setgid bit only affects new files; John still needs group membership to access existing files.

Full breakdown with real-world context →

Question 18mediumdrag order

Read the full User and Group Management explanation →

Arrange the steps to configure a new user account with sudo privileges on a Linux system.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Question 19mediumdrag order

Read the full User and Group Management explanation →

Order the steps to create a systemd service unit that runs a script at boot.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Question 20mediumdrag order

Read the full User and Group Management explanation →

Order the steps to set up passwordless SSH key-based authentication.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused User and Group Management sessions

Start a User and Group Management only practice session

Every question in these sessions is drawn from the User and Group Management domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all User and Group Management questions →Mixed LFCS session

Frequently asked questions

What does the LFCS exam test about User and Group Management?: User and Group Management questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just User and Group Management questions in a focused session?: Yes — the session launcher on this page draws every question from the User and Group Management domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other LFCS topics?: Use the topic links above to move to related areas, or go back to the LFCS question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the LFCS exam covers. They are not copied from any real exam or dump site.

User and Group Management only

10 questions 20 questions 30 questions 50 questions

Mixed LFCS session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All LFCS questions User and Group Management domain overview LFCS exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

User and Group Management practice questions

What to know about User and Group Management

Common User and Group Management exam traps

User and Group Management questions

A developer was removed from the 'developers' group but still needs to run commands that require membership in that group. The user has logged out and back in, but the issue persists. What is the most likely cause?

A system administrator needs to create a user 'john' with a home directory in /data/users and an expiry date of 2025-12-31. Which command accomplishes this?

A user 'alice' is unable to log in via SSH. The administrator checks /etc/shadow and sees 'alice:!:19234:0:99999:7:::'. What does the '!' in the password field indicate?

An administrator wants to enforce that users in the 'contractors' group must change their password every 30 days, with a warning 7 days before expiry. Which command should be used?

Which TWO commands can be used to list all users currently logged into the system?

Which THREE files are directly related to user and group management in a Linux system? (Select three.)

A system administrator needs to ensure that all users in the 'developers' group have read and write access to a shared project directory /project/data, but new files created in that directory should belong to the 'developers' group automatically. Which command sequence achieves this goal?

A user 'alice' cannot log in via SSH. The administrator checks /etc/passwd and sees: alice:x:1002:1002::/home/alice:/sbin/nologin. Which command should be used to allow alice to log in with a bash shell?

An administrator wants to add user 'bob' to the supplementary group 'docker' without removing bob from any existing groups. Which command accomplishes this?

A security policy requires that user 'svc_backup' have a password that never expires. Additionally, the account should be locked after 90 days of inactivity. Which set of commands achieves this?

Which TWO commands can be used to display the groups to which the current user belongs? (Select exactly two.)

An administrator needs to grant a user named 'john' the ability to switch to any other user without a password. Which TWO of the following steps are required to achieve this?

A user named 'charlie' has just been added to the 'devops' group. However, when 'charlie' runs 'sudo -l', no sudo entries are shown. What is the most likely cause?

Exhibit

Arrange the steps to configure a new user account with sudo privileges on a Linux system.

Order the steps to create a systemd service unit that runs a script at boot.

Order the steps to set up passwordless SSH key-based authentication.

Track your progress over time

Start a User and Group Management only practice session

Related LFCS topic practice pages