LFCS Storage Management Practice Question
An administrator has enabled quotas on the /home filesystem by adding usrquota,grpquota to /etc/fstab and remounting. Then ran quotacheck -cug /home and it completed successfully. However, users are still able to write beyond their assigned soft limits. What step is missing?
⚠ Common exam trap
A common mix-up: candidates assume running `quotacheck -cug` both creates the quota database and activates quotas, but `quotacheck` only scans and builds the database, while `quotaon` is a separate mandatory step to enable enforcement.
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
✓
Running quotaon to activate quotas.
The missing step is activating quotas with `quotaon`. Even after configuring `/etc/fstab` with `usrquota,grpquota`, remounting the filesystem, and running `quotacheck -cug` to create the quota database files (`aquota.user` and `aquota.group`), quotas remain inactive until explicitly enabled with `quotaon`. Without this command, the kernel does not enforce quota limits, allowing users to exceed soft limits without warning.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Setting limits with edquota.
Why it's wrong here
edquota only edits limits interactively; the missing step is turning enforcement on with quotaon, since quotacheck merely builds the accounting files. It is tempting because edquota is the familiar tool for assigning per-user soft and hard limits, and it would be correct when limits genuinely need to be created or changed.
- ✗
Running repquota to view quotas.
Why it's wrong here
repquota only reports current usage against limits; it changes nothing, so quotas remain unenforced until quotaon runs. It is tempting because it confirms whether limits are being applied, and it would be correct when auditing usage or verifying that quotas are active after configuration.
- ✗
Setting limits with setquota.
Why it's wrong here
setquota writes limits non-interactively, but enforcement still requires quotaon; quotacheck only creates the accounting database. It is tempting because setquota is the scriptable way to assign per-user soft and hard limits, and it would be correct when limits must be set or amended in bulk.
- ✓
Running quotaon to activate quotas.
Why this is correct
Quotas remain inactive until explicitly enabled; `quotacheck` only builds the quota database files (aquota.user, aquota.group), it does not enforce limits. Running `quotaon /home` activates enforcement, satisfying the stem's requirement to stop users writing beyond their soft limits.
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.