101-400 · Question #446
Which of the following commands is used to modify quota settings? (Choose two.)
The correct answer is B. setquota C. edquota. See the full explanation below for the reasoning.
Question
Options
- Aeditquota
- Bsetquota
- Cedquota
- Dquotaedit
- Equotaset
How the community answered
(30 responses)- A3% (1)
- B73% (22)
- D10% (3)
- E13% (4)
Community Discussion
7The answers are B and C, setquota and edquota. Edquota is the one you probably think of first because it drops you into a text editor to manually set soft and hard limits for a user or group, and it showed up on my exam in a context where they described that interactive editing behavior. Setquota does the same job but takes everything as command-line arguments, which makes it useful for scripting, and the exam tested whether you knew both tools exist for the same purpose. The other three options, editquota, quotaedit, and quotaset, are just made-up names that do not exist as real commands, so if you can remember edquota and setquota as the real pair, you can eliminate the rest pretty fast.
Run man edquota and man setquota back to back and you will see the two that actually ship with the quota package on any standard distro, the others are just noise. Quick question though: do you know the difference between how edquota handles limits compared to setquota, specifically which one you would pipe into a script versus use at the terminal interactively?
setquota is the one for scripts since it takes everything on the command line, while edquota drops you into a text editor which is useless in automation but way nicer for one-off adjustments on a specific user.
This one maps to objective 104.4, Manage Disk Quotas, which carries a weight of 1 on the 101-400, so it shows up lightly but it absolutely shows up. The two real commands are edquota and setquota. edquota drops you into a text editor, usually vi, where you set soft and hard limits interactively for a specific user or group, while setquota lets you do the same thing entirely from the command line without opening an editor at all, which is what you reach for in scripts. The other three options, editquota, quotaedit, and quotaset, are fabricated names that follow a plausible naming pattern but do not exist as actual utilities, and that is exactly the trap LPI sets for you. When I sat this exam I actually second-guessed setquota for a moment because I had mostly drilled edquota during my prep and setquota felt like a distractor invented to mirror the real command. The memory hook that saved me was thinking of it this way: ed in edquota stands for editor, and set in setquota stands for scripted, one stays in the editor and one sets it and steps away. I locked in B and C and moved on without looking back, and they were both correct. If you are tight on lab time before the exam, practice both commands on a filesystem with quota support enabled, because seeing the output once makes the syntax stick far better than reading it off a notes sheet.
setquota is also the one to reach for when you're provisioning users in bulk via a loop, so pairing it with repquota for auditing after the fact rounds out that objective nicely.
I been doing quota management since before half you kids knew what a filesystem was, and I am telling you D is one of the two. quotaedit is what they used to call that wrapper utility back when the quota tools got reorganized, and it still shows up in some distro implementations. Pair it with B setquota and you have your two, because setquota handles the non-interactive scripted side and quotaedit gives you the direct edit interface, same job edquota does but that got deprecated on the systems I ran for years.
Tom, you are right that setquota belongs here, but the standard paired tool the LPI objectives and the quota-tools package both recognize is edquota, option C, not quotaedit, which is not a utility you will find documented in the exam blueprint or shipped as a standard binary in the quota package on either RHEL or Debian lineages.