LFCS 168 🐧 LFCS — 10-Week Study Plan - KandZ

⏱️ Estimated read: 10 min | |

The previous chapters covered the technical content of every domain and the practice scenarios. This chapter covers the structure that turns the content into the certification: the 10-week study plan. The LFCS is the performance-based exam with the 2-hour limit and the 15–20 hands-on tasks . The exam requires the fluency, not the familiarity. The 10-week plan is the realistic timeline for the candidate with the intermediate Linux experience, the dedicated lab environment, and the 10–15 hours per week of study time . The critical trap is the passive study. The reading and the video courses are the supplement. The typing and the breaking and the fixing are the requirement. The candidates who spend the 60% of the study time in the live lab pass at the roughly twice the rate of those who focus primarily on the reading .

Key point: The 10-week plan covers the five domains in the order of the dependency: the Essential Commands and the Users/Groups first, the Operations Deployment and the Networking second, the Storage and the Services third, and the practice exams and the weak-area review last. The plan assumes the lab VM (the Ubuntu Server or the CentOS Stream) that the candidate can destroy and rebuild . The exam allows the man pages but not the internet . The study must include the man page practice.

Why a structured study plan matters

The breadth problem. The exam covers the five domains with the combined 100% weight: the Operations Deployment (25%), the Networking (25%), the Storage (20%), the Essential Commands (20%), and the Users & Groups (10%) . The candidate who focuses on the favorite domain misses the points in the others. The plan allocates the weeks proportionally to the weights.

The depth problem. The exam tests the persistence, the recovery, and the edge cases. The sysctl -w is not the persistence. The systemctl start is not the enable. The ip addr add is not the NetworkManager profile. The plan must include the persistence drills and the recovery drills, not just the command drills.

The speed problem. The exam is the 2 hours for the 15–20 tasks . The candidate who knows the commands but types them slowly runs out of the time. The plan must include the timed practice from the week 7. The killer.sh simulator (the included with the exam purchase) is the best practice for the exam environment .

The trap problem. The exam allows the man pages . The candidate who memorizes the flags instead of the man page navigation wastes the study time. The man -k (the apropos) is the skill that the exam rewards .

The trade-off. The 10-week plan is the aggressive for the candidate with the full-time job. The 12-week plan is the realistic . The 10-week plan assumes the 10–15 hours per week and the prior Linux experience. The candidate who is brand-new to Linux should take the LFCA first .

a. Weeks 1–3: Essential Commands and Users/Groups

The weeks 1–3 cover the Essential Commands (20%) and the Users & Groups (10%) . The focus is the file operations, the text processing, the permissions, the user lifecycle, and the sudo.

# Week 1: File operations and text processing
mkdir -p ~/lab/week1
cp -r /etc ~/lab/week1/etc-backup
grep -r "error" /var/log/ 2>/dev/null | head
sed -i 's/old/new/g' ~/lab/week1/config.txt
awk -F: '{print $1, $3}' /etc/passwd

# Week 2: Permissions and links
chmod 750 ~/lab/week1/script.sh
ln -s ~/lab/week1/script.sh ~/lab/week1/script-link
ln ~/lab/week1/file.txt ~/lab/week1/file-hard
find / -type f -name "*.conf" 2>/dev/null | head

# Week 3: Users, groups, sudo
sudo useradd -m -s /bin/bash -G developers alice
sudo chage -M 90 -W 7 alice
sudo tee /etc/sudoers.d/alice <<'EOF'
alice ALL=(ALL) NOPASSWD: /usr/bin/systemctl restart nginx
EOF
sudo chmod 440 /etc/sudoers.d/alice
sudo visudo -c

The grep -r searches the directory. The sed -i edits in place. The awk -F: prints the fields. The chmod 750 sets the octal. The ln -s creates the soft link. The ln creates the hard link. The find searches the type and the name. The useradd -m -s -G creates the user. The chage sets the aging. The sudoers.d with the 440 and the visudo -c is the safe sudo.

The daily drill: the 30 minutes of the man page practice with the man -k and the apropos .

b. Weeks 4–6: Operations Deployment and Networking

The weeks 4–6 cover the Operations Deployment (25%) and the Networking (25%) . The focus is the systemd, the journal, the packages, the ip commands, the firewall, and the SSH.

# Week 4: systemd and processes
systemctl list-units --type=service
systemctl enable --now nginx
journalctl -u nginx -p err --since "1 hour ago"
ps aux | grep nginx
systemctl edit nginx  # the override

# Week 5: Networking
nmcli connection modify "Wired connection 1" ipv4.method manual ipv4.addresses 192.168.1.100/24
nmcli connection up "Wired connection 1"
ip addr show
ip route show
ss -tlnp

# Week 6: Firewall and SSH
firewall-cmd --permanent --add-service=http
firewall-cmd --reload
firewall-cmd --list-all
ssh-keygen -t ed25519
ssh-copy-id alice@server
sshd -t

The systemctl list-units shows the services. The journalctl -u filters. The nmcli is the persistent. The ip addr and the ip route are the runtime verification. The firewall-cmd --permanent is the persistence. The sshd -t is the validation.

The drill: the break the config and the fix it. The nginx -t with the typo, the sshd -t with the wrong port, the firewall-cmd with the missing rule.

c. Weeks 7–10: Storage, Services, and the practice exams

The weeks 7–10 cover the Storage (20%) and the Services (the part of the Operations) . The focus is the LVM, the RAID, the fstab, the web server, and the exam simulation.

# Week 7: Storage
sudo pvcreate /dev/sdc
sudo vgcreate vgdata /dev/sdc
sudo lvcreate -L 5G -n lvdata vgdata
sudo mkfs.ext4 /dev/vgdata/lvdata
sudo mount /dev/vgdata/lvdata /mnt/data
echo "UUID=$(blkid -s UUID -o value /dev/vgdata/lvdata) /mnt/data ext4 defaults 0 2" | sudo tee -a /etc/fstab
sudo mount -a

# Week 8: Web server
sudo apt install nginx
sudo tee /etc/nginx/sites-available/mysite <<'EOF'
server { listen 80; server_name mysite.local; root /var/www/mysite; }
EOF
sudo ln -s /etc/nginx/sites-available/mysite /etc/nginx/sites-enabled/
sudo nginx -t
sudo systemctl reload nginx
curl -H "Host: mysite.local" http://localhost

# Week 9: Practice exam 1 (timed, 2 hours)
# Use the killer.sh or the KodeKloud mock 

# Week 10: Weak-area review and Practice exam 2 (timed)
# Review the error log, the command reference, and the man pages

The pvcreate, the vgcreate, the lvcreate are the LVM stack. The blkid and the /etc/fstab are the persistence. The nginx -t and the reload are the apply. The curl -H tests the virtual host. The week 9 and the week 10 are the timed practice .

The killer.sh simulator is the closest to the exam environment. The included with the exam purchase . The practice exam reveals the weak areas: the storage persistence, the firewall rule, the SELinux context, or the time management.

Complete Example Session

# ============================================
# PART 1: WEEK 1 — TEXT PROCESSING
# ============================================

grep -r "sshd" /var/log/ 2>/dev/null | head
sed -i 's/PasswordAuthentication yes/PasswordAuthentication no/' /tmp/sshd_test
awk '{print $1}' /tmp/list.txt

# ============================================
# PART 2: WEEK 2 — PERMISSIONS
# ============================================

chmod 755 /tmp/script.sh
chmod u+x,g-w /tmp/script.sh
ln -s /tmp/file.txt /tmp/link

# ============================================
# PART 3: WEEK 3 — USERS AND SUDO
# ============================================

sudo useradd -m -s /bin/bash -G wheel alice
sudo chage -M 90 alice
sudo tee /etc/sudoers.d/alice <<'EOF'
alice ALL=(ALL) NOPASSWD: /usr/bin/systemctl
EOF
sudo chmod 440 /etc/sudoers.d/alice

# ============================================
# PART 4: WEEK 4 — SYSTEMD
# ============================================

systemctl enable --now nginx
journalctl -u nginx -p err
systemctl edit nginx

# ============================================
# PART 5: WEEK 5 — NETWORKING
# ============================================

nmcli connection modify "Wired connection 1" ipv4.method manual ipv4.addresses 192.168.1.100/24
nmcli connection up "Wired connection 1"
ip addr show

# ============================================
# PART 6: WEEK 6 — FIREWALL AND SSH
# ============================================

firewall-cmd --permanent --add-service=ssh
firewall-cmd --reload
sshd -t

# ============================================
# PART 7: WEEK 7 — LVM
# ============================================

pvcreate /dev/sdc
vgcreate vgdata /dev/sdc
lvcreate -L 5G -n lvdata vgdata
mkfs.ext4 /dev/vgdata/lvdata

# ============================================
# PART 8: WEEK 8 — WEB SERVER
# ============================================

nginx -t
systemctl reload nginx
curl -H "Host: mysite.local" http://localhost

# ============================================
# PART 9: WEEK 9-10 — TIMED PRACTICE
# ============================================

# killer.sh or KodeKloud mock exam
# 2 hours, 15-20 tasks
# Review the weak areas

The nine parts trace the 10-week plan: the text processing, the permissions, the users and sudo, the systemd, the networking, the firewall and SSH, the LVM, the web server, and the timed practice.

Quick Reference

Week Allocation

Week	Focus	Domain Weight
1–3	Essential Commands, Users	30%
4–6	Operations, Networking	50%
7–8	Storage, Services	20%
9–10	Practice exams, review	—

Daily Drill

Activity	Time
Terminal practice	60%
Reading/video	20%
Man page practice	20%

Exam Facts

Item	Value
Format	Performance-based
Tasks	15–20
Duration	2 hours
Passing	66%
Retake	One free within 12 months

Best Practices

✅ Do This:

man -k "network" | grep -i route
<!-- Practice the man page search -->                # ✅

systemctl enable --now nginx
<!-- Use --now for both the start and the boot -->    # ✅

UUID=$(blkid -s UUID -o value /dev/sdb1)
echo "UUID=$UUID /mnt/data ext4 defaults 0 2" >> /etc/fstab
<!-- Use the UUID in the fstab -->                   # ✅

❌ Don’t Do This:

# Read the books without the terminal
<!-- The exam tests the typing -->                  # ❌

# Memorize the flags instead of the man pages
<!-- The man pages are available in the exam -->     # ❌

# Skip the timed practice
<!-- The time management is the skill -->            # ❌

Common Pitfalls

Pitfall	Why It Happens	Fix
Passive study	Reading without the typing	60% in the terminal
Domain imbalance	Focusing on the favorite	Follow the weights
No timed practice	Reading the tasks	Week 9–10 the mocks
Persistence forgotten	Using the runtime commands	Drill the `/etc/fstab`, the `enable`, the `--permanent`
Man pages unused	Memorizing the flags	Practice `man -k`

Real-World Examples

1. Week 1 Drill

grep -r "error" /var/log/

2. Week 2 Drill

chmod 750 /tmp/script.sh

3. Week 3 Drill

useradd -m -s /bin/bash alice

4. Week 4 Drill

systemctl enable --now nginx

5. Week 5 Drill

nmcli connection modify "Wired connection 1" ipv4.method manual

6. Week 6 Drill

firewall-cmd --permanent --add-service=http

7. Week 7 Drill

lvcreate -L 5G -n lvdata vgdata

8. Week 8 Drill

nginx -t && systemctl reload nginx

9. Week 9 Drill

killer.sh mock exam (2 hours)

10. Week 10 Drill

Review the weak areas and the error log

Visual

10-Week Timeline

┌──────────────────────────────────────────────┐
│  Weeks 1-3: Essential + Users (30%)          │
└──────────────────┬───────────────────────────┘
                   │
                   ▼
┌──────────────────────────────────────────────┐
│  Weeks 4-6: Operations + Networking (50%)    │
└──────────────────┬───────────────────────────┘
                   │
                   ▼
┌──────────────────────────────────────────────┐
│  Weeks 7-8: Storage + Services (20%)         │
└──────────────────┬───────────────────────────┘
                   │
                   ▼
┌──────────────────────────────────────────────┐
│  Weeks 9-10: Practice exams + Review         │
└──────────────────────────────────────────────┘

Study Time Allocation

┌──────────────────────────────────────────────┐
│  60%: Terminal practice                      │
│  20%: Reading and video                      │
│  20%: Man page navigation                    │
└──────────────────────────────────────────────┘

Summary

Item	Value
Duration	10 weeks
Study time	10–15 hours/week
Week 1–3	Essential Commands, Users
Week 4–6	Operations, Networking
Week 7–8	Storage, Services
Week 9–10	Practice exams
Terminal time	60%
Man page time	20%
Exam duration	2 hours
Exam tasks	15–20

Key takeaways:

The plan follows the domain weights. The Operations and the Networking are the 25% each, the Storage and the Essential are the 20% each, and the Users is the 10% . The weeks are allocated proportionally.
The terminal practice is the 60%. The reading and the video are the supplement. The candidates who spend the majority of the time in the live lab pass at the roughly twice the rate .
The man pages are the exam tool. The exam allows the man pages but not the internet . The man -k and the apropos are the skills that the exam rewards .
The timed practice is the week 9–10. The killer.sh or the KodeKloud mock exam simulates the exam environment. The practice reveals the weak areas and the time management .
The persistence and the recovery are the traps. The /etc/fstab, the systemctl enable, the --permanent, the restorecon, the /etc/audit/rules.d/. The exam tests the state after the reboot, not just the command output.

Remember: The 10-week plan is the structure. The terminal is the study. The man pages are the tool. The timed practice is the test. The exam is the 2 hours, the 15–20 tasks, the 66% passing . The plan is the guide, not the guarantee. The practice is the requirement.

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!