LFCE study guide
LFCE · Work through your exam, one topic at a time.
The Linux Foundation Certified Engineer (LFCE) was an advanced, performance-based certification from the Linux Foundation, positioned above the entry-level LFCS and aimed at engineers who already administered Linux systems daily and wanted to prove depth in networking, storage, services, security, and automation. It was designed for working system administrators, DevOps and site reliability practitioners, and support engineers moving beyond single-host administration toward multi-service, multi-host environments. The LFCE study guide has 5 sections and about 1,783 words.
01Linux System Administration
The system administration domain of the LFCE checks whether you can operate a systemd-era host rather than just log in to one: unit and target control, persistent kernel tuning, logging, and resource constraints. Expect tasks where the command is easy but the persistence or the diagnosis is what is graded.
348 words, about 2 min02Networking
The networking domain moves past a single DHCP interface: bonds, bridges, VLANs, static and policy routing, and packet filtering with firewalld or nftables. Grading usually hinges on whether configuration survives a reboot and whether the packet path is actually open end to end.
354 words, about 2 min03Storage Management
Storage tasks span the local stack (LVM, mdadm RAID, filesystem growth, encryption) and networked storage (NFS, iSCSI, multipath). The exam rewards knowing which resize operation is possible online and which export or target option actually grants the access asked for.
346 words, about 2 min04Service Configuration and Security
This domain pairs service deployment with the controls that decide whether it actually works: SELinux labeling and booleans, firewalld, TLS configuration, SSH hardening, sudo and PAM policy, auditd, and systemd sandboxing directives. Virtual hosts: Apache uses <VirtualHost :443 blocks in /etc/httpd/conf.d/ .conf; nginx uses server blocks.
357 words, about 2 min05Troubleshooting and Automation
The final domain tests method plus repeatability: a layered diagnostic approach (kernel, service, network, permissions/SELinux, resources) and automation that produces the same result every run - shell scripts, Ansible, systemd timers, and log rotation. Work the stack in order.
378 words, about 2 min