What a performance exam rewards
LFCS gives you a live system and a list of tasks, and grades the state the machine ends in. Nobody reads your commands. That changes what is worth practising: not memorising one blessed route, but finishing, making it survive a reboot, and checking it as the grader will - which is not the same as checking it as yourself.
Readiness Guide 38 of 38 Intermediate
- PlatformsUbuntu 26.04 LTS + AlmaLinux 10.2
- LVM2.03.31 (Ubuntu) / 2.03.36 (AlmaLinux)
- nftables1.1.6 (Ubuntu) / 1.1.5 (AlmaLinux)
- TimeAbout 16 min
Captured on RHEL 10 because the Ubuntu hosts were offline; every command here behaves identically on both families, which is why this guide is the one that could be written while they were down.
- Firewallufw 0.36.2 enabled but reporting inactive / firewalld active
- Network confignetplan + systemd-networkd / NetworkManager 1.56.0
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| LFCS-A01 | 192.168.0.70 | Ubuntu 26.04 LTS | Primary host - most guides run only here | 2 Core | 4 GB | 50 GB |
| LFCS-C01 | 192.168.0.72 | AlmaLinux 10.2 | The other distribution - dnf, firewalld and NetworkManager | 2 Core | 4 GB | 50 GB |
This guide includes
Use this before sitting the exam. This matters because LFCS grades the state of the machine rather than your route to it - and a task is not finished until it survives a reboot.
- reaching one end state by three different routes
- checking the end state rather than your memory of it
- seeing why verifying as the wrong user looks like a failure
- making changes that survive a reboot, for services and for mounts
- running the same checks on a host that spells the units differently
Before you start
-
Three routes, one end state
-
So check the end state, not your memory of it
-
And verifying as the wrong user looks like a failure
-
A task is not finished until it survives a reboot
-
The same rule, for everything else you change
-
The same check, on a host that spells the units differently