What does the Filesystem Hierarchy Standard enable? (Select TWO answers)

Imani T.May 27, 2026

The correct answers are A and C. The Filesystem Hierarchy Standard defines where things live on a Linux system, so both software and users can predict file and directory locations without guessing. Think /etc for config, /usr/bin for user binaries, /var for logs and variable data, that structure is what FHS enforces across distros. B is wrong because FHS says nothing about ownership or permissions, that is handled by the permission model separately. D is also wrong because FHS has nothing to do with filesystem formatting like ext4 or xfs, it is strictly about the directory tree layout. On the exam, whenever you see a question about predictability of file locations, FHS is your answer every time.

Mei-Ling H.May 17, 2026

The word to catch here is "enables," and the FHS is specifically about standardizing directory structure so both software and users can reliably predict WHERE files live, not who owns them or how the disk is formatted. Option B trips people up because permissions and ownership sound very "filesystem-ish," but those are controlled by the OS and tools like chmod and chown, not by the FHS standard itself. Option D is also wrong because formatting is about partition type, like ext4 or xfs, which is a completely separate concern from the directory hierarchy. The FHS just says, for example, that user binaries go under /usr/bin and configuration files go under /etc, so both a shell script and a human administrator can count on finding things in consistent places. When I sat the real 101-350 last year I almost picked B because I was rushing and read "predict" too fast, then I stopped and asked myself, does FHS say anything about permissions? No, it does not. That one-second pause saved me. I went back, eliminated B and D, confirmed A and C were both about location prediction for two different audiences, software and users, and moved on. The question uses "Select TWO" so if you only pick one of those you still lose the point, make sure you mark both.

Hiroshi T.May 31, 2026

I initially marked B along with A, figuring ownership and permissions had to be part of any standard that governs filesystem layout, which was sloppy thinking on my part. Going back to the actual FHS specification cleared it up fast. The standard explicitly states its purpose as making it possible for software and users to predict the location of installed files and directories, and those two audiences map directly to A and C. Permissions and ownership are governed by the OS, the package manager, and administrator policy, none of which the FHS defines or promises. D is a distractor that conflates the standard with filesystem formatting tools like mkfs, which have nothing to do with the FHS at all.