| |

LFCE 161 ๐Ÿง LFCE โ€” 12-Week Study Plan

โฑ๏ธ Estimated read: 13 min | |

The LFCE exam is a performance-based, two-hour test with approximately 15 to 25 tasks to complete in a live terminal . The official domains and competencies were last updated in June 2018 and remain the reference for the exam structure . A realistic preparation timeline for the LFCE is 12 to 20 weeks, because the exam tests advanced engineering skills that build on the LFCS foundation . Twelve weeks is the aggressive end of that range; it assumes the candidate already has LFCS-level administration skills and can dedicate consistent lab time.

This chapter lays out a twelve-week plan that maps each week to the exam domains, allocates the majority of the time to hands-on practice, and builds toward full-scenario drills in the final weeks. The plan is a structure, not a prescription. The candidate who needs more time on Networking or System Design should extend those weeks and compress the ones that are already familiar.

Key point: The exam is hands-on, and the study plan must be hands-on. Reading about nftables rules or Pacemaker configuration does not build the procedural memory that the two-hour performance-based format requires . Every week in this plan allocates the majority of the time to a live lab.


Why twelve weeks is the minimum

The domain weight problem. The LFCE domains are weighted heavily toward engineering tasks: System Design and Deployment is 25%, Operation of Running Systems is 18%, Service Configuration is 17%, and Networking is 15% . Together, those four domains account for 75% of the exam. Each one requires configuration on a live system, not recall of definitions.

The prerequisite problem. The LFCE assumes the LFCS skills are already in place. The Essential Commands domain is only 5%, and User and Group Management is 10% . If the candidate is still learning sed, awk, or basic user management, the twelve-week plan is not enough. The plan assumes those skills are automatic.

The lab problem. The exam environment provides Ubuntu and CentOS Stream . The candidate needs a lab with at least two or three virtual machines to practice the networking, clustering, and service scenarios. A single VM is not sufficient for the multi-host tasks that the System Design and Networking domains require .


Week 1: Lab setup and Essential Commands

The first week is the foundation. The lab must be built before any of the domain content is practiced. Two or three VMs with a shared network, snapshots enabled, and the ability to rebuild from scratch. The distributions should match the exam environment: Ubuntu Server and CentOS Stream .

The Essential Commands domain is only 5% of the exam, but the skills are used in every other domain. The week covers the text-processing tools (grep, sed, awk), the redirection operators, the Git workflow, and the SSH loop for running commands across multiple hosts. The installation competency is practiced by building the lab from ISO images.

The practice for the week is a set of drills: extract a field from a log file with awk, substitute a configuration value with sed, commit a change to a Git repository, and run a command across all the VMs with an SSH loop.


Week 2: Operation of Running Systems (Part 1)

The Operation domain is 18% and covers the day-to-day work of keeping a system running. The first part covers performance monitoring and kernel updates.

The performance tools are vmstat, iostat, sar, ss, and mtr. The practice is to generate load on a VM and identify the bottleneck with the tools. The kernel update practice is to install a new kernel, verify the GRUB entries with grubby, and boot the previous kernel if the new one fails.

The security auditing part is the journalctl and auditd practice: read the logs for a service, filter by priority, and identify a failed login attempt.


Week 3: Operation of Running Systems (Part 2)

The second part of the Operation domain covers recovery, SELinux, and udev.

The recovery practice is to break the bootloader on a VM, boot into rescue mode, mount the root filesystem, chroot into it, and repair GRUB with grub2-install and grub2-mkconfig. The SELinux practice is to set a boolean with setsebool -P, change a file context with chcon, and restore it with restorecon. The udev practice is to write a rule that assigns a persistent name to a device.

The verification for each practice is the same: reboot the VM and confirm that the fix persists.


Week 4: Storage Management

The Storage Management domain is 10% and covers LVM, filesystems, and remote block storage. The LVM practice is to create a physical volume, a volume group, and a logical volume, extend the volume, and resize the filesystem. The filesystem practice is to create an XFS and an ext4 filesystem, set the mount options in /etc/fstab, and verify the mount survives a reboot.

The remote block storage practice is the iSCSI target and initiator setup. The target exports a LUN, the initiator discovers it, logs in, and mounts it. The network share practice is the NFS export and the CIFS mount.


Week 5: User and Group Management

The User and Group Management domain is 10% and covers the external authentication source and PAM. The practice is to configure sssd against an LDAP directory (a local 389-ds instance is sufficient for the lab), verify with getent passwd, and configure the PAM stack for a failed-attempt lockout with pam_faillock.

The critical practice is the PAM test: make the change in a separate terminal, verify that the login works, and confirm that the current session is not locked out.


Week 6: Networking (Part 1)

The Networking domain is 15% and covers performance, tunneling, and NAT. The performance practice is the ss -i retransmission diagnosis and the mtr path analysis. The tunnel practice is the GRE tunnel between two VMs and the SSH local and remote forwards. The NAT practice is the SNAT masquerade and the DNAT port forward, with the verification from a client on the other side of the router.

The forwarding flag (net.ipv4.ip_forward=1) is the prerequisite for both the NAT and the routing practices.


Week 7: Networking (Part 2)

The second part of the Networking domain covers dynamic routing and advanced packet filtering. The dynamic routing practice is the OSPF configuration with frr on two routers, verified with show ip ospf neighbor and show ip route. The packet filtering practice is the nftables rate limit and the stateful ct state rules, verified with nc and nft list ruleset.

The practice for the week is a scenario: two routers, a transit network, and a loopback on each side. The candidate configures OSPF, verifies the adjacency, and pings the remote loopback.


Week 8: Service Configuration (Part 1)

The Service Configuration domain is 17% and covers ten services. The first part covers the HTTP server, the time synchronization server, and the network logging server.

The HTTP practice is the virtual host configuration, the apachectl configtest validation, the SELinux context on the document root, and the curl verification with the Host header. The time synchronization practice is the chrony server and client configuration, verified with chronyc tracking. The network logging practice is the rsyslog TCP listener and the per-host template, verified with a logger command from a client.


Week 9: Service Configuration (Part 2)

The second part of the Service Configuration domain covers DHCP, SMTP, the HTTP proxy, and the authoritative DNS server. The DHCP practice is the dhcpd.conf subnet declaration and the lease verification. The SMTP practice is the postfix configuration and the nc test. The proxy practice is the squid ACL and the curl -x test. The DNS practice is the BIND zone file, validated with named-checkzone, and the dig verification.

The DNS server is the most likely service to be tested in combination with the other services: the DHCP server points to it, the HTTP server uses it for the virtual host name, and the SMTP server uses it for the mail domain.


Week 10: System Design and Deployment

The System Design and Deployment domain is the largest at 25% . It covers capacity planning, post-deployment verification, software packaging, containers, and high availability.

The container practice is the Docker or Podman image build, the Compose stack, and the network configuration. The high availability practice is the Pacemaker and Corosync cluster setup on two VMs, with a shared resource (a virtual IP or a filesystem) that moves between the nodes when one fails. The packaging practice is the RPM or DEB build for a simple script.

The post-deployment verification practice is the checklist: the service is enabled, the firewall is open, the SELinux context is correct, and the functional test passes.


Week 11: Full-scenario drills and timed practice

The eleventh week is the transition from topic practice to exam simulation. The candidate works through full scenarios that combine multiple domains: a web server behind a proxy with a DNS record and a firewall rule, a cluster with a shared storage backend, a centralized logging setup with an authentication source.

The timed drills are the most important part of the week. The candidate sets a timer and completes a set of tasks within the limit. The review after each drill identifies the tasks that took too long and the commands that required reference material.


Week 12: Review and exam preparation

The final week is review, not new material. The candidate reviews the domains that are weakest, re-runs the timed drills, and confirms that the lab environment is stable. The day before the exam is a light review of the command patterns and the verification steps.

The exam-day preparation is the logistics: the environment, the allowed resources (man pages are available), and the time allocation. The candidate should have a mental plan for the tasks that are likely to appear and the order in which to attempt them.


Complete Example Session

# ============================================
# WEEK 1: LAB AND ESSENTIAL COMMANDS
# ============================================
# Build 3 VMs: Ubuntu, CentOS Stream, and a client.
# Practice: sed, awk, grep, git, ssh loop.

# ============================================
# WEEK 2: OPERATION (PERFORMANCE, KERNEL)
# ============================================
# Practice: vmstat, iostat, sar, grubby, journalctl.

# ============================================
# WEEK 3: OPERATION (RECOVERY, SELINUX)
# ============================================
# Practice: rescue mode, chroot, grub2-install, setsebool.

# ============================================
# WEEK 4: STORAGE
# ============================================
# Practice: LVM, XFS/ext4, iSCSI, NFS, CIFS.

# ============================================
# WEEK 5: USER MANAGEMENT
# ============================================
# Practice: sssd, PAM, pam_faillock.

# ============================================
# WEEK 6: NETWORKING (TUNNEL, NAT)
# ============================================
# Practice: GRE, SSH -L/-R, SNAT, DNAT.

# ============================================
# WEEK 7: NETWORKING (ROUTING, FILTERING)
# ============================================
# Practice: OSPF with frr, nft rate limit.

# ============================================
# WEEK 8: SERVICES (HTTP, TIME, LOGGING)
# ============================================
# Practice: httpd, chrony, rsyslog.

# ============================================
# WEEK 9: SERVICES (DHCP, SMTP, PROXY, DNS)
# ============================================
# Practice: dhcpd, postfix, squid, named.

# ============================================
# WEEK 10: SYSTEM DESIGN
# ============================================
# Practice: Pacemaker, Corosync, containers.

# ============================================
# WEEK 11: SCENARIOS AND TIMED DRILLS
# ============================================
# Full scenarios, timer, review.

# ============================================
# WEEK 12: REVIEW
# ============================================
# Weak domains, verification drills, exam logistics.

The twelve weeks covered the lab setup, the two parts of the Operation domain, Storage, User Management, the two parts of Networking, the two parts of Service Configuration, System Design, the scenario drills, and the review.


Quick Reference

Domain weights and weeks

DomainWeightWeeks
Essential Commands5%1
Operation of Running Systems18%2โ€“3
Storage Management10%4
User and Group Management10%5
Networking15%6โ€“7
Service Configuration17%8โ€“9
System Design and Deployment25%10
Review and scenariosโ€”11โ€“12

Lab requirements

ItemDetail
VMsAt least 3 (Ubuntu, CentOS Stream, client)
SnapshotsBefore every major change
NetworkShared network for multi-host tasks
RebuildAbility to reinstall from ISO

Practice allocation

ActivityTime share
Hands-on lab60% or more
Reading and videoLess than 40%
Timed drillsFinal 2 weeks

Best Practices

โœ… Do This:

# Build the lab before starting the domain content
virt-install --cdrom /path/to/ubuntu.iso                     # โœ…
# Take a snapshot before every major change
virsh snapshot-create-as vm pre-change                       # โœ…
# Practice each task until it is automatic
for i in {1..5}; do # repeat the task; done                  # โœ…
# Use timed drills in the final weeks
time # the task                                              # โœ…

โŒ Don’t Do This:

# Read the material without practicing it
# The exam is performance-based                              # โŒ
# Practice on a single VM
# The multi-host scenarios require at least two              # โŒ
# Introduce new topics in the final week
# Review only                                                 # โŒ

Common Pitfalls

PitfallWhy It HappensFix
The lab is not readySkipped week 1Build the VMs before the domain content
A practice task fails and is not repeatedNo snapshotSnapshot before the change; repeat the task
The timed drill is not realisticNo timerSet a timer; review the time spent per task
A domain is under-practicedTime allocation is unevenFollow the domain weights; spend more time on 25% and 18%
The exam-day environment is unfamiliarNo simulationPractice from a clean VM with only man pages

Real-World Examples

1. Lab build

# Three VMs: ubuntu, centos, client

2. Snapshot before a change

virsh snapshot-create-as vm pre-nat

3. Timed drill

time (configure the httpd virtual host and verify with curl)

4. Domain review

# Mark each objective: can do quickly / with docs / needs practice

5. Exam-day plan

Read all tasks first, do the quick wins, return to the hard ones.

6. The domain weights

System Design 25%, Operation 18%, Services 17%, Networking 15%.

7. The verification habit

curl -H "Host: example.com" http://localhost/

8. The persistence check

systemctl is-enabled httpd && reboot && curl http://localhost/

9. The recovery practice

# Break GRUB, boot rescue, chroot, repair.

10. The final review

# Weak domains, verification drills, man pages.

Visual

The twelve-week allocation

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚  WEEK 1   Lab + Essential Commands                          โ”‚
โ”‚  WEEK 2   Operation (performance, kernel)                   โ”‚
โ”‚  WEEK 3   Operation (recovery, SELinux)                     โ”‚
โ”‚  WEEK 4   Storage                                            โ”‚
โ”‚  WEEK 5   User Management                                    โ”‚
โ”‚  WEEK 6   Networking (tunnel, NAT)                           โ”‚
โ”‚  WEEK 7   Networking (routing, filtering)                    โ”‚
โ”‚  WEEK 8   Services (HTTP, time, logging)                     โ”‚
โ”‚  WEEK 9   Services (DHCP, SMTP, proxy, DNS)                 โ”‚
โ”‚  WEEK 10  System Design                                      โ”‚
โ”‚  WEEK 11  Scenarios and timed drills                         โ”‚
โ”‚  WEEK 12  Review                                             โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

The domain weights

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚  System Design      25%  โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆ          โ”‚
โ”‚  Operation          18%  โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆ                 โ”‚
โ”‚  Services           17%  โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆ                  โ”‚
โ”‚  Networking         15%  โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆ                    โ”‚
โ”‚  Storage            10%  โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆ                         โ”‚
โ”‚  User Management    10%  โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆ                         โ”‚
โ”‚  Essential          5%   โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆ                              โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

The practice allocation

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚  Hands-on lab        60%+                                    โ”‚
โ”‚  Reading/video       40%-                                    โ”‚
โ”‚  Timed drills        Weeks 11โ€“12                             โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

The lab topology

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚  VM 1 (Ubuntu) โ”€โ”€โ”                                           โ”‚
โ”‚                   โ”œโ”€โ”€ shared network โ”€โ”€โ–บ VM 3 (client)      โ”‚
โ”‚  VM 2 (CentOS) โ”€โ”€โ”˜                                           โ”‚
โ”‚                                                              โ”‚
โ”‚  Snapshots enabled. Rebuild from ISO.                        โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

Summary

ItemValue
Preparation timeline12โ€“20 weeks
Twelve-week planMinimum for LFCS-level candidates
Largest domainSystem Design and Deployment (25%)
Second largestOperation of Running Systems (18%)
Lab requirementAt least 3 VMs with snapshots
Practice allocation60%+ hands-on
Final weeksTimed drills and review, not new material
Exam formatPerformance-based, 2 hours

Key takeaways:

  • Twelve weeks is the minimum, not the target. The realistic range for LFCE preparation is 12 to 20 weeks, and the twelve-week plan assumes the candidate already has LFCS-level skills . A candidate who is still learning the command line needs more time.
  • The lab is the study environment. At least three VMs, snapshots before every change, and the ability to rebuild from ISO. The multi-host scenarios in Networking, System Design, and Service Configuration cannot be practiced on a single VM.
  • The domain weights determine the time allocation. System Design and Deployment (25%) and Operation of Running Systems (18%) receive the most weeks. Essential Commands (5%) receives the least, because the skills are already assumed .
  • The practice must be hands-on. Reading about a service configuration does not build the procedural memory that the performance-based exam requires. Every week allocates the majority of the time to a live lab .
  • The final weeks are for simulation, not new material. The timed drills in weeks 11 and 12 are the transition from topic practice to exam simulation. Introducing new topics in the final week is a distraction, not a preparation.
  • The verification habit is the exam habit. Every practice task ends with a functional test: curl for the web server, dig for the DNS, chronyc for the time server, and a reboot for the persistence. The exam evaluates the system’s state, not the commands typed.

Remember: The LFCE is a performance-based exam, and the study plan must be a performance-based plan. Build the lab first, allocate the time according to the domain weights, practice every task until it is automatic, and simulate the exam conditions in the final weeks. The twelve-week plan is a structure for a candidate who already has the LFCS foundation; the candidate who needs more time on a specific domain should extend that week and compress the ones that are already familiar.

Was this helpful?


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!