LFCS: Linux Foundation Certified System Administrator
Browse certifications
Exam Resources
Official learning paths, exam details, skills measured, and community resources to supplement your study.
About the LFCS exam
The Linux Foundation Certified System Administrator (LFCS) exam is a two-hour, online, remotely proctored, performance-based assessment. You complete administration tasks at a Linux command line rather than answer multiple-choice questions.
The exam is distribution-neutral and has no formal prerequisites. It expects you to operate a Linux system, diagnose problems and verify the result—not just recognise a command name.
Before buying: The Guided LFCS product contains multiple-choice learning questions only. It is not a hands-on lab, exam simulator or practical-skills assessment. Its scores do not predict an LFCS result. Access does not include the official exam, a course, a voucher, a badge or Linux Foundation endorsement.
Exam facts
| Detail | Current published information |
|---|---|
| Certification | Linux Foundation Certified System Administrator (LFCS) |
| Format | Performance-based command-line tasks |
| Delivery | Online and remotely proctored |
| Duration | 120 minutes |
| Distribution | Distribution-neutral |
| Prerequisites | None |
| Price and booking | Check the official LFCS page for current pricing and policies |
The Linux Foundation does not publish a fixed task count or passing score on the official LFCS page, so this guide does not invent either.
Domains and learning-question allocation
The weights below come from the current official LFCS domains. The question counts describe this independent 250-question knowledge companion, not the number or distribution of tasks in the real exam.
| Official domain | Official weight | Learning questions |
|---|---|---|
| Operations Deployment | 25% | 63 |
| Networking | 25% | 62 |
| Storage | 20% | 50 |
| Essential Commands | 20% | 50 |
| Users and Groups | 10% | 25 |
| Total | 100% | 250 |
Operations Deployment
Learn to inspect and control services, read logs, schedule work, tune runtime kernel parameters and distinguish a temporary change from persistent configuration. Practise virtual-machine and container lifecycle tasks in a disposable environment. When security controls are distribution-specific, such as SELinux tooling on a RHEL-family system, keep that premise explicit.
Networking
Work with IPv4 and IPv6 addresses, routes, name resolution and time synchronization. Understand the difference between local input, forwarded traffic and locally generated output before writing firewall rules. Practise SSH configuration carefully: Include, Match, file ownership, permissions and first-obtained values can all change the effective result.
Storage
Move from block devices through partitions, LVM, filesystems and mount configuration. Treat logical-volume growth and filesystem growth as separate operations. Remember that ext4 and XFS do not have identical resize capabilities: XFS can grow online but does not support shrinking. Include swap, NFS, automounting, network block devices and evidence-led I/O diagnosis.
Essential Commands
Practise file operations, links, permissions, text processing, redirection, archives, searching and Git. Predict what the shell expands and where standard output and standard error go before running a command. Use man, --help and upstream documentation rather than memorising unexplained command fragments.
Users and Groups
Create and manage local users and groups, password ageing, default files and resource limits. Understand file and directory permission differences, special permission bits and the ACL mask. For directory-backed identities, name the distribution and client stack rather than assuming one universal LDAP configuration path.
A practical study approach
- Build a disposable lab. A local VM is enough for most objectives. Take a snapshot before storage, firewall or boot changes.
- Predict before typing. Write down the expected state, run the command, then inspect the actual state.
- Make changes persistent. Reboot or restart the relevant service when safe, then prove the setting survived.
- Break and recover. Introduce one controlled fault, collect evidence, repair it and verify the original symptom is gone.
- Practise under a clock. Use short task sets that require a working end state, but do not treat a multiple-choice score as evidence of command-line readiness.
Good verification habits matter as much as command recall. Check effective service configuration, active routes, mounted filesystems, permission paths and logs. A command returning without an error does not always mean the requested state is correct or persistent.
Independent knowledge practice
LFCS Knowledge Companion includes 250 original single-answer learning questions grounded in public Linux Foundation and upstream project documentation. Twenty questions are free; full access is US$9 for one year.
Each question explains the mechanism, gives specific feedback for the distractors and links to relevant public documentation. Use it to find knowledge gaps before returning to a real shell. It does not reproduce official tasks, provide a lab or guarantee a pass.
Linux Foundation® is a registered trademark of The Linux Foundation. Linux® is a registered trademark of Linus Torvalds. This independent resource is not affiliated with, endorsed by or sponsored by either trademark owner. No official logo or certification badge is used.