LFCS Study Strategy¶

Study Approach¶

Phase 1: Command-Line Foundation (2-3 weeks)¶

1. Essential Commands
2. Master text processing (grep, sed, awk)
3. File operations and permissions
4. Finding files and archiving

5. I/O redirection and pipes

6. User and Group Management

7. Create and modify users and groups
8. Configure sudo access
9. Understand PAM basics

Phase 2: System Administration (2-3 weeks)¶

1. Running Systems
2. systemd service management
3. Process management and scheduling
4. Boot process and targets

5. Kernel module management

6. Networking

7. IP configuration (static and dynamic)
8. Firewall configuration with firewalld
9. SSH setup and hardening
10. Network troubleshooting tools

Phase 3: Storage and Services (2-3 weeks)¶

1. Storage Management
2. Disk partitioning and filesystems
3. LVM workflow (create, extend, resize)
4. RAID configuration

5. Swap management

6. Service Configuration

7. Apache/Nginx web server setup
8. NFS and Samba file sharing
9. Basic DNS configuration
10. SSH and database configuration

Phase 4: Exam Preparation (1 week)¶

1. Practice Under Exam Conditions
2. Timed full practice sessions
3. Use killer.sh exam simulator if available

4. Focus on weak areas

5. Final Review

6. Command syntax review
7. Configuration file locations
8. Troubleshooting methodology

Study Resources¶

Official¶

• 📖 LFCS Certification Page - Exam details
• 📖 LFCS Exam Domains - Exam objectives
• 📖 LFS201 Training Course - Official training
• 📖 LFCS Candidate Handbook - Exam rules

Practice Environments¶

• 📖 killer.sh - Exam simulator (included with exam purchase)
• 📖 KodeKloud LFCS - Interactive labs
• VirtualBox/VMware - Local VM for unlimited practice
• AWS Free Tier - Cloud-based Ubuntu instance

Reference Documentation¶

• 📖 Ubuntu Server Guide - Ubuntu server administration
• 📖 GNU Coreutils Manual - Essential command reference
• 📖 systemd Documentation - systemd reference
• 📖 Linux man pages online - Online man pages

Books¶

1. LFCS Study Guide by Sander van Vugt
2. The Linux Command Line by William Shotts (free at linuxcommand.org)
3. How Linux Works by Brian Ward

Exam-Specific Strategy¶

Understanding the Exam Format¶

• Terminal-based exam with live Linux environment
• Multiple tasks to complete within 2 hours
• Each task has specific requirements and is scored independently
• Partial credit may be available for some tasks
• You can access man pages and installed documentation
• You CANNOT access the internet during the exam
• One free retake included with exam purchase

Time Management¶

• 2 hours for all tasks - allocate time based on task complexity
• Read all tasks first - get an overview before starting
• Start with confident tasks - build momentum with tasks you know well
• Skip difficult tasks - come back to them later rather than getting stuck
• Verify as you go - check each task works before moving to the next
• Save 15-20 minutes - for review and verification at the end

Using Man Pages Effectively¶

man command             # full manual page
man -k keyword          # search manual pages by keyword
command --help          # quick help (often enough)
apropos keyword         # find related commands
info command            # sometimes more detailed than man
/pattern                # search within man page
n / N                   # next/previous search match

Practice tip: Before the exam, practice finding information in man pages. Know the structure: NAME, SYNOPSIS, DESCRIPTION, OPTIONS, EXAMPLES.

Key Configuration File Locations¶

Common Exam Pitfalls¶

1. Forgetting persistence - Changes must survive a reboot
2. Add mounts to /etc/fstab
3. Enable services with systemctl enable
4. Use firewall-cmd --permanent

5. Save cron jobs properly

6. Permission errors - Run as root or use sudo when needed

7. Check file and directory permissions after creation

8. Verify ownership is correct

9. Not verifying work - Always test your solution

10. Mount and verify filesystems
11. Restart services and check they come back
12. Test firewall rules from another perspective

13. Verify user/group configurations with id command

14. Typos in configuration files - Use config test commands

15. apache2ctl configtest
16. nginx -t
17. visudo (validates syntax)

18. testparm (Samba)

19. Forgetting to restart/reload services - After configuration changes

20. systemctl restart service
21. systemctl reload service
22. firewall-cmd --reload
23. exportfs -a (NFS)

Domain-Specific Tips¶

Essential Commands (20%): - Know grep, sed, awk cold - these are foundational - Practice find with -exec and -delete - Know tar flags: -c (create), -x (extract), -z (gzip), -j (bzip2), -f (file) - Understand SUID (4), SGID (2), and sticky bit (1)

User and Group Management (15%): - Always use -m with useradd to create home directory - Use -aG (append to group) with usermod, NOT -G alone (replaces groups) - Use visudo or /etc/sudoers.d/ for sudo configuration - Know /etc/login.defs for default user settings

Running Systems (15%): - systemctl is your primary tool - master it - journalctl -u service -f for following service logs - Know cron field order: minute hour day-of-month month day-of-week - Default target change: systemctl set-default target-name

Networking (15%): - Know both nmcli and netplan (depending on Ubuntu version) - firewall-cmd --permanent followed by --reload - SSH key auth: ssh-keygen, ssh-copy-id, verify sshd_config - Use ss -tunlp to check listening ports

Storage Management (15%): - LVM workflow: pvcreate -> vgcreate -> lvcreate -> mkfs -> mount - After lvextend, resize filesystem: resize2fs (ext4) or xfs_growfs (XFS) - Use UUID in /etc/fstab (from blkid) - mount -a to test fstab entries without rebooting

Service Configuration (20%): - Apache: a2ensite/a2dissite, a2enmod/a2dismod - Nginx: symlink from sites-available to sites-enabled - NFS: /etc/exports syntax, exportfs -a - Always test configs before restarting services

Pre-Exam Checklist¶

One Week Before¶

• Complete at least 2 full practice sessions under timed conditions
• All commands executable from memory (with man page for details)
• Comfortable with LVM and storage management
• Can configure services (Apache, NFS, SSH) without reference
• Used killer.sh exam simulator

Day Before¶

• Light review of key file locations
• Verify PSI browser works
• Check internet connection stability
• Prepare exam workspace (clean desk, quiet room)
• Get a good night's rest

Exam Day¶

• Start PSI session 15 minutes early
• Read ALL tasks before starting
• Tackle confident tasks first
• Verify each task works before moving on
• Use man pages when unsure of syntax
• Do not panic - 66% is passing, you do not need perfection
• Save time at end for review and verification