LFCE 155 ๐ง LFCE Exam Objectives Review โ Domain 1
The LFCE exam is a performance-based, command-line test with no multiple-choice questions. The official domains and competencies were updated in June 2018 and remain the reference for the exam structure . Domain 1, Essential Commands, carries a weight of 5%. It is the smallest domain by percentage, but it is foundational: every other domain assumes the candidate can manipulate files programmatically, run commands across many systems, use version control, and install a Linux distribution from scratch.
This chapter reviews Domain 1’s four competencies, what each one means in practice, and how the skills connect to the larger domains. It is a review, not a tutorial: the goal is to confirm that the candidate can perform each task from the command line without reference material.
Key point: Domain 1 is only 5% of the exam, but the skills it covers are used in every other domain. The sed, awk, and grep commands are used in Service Configuration. The SSH loop is used in System Design and Deployment. Git is used to manage configuration files. The installation competency is the baseline for every lab exercise.
Why Domain 1 is small but essential
The tooling problem. The other domains test specific services: an HTTP server, a DNS server, a storage backend. Domain 1 tests the general-purpose tools that make those services manageable. A candidate who cannot edit a configuration file with sed or run a command across ten hosts with a loop will struggle in the Service Configuration and System Design domains, regardless of how well they understand the service itself.
The performance-based problem. The LFCE is not a multiple-choice exam. The candidate is given a live terminal and a set of tasks to complete within two hours . There is no opportunity to look up a command syntax. Domain 1’s competencies are the ones that must be automatic: the file manipulation, the remote execution, the version control, and the installation.
a. Use version control tools
The competency requires the candidate to use a version control system, which in practice means Git. The exam does not test Git internals; it tests the ability to manage configuration files and scripts in a repository.
The commands that matter are the ones used in a daily workflow: git init, git add, git commit, git status, git log, git diff, git branch, git checkout, and git remote. A candidate should be able to initialize a repository, commit a change, view the history, create a branch, and push to a remote.
The connection to the other domains is direct. A playbook, a Terraform configuration, a Prometheus scrape config, and an rsyslog rule are all files that should be version-controlled. The exam may present a scenario where a configuration change must be committed with a meaningful message, or where a previous version must be restored.
b. Manipulate file content programmatically
This is the largest of the four competencies in practice. It covers the text-processing tools that are used to edit configuration files, extract data from logs, and transform output. The core tools are grep, sed, awk, and the shell’s own parameter expansion and redirection.
grep is used to search for a pattern in a file or a stream. The variants that matter are -i (case-insensitive), -v (invert), -r (recursive), -E (extended regex), and -o (output only the match). sed is used to transform text: substitution (s/old/new/g), deletion (d), and printing specific lines (-n '5,10p'). awk is used for field-based processing: awk -F: '{print $1}' extracts the first colon-separated field from each line.
The shell redirection operators are part of this competency: > for overwrite, >> for append, 2> for stderr, 2>&1 for merging, and the pipe | for chaining commands. A candidate should be able to construct a pipeline that extracts a specific value from a log file and writes it to a new file.
c. Run commands on many systems simultaneously
This competency tests the ability to execute a command across multiple hosts without logging into each one individually. The tools are SSH and its loop patterns, or a configuration management tool if the scenario calls for it.
The SSH loop pattern is the baseline. A for loop over a list of hostnames, with ssh in the body, runs the command on each host in sequence. The loop must handle the failure cases: a host that is unreachable, a command that returns a non-zero status, and a host that requires a different user or key. The BatchMode=yes option prevents the script from hanging on a password prompt, and the </dev/null redirect prevents SSH from consuming the loop’s input.
The competency also connects to Ansible. A playbook that targets a group of hosts is the higher-level version of the same task. The exam may present a scenario where a command must be run on all web servers, and the candidate can choose the SSH loop or the Ansible ad-hoc command (ansible webservers -m command -a '...').
d. Install a Linux distribution
The installation competency is the baseline for every lab exercise and every recovery scenario. The candidate should be able to install a Linux distribution from an ISO, either on bare metal or in a virtual machine, and configure the essential settings: the hostname, the network, the partitioning, the user accounts, and the package selection.
The exam environment provides Ubuntu and CentOS Stream as the available distributions . A candidate should be comfortable with both installers: the Ubuntu Server installer (Subiquity) and the CentOS Stream installer (Anaconda). The partitioning step is the one that connects to the Storage Management domain: the candidate should understand the difference between a standard partition, an LVM volume, and a filesystem on a logical volume.
The installation competency also covers the post-installation steps: updating the package index, installing the essential tools, and verifying that the system boots. A candidate who has installed the distribution in a VM has already practiced the recovery and boot scenarios that the Operation of Running Systems domain tests.
Complete Example Session
# ============================================
# PART 1: GIT WORKFLOW
# ============================================
git init
git add nginx.conf
git commit -m "Add nginx configuration"
git log --oneline
# ============================================
# PART 2: GREP AND SED
# ============================================
grep -E '^PermitRootLogin' /etc/ssh/sshd_config
sed -i 's/^PermitRootLogin.*/PermitRootLogin no/' /etc/ssh/sshd_config
# ============================================
# PART 3: AWK FIELD EXTRACTION
# ============================================
awk -F: '$3 >= 1000 {print $1}' /etc/passwd
# ============================================
# PART 4: REDIRECTION
# ============================================
command > output.txt 2>&1
command >> append.txt
# ============================================
# PART 5: SSH LOOP
# ============================================
for host in web1 web2 web3; do
ssh -o BatchMode=yes "$host" 'systemctl restart nginx' </dev/null
done
# ============================================
# PART 6: ANSIBLE AD-HOC
# ============================================
ansible webservers -m command -a 'systemctl restart nginx'
# ============================================
# PART 7: INSTALLATION CHECKLIST
# ============================================
# - Boot from ISO
# - Configure network
# - Partition disk (standard or LVM)
# - Set hostname and timezone
# - Create user and set password
# - Select package set
# - Reboot and verify
# ============================================
# PART 8: POST-INSTALL
# ============================================
dnf update -y
dnf install -y vim git curl
systemctl status sshd
# ============================================
# PART 9: THE CONNECTION TO OTHER DOMAINS
# ============================================
# Service Configuration uses sed/awk on config files.
# System Design uses SSH loops for deployment.
# Storage Management uses LVM partitioning.
# ============================================
# PART 10: THE EXAM CONTEXT
# ============================================
# 2 hours, performance-based, ~15-25 tasks.
# Domain 1 is 5% of the total.
# The skills are used in every other domain.
The ten parts covered the Git workflow, grep and sed, awk, redirection, the SSH loop, the Ansible ad-hoc command, the installation checklist, post-install steps, the connection to other domains, and the exam context.
Quick Reference
Domain 1 competencies
| Competency | Tools |
|---|---|
| Version control | git init, add, commit, log, branch |
| File manipulation | grep, sed, awk, redirection, pipes |
| Multi-host execution | SSH loop, Ansible ad-hoc |
| Distribution installation | ISO install, partitioning, post-install |
Text processing commands
| Command | Purpose |
|---|---|
grep -E | Extended regex search |
grep -v | Invert match |
sed -i 's/old/new/g' | In-place substitution |
awk -F: '{print $1}' | Field extraction |
command > file | Redirect stdout |
command 2>&1 | Merge stderr into stdout |
SSH loop options
| Option | Purpose |
|---|---|
BatchMode=yes | No prompts |
ConnectTimeout=10 | Timeout |
</dev/null | Prevent stdin consumption |
Installation checklist
| Step | Detail |
|---|---|
| Partitioning | Standard or LVM |
| Network | Static or DHCP |
| Hostname | FQDN |
| User | Sudo-enabled |
| Packages | Minimal or server |
Best Practices
โ Do This:
# Commit configuration changes with meaningful messages
git commit -m "Disable root SSH login" # โ
# Use sed -i for in-place config edits
sed -i 's/^#PermitRootLogin.*/PermitRootLogin no/' file # โ
# Use BatchMode in SSH loops
ssh -o BatchMode=yes host 'cmd' # โ
# Test the install in a VM before the exam
virt-install --cdrom /path/to/iso # โ
โ Don’t Do This:
# Run sed without -i and expect the file to change
sed 's/old/new/' file # prints, does not edit # โ
# Use an SSH loop without </dev/null
for h in hosts; do ssh $h cmd; done < hosts.txt # โ (skips hosts)
# Install without configuring the network
# The post-install update will fail # โ
Common Pitfalls
| Pitfall | Why It Happens | Fix |
|---|---|---|
sed does not edit the file | Missing -i | Use sed -i |
| SSH loop skips hosts | SSH consumes stdin | Add </dev/null |
| Git commit fails | No user configured | git config user.email |
| Installer cannot find the disk | No partitioning configured | Use automatic or manual partitioning |
awk prints the wrong field | Wrong -F delimiter | Check the field separator |
Real-World Examples
1. Git commit
git add config.yml && git commit -m "Update config"
2. Grep for a pattern
grep -E 'error|fail' /var/log/messages
3. Sed substitution
sed -i 's/old_value/new_value/g' /etc/app/config
4. Awk field extraction
awk -F: '{print $1}' /etc/passwd
5. Redirection
command > output.txt 2>&1
6. SSH loop
for h in web1 web2; do ssh -o BatchMode=yes $h 'uptime' </dev/null; done
7. Ansible ad-hoc
ansible webservers -m command -a 'uptime'
8. Install checklist
Boot ISO โ network โ partition โ hostname โ user โ packages โ reboot
9. Post-install update
dnf update -y
10. Verify the boot
systemctl status
Visual
The Domain 1 connection
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ DOMAIN 1 (5%) โ
โ โโโ Git โ
โ โโโ sed/awk/grep โ
โ โโโ SSH loop โ
โ โโโ Installation โ
โ โ
โ Used by: โ
โ โโโ Service Configuration (config edits) โ
โ โโโ System Design (deployment) โ
โ โโโ Storage Management (partitioning) โ
โ โโโ Operation of Running Systems (troubleshooting) โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
The SSH loop
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ for host in web1 web2 web3; do โ
โ ssh -o BatchMode=yes "$host" 'command' </dev/null โ
โ done โ
โ โ
โ Runs the command on each host in sequence. โ
โ BatchMode prevents prompts. โ
โ </dev/null prevents stdin consumption. โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
The text-processing pipeline
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ grep 'error' /var/log/app.log โ
โ โ โ
โ โผ โ
โ awk '{print $5}' โ
โ โ โ
โ โผ โ
โ sort | uniq -c | sort -rn โ
โ โ
โ Extract, transform, count, rank. โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
The installation flow
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ ISO โโโบ installer โโโบ partition โโโบ network โโโบ user โ
โ โ โ
โ โผ โ
โ reboot โโโบ login โโโบ update โโโบ install tools โ
โ โ
โ The baseline for every lab exercise. โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Summary
| Item | Value |
|---|---|
| Domain weight | 5% |
| Competency 1 | Version control (Git) |
| Competency 2 | File content manipulation (grep, sed, awk) |
| Competency 3 | Multi-host execution (SSH loop, Ansible) |
| Competency 4 | Linux distribution installation |
| Exam format | Performance-based, 2 hours |
| Distributions | Ubuntu, CentOS Stream |
| Connection | Skills used in every other domain |
Key takeaways:
- Domain 1 is small but foundational. The 5% weight understates its importance. The text-processing, remote execution, and installation skills are prerequisites for the Service Configuration, System Design, and Storage Management domains.
- Git is the version control tool. The candidate should be able to initialize a repository, commit changes, view history, and restore a previous version. The exam may test the workflow on a configuration file or a script.
grep,sed, andawkare the text-processing core. The candidate should be able to search for a pattern, substitute a value in place, and extract a field. The shell redirection and piping operators are part of the same competency.- The SSH loop runs commands on many hosts. The
BatchMode=yesoption and the</dev/nullredirect are the two details that separate a working loop from one that hangs or skips hosts. - Installation is the baseline. The candidate should be able to install Ubuntu or CentOS Stream from an ISO, configure the network and partitioning, create a user, and verify the boot. The partitioning step connects directly to the Storage Management domain.
Remember: Domain 1 is the toolbox. The other domains are the tasks. A candidate who can commit a configuration change, edit a file with sed, run a command across a group of hosts, and install a distribution has the foundation that every other domain requires. The exam does not test these skills in isolation; it tests them in the context of a service configuration, a deployment, or a recovery scenario. Practice them until they are automatic, because the two-hour performance-based format leaves no time to look up syntax.
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!