LFCA 129 🐧 LFCA — 8-Week Study Plan - KandZ

The LFCA exam covers six domains with different weights, and most candidates prepare for it while working full time. An eight-week plan is long enough to cover every domain without rushing and short enough to keep the material fresh. The plan is not a schedule of hours per day; it is a sequence of topics with checkpoints. The goal is to move through the domains in order of weight, practice the commands in a real environment, and finish with timed practice that builds exam stamina.

This chapter lays out the eight weeks, the domain coverage for each, the practice activities, and the checkpoints that tell you whether you are ready to move on. It also includes the study resources that align with the exam objectives and the strategies that keep the plan sustainable.

Key point: The plan weights study time by domain weight. System Administration Fundamentals (30%) receives the most time. Linux Fundamentals (16%) receives less than Cloud Computing (18%) despite being the more familiar topic. Following the weights is more efficient than following interest.

Why an eight-week plan works

The forgetting problem. A two-week cram covers the material but does not retain it. Eight weeks provides enough spacing for the material to consolidate. Each week builds on the previous one, and the review weeks revisit earlier domains before moving to new ones.

The practice problem. The LFCA tests recognition and reasoning, not recall. Reading about chmod is not the same as using it. The plan includes hands-on practice in every week—commands typed in a shell, files created and modified, services started and stopped. The commands become muscle memory.

The weighting problem. The domains are weighted differently. A plan that spends equal time on each domain over-prepares for Linux Fundamentals and under-prepares for System Administration. The plan allocates weeks according to weight: three weeks for System Administration, two for Cloud Computing, and one each for the remaining domains and review.

The energy problem. Studying for eight weeks requires pacing. The plan alternates heavy technical weeks with lighter conceptual weeks. Cloud Computing and Project Management are conceptual and can be studied in shorter sessions. System Administration and Linux Fundamentals require hands-on practice and longer sessions.

The checkpoint problem. Each week ends with a checkpoint—a set of practice questions or a hands-on task that confirms the material is understood. If the checkpoint is not passed, the week is repeated or the gaps are filled before moving on. Moving forward without a checkpoint means compounding gaps.

a. Weeks one through three: foundations and the heaviest domain

Week one covers exam logistics and Linux Fundamentals. The first day is orientation: the exam format, the domain weights, the passing score, and the registration process. The remaining days cover distributions and package managers, the Filesystem Hierarchy Standard, and basic commands. The practice is installing a package on two different distributions (or reading the equivalent commands), navigating the filesystem, and using grep and find.

Week 1: Linux Fundamentals
  Day 1: Exam overview, domains, weights
  Day 2: Distributions and package managers
  Day 3: Filesystem Hierarchy Standard
  Day 4: Basic commands (ls, cd, cp, mv, rm, mkdir)
  Day 5: grep, find, I/O redirection
  Day 6: Open source licenses
  Day 7: Checkpoint — Domain 2 practice questions

Week two begins System Administration Fundamentals, the heaviest domain. The week covers user and group management and file permissions. The practice is creating users, assigning groups, setting permissions in numeric and symbolic notation, and changing ownership.

Week 2: System Administration — Users and Permissions
  Day 1: useradd, usermod, userdel, passwd
  Day 2: groupadd, groups, /etc/passwd, /etc/group
  Day 3: Permissions — numeric notation
  Day 4: Permissions — symbolic notation
  Day 5: chown, chgrp, ownership
  Day 6: sudo and the sudoers file
  Day 7: Checkpoint — create a user, set permissions

Week three continues System Administration with services, processes, and logs. The week covers systemctl commands, journalctl for service logs, process inspection with ps, and resource monitoring with top, free, df, and iostat. The practice is managing a real service, reading its logs, and diagnosing a simulated problem.

Week 3: System Administration — Services, Processes, Logs
  Day 1: systemctl start/stop/restart/enable/status
  Day 2: journalctl -u service, log locations
  Day 3: ps, top, process states
  Day 4: free, df, df -i, iostat
  Day 5: Troubleshooting methodology
  Day 6: Backup concepts — tar, rsync, restore drills
  Day 7: Checkpoint — Domain 1 practice questions

b. Weeks four through six: networking, cloud, security, and DevOps

Week four covers networking and troubleshooting, completing Domain 1. The week covers the layered model, the commands for each layer, and the diagnostic sequence. The practice is setting up a network diagnostic scenario: an interface that is down, a gateway that does not respond, a DNS failure, and a closed port.

Week 4: Networking and Troubleshooting
  Day 1: ip link, ip addr, ip route
  Day 2: ping, traceroute, mtr
  Day 3: dig, /etc/resolv.conf
  Day 4: ss, nc, port testing
  Day 5: curl -v, HTTP diagnostics
  Day 6: tcpdump basics
  Day 7: Checkpoint — full diagnostic sequence

Week five covers Cloud Computing Fundamentals, the second-heaviest domain. The material is conceptual, so the practice is scenario-based: identifying which service model fits a given situation, which deployment model is being described, and which scaling approach is being used.

Week 5: Cloud Computing Fundamentals
  Day 1: IaaS, PaaS, SaaS, FaaS
  Day 2: Deployment models — public, private, hybrid, multi-cloud
  Day 3: Virtualization vs containers
  Day 4: Scaling — vertical, horizontal, elasticity
  Day 5: Availability and the shared responsibility model
  Day 6: Budgeting — on-demand, reserved, spot
  Day 7: Checkpoint — Domain 3 practice questions

Week six covers Security and DevOps. The Security material is conceptual: the CIA triad, authentication versus authorization, encryption types, and common threats. The DevOps material is workflow-based: CI/CD, Git commands, containers, and Kubernetes basics.

Week 6: Security and DevOps
  Day 1: CIA triad
  Day 2: Authentication vs authorization, MFA, least privilege
  Day 3: Encryption — symmetric, asymmetric, hashing
  Day 4: Firewalls, compliance, common threats
  Day 5: CI/CD, Git workflow
  Day 6: Containers, Kubernetes basics
  Day 7: Checkpoint — Domain 4 and Domain 5 practice questions

c. Weeks seven and eight: project management and review

Week seven covers IT Project Management Fundamentals and begins the review. The project management material is non-technical: methodologies, architecture, and licensing. The review revisits the earlier domains with practice questions and hands-on exercises.

Week 7: Project Management and Review Begins
  Day 1: Waterfall vs Agile
  Day 2: Scrum, Kanban
  Day 3: Monolith vs microservices
  Day 4: Functional analysis
  Day 5: Open source licensing review
  Day 6: Review — Domain 1 and Domain 2 practice
  Day 7: Checkpoint — Domain 6 practice questions

Week eight is dedicated to review and timed practice. The goal is not to learn new material but to consolidate what has been covered, identify weak areas, and build the stamina to answer 60 questions in 90 minutes.

Week 8: Full Review and Timed Practice
  Day 1: Review — Domain 3 (Cloud)
  Day 2: Review — Domain 4 (Security)
  Day 3: Review — Domain 5 (DevOps) and Domain 6 (PM)
  Day 4: Full timed practice exam 1
  Day 5: Review missed questions
  Day 6: Full timed practice exam 2
  Day 7: Final review, rest, exam logistics

Complete Example Session

# ============================================
# PART 1: WEEK 1 — LINUX FUNDAMENTALS
# ============================================
Study: distributions, FHS, basic commands, licenses
Practice: navigate filesystem, use grep and find
Checkpoint: Domain 2 questions

# ============================================
# PART 2: WEEK 2 — USERS AND PERMISSIONS
# ============================================
Study: useradd, usermod, chmod, chown
Practice: create user, set permissions, change ownership
Checkpoint: create a user with home and specific permissions

# ============================================
# PART 3: WEEK 3 — SERVICES AND LOGS
# ============================================
Study: systemctl, journalctl, ps, df, free
Practice: manage a service, read logs, diagnose a problem
Checkpoint: Domain 1 questions (part 1)

# ============================================
# PART 4: WEEK 4 — NETWORKING
# ============================================
Study: ip, ping, dig, ss, nc, curl
Practice: full diagnostic sequence on a broken network
Checkpoint: Domain 1 questions (part 2)

# ============================================
# PART 5: WEEK 5 — CLOUD
# ============================================
Study: IaaS/PaaS/SaaS/FaaS, deployment models, scaling
Practice: scenario identification
Checkpoint: Domain 3 questions

# ============================================
# PART 6: WEEK 6 — SECURITY AND DEVOPS
# ============================================
Study: CIA, auth, encryption, CI/CD, Git, containers
Practice: Git commands, container commands
Checkpoint: Domain 4 and Domain 5 questions

# ============================================
# PART 7: WEEK 7 — PROJECT MANAGEMENT
# ============================================
Study: methodologies, architecture, licensing
Practice: review earlier domains
Checkpoint: Domain 6 questions

# ============================================
# PART 8: WEEK 8 — TIMED PRACTICE
# ============================================
Day 4: 60 questions, 90 minutes
Day 5: review missed questions
Day 6: second timed exam
Day 7: rest and logistics

# ============================================
# PART 9: DAILY ROUTINE
# ============================================
30–60 minutes: new material
15–30 minutes: hands-on practice
15 minutes: review previous day
Weekly: checkpoint questions

# ============================================
# PART 10: CHECKPOINT CRITERIA
# ============================================
Domain 1: 75%+ on practice questions
Domain 2: 75%+ on practice questions
Domain 3: 75%+ on practice questions
Domain 4: 75%+ on practice questions
Domain 5: 75%+ on practice questions
Domain 6: 75%+ on practice questions
If below 75%: review the domain before moving on

The ten parts covered the eight weeks, the daily routine, and the checkpoint criteria.

Quick Reference

Eight-Week Overview

Week	Domain	Focus	Weight
1	Linux Fundamentals	Distributions, FHS, commands, licenses	16%
2	System Administration	Users, groups, permissions	30%
3	System Administration	Services, processes, logs, backup	30%
4	System Administration	Networking, troubleshooting	30%
5	Cloud Computing	Service models, deployment, scaling	18%
6	Security + DevOps	CIA, encryption, CI/CD, Git, containers	26%
7	Project Management + Review	Methodologies, architecture, review	10%
8	Full Review	Timed practice, weak areas	All

Weekly Structure

Day	Activity
1–4	New material
5	Practice and hands-on
6	Review and weak areas
7	Checkpoint questions

Study Resources

Resource	Use
Linux Foundation LFCA page	Official objectives
`man` pages	Command reference
A Linux VM or container	Hands-on practice
Practice question sets	Checkpoint assessment
Official training course	Structured coverage

Checkpoint Criteria

Score	Action
85%+	Move to next week
75–84%	Review weak areas, then move on
Below 75%	Repeat the week

Best Practices

✅ Do This:

# Follow the domain weights
Spend 3 weeks on System Administration (30%)             # ✅

# Practice in a real environment
Create users, set permissions, manage services           # ✅

# Use checkpoints before moving on
75%+ on practice questions before the next week          # ✅

# Review previous material weekly
15 minutes per day on earlier domains                    # ✅

# Take timed practice exams in week 8
60 questions, 90 minutes                                 # ✅

# Rest before the exam
No cramming the night before                             # ✅

❌ Don’t Do This:

# Don't spend equal time on all domains
Linux is 16%, System Administration is 30%               # ❌

# Don't skip hands-on practice
Reading commands is not the same as using them           # ❌

# Don't move on without a checkpoint
Gaps compound                                            # ❌

# Don't cram in the final week
Review, don't learn new material                         # ❌

# Don't neglect non-technical domains
Project Management is 10%                                # ❌

Common Pitfalls

Pitfall	Why It Happens	Fix
Over-studying Linux	Familiar topic	Check the weights
Skipping practice	Reading feels faster	Type the commands
Moving on without checkpoint	Impatience	75%+ before next week
Ignoring Cloud	Feels abstract	It is 18% of the exam
Cramming in week 8	Anxiety	Review, do not learn new
No timed practice	Unfamiliarity with pace	Two full practice exams

Real-World Examples

1. Week 1 Practice

ls -la /etc
cat /etc/os-release
grep -r "error" /var/log/
find /etc -name "*.conf" -mtime -7

2. Week 2 Practice

sudo useradd -m -s /bin/bash jsmith
sudo passwd jsmith
sudo usermod -aG developers jsmith
chmod 755 script.sh
chown jsmith:developers file.txt

3. Week 3 Practice

sudo systemctl status nginx
sudo journalctl -u nginx -n 20
ps aux --sort=-%mem | head
df -h && df -i
tar -czpf backup.tar.gz /etc
tar -tzf backup.tar.gz > /dev/null && echo "OK"

4. Week 4 Practice

ip link show && ip addr show
ip route show
ping -c 3 8.8.8.8
dig example.com
ss -tulpn | grep :443
nc -zv example.com 443
curl -v https://example.com

5. Week 5 Practice

Scenario: A team wants to deploy code without managing servers.
Answer: PaaS.

Scenario: A company uses AWS and Azure.
Answer: Multi-cloud.

Scenario: A database gets more RAM.
Answer: Vertical scaling.

6. Week 6 Practice — Git

git clone https://github.com/org/repo.git
git checkout -b feature/new
git add .
git commit -m "Add feature"
git push -u origin feature/new
git pull origin main

7. Week 6 Practice — Containers

docker pull nginx:alpine
docker run -d --name web -p 8080:80 nginx:alpine
docker ps
docker logs web
docker stop web
docker rm web

8. Week 7 Practice — Project Management

Waterfall: sequential phases
Agile: iterative sprints
Monolith: single deployable unit
Microservices: independent services
GPL: copyleft
MIT: permissive

9. Week 8 — Timed Exam

Set a timer for 90 minutes.
Answer 60 questions.
Do not pause the timer.
Score at the end.
Review every missed question.

10. Week 8 — Final Review

Review the domains where you scored lowest.
Re-read the summaries.
Re-do the checkpoint questions.
Rest the night before.

Visual

Eight-Week Timeline

┌─────────────────────────────────────────────────────────────┐
│  EIGHT-WEEK STUDY PLAN                                      │
│                                                             │
│  Week 1  ████ Linux Fundamentals (16%)                      │
│  Week 2  ████ System Administration — Users/Perms (30%)     │
│  Week 3  ████ System Administration — Services/Logs (30%)   │
│  Week 4  ████ System Administration — Networking (30%)      │
│  Week 5  ████ Cloud Computing (18%)                         │
│  Week 6  ████ Security (14%) + DevOps (12%)                 │
│  Week 7  ████ Project Management (10%) + Review             │
│  Week 8  ████ Full Review + Timed Practice                  │
│                                                             │
│  Domain weights drive the allocation.                       │
│  System Administration gets the most time.                  │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Weekly Cycle

┌─────────────────────────────────────────────────────────────┐
│  WEEKLY ROUTINE                                             │
│                                                             │
│  Day 1  ──▶ New material                                    │
│  Day 2  ──▶ New material                                    │
│  Day 3  ──▶ New material                                    │
│  Day 4  ──▶ New material + practice                         │
│  Day 5  ──▶ Hands-on practice                               │
│  Day 6  ──▶ Review + weak areas                             │
│  Day 7  ──▶ Checkpoint questions                            │
│                                                             │
│  Daily: 30–60 min new, 15–30 min practice, 15 min review    │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Checkpoint Flow

┌─────────────────────────────────────────────────────────────┐
│  CHECKPOINT DECISION                                        │
│                                                             │
│  Take checkpoint questions                                  │
│    │                                                        │
│    ▼                                                        │
│  Score?                                                     │
│    │                                                        │
│    ├── 85%+ ──▶ Move to next week                           │
│    │                                                        │
│    ├── 75–84% ──▶ Review weak areas, then move on           │
│    │                                                        │
│    └── Below 75% ──▶ Repeat the week                        │
│                                                             │
│  Do not move forward with gaps.                             │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Study Time Allocation

┌─────────────────────────────────────────────────────────────┐
│  TIME BY DOMAIN                                             │
│                                                             │
│  System Administration  ██████████████████████████ 3 weeks  │
│  Cloud Computing        ██████████████████         2 weeks  │
│  Linux Fundamentals     ████████                   1 week   │
│  Security + DevOps      ████████                   1 week   │
│  Project Management     ████                       0.5 week │
│  Review                 ████████                   1.5 weeks│
│                                                             │
│  Matches the exam weights.                                  │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Summary

Week	Focus	Domain Weight
1	Linux Fundamentals	16%
2	Users and permissions	30%
3	Services, logs, backup	30%
4	Networking, troubleshooting	30%
5	Cloud Computing	18%
6	Security and DevOps	26%
7	Project Management and review	10%
8	Full review and timed practice	All

Item	Value
Total duration	8 weeks
Daily study	1–2 hours
Hands-on practice	Every week
Checkpoints	Weekly, 75% threshold
Timed exams	Week 8, two full practice exams
Domain weighting	Follows exam weights

Key takeaways:

The plan follows the exam weights. System Administration Fundamentals (30%) receives three weeks. Cloud Computing (18%) receives one full week and part of another. Linux Fundamentals (16%) receives one week. The allocation matches what the exam tests.
Hands-on practice is not optional. The commands in Domain 1 and Domain 2 are learned by typing them, not by reading about them. Every week includes practice in a real shell or container.
Checkpoints prevent compounding gaps. Each week ends with practice questions. If the score is below 75%, the week is repeated. Moving forward without understanding the previous material makes the next week harder.
Review is built into the plan. Week 7 includes review of earlier domains, and Week 8 is entirely review and timed practice. Spaced repetition consolidates the material.
Timed practice builds exam stamina. Sixty questions in ninety minutes is a specific pace. Two full practice exams in Week 8 develop the rhythm and identify the areas that need a final review.
The non-technical domains are not optional. Project Management is 10% of the exam. Security and DevOps together are 26%. The plan allocates time to each.
Rest before the exam is part of the plan. The night before the exam is not for cramming. It is for rest. The material has been covered over eight weeks; the final night does not change the outcome.

Remember: The eight-week plan is a framework, not a contract. If a week takes longer, repeat it. If a domain is already familiar, move through it faster. The important things are the weights, the practice, and the checkpoints. Follow the weights so the time goes where the exam tests. Practice so the commands are familiar. Check the checkpoints so the gaps are caught early. Eight weeks is enough time to prepare thoroughly if the preparation is structured, and the structure is what the plan provides.

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!