Select the THREE true statements about the special permission bits on Linux.
LPIC-1 Exam 101-500, objective 104. Devices, Linux filesystems, filesystem hierarchy standard hard
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.
The options
Choose 3.
Not correct SUID on a shell script causes the Linux kernel to run the script with the owner's privileges.
False, and an important trap. Linux ignores the SUID bit on interpreted scripts because of unavoidable race conditions between the exec and the interpreter opening the file. Privileged helpers must be compiled binaries, or invoked through sudo.
Correct SUID on an executable file makes it run with the effective user ID of the file's owner.
True. This is how /usr/bin/passwd, owned by root, can write /etc/shadow when an ordinary user runs it.
Correct SGID on a directory makes files created inside it inherit the directory's group.
True, and it is the standard way to build a shared project directory so that everyone in the group can read each other's new files.
Correct The sticky bit on a world-writable directory stops users from deleting files they do not own.
True. Only the file's owner, the directory's owner and root may unlink or rename; this is why /tmp is mode 1777.
Not correct The sticky bit on a regular file keeps that file's contents cached in memory for faster execution.
False on Linux. That was the original 1970s Unix meaning of the bit on executables; Linux ignores it on regular files entirely. Today it is meaningful only on directories.
Why
Octal values: SUID 4000, SGID 2000, sticky 1000, written as a fourth leading digit (chmod 4755, 2775, 1777) or symbolically (u+s, g+s, +t). SGID is meaningful on both executables (run with the file's group) and directories (group inheritance); the sticky bit is meaningful only on directories; SUID is meaningful only on binary executables.
Where this comes from
- Cited
- LPI exam objective 104.5
- What it says
- Use the suid, sgid and sticky bits and know where each applies.
Practise this
Reading one question is not practice. The trainer will draw a short set from objective 104 and space the ones you get wrong.
More questions on this objective
- A new disk /dev/sdb has no partition table at all. Which command writes an empty GPT partition table onto it without dropping you into an interactive editor? machine-checked
- You need the partition /dev/sdc1 on a USB stick to carry a FAT32 filesystem so that Windows machines can read and write it. Which command creates it? machine-checked
- You have just run `mkswap /dev/sdb2`. Which command makes the kernel start using that swap area immediately, without a reboot? machine-checked
- Why is it dangerous to run e2fsck against an ext4 filesystem that is currently mounted read-write? machine-checked
- On an ext4 filesystem at /dev/sda1 you want an automatic check to be forced after every 30 mounts. Which command sets that? machine-checked
- `df -h /var` reports the filesystem 100% full, but `du -sh /var` accounts for only about half that space. Nothing is hidden under a mount point. What is the most likely explanation? machine-checked
All questions on Devices, Linux filesystems, filesystem hierarchy standard