XK0-006
The specific exam code for the current CompTIA Linux+ certification.
Getting Started: How the Exam Works
Free knowledge base
CompTIA Linux+ (XK0-006) — key terms, tricks & tips
Everything from the course in one searchable place: 267 entries. Use it to review before a practice test or look up a word you forgot.
267 results
Performance-Based Item
Exam questions requiring hands-on tasks in a simulated environment.
Getting Started: How the Exam Works
Scaled Score
A conversion of raw scores to account for varying exam difficulty.
Getting Started: How the Exam Works
Exam Domain
A major content area covered by the certification exam.
Getting Started: How the Exam Works
Exam Objectives
Detailed list of topics and skills tested within each domain.
Getting Started: How the Exam Works
Passing Score
The minimum score (720 out of 900) required to pass the exam.
Getting Started: How the Exam Works
CompTIA
Computing Technology Industry Association, the certifying body.
Getting Started: How the Exam Works
XK0-006 Exam Overview, Domains & Scoring
To remember the passing score, think 'Seven Two Oh, Linux Pro!' (720).
Getting Started: How the Exam Works
XK0-006 Exam Overview, Domains & Scoring
Memorize the passing score of 720 and the maximum number of questions (90). Understand that PBIs are hands-on and require command-line proficiency.
Getting Started: How the Exam Works
XK0-006 Exam Overview, Domains & Scoring
Ignoring the official exam objectives document, leading to studying irrelevant topics or missing key ones.
Getting Started: How the Exam Works
XK0-006 Exam Overview, Domains & Scoring
Underestimating the importance of performance-based items (PBIs) and not practicing hands-on in a lab environment.
Getting Started: How the Exam Works
XK0-006 Exam Overview, Domains & Scoring
Not managing time effectively during the exam, especially on PBIs, and leaving questions unanswered.
Getting Started: How the Exam Works
Virtual Machine (VM)
Software-based emulation of a computer system.
Getting Started: How the Exam Works
Virtualization Software
Programs like VirtualBox that create and manage VMs.
Getting Started: How the Exam Works
ISO Image
A file containing a complete copy of a data medium.
Getting Started: How the Exam Works
Guest Operating System
An OS running inside a virtual machine.
Getting Started: How the Exam Works
Host Operating System
The OS running directly on the physical computer.
Getting Started: How the Exam Works
Practice Exam
Simulated test to assess readiness and identify weak areas.
Getting Started: How the Exam Works
Process of Elimination
Strategy to remove incorrect answer choices.
Getting Started: How the Exam Works
Study Strategy, Lab Setup & Exam Day Tips
LABS: Learn, Apply, Build, Study. Learn the concepts, Apply them in your lab, Build your skills, and Study your weak points!
Getting Started: How the Exam Works
Study Strategy, Lab Setup & Exam Day Tips
The exam expects you to have practical experience. While specific lab setup details aren't directly tested, the ability to execute commands, interpret output, and troubleshoot common Linux scenarios, which are gained through lab practice, is fundamental to passing. Look for keywords like 'given a scenario', 'which command', or 'what is the output'.
Getting Started: How the Exam Works
Study Strategy, Lab Setup & Exam Day Tips
Relying solely on reading without hands-on practice; this leads to theoretical knowledge without practical application.
Getting Started: How the Exam Works
Study Strategy, Lab Setup & Exam Day Tips
Cramming the night before the exam; consistent, spaced repetition is far more effective for long-term retention.
Getting Started: How the Exam Works
Study Strategy, Lab Setup & Exam Day Tips
Not reviewing incorrect answers on practice tests; understanding 'why' you got something wrong is crucial for learning.
Getting Started: How the Exam Works
BIOS
Basic Input/Output System, legacy firmware for system startup.
System Management: Boot, Kernel, Storage & Packages
UEFI
Unified Extensible Firmware Interface, modern firmware successor to BIOS.
System Management: Boot, Kernel, Storage & Packages
GRUB
GRand Unified Bootloader, the common Linux bootloader.
System Management: Boot, Kernel, Storage & Packages
initramfs
Initial RAM filesystem, provides minimal root for kernel to boot.
System Management: Boot, Kernel, Storage & Packages
systemd
Init system and service manager, PID 1, orchestrates system startup.
System Management: Boot, Kernel, Storage & Packages
Target
systemd's equivalent of runlevels, defining system states.
System Management: Boot, Kernel, Storage & Packages
POST
Power-On Self-Test, firmware check of hardware components.
System Management: Boot, Kernel, Storage & Packages
Boot Process: BIOS/UEFI, GRUB & systemd Targets
Brave Geese Know Incredibly Sweet Tunes. (BIOS/UEFI, GRUB, Kernel, Initramfs, systemd, Target)
System Management: Boot, Kernel, Storage & Packages
Boot Process: BIOS/UEFI, GRUB & systemd Targets
Memorize the order of the boot stages: BIOS/UEFI -> GRUB -> Kernel -> initramfs -> systemd -> Target. Be able to identify the purpose of each component, especially GRUB and systemd targets. Keywords like 'bootloader', 'init system', and 'runlevel' (as it relates to targets) are common.
System Management: Boot, Kernel, Storage & Packages
Boot Process: BIOS/UEFI, GRUB & systemd Targets
Confusing the roles of GRUB (bootloader) and systemd (init system).
System Management: Boot, Kernel, Storage & Packages
Boot Process: BIOS/UEFI, GRUB & systemd Targets
Not understanding that initramfs is temporary and helps the kernel mount the real root filesystem.
System Management: Boot, Kernel, Storage & Packages
Boot Process: BIOS/UEFI, GRUB & systemd Targets
Forgetting that `multi-user.target` is for text-based login and `graphical.target` is for a GUI.
System Management: Boot, Kernel, Storage & Packages
Kernel Module
Code loaded/unloaded into kernel on demand.
System Management: Boot, Kernel, Storage & Packages
lsmod
Command to list currently loaded kernel modules.
System Management: Boot, Kernel, Storage & Packages
modprobe
Command to add or remove kernel modules.
System Management: Boot, Kernel, Storage & Packages
Filesystem Hierarchy Standard (FHS)
Standardized Linux directory structure.
System Management: Boot, Kernel, Storage & Packages
/etc
Directory for host-specific configuration files.
System Management: Boot, Kernel, Storage & Packages
/var
Directory for variable data like logs and spool files.
System Management: Boot, Kernel, Storage & Packages
/usr
Directory for shareable, read-only user programs/data.
System Management: Boot, Kernel, Storage & Packages
/dev
Directory containing device files.
System Management: Boot, Kernel, Storage & Packages
Kernel Modules (lsmod, modprobe) & Filesystem Hierarchy
For FHS, remember 'Every Vulture Has Ugly Big Devourers' to recall /etc, /var, /home, /usr, /boot, /dev.
System Management: Boot, Kernel, Storage & Packages
Kernel Modules (lsmod, modprobe) & Filesystem Hierarchy
The exam expects you to know the purpose of `lsmod` and `modprobe`, including their basic options. Be able to identify the purpose of key FHS directories like `/etc`, `/var`, `/home`, `/boot`, `/dev`, and `/usr`. Keywords: kernel modules, FHS, lsmod, modprobe, /etc, /var, /home.
System Management: Boot, Kernel, Storage & Packages
Kernel Modules (lsmod, modprobe) & Filesystem Hierarchy
Forgetting to use `sudo` when attempting to load or unload kernel modules, as these operations require root privileges.
System Management: Boot, Kernel, Storage & Packages
Kernel Modules (lsmod, modprobe) & Filesystem Hierarchy
Confusing the purpose of `/bin` (essential user binaries) with `/usr/bin` (non-essential user binaries) or `/sbin` (essential system binaries).
System Management: Boot, Kernel, Storage & Packages
Kernel Modules (lsmod, modprobe) & Filesystem Hierarchy
Attempting to manually remove a module that is still in use by another module or process, which can lead to system instability.
System Management: Boot, Kernel, Storage & Packages
Partition
A logical division of a physical disk.
System Management: Boot, Kernel, Storage & Packages
fdisk
A command-line utility for managing MBR partition tables.
System Management: Boot, Kernel, Storage & Packages
parted
A command-line utility for managing MBR and GPT partition tables.
System Management: Boot, Kernel, Storage & Packages
LVM
Logical Volume Management, a system for flexible disk space management.
System Management: Boot, Kernel, Storage & Packages
Physical Volume (PV)
A raw disk or partition initialized for LVM use.
System Management: Boot, Kernel, Storage & Packages
Volume Group (VG)
A pool of storage created from one or more Physical Volumes.
System Management: Boot, Kernel, Storage & Packages
Logical Volume (LV)
A flexible, resizable partition created from a Volume Group.
System Management: Boot, Kernel, Storage & Packages
/etc/fstab
Configuration file for static information about filesystems to be mounted.
System Management: Boot, Kernel, Storage & Packages
Partitions, LVM & Mounting: fdisk, parted, lvm2, /etc/fstab
For LVM, remember 'PV-VG-LV': Physical Volumes form Volume Groups, which contain Logical Volumes. It's like building with LEGOs: individual bricks (PVs) form a big bin (VG), from which you build your creation (LV).
System Management: Boot, Kernel, Storage & Packages
Partitions, LVM & Mounting: fdisk, parted, lvm2, /etc/fstab
The exam often tests the correct sequence of LVM commands (pvcreate, vgcreate, lvcreate) and the fields within /etc/fstab. Pay attention to the 'dump' and 'pass' numbers and when to use UUIDs versus device names.
System Management: Boot, Kernel, Storage & Packages
Partitions, LVM & Mounting: fdisk, parted, lvm2, /etc/fstab
Forgetting to run 'mkfs' after creating a partition or Logical Volume, leading to 'mount: special device does not exist' errors.
System Management: Boot, Kernel, Storage & Packages
Partitions, LVM & Mounting: fdisk, parted, lvm2, /etc/fstab
Incorrectly editing /etc/fstab, especially using incorrect device names or UUIDs, which can prevent the system from booting. Always use 'mount -a' to test.
System Management: Boot, Kernel, Storage & Packages
Partitions, LVM & Mounting: fdisk, parted, lvm2, /etc/fstab
Attempting to use fdisk on disks larger than 2TB or with GPT partition tables; parted is required for these scenarios.
System Management: Boot, Kernel, Storage & Packages
Package Manager
Software that automates installing, updating, and removing software.
System Management: Boot, Kernel, Storage & Packages
Repository
Centralized server storing software packages for a distribution.
System Management: Boot, Kernel, Storage & Packages
apt
Advanced Package Tool, package manager for Debian/Ubuntu systems.
System Management: Boot, Kernel, Storage & Packages
dnf
Dandified YUM, package manager for Red Hat/Fedora/CentOS systems.
System Management: Boot, Kernel, Storage & Packages
Dependency
A software component required by another program to function.
System Management: Boot, Kernel, Storage & Packages
ip addr show
Command to display network interface IP addresses and details.
System Management: Boot, Kernel, Storage & Packages
df -h
Command to report file system disk space usage in human-readable format.
System Management: Boot, Kernel, Storage & Packages
Package Management: apt, dnf & Common Commands
APT is for 'A Pretty Terrific' system (Debian/Ubuntu). DNF is for 'Definitely New Fedora' (Red Hat/Fedora).
System Management: Boot, Kernel, Storage & Packages
Package Management: apt, dnf & Common Commands
The exam often tests the correct syntax and purpose of `apt` and `dnf` commands. Pay close attention to the `update`, `install`, `remove`, and `upgrade` subcommands. Memorize which command belongs to which distribution family (Debian vs. Red Hat).
System Management: Boot, Kernel, Storage & Packages
Package Management: apt, dnf & Common Commands
Forgetting to run `sudo apt update` or `sudo dnf check-update` before installing new software, leading to outdated package information.
System Management: Boot, Kernel, Storage & Packages
Package Management: apt, dnf & Common Commands
Confusing `apt` commands with `dnf` commands, e.g., trying to use `apt install` on a CentOS system.
System Management: Boot, Kernel, Storage & Packages
Package Management: apt, dnf & Common Commands
Not understanding the difference between `apt remove` (removes package) and `apt purge` (removes package and config files).
System Management: Boot, Kernel, Storage & Packages
Unit
A configuration file describing how to manage a system resource.
Services and User Management
Unit File
The actual text file defining a systemd unit's behavior.
Services and User Management
systemctl
The command-line utility for controlling systemd units.
Services and User Management
Service Unit
A systemd unit type (.service) for managing daemons/applications.
Services and User Management
Target Unit
A systemd unit type (.target) that groups other units and defines system states.
Services and User Management
daemon-reload
Command to make systemd aware of new or changed unit files.
Services and User Management
systemd Units, Unit Files & Targets
Think of 'systemctl' as your 'system control' panel. 'Start' gets it going now, 'Enable' makes it start with the system, 'Status' tells you how it's doing.
Services and User Management
systemd Units, Unit Files & Targets
The exam often asks about the purpose of systemd, common systemctl commands (start, stop, enable, disable, status), and the location of unit files. Pay close attention to the difference between starting a service and enabling it for boot.
Services and User Management
systemd Units, Unit Files & Targets
Forgetting to run systemctl daemon-reload after modifying or creating a unit file, leading to systemd not recognizing the changes.
Services and User Management
systemd Units, Unit Files & Targets
Confusing 'start' (runs now) with 'enable' (runs at boot). A service can be started but not enabled, or vice-versa.
Services and User Management
systemd Units, Unit Files & Targets
Not specifying the full unit name (e.g., 'apache2' instead of 'apache2.service') in systemctl commands, which can sometimes lead to ambiguity or errors.
Services and User Management
UID
User ID; a unique numerical identifier for each user account.
Services and User Management
GID
Group ID; a unique numerical identifier for each group.
Services and User Management
Primary Group
The main group a user belongs to, specified in `/etc/passwd`.
Services and User Management
Supplementary Group
Additional groups a user belongs to, listed in `/etc/group`.
Services and User Management
/etc/passwd
Configuration file storing basic user account information (world-readable).
Services and User Management
/etc/shadow
Configuration file storing encrypted passwords and password aging data (root-only readable).
Services and User Management
/etc/group
Configuration file storing group names, GIDs, and members.
Services and User Management
GECOS field
A field in `/etc/passwd` for general user information like full name.
Services and User Management
User & Group Management: useradd, passwd, /etc/shadow
Pass-W-D for 'Password Details' (like UID, GID, home, shell) and Shadow for 'Secret Hash Of Data Overwritten' (encrypted passwords).
Services and User Management
User & Group Management: useradd, passwd, /etc/shadow
The exam often tests the specific fields within `/etc/passwd` and `/etc/shadow`, and the permissions of these files. Remember that `/etc/passwd` is world-readable, but `/etc/shadow` is only readable by root for security.
Services and User Management
User & Group Management: useradd, passwd, /etc/shadow
Forgetting to set a password after creating a user with `useradd`, leading to the user being unable to log in.
Services and User Management
User & Group Management: useradd, passwd, /etc/shadow
Attempting to directly edit `/etc/shadow` instead of using `passwd` or other dedicated tools, which can corrupt the file.
Services and User Management
User & Group Management: useradd, passwd, /etc/shadow
Not understanding the difference between primary and supplementary groups, or how they affect file permissions.
Services and User Management
chmod
Command to change file or directory permissions.
Services and User Management
chown
Command to change file or directory owner and/or group.
Services and User Management
chgrp
Command to change file or directory group ownership.
Services and User Management
umask
A value that determines default permissions for new files/directories.
Services and User Management
ACLs
Access Control Lists, providing granular permissions beyond standard u/g/o.
Services and User Management
Octal Mode
Numeric representation of permissions (r=4, w=2, x=1).
Services and User Management
Symbolic Mode
Text-based representation of permissions (u/g/o/a +/ - / = r/w/x).
Services and User Management
Execute (x)
Permission to run a file or traverse a directory.
Services and User Management
Permissions: chmod, chown, umask & ACLs
Remember 'Read, Write, eXecute' for the permissions, and 'User, Group, Others' for the categories. Think of 'CHange MODe' for chmod and 'CHange OWNer' for chown.
Services and User Management
Permissions: chmod, chown, umask & ACLs
The CompTIA Linux+ exam heavily tests octal permission values. Memorize r=4, w=2, x=1 and how to combine them. Also, remember that only root can change a file's owner with 'chown'.
Services and User Management
Permissions: chmod, chown, umask & ACLs
Forgetting that 'x' permission is required to enter (traverse) a directory, not just 'r'.
Services and User Management
Permissions: chmod, chown, umask & ACLs
Confusing octal values (e.g., thinking 777 means 'no permissions').
Services and User Management
Permissions: chmod, chown, umask & ACLs
Attempting to change file ownership with 'chown' as a non-root user (it will fail).
Services and User Management
Permissions: chmod, chown, umask & ACLs
Not using the '-R' option with 'chmod' or 'chown' when intending to change permissions/ownership recursively for a directory and its contents.
Services and User Management
Cron
A time-based job scheduler in Unix-like operating systems.
Services and User Management
Crontab
A file that specifies shell commands to run periodically on a given schedule.
Services and User Management
systemd Timer
A systemd unit file that activates another unit (often a service) at a specific time or interval.
Services and User Management
journalctl
A command-line utility for querying and displaying logs from the systemd journal.
Services and User Management
Container
A lightweight, isolated, executable package of software that includes everything needed to run it.
Services and User Management
Namespaces
A Linux kernel feature that isolates system resources for processes, crucial for containers.
Services and User Management
cgroups
Control Groups; a Linux kernel feature that limits, accounts for, and isolates resource usage.
Services and User Management
Cron/Timers, journalctl Logging & Container Basics
CRON: 'C'ommand 'R'uns 'O'n 'N'umerical times. JOURNALCTL: 'J'ust 'O'utput 'U'nit 'R'ecords 'N'ow, 'A'nd 'L'ook 'C'arefully 'T'hrough 'L'ogs.
Services and User Management
Cron/Timers, journalctl Logging & Container Basics
The exam frequently tests the syntax of crontab entries. Memorize the order: minute, hour, day of month, month, day of week. Also, be ready to use `journalctl` with common filtering options like `-u` for unit, `-b` for boot, and `-f` for follow.
Services and User Management
Cron/Timers, journalctl Logging & Container Basics
Forgetting to specify the full path to a script in a cron job, leading to execution failures.
Services and User Management
Cron/Timers, journalctl Logging & Container Basics
Not understanding that `journalctl` logs are binary and cannot be directly `cat`ed like traditional syslog files.
Services and User Management
Cron/Timers, journalctl Logging & Container Basics
Confusing containers with virtual machines; containers share the host kernel, VMs run their own kernel.
Services and User Management
Mandatory Access Control (MAC)
System-wide security policy enforced by the OS, not user-modifiable.
Security: Access Control, Firewalls & Encryption
Discretionary Access Control (DAC)
Access control based on user/group permissions, set by object owner.
Security: Access Control, Firewalls & Encryption
SELinux
Security-Enhanced Linux; a MAC system using security contexts and labels.
Security: Access Control, Firewalls & Encryption
AppArmor
Application Armor; a MAC system using path-based profiles for applications.
Security: Access Control, Firewalls & Encryption
Security Context
A label applied to subjects/objects in SELinux defining their security attributes.
Security: Access Control, Firewalls & Encryption
AVC Denial
Access Vector Cache denial; an SELinux message indicating a blocked action.
Security: Access Control, Firewalls & Encryption
Enforcing Mode
MAC mode where unauthorized actions are actively blocked and logged.
Security: Access Control, Firewalls & Encryption
Permissive Mode
MAC mode where unauthorized actions are logged but allowed to proceed.
Security: Access Control, Firewalls & Encryption
Mandatory Access Control: SELinux & AppArmor
SELinux is like a Strict Editor, labeling Everything. AppArmor is like an Application's Armor, protecting just that one app.
Security: Access Control, Firewalls & Encryption
Mandatory Access Control: SELinux & AppArmor
The exam expects you to differentiate between SELinux and AppArmor, know their basic modes (enforcing, permissive/complain), and identify commands like `sestatus` and `aa-status` for checking their state. Remember which distributions typically use which system.
Security: Access Control, Firewalls & Encryption
Mandatory Access Control: SELinux & AppArmor
Disabling SELinux/AppArmor entirely instead of troubleshooting denials, which compromises security.
Security: Access Control, Firewalls & Encryption
Mandatory Access Control: SELinux & AppArmor
Assuming DAC permissions are the only factor when an application gets 'Permission denied' errors.
Security: Access Control, Firewalls & Encryption
Mandatory Access Control: SELinux & AppArmor
Trying to apply SELinux commands on an AppArmor system, or vice-versa, leading to confusion.
Security: Access Control, Firewalls & Encryption
Firewall
A system that controls network traffic based on security rules.
Security: Access Control, Firewalls & Encryption
iptables
Traditional Linux command-line utility for configuring Netfilter rules.
Security: Access Control, Firewalls & Encryption
firewalld
Dynamic firewall management service using zones for rule organization.
Security: Access Control, Firewalls & Encryption
nftables
Modern, unified packet filtering framework, successor to iptables.
Security: Access Control, Firewalls & Encryption
Netfilter
The packet filtering framework built into the Linux kernel.
Security: Access Control, Firewalls & Encryption
Zone
In firewalld, a predefined set of rules for a network connection's trust level.
Security: Access Control, Firewalls & Encryption
Service
A predefined port or port range used by firewalld (e.g., http, ssh).
Security: Access Control, Firewalls & Encryption
Firewalls: firewalld, iptables & nftables
Remember 'F-I-N': Firewalld is the friendly interface, Iptables is the old interface, Nftables is the new interface to Netfilter.
Security: Access Control, Firewalls & Encryption
Firewalls: firewalld, iptables & nftables
The CompTIA Linux+ exam expects you to know that firewalld is the default firewall management tool on RHEL-based systems and understand its zone-based concept. Be familiar with 'firewall-cmd' options like --add-service, --add-port, --permanent, and --reload.
Security: Access Control, Firewalls & Encryption
Firewalls: firewalld, iptables & nftables
Forgetting to use '--permanent' with 'firewall-cmd' for changes to persist after a reboot, leading to lost configurations.
Security: Access Control, Firewalls & Encryption
Firewalls: firewalld, iptables & nftables
Not reloading firewalld after making permanent changes, causing the new rules to not take effect immediately.
Security: Access Control, Firewalls & Encryption
Firewalls: firewalld, iptables & nftables
Overly permissive firewall rules (e.g., opening all ports) which defeat the purpose of having a firewall and expose the system to unnecessary risks.
Security: Access Control, Firewalls & Encryption
SSH Hardening
Configuring SSH to enhance security and reduce attack surface.
Security: Access Control, Firewalls & Encryption
Key-Based Authentication
Using public/private key pairs for secure SSH logins.
Security: Access Control, Firewalls & Encryption
Public Key
Part of a key pair, shared publicly, used for encryption/verification.
Security: Access Control, Firewalls & Encryption
Private Key
Part of a key pair, kept secret, used for decryption/signing.
Security: Access Control, Firewalls & Encryption
sudo
Command allowing authorized users to execute commands as another user.
Security: Access Control, Firewalls & Encryption
/etc/sudoers
Configuration file for the sudo command, edited with 'visudo'.
Security: Access Control, Firewalls & Encryption
PAM
Pluggable Authentication Modules, a modular authentication framework.
Security: Access Control, Firewalls & Encryption
/etc/pam.d/
Directory containing PAM configuration files for various services.
Security: Access Control, Firewalls & Encryption
SSH Hardening, Key-Based Auth, sudo & PAM
SSH: Secure Shell, Secure Habits. Remember to always harden your SSH for a secure system.
Security: Access Control, Firewalls & Encryption
SSH Hardening, Key-Based Auth, sudo & PAM
The exam often tests your knowledge of SSH configuration files and common hardening directives in '/etc/ssh/sshd_config', such as 'PermitRootLogin', 'PasswordAuthentication', and 'Port'. Be prepared to identify the purpose of 'authorized_keys' and the 'visudo' command.
Security: Access Control, Firewalls & Encryption
SSH Hardening, Key-Based Auth, sudo & PAM
Forgetting to restart the sshd service after making changes to '/etc/ssh/sshd_config', which means the changes won't take effect.
Security: Access Control, Firewalls & Encryption
SSH Hardening, Key-Based Auth, sudo & PAM
Editing '/etc/sudoers' directly with a text editor instead of 'visudo', risking syntax errors that can lock out all administrative access.
Security: Access Control, Firewalls & Encryption
SSH Hardening, Key-Based Auth, sudo & PAM
Not protecting your private SSH key with a strong passphrase or storing it insecurely, which compromises the entire key-based authentication system.
Security: Access Control, Firewalls & Encryption
Hashing
Generating a fixed-size string of characters from data, used for integrity checks.
Security: Access Control, Firewalls & Encryption
Checksum
A value calculated from data to detect errors or changes during transmission or storage.
Security: Access Control, Firewalls & Encryption
GnuPG (GPG)
A free implementation of the OpenPGP standard for encrypting and signing data.
Security: Access Control, Firewalls & Encryption
Symmetric Encryption
Encryption using the same secret key for both encryption and decryption.
Security: Access Control, Firewalls & Encryption
Asymmetric Encryption
Encryption using a public key for encryption and a private key for decryption.
Security: Access Control, Firewalls & Encryption
LUKS
Linux Unified Key Setup, the standard for disk encryption on Linux.
Security: Access Control, Firewalls & Encryption
Block Device
A storage device that transfers data in fixed-size blocks, like a hard drive.
Security: Access Control, Firewalls & Encryption
Passphrase
A sequence of words or characters used to authenticate or decrypt data.
Security: Access Control, Firewalls & Encryption
File Integrity & Encryption: LUKS & GPG
Hash for 'H'onesty, GPG for 'G'uarding 'P'rivacy, LUKS for 'L'ocking 'U'p 'K'ey 'S'torage.
Security: Access Control, Firewalls & Encryption
File Integrity & Encryption: LUKS & GPG
The exam expects you to know the purpose of hashing (integrity) and encryption (confidentiality). Be familiar with `sha256sum` for integrity and `gpg` for file encryption/decryption. Understand that LUKS is for full disk/partition encryption and its basic function.
Security: Access Control, Firewalls & Encryption
File Integrity & Encryption: LUKS & GPG
Using MD5 or SHA1 for security-critical integrity checks when SHA256/SHA512 should be used.
Security: Access Control, Firewalls & Encryption
File Integrity & Encryption: LUKS & GPG
Forgetting the passphrase for a GPG-encrypted file or LUKS volume, rendering data inaccessible.
Security: Access Control, Firewalls & Encryption
File Integrity & Encryption: LUKS & GPG
Not backing up GPG private keys, which can lead to data loss if the original key is lost or corrupted.
Security: Access Control, Firewalls & Encryption
Variable
A named storage location for data in a script.
Automation, Orchestration and Scripting
Positional Parameter
Variables ($1, $2, etc.) holding arguments passed to a script.
Automation, Orchestration and Scripting
Exit Code
An integer (0 for success, non-zero for error) returned by a command or script.
Automation, Orchestration and Scripting
Conditional Statement
A control structure (e.g., `if`) that executes code based on a condition.
Automation, Orchestration and Scripting
Loop
A control structure (e.g., `for`, `while`) that repeats a block of code.
Automation, Orchestration and Scripting
Bash
The default command-line interpreter on most Linux systems, used for scripting.
Automation, Orchestration and Scripting
Shebang
The `#!` line at the start of a script, specifying the interpreter.
Automation, Orchestration and Scripting
Bash Scripting: Variables, Loops, Conditionals & Exit Codes
For 'if' conditions, remember: 'Square brackets are like a strict referee, checking the conditions carefully.'
Automation, Orchestration and Scripting
Bash Scripting: Variables, Loops, Conditionals & Exit Codes
Memorize the meaning of common special variables like `$?` (exit status) and `$#` (number of arguments). Understand the difference between `[ condition ]` and `[[ condition ]]` (double brackets offer more features and are often preferred). Know that `0` means success for exit codes.
Automation, Orchestration and Scripting
Bash Scripting: Variables, Loops, Conditionals & Exit Codes
Forgetting spaces around conditional operators (e.g., `[VAR=value]` instead of `[ VAR = value ]`).
Automation, Orchestration and Scripting
Bash Scripting: Variables, Loops, Conditionals & Exit Codes
Not quoting variables when they might contain spaces (e.g., `ls $MY_VAR` instead of `ls "$MY_VAR"`).
Automation, Orchestration and Scripting
Bash Scripting: Variables, Loops, Conditionals & Exit Codes
Confusing `==` (string comparison) with `-eq` (numeric comparison) inside `[` `]` conditions.
Automation, Orchestration and Scripting
Bash Scripting: Variables, Loops, Conditionals & Exit Codes
Not making a script executable (`chmod +x script.sh`) before trying to run it.
Automation, Orchestration and Scripting
Python
A high-level, interpreted programming language widely used for scripting and automation.
Automation, Orchestration and Scripting
pip
The package installer for Python, used to install and manage third-party libraries.
Automation, Orchestration and Scripting
Module
A file containing Python definitions and statements, extending functionality.
Automation, Orchestration and Scripting
Virtual Environment
An isolated Python environment for managing project-specific dependencies.
Automation, Orchestration and Scripting
Indentation
Whitespace used in Python to define code blocks, crucial for syntax.
Automation, Orchestration and Scripting
Data Type
Classification of data, such as integers, strings, booleans, and lists.
Automation, Orchestration and Scripting
Python Basics for Linux Automation
PIP: 'P'ython 'I'nstalls 'P'ackages. Remember this for the command to manage libraries!
Automation, Orchestration and Scripting
Python Basics for Linux Automation
The exam expects you to know how to execute basic Python scripts, understand the purpose of pip for package management, and recognize common Python syntax elements like 'if/else' and 'for' loops. Pay attention to the shebang line and execute permissions.
Automation, Orchestration and Scripting
Python Basics for Linux Automation
Forgetting the shebang line or execute permissions, leading to scripts not running directly.
Automation, Orchestration and Scripting
Python Basics for Linux Automation
Mixing Python 2 and Python 3 syntax; always use 'python3' and its compatible libraries.
Automation, Orchestration and Scripting
Python Basics for Linux Automation
Not using virtual environments, which can lead to dependency conflicts between projects.
Automation, Orchestration and Scripting
Python Basics for Linux Automation
Incorrect indentation, causing 'IndentationError' as Python relies on it for code blocks.
Automation, Orchestration and Scripting
Commit
A snapshot of your repository at a specific point in time, with a message.
Automation, Orchestration and Scripting
Branch
An independent line of development within a repository.
Automation, Orchestration and Scripting
Merge
The process of combining changes from one branch into another.
Automation, Orchestration and Scripting
Clone
To create a local copy of a remote Git repository.
Automation, Orchestration and Scripting
Push
To upload your local committed changes to a remote repository.
Automation, Orchestration and Scripting
Pull
To download and integrate changes from a remote repository into your local one.
Automation, Orchestration and Scripting
Staging Area
An intermediate area where changes are prepared before being committed.
Automation, Orchestration and Scripting
Version Control with Git: Workflow & Commands
Git's core cycle: 'Add' to Stage, 'Commit' to Repo, 'Push' to Cloud. (ASRPC)
Automation, Orchestration and Scripting
Version Control with Git: Workflow & Commands
The exam expects you to know the basic Git workflow and common commands for managing local and remote repositories. Keywords to spot include 'version control,' 'commit,' 'branch,' 'merge,' 'clone,' 'push,' and 'pull.'
Automation, Orchestration and Scripting
Version Control with Git: Workflow & Commands
Forgetting to `git add` files before `git commit`, leading to an empty commit or missing changes.
Automation, Orchestration and Scripting
Version Control with Git: Workflow & Commands
Committing directly to the `main` or `master` branch without using a feature branch, especially in team environments.
Automation, Orchestration and Scripting
Version Control with Git: Workflow & Commands
Not pulling the latest changes from the remote repository before starting new work, leading to merge conflicts.
Automation, Orchestration and Scripting
Infrastructure as Code (IaC)
Managing infrastructure using machine-readable definition files.
Automation, Orchestration and Scripting
Ansible
Agentless automation tool for configuration, deployment, and orchestration.
Automation, Orchestration and Scripting
Playbook
YAML file defining Ansible tasks and desired state for hosts.
Automation, Orchestration and Scripting
Continuous Integration (CI)
Automated process of merging code, building, and testing frequently.
Automation, Orchestration and Scripting
Continuous Delivery (CD)
Automated preparation of code for release after CI.
Automation, Orchestration and Scripting
Regular Expression (Regex)
Sequence of characters defining a search pattern for text.
Automation, Orchestration and Scripting
Agentless
Software that does not require client-side agents on managed nodes.
Automation, Orchestration and Scripting
Ansible, IaC, CI/CD & Regular Expressions
Imagine an 'Ansible' is a friendly robot butler (agentless!) who reads your 'Playbook' (a YAML recipe) to 'Automate' your house (infrastructure).
Automation, Orchestration and Scripting
Ansible, IaC, CI/CD & Regular Expressions
The exam expects you to know the fundamental concepts of IaC, the agentless nature of Ansible, and how to interpret basic regular expressions. Pay attention to common regex metacharacters and their meanings.
Automation, Orchestration and Scripting
Ansible, IaC, CI/CD & Regular Expressions
Confusing IaC with simple scripting; IaC focuses on desired state, not just sequential commands.
Automation, Orchestration and Scripting
Ansible, IaC, CI/CD & Regular Expressions
Forgetting that Ansible is agentless and uses SSH/WinRM for communication.
Automation, Orchestration and Scripting
Ansible, IaC, CI/CD & Regular Expressions
Underestimating the precision required for regular expressions; a single character can drastically change the match.
Automation, Orchestration and Scripting
Load Average
Average number of processes in runnable or uninterruptible state.
Troubleshooting Linux Systems
CPU Utilization
Percentage of time CPU spends on user, system, idle, or I/O wait tasks.
Troubleshooting Linux Systems
Swap Memory
Portion of disk used as virtual memory when RAM is full.
Troubleshooting Linux Systems
Buffers/Cache
Memory used by kernel for disk I/O operations to speed up access.
Troubleshooting Linux Systems
I/O Wait (wa)
CPU time spent waiting for I/O operations to complete.
Troubleshooting Linux Systems
Disk Utilization (%util)
Percentage of time a disk device is busy processing requests.
Troubleshooting Linux Systems
await
Average time (ms) for I/O requests to be serviced, including queue time.
Troubleshooting Linux Systems
Performance Troubleshooting: top, free & iostat
To remember the key performance tools: 'T'op for Tasks, 'F'ree for RAM, 'I'ostat for I/O. TFI: 'Trouble-Free Investigation'.
Troubleshooting Linux Systems
Performance Troubleshooting: top, free & iostat
The CompTIA Linux+ exam expects you to know the purpose and basic output interpretation of 'top', 'free', and 'iostat'. Pay attention to load averages, CPU states (user, system, idle, wa), memory metrics (total, used, free, buff/cache, available), and disk I/O metrics (%util, await).
Troubleshooting Linux Systems
Performance Troubleshooting: top, free & iostat
Misinterpreting high 'used' memory as a problem without considering 'buff/cache' or 'available' memory.
Troubleshooting Linux Systems
Performance Troubleshooting: top, free & iostat
Only looking at the 1-minute load average in 'top' and not considering the 5- and 15-minute averages for trends.
Troubleshooting Linux Systems
Performance Troubleshooting: top, free & iostat
Forgetting to install the 'sysstat' package before trying to use 'iostat'.
Troubleshooting Linux Systems
MBR/GPT
Master Boot Record/GUID Partition Table, disk partitioning schemes.
Troubleshooting Linux Systems
fsck
Filesystem check and repair utility.
Troubleshooting Linux Systems
dmesg
Displays kernel messages, including hardware errors.
Troubleshooting Linux Systems
lsblk
Lists block devices and their partitions.
Troubleshooting Linux Systems
smartctl
Utility to monitor S.M.A.R.T. data for disk health.
Troubleshooting Linux Systems
chroot
Changes the root directory for a process.
Troubleshooting Linux Systems
Diagnosing Boot & Storage Issues
GRUB: Get Running, Under Bootloader. Remember the order: BIOS -> GRUB -> Kernel -> initramfs -> systemd.
Troubleshooting Linux Systems
Diagnosing Boot & Storage Issues
The exam often tests your knowledge of the boot process stages and the commands used to diagnose and repair bootloader or filesystem issues. Pay attention to 'grub-install', 'update-grub', and 'fsck'.
Troubleshooting Linux Systems
Diagnosing Boot & Storage Issues
Running 'fsck' on a mounted filesystem, which can cause data corruption.
Troubleshooting Linux Systems
Diagnosing Boot & Storage Issues
Incorrectly specifying the disk for 'grub-install' (e.g., '/dev/sda1' instead of '/dev/sda').
Troubleshooting Linux Systems
Diagnosing Boot & Storage Issues
Forgetting to 'chroot' into the target system before running repair commands from a live environment.
Troubleshooting Linux Systems
ip command
Modern Linux utility for managing and displaying network interfaces, routing, and ARP.
Troubleshooting Linux Systems
ss command
Utility to display socket statistics, showing active connections and open ports.
Troubleshooting Linux Systems
dig command
Tool for querying DNS name servers to perform hostname-to-IP resolution.
Troubleshooting Linux Systems
Network Interface
Hardware or virtual component that connects a system to a network (e.g., eth0).
Troubleshooting Linux Systems
Routing Table
A set of rules defining how network packets are forwarded to their destinations.
Troubleshooting Linux Systems
DNS (Domain Name System)
Translates human-readable domain names into numerical IP addresses.
Troubleshooting Linux Systems
Socket
An endpoint of a two-way communication link across a network.
Troubleshooting Linux Systems
Network Troubleshooting: ip, ss & dig
Imagine a detective: 'IP' checks the ID (interface/IP), 'SS' checks who's talking (sockets/services), and 'DIG' checks the phone book (DNS).
Troubleshooting Linux Systems
Network Troubleshooting: ip, ss & dig
The exam expects you to know the modern commands 'ip' and 'ss' as replacements for 'ifconfig', 'route', and 'netstat'. Be prepared to interpret their output for interface status, IP addresses, routing, and open ports. For DNS, 'dig' is the primary tool to know.
Troubleshooting Linux Systems
Network Troubleshooting: ip, ss & dig
Forgetting to use 'sudo' for commands that require elevated privileges to modify network settings or view certain socket details.
Troubleshooting Linux Systems
Network Troubleshooting: ip, ss & dig
Confusing 'ip a' (address) with 'ip r' (route) – they provide distinct but related information.
Troubleshooting Linux Systems
Network Troubleshooting: ip, ss & dig
Assuming a network issue is always a physical problem; often, it's a misconfiguration of IP, routing, or DNS.
Troubleshooting Linux Systems
Permissions
Rules defining who can read, write, or execute files/directories.
Troubleshooting Linux Systems
Owner
The user account that owns a file or directory.
Troubleshooting Linux Systems
Group
A collection of users who share common access rights to files.
Troubleshooting Linux Systems
Resolving Permission Problems & Service Failures
For permissions, remember 'R-W-X' (Read, Write, Execute) and 'O-G-A' (Owner, Group, All). For `chmod`, think 'Change Mode' and for `chown`, 'Change Owner'.
Troubleshooting Linux Systems
Resolving Permission Problems & Service Failures
The exam frequently tests your knowledge of `chmod` and `chown` syntax, especially octal permissions. Be prepared to interpret `ls -l` output and troubleshoot service states using `systemctl status` and `journalctl -u`.
Troubleshooting Linux Systems
Resolving Permission Problems & Service Failures
Forgetting to use `-R` with `chmod` or `chown` when applying changes recursively to directories and their contents.
Troubleshooting Linux Systems
Resolving Permission Problems & Service Failures
Trying to fix a service failure by blindly restarting it without first checking `systemctl status` and `journalctl` for clues.
Troubleshooting Linux Systems
Resolving Permission Problems & Service Failures
Confusing the owner and group categories when setting octal permissions, leading to incorrect access rights.
Troubleshooting Linux Systems