How many Drag and Drop Matching Questions questions are on this page?

This page has 5 Drag and Drop Matching Questions scenario questions for the LPIC-1 exam, each with detailed explanations and wrong-answer analysis.

How should I approach LPIC-1 scenario questions?

Read the full scenario before looking at the answer options. Identify the constraint or requirement in the scenario, then eliminate options that are generally true but wrong for this specific case. Scenario questions reward careful reading over pattern matching.

← Back to Linux Professional Institute Certification Level 1 LPIC-1 questions

Scenario-based practice

Drag and Drop Matching Questions

Practise Linux Professional Institute Certification Level 1 LPIC-1 practice questions — original exam-style scenarios covering every exam domain, with detailed explanations, wrong-answer analysis, and common exam traps.

Start full practice test Read exam guide

scenario questions

LPIC-1

exam code

LPI

vendor

Scenario guide

How to approach drag and drop matching questions

Matching questions give you two columns — concepts, commands, or protocols on the left, and their definitions or use-cases on the right. You drag each left item to its correct match. These appear on most certification exams and punish superficial memorisation.

Quick answer

Drag and Drop Matching Questions questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Practice scenarios

Question 1mediummatching

Study the full ACL explanation →

Match each ACL term to its meaning.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Permissions for a specific user

Permissions for a specific group

Maximum permissions for named users and groups

Permissions for everyone else

Inherited ACL for new files/directories

A
Access ACL: Defines permissions for a file or directory.
Access ACL is used to define permissions for any file or directory, not just directories.
B
Default ACL: Specifies permissions inherited by new objects in a directory.
Default ACL applies to newly created files and subdirectories within a directory.
C
Mask: Sets the maximum permissions for named users and groups.
Mask in ACL restricts the permissions that named users and groups can have, overriding their specific entries.
D
Access ACL: Applied only to directories.
Why it fails: Incorrect — Access ACL applies to both files and directories, not only directories.
E
Default ACL: Controls access to the current directory's contents.
Why it fails: Incorrect — Default ACL does not affect current access; it only applies to new objects.
F
Mask: Permissions for the file owner.
Why it fails: Incorrect — Mask is not owner permissions; owner permissions are separate.

Full breakdown with real-world context →

Question 2mediummatching

Full question →

Match each Linux runlevel to its typical description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Halt

Single-user mode

Multi-user with networking

Multi-user with GUI

Reboot

A
runlevel 0: Halt
Runlevel 0 is used to halt the system.
B
runlevel 1: Single-user mode
Runlevel 1 is single-user mode, often used for maintenance.
C
runlevel 3: Graphical multi-user mode
Why it fails: Incorrect — runlevel 3 is multi-user mode with network but no graphical interface; graphical mode is runlevel 5.
D
runlevel 5: Multi-user mode with network
Why it fails: Incorrect — runlevel 5 is graphical multi-user mode; multi-user with network is runlevel 3.
E
runlevel 6: Reboot
Runlevel 6 is used to reboot the system.

Full breakdown with real-world context →

Question 3mediummatching

Full question →

Match each Linux command to its primary function.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Search text using patterns

Change file permissions

Report snapshot of current processes

Archive files

Stream editor for filtering and transforming text

A
cp: Copy files or directories
cp is the command used to copy files and directories in Linux.
B
cp: Search text using patterns
Why it fails: Incorrect — this describes grep, not cp.
C
grep: Search text using patterns
grep is used to search text using regular expressions.
D
grep: Change file permissions
Why it fails: Incorrect — this describes chmod, not grep.
E
chmod: Change file permissions
chmod changes the file permissions (mode) for files and directories.
F
chmod: List directory contents
Why it fails: Incorrect — this describes ls, not chmod.

Full breakdown with real-world context →

Question 4mediummatching

Full question →

Match each Linux directory to its standard purpose.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

System configuration files

Variable data (logs, databases)

User-installed software and libraries

Temporary files (often cleared on reboot)

Virtual file system for process and kernel info

A
/bin: Essential user command binaries
/bin contains essential command binaries needed for booting and repairing the system, available to all users.
B
/etc: Host-specific system configuration
/etc stores configuration files for the system and applications, specific to the host.
C
/var: Variable data such as logs and spool files
/var contains data that changes frequently, like log files, spool directories, and temporary caches.
D
/bin: Variable data such as logs and spool files
Why it fails: Incorrect — /bin does not store variable data; that is the purpose of /var.
E
/etc: Temporary files cleared on reboot
Why it fails: Incorrect — /etc holds configuration files, not temporary files; that is /tmp.
F
/var: Essential user command binaries
Why it fails: Incorrect — /var does not contain binaries; essential binaries reside in /bin.

Full breakdown with real-world context →

Question 5mediummatching

Full question →

Match each package manager to its associated distribution family.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Debian, Ubuntu

RHEL, CentOS 7

Fedora, RHEL 8+

openSUSE

Arch Linux

A
APT: Debian-based distributions
APT is the package manager used by Debian, Ubuntu, and their derivatives.
B
YUM: Red Hat-based distributions
YUM (now often replaced by DNF) is the package manager for Red Hat Enterprise Linux, Fedora, CentOS, etc.
C
ZYpp: SUSE-based distributions
ZYpp is the package manager used by openSUSE and SUSE Linux Enterprise.
D
pacman: Arch Linux
pacman is the package manager for Arch Linux and its derivatives.
E
APT: Red Hat-based distributions
Why it fails: Incorrect — APT is associated with Debian-based distributions, not Red Hat-based.
F
YUM: SUSE-based distributions
Why it fails: Incorrect — YUM is associated with Red Hat-based distributions, not SUSE-based.

Full breakdown with real-world context →

These LPIC-1 practice questions are part of Courseiva's free LPI certification practice question bank. Courseiva provides original exam-style LPIC-1 questions with detailed explanations, topic-based practice, mock exams, readiness tracking, and study analytics.

Drag and Drop Matching Questions

How to approach drag and drop matching questions

Quick answer

Related LPIC-1 topic practice pages

Administrative Tasks practice questions

Linux Installation and Package Management practice questions

GNU and Unix Commands practice questions

Essential System Services and Networking practice questions

Devices, Filesystems and FHS practice questions

Shells, Scripting and Data Management practice questions

System Architecture practice questions

LPIC-1 fundamentals practice questions

LPIC-1 scenario practice questions

LPIC-1 troubleshooting practice questions

Practice scenarios

Match each ACL term to its meaning.

Match each Linux runlevel to its typical description.

Match each Linux command to its primary function.

Match each Linux directory to its standard purpose.

Match each package manager to its associated distribution family.