LFCE 162 ๐ง LFCE โ Final Review and Exam Day Tips
The LFCE exam is a performance-based, two-hour test with approximately 15 to 25 tasks completed in a live terminal . The official domains and competencies were updated in June 2018 and remain the reference for the exam structure: Essential Commands (5%), Operation of Running Systems (18%), User and Group Management (10%), Networking (15%), Service Configuration (17%), Storage Management (10%), and System Design and Deployment (25%) . The preparation timeline is 12 to 20 weeks, and the final review is not about learning new material. It is about confirming that the procedural memory is in place, that the verification habits are automatic, and that the exam-day logistics are settled.
This chapter covers the final review checklist, the exam-day strategy for the two-hour format, and the common mistakes that cost points even when the candidate knows the material.
Key point: The exam is evaluated by the system’s state, not by the commands typed. Every task is complete only when the verification passes. The candidate who configures a service and forgets to enable it, or opens a firewall port at runtime and forgets the --permanent flag, loses points for a task that was almost correct.
Why the final review is different
The procedural memory problem. The final review is not a reading week. The candidate has already practiced the tasks; the review confirms that each one can be performed without reference material. The practice is the verification: run the task, run the check, and measure the time.
The integration problem. The exam tasks combine domains. A web server task may require the DNS record, the firewall rule, the SELinux context, and the TLS certificate. The final review is the practice of the complete sequence, not the individual command.
The time problem. Two hours for 15 to 25 tasks is approximately 5 to 8 minutes per task. The candidate who knows the commands but needs to look up the flags will run out of time. The final review is the practice of the commands that are used most often.
a. The final review checklist
The checklist is organized by domain. Each item is a task that can be performed in a lab and verified with a command.
Essential Commands. sed -i for in-place substitution, awk -F: for field extraction, grep -E for extended regex, git add and git commit, and the SSH loop with BatchMode=yes and </dev/null. The verification is the output of the pipeline and the exit code of the loop.
Operation of Running Systems. systemctl status and journalctl -u for a service, vmstat and iostat for performance, grubby and grub2-mkconfig for the kernel, and setsebool -P and restorecon for SELinux. The verification is a reboot and a functional test.
Storage Management. LVM create and extend, XFS and ext4 creation, /etc/fstab with _netdev for network filesystems, iSCSI target and initiator, and NFS and CIFS mounts. The verification is a mount and a write.
User and Group Management. sssd configuration, authselect, nsswitch.conf, and the PAM stack with pam_faillock. The verification is getent passwd and a login test in a separate terminal.
Networking. GRE tunnel, SSH forwards, SNAT and DNAT with nft, OSPF with frr, and the nft rate limit. The verification is ping, curl, show ip route, and nft list ruleset.
Service Configuration. HTTP virtual host, chrony, rsyslog, dhcpd, postfix, squid, BIND zone, and PXE. The verification is curl, dig, chronyc, and nc.
System Design and Deployment. Pacemaker and Corosync cluster, container build and Compose stack, RPM or DEB packaging, and the post-deployment checklist. The verification is the cluster failover, the container health check, and the package installation.
b. The exam-day strategy
Read all tasks first. The exam presents the tasks in a list. The candidate should read all of them before starting, identify the quick wins, and estimate the time for each. The tasks that are already familiar are completed first, which builds confidence and banks the points.
Do the quick wins first. The tasks that can be completed in 2 to 3 minutes are done first: a sed substitution, a systemctl enable, a firewall rule, a DNS record. The longer tasksโthe cluster, the PXE server, the OSPF configurationโare left for the middle of the session.
Verify every task. Every task ends with a functional test. The curl with the Host header, the dig against the local resolver, the chronyc tracking, the ss -tlnp for the listener, and the systemctl is-enabled for the persistence. The verification is the evidence that the task is complete.
Leave the hardest task for last. The task that requires the most time is left for the end. If the time runs out, the candidate has completed the tasks that were quick and has a partial result on the hardest one, rather than a partial result on several.
Use the man pages. The exam environment provides the man pages. The candidate who forgets a flag can check it without losing time. The man command and the --help flag are the reference.
c. The common mistakes
The persistence mistake. A service that is started but not enabled will not survive a reboot. The exam tasks often specify “ensure the service starts at boot.” The systemctl enable command is the fix.
The firewall mistake. A firewall-cmd --add-service that is not --permanent is lost on the next reload. The --permanent flag followed by --reload is the correct sequence.
The SELinux mistake. A service that returns a 403 despite a correct configuration is a SELinux context problem. The semanage fcontext and restorecon commands are the fix. Disabling SELinux is not.
The validation mistake. A restart without a configuration check is a restart that may fail. The apachectl configtest, named-checkconf, postfix check, and squid -k parse commands are the validation steps.
The verification mistake. A command that exits zero is not evidence. The curl, dig, chronyc, and nc tests are the evidence.
Complete Example Session
# ============================================
# PART 1: THE ESSENTIAL COMMANDS REVIEW
# ============================================
sed -i 's/old/new/g' file
awk -F: '{print $1}' /etc/passwd
grep -E 'error|fail' /var/log/messages
git add . && git commit -m "change"
for h in web1 web2; do ssh -o BatchMode=yes "$h" 'cmd' </dev/null; done
# ============================================
# PART 2: THE OPERATION REVIEW
# ============================================
systemctl status httpd
journalctl -u httpd -n 50
vmstat 1 5
grubby --info=ALL
setsebool -P httpd_can_network_connect on
restorecon -Rv /var/www/html
# ============================================
# PART 3: THE STORAGE REVIEW
# ============================================
pvcreate /dev/sdb && vgcreate vg0 /dev/sdb
lvcreate -L 10G -n lv0 vg0
mkfs.xfs /dev/vg0/lv0
mount /dev/vg0/lv0 /mnt
# ============================================
# PART 4: THE USER REVIEW
# ============================================
getent passwd alice
authselect select sssd with-mkhomedir
# PAM: pam_faillock in /etc/pam.d/system-auth
# ============================================
# PART 5: THE NETWORKING REVIEW
# ============================================
ip tunnel add gre1 mode gre remote 192.168.2.1 local 192.168.1.1
nft add rule ip nat postrouting oifname "eth0" masquerade
nft add rule ip nat prerouting tcp dport 8080 dnat to 192.168.1.10:80
nft add rule ip filter input tcp dport 22 ct state new limit rate 5/minute accept
# ============================================
# PART 6: THE SERVICES REVIEW
# ============================================
apachectl configtest && systemctl reload httpd
named-checkconf && named-checkzone example.com zonefile
postfix check && systemctl reload postfix
squid -k parse && systemctl reload squid
# ============================================
# PART 7: THE SYSTEM DESIGN REVIEW
# ============================================
pcs cluster setup mycluster node1 node2 --start --enable
pcs status
docker compose up -d
rpmbuild -ba specfile
# ============================================
# PART 8: THE VERIFICATION HABIT
# ============================================
curl -H "Host: example.com" http://localhost/
dig @localhost example.com
chronyc tracking
systemctl is-enabled httpd
# ============================================
# PART 9: THE EXAM-DAY PLAN
# ============================================
# 1. Read all tasks.
# 2. Do the quick wins.
# 3. Verify each task.
# 4. Leave the hardest for last.
# 5. Use man pages for flags.
# ============================================
# PART 10: THE PERSISTENCE CHECK
# ============================================
systemctl is-enabled httpd
firewall-cmd --list-all
reboot
curl http://localhost/
The ten parts covered the Essential Commands review, the Operation review, the Storage review, the User review, the Networking review, the Services review, the System Design review, the verification habit, the exam-day plan, and the persistence check.
Quick Reference
The final review by domain
| Domain | Key task | Verification |
|---|---|---|
| Essential Commands | sed -i, awk, SSH loop | Output and exit code |
| Operation | journalctl, kernel, SELinux | Reboot, functional test |
| Storage | LVM, filesystems, iSCSI | Mount, write |
| User Management | sssd, PAM | getent, login test |
| Networking | Tunnel, NAT, OSPF, nft | ping, curl, show ip route |
| Services | HTTP, DNS, DHCP, mail, proxy | curl, dig, nc |
| System Design | Cluster, containers, packages | Failover, health check |
The exam-day checklist
| Step | Action |
|---|---|
| 1 | Read all tasks |
| 2 | Do the quick wins |
| 3 | Verify each task |
| 4 | Leave the hardest for last |
| 5 | Use man pages |
The persistence checklist
| Item | Command |
|---|---|
| Service at boot | systemctl enable <svc> |
| Firewall permanent | firewall-cmd --permanent --add-service |
| SELinux context | semanage fcontext, restorecon |
| fstab entry | _netdev, nofail |
The common mistakes
| Mistake | Fix |
|---|---|
| Service not enabled | systemctl enable |
| Firewall not permanent | --permanent + --reload |
| SELinux context wrong | semanage fcontext, restorecon |
| Config not validated | configtest, checkconf |
| No functional test | curl, dig, nc |
Best Practices
โ Do This:
# Verify every task with a functional test
curl -H "Host: example.com" http://localhost/ # โ
# Enable the service at boot
systemctl enable --now httpd # โ
# Make the firewall change permanent
firewall-cmd --permanent --add-service=http && firewall-cmd --reload # โ
# Read all tasks before starting
# Identify the quick wins # โ
โ Don’t Do This:
# Start the service without enabling it
systemctl start httpd # โ
# Add the firewall rule at runtime only
firewall-cmd --add-service=http # โ
# Restart without validating the configuration
systemctl restart named # โ
# Assume the task is done because the command exited zero
systemctl status httpd # โ
Common Pitfalls
| Pitfall | Why It Happens | Fix |
|---|---|---|
| Points lost on a “working” service | Not enabled at boot | systemctl enable |
| Firewall rule lost after reload | Not --permanent | --permanent + --reload |
| 403 despite correct config | SELinux context | restorecon |
| Service fails after restart | Config not validated | configtest |
| Time runs out | Hard task attempted first | Quick wins first |
Real-World Examples
1. The verification
curl -H "Host: example.com" http://localhost/
2. The persistence
systemctl is-enabled httpd
3. The firewall
firewall-cmd --permanent --add-service=http && firewall-cmd --reload
4. The SELinux fix
restorecon -Rv /var/www/html
5. The config validation
named-checkconf && named-checkzone example.com zonefile
6. The cluster
pcs status
7. The container
docker compose ps
8. The package
rpm -qa | grep mypackage
9. The exam-day plan
Read all โ quick wins โ verify โ hardest last โ man pages
10. The final check
reboot && curl http://localhost/
Visual
The exam-day flow
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ Read all tasks โ
โ โ โ
โ โผ โ
โ Identify quick wins โ
โ โ โ
โ โผ โ
โ Complete quick wins + verify โ
โ โ โ
โ โผ โ
โ Complete medium tasks + verify โ
โ โ โ
โ โผ โ
โ Attempt the hardest task โ
โ โ โ
โ โผ โ
โ Final verification pass โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
The persistence checklist
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ Service enabled? โโโบ systemctl is-enabled โ
โ Firewall open? โโโบ firewall-cmd --list-all โ
โ SELinux correct? โโโบ ls -Z, restorecon โ
โ Mount persistent? โโโบ /etc/fstab with _netdev โ
โ Reboot and verify? โโโบ the only real test โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
The verification habit
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ Command exits zero โ NOT evidence โ
โ curl / dig / nc / chronyc โ evidence โ
โ reboot + test โ persistence evidence โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
The common mistake pattern
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ Config applied โโโบ service restarted โโโบ looks fine โ
โ โ โ
โ โผ โ
โ Not enabled / not permanent / no SELinux / no test โ
โ โ โ
โ โผ โ
โ Points lost on a task that "worked" in the session โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Summary
| Item | Value |
|---|---|
| Exam format | Performance-based, 2 hours |
| Task count | Approximately 15โ25 |
| Largest domain | System Design and Deployment (25%) |
| Final review focus | Procedural memory and verification habits |
| Exam-day strategy | Read all, quick wins first, verify, hardest last |
| Persistence checks | systemctl enable, --permanent, restorecon |
| Verification tools | curl, dig, nc, chronyc |
| Allowed resources | Man pages |
Key takeaways:
- The exam is evaluated by the system’s state, not by the commands typed. Every task is complete only when the verification passes. The
curl,dig,nc, andchronyctests are the evidence that the task is done. - The persistence checks are the most common source of lost points. A service that is started but not enabled, a firewall rule that is not
--permanent, and an SELinux context that is not restored are all tasks that “worked” in the session but will not survive the evaluation. - The final review is not a reading week. The candidate has already practiced the tasks; the review confirms that each one can be performed without reference material. The practice is the verification, and the measure is the time.
- The exam-day strategy is to read all tasks first and do the quick wins. The tasks that are already familiar are completed first, which banks the points and leaves the hardest task for the end. The man pages are available for the flags that are forgotten.
- The integration tasks combine domains. A web server task may require the DNS record, the firewall rule, the SELinux context, and the TLS certificate. The candidate who practices the complete sequence is the candidate who completes the task in the time available.
- The two-hour format rewards the candidate who is fast and correct. The commands that are automatic are the ones that save time. The final review is the practice of those commands, not the study of new material.
Remember: The LFCE is a performance-based exam, and the final review is a performance review. The candidate who can configure a service, validate the configuration, enable it at boot, open the firewall permanently, fix the SELinux context, and verify with a functional test has the complete pattern. The exam-day strategy is to read all tasks, do the quick wins, verify every task, and leave the hardest for last. The persistence checks are the difference between a task that works in the session and a task that passes the evaluation.
Stop using slow, ad-bloated tool sites! ๐คฎ
๐ Search “KandZ Tools” on Google to use many professional utilities for free.
KandZ.me is the ultimate minimalist hub for:
โ
Finance (Mortgage, Interest, Inflation)
โ
Tech (Base64, JSON, Dev Suite, IP)
โ
Health (BMI, BMR, TDEE)
โ
Productivity (Timer, Workspace, QR)
โก๏ธ Fast & Private
๐ No data leaves your device
๐ 100% Free
๐ Use it now: https://tools.kandz.me
๐ Bookmark itโyouโll need it later!