LFCS Essential Commands Practice Question
An administrator runs `ls -l` and sees a file entry whose permission string begins with a lowercase `l`. What does this indicate about the entry?
⚠ Common exam trap
The trap here is reading the leading character as a permission rather than a file type indicator.
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
✓
It is a symbolic link whose target is resolved when the link is accessed.
The first character of the permission string encodes file type, and l specifically means symbolic link. Device nodes, regular files, and FIFOs each have their own distinct type character, so recognizing the type column is essential before choosing commands such as readlink, stat, or find -type l.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
It is a symbolic link whose target is resolved when the link is accessed.
Why this is correct
A leading l in the file type column denotes a symbolic link, a special file holding a pathname that the kernel resolves at access time. Unlike hard links, a symlink has its own inode and can point across filesystems, and it becomes dangling if the target path no longer exists.
- ✗
It is a named pipe used for inter-process communication.
Why it's wrong here
FIFOs are marked with a leading p and are created with mkfifo. Their purpose is byte-stream communication between processes, which is unrelated to the l type character. Confusing the two would send the administrator looking for a reader or writer process rather than a link target.
- ✗
It is a regular file that has the setuid bit enabled.
Why it's wrong here
A regular file is marked with a leading hyphen, and the setuid bit appears in the execute position of the owner triad as s or S. The leading character describes file type, not special permission bits, so setuid files still begin with a dash in the long listing.
- ✗
It is a block device node used for buffered disk access.
Why it's wrong here
Block devices are marked with a leading b, not l, and they appear as special files under /dev created with mknod. The l flag never denotes a device node, so this interpretation misreads the file type column and would lead the administrator to the wrong tooling.
Go deeper
Related to this question
About these practice questions
Courseiva writes every LFCS question from scratch — 406 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Linux Foundation exam blueprint
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.