LPIC-1 Matching — 10 Questions

Question 1

Match each Linux signal to its default action.

Accepted Answer

SIGINT: Terminate the process. Common Linux signals: SIGINT, SIGTERM, and SIGKILL terminate processes; SIGSTOP and SIGTSTP stop processes; SIGQUIT terminates with a core dump.

Answer

SIGTERM: Stop the process

Answer

SIGKILL: Core dump

Answer

SIGTSTP: Terminate the process

Question 2

Match each device file naming pattern to its device type.

Accepted Answer

/dev/sda: SATA/SCSI hard disk. Common Linux device naming conventions: /dev/sdX for SATA/SCSI, /dev/hdX for IDE, /dev/ttySX for serial ports, /dev/srX for optical drives, /dev/nvmeXnY for NVMe. Be cautious not to confuse with floppy (/dev/fdX) or other types.

Answer

/dev/sr0: Floppy disk

Question 3

Match each networking tool to its primary use.

Accepted Answer

ping: Test connectivity to a remote host. The correct matches are: ping for connectivity testing, ifconfig for interface configuration, and traceroute for path tracing. Common confusions include swapping netstat and nslookup definitions, or mistaking traceroute's purpose for ping's.

Answer

netstat: Query DNS name servers for host information

Answer

nslookup: Display network connections and routing tables

Answer

traceroute: Test connectivity to a remote host

Question 4

Match each ACL term to its meaning.

Accepted Answer

Access ACL: Defines permissions for a file or directory.. The correct matches: Access ACL applies to files and directories; Default ACL applies to new objects; Mask limits permissions for named users/groups. Common confusions include applying ACLs only to directories or misinterpreting mask as owner permissions.

Answer

Access ACL: Applied only to directories.

Answer

Default ACL: Controls access to the current directory's contents.

Answer

Mask: Permissions for the file owner.

Question 5

Match each Linux runlevel to its typical description.

Accepted Answer

runlevel 0: Halt. Standard SysV init runlevels: 0 (halt), 1 (single-user), 3 (multi-user with network), 5 (graphical multi-user), 6 (reboot). Common confusions involve swapping definitions between runlevels 3 and 5.

Answer

runlevel 3: Graphical multi-user mode

Answer

runlevel 5: Multi-user mode with network

Question 6

Match each package manager to its associated distribution family.

Accepted Answer

APT: Debian-based distributions. Common package managers and their distribution families: APT (Debian), YUM/DNF (Red Hat), ZYpp (SUSE), pacman (Arch). Distractor options swap these associations.

Answer

APT: Red Hat-based distributions

Answer

YUM: SUSE-based distributions

Question 7

Match each file system type to its typical description.

Accepted Answer

ext4: Default Linux file system with journaling and support for large files. The correct matches are: ext4 (default journaling FS), XFS (large file performance), Btrfs (advanced features), and swap (virtual memory). Common confusions include attributing XFS features to ext4 and mischaracterizing swap as a metadata file system.

Answer

ext4: File system optimized for large storage arrays and high concurrency

Answer

swap: File system that stores file metadata in a tree structure

Question 8

Match each Linux command to its primary function.

Accepted Answer

cp: Copy files or directories. The correct matches are: cp for copying files, grep for searching text, and chmod for changing permissions. Common confusions include mixing these commands due to similar syntax or overlapping contexts.

Answer

cp: Search text using patterns

Answer

grep: Change file permissions

Answer

chmod: List directory contents

Question 9

Match each Linux directory to its standard purpose.

Accepted Answer

/bin: Essential user command binaries. Correct matches: /bin holds essential binaries, /etc stores system configuration, /var contains variable data. Common confusions arise from swapping purposes: /bin is not for variable data, /etc is not for temporary files, and /var does not hold binaries.

Answer

/bin: Variable data such as logs and spool files

Answer

/etc: Temporary files cleared on reboot

Answer

/var: Essential user command binaries

Question 10

Match each SELinux context component to its purpose.

Accepted Answer

user: Identifies the SELinux user identity. In SELinux, the context format is user:role:type:level. User identifies the SELinux user, role defines accessible roles, type defines domain/object type, and level defines sensitivity/categories. Common confusions include swapping user/role or role/type.

Answer

user: Defines the set of roles that can be accessed

Answer

role: Defines the domain for processes