LFCS User and Group Management Practice Question
Which THREE files are directly related to user and group management in a Linux system? (Select three.)
⚠ Common exam trap
Candidates often confuse configuration files like /etc/sudoers or /etc/login.defs with the actual user/group database files, but the question specifically asks for files 'directly related to user and group management'—meaning the files that store the user and group records themselves, not files that configure how those records are created or used.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
/etc/group
The three files directly related to user and group management are /etc/group (C), /etc/passwd (D), and /etc/shadow (E). /etc/passwd stores user account entries with UID, GID, home directory, and login shell, making it a core user-management file. /etc/group defines group names, GIDs, and group membership lists, so it is essential for group management. /etc/shadow stores encrypted password hashes and password-aging fields for local users, which is a fundamental part of user account administration. /etc/sudoers (A) controls sudo privilege delegation, and /etc/login.defs (B) sets defaults for login and user-creation tools; both are related to authentication or account policy, but they are not the primary user/group database files.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
/etc/sudoers
Why it's wrong here
/etc/sudoers governs privilege delegation, not user or group account data. It defines which principals may run commands as others, so it belongs to authorisation rather than account management. It would be the right file when configuring who may escalate via sudo, but the question asks for the files holding user and group definitions.
- ✗
/etc/login.defs
Why it's wrong here
/etc/login.defs sets system-wide defaults for the shadow password suite — UID/GID ranges, password aging, umask — but holds no user or group entries itself. It is tempting because it configures how useradd and passwd behave, and would be relevant when tuning account-creation policy, not when identifying the files that actually store accounts.
- ✓
/etc/group
Why this is correct
/etc/group stores group names, GIDs and membership lists, forming the core database consulted by group management tools. It is directly related to user and group management, unlike unrelated system files such as /etc/fstab or /etc/hosts.
- ✓
/etc/passwd
Why this is correct
/etc/passwd stores user account records — username, UID, GID, home directory and login shell — making it a core file for user management. Group membership is also referenced here via the primary GID field, satisfying the stem's requirement for files directly tied to user and group administration.
- ✓
/etc/shadow
Why this is correct
/etc/shadow holds the encrypted password hashes and ageing fields — last change, minimum, maximum and warning days — separate from /etc/passwd to restrict read access. It directly governs user authentication and password policy, satisfying the stem's user-management criterion.
Go deeper
Related to this question
About these practice questions
One of 406 original LFCS practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This LFCS practice question is part of Courseiva's free Linux Foundation certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the LFCS exam.