LPI 010-160 Bundle

GPL-style copyleft licenses attach specified source availability and licensing requirements to redistributed derivative software under their terms. “Check the exact license version and distribution conditions before promising proprietary-only redistribution of copyleft code” would remedy that alternative situation, but it would not correct the present issue: samba commonly implements SMB interoperability with Windows file-sharing clients, while NFS uses a different file-sharing protocol and ecosystem.

“Classify software by its purpose and avoid substituting document editing tools for a persistent relational data service” is the supported response when mariaDB and PostgreSQL are database management systems that maintain structured tables and queries, unlike a simple text editing application. Here the decisive response is “Select the network file-sharing protocol based on client compatibility and permissions, not simply network connectivity”, so that different intervention does not meet the stated requirement.

Open source licensing does not imply identical application roles; LibreOffice provides office document and spreadsheet editing functionality. “Match open source application selection to actual document, media or development tasks rather than to licensing alone” applies to that other condition. The reported evidence is a small business needs Windows and Linux staff to exchange files through a shared folder but chooses NFS solely because every computer on the network uses IP; this alternative would address the wrong dependency.

A path without a leading slash is interpreted relative to the current working directory rather than from the filesystem root. “Use the appropriate absolute path starting at / or deliberately change into the required base directory before invoking the command” would remedy that alternative situation, but it would not correct the present issue: linux packages often install local documentation and examples in conventional directories such as /usr/share/doc.

“Run the utility's supported help flag for basic syntax and consult its manual for deeper option semantics” is the supported response when short command help commonly summarizes syntax, whereas man pages or extended documentation provide additional concepts and examples. Here the decisive response is “Inspect the appropriate package documentation directory and use local README files or examples to learn intended usage”, so that different intervention does not meet the stated requirement.

GNU Info documentation can contain linked, structured chapters that supplement terse command help and manual page summaries. “Open the supported info documentation and follow its nodes to the relevant section before changing command usage” applies to that other condition. The reported evidence is a learner installs a small Unix utility but cannot find its bundled README and assumes all software documentation must be online; this alternative would address the wrong dependency.

A normal account and the root superuser have different default privileges, and protected system changes require authorized elevated access. “Use the approved administrative procedure under an authorized privileged identity rather than removing broad filesystem protections” would remedy that alternative situation, but it would not correct the present issue: the /etc/skel directory conventionally supplies default initial home-directory content for user creation, separate from arbitrary existing home files.

“Set a least-privilege numeric mode appropriate for the script's intended owner and authorized readers or executors” is the supported response when numeric Unix permission digits combine read 4, write 2 and execute 1 bits for owner, group and other classes. Here the decisive response is “Configure approved generic starter files in /etc/skel and create a disposable test user with the appropriate home creation settings”, so that different intervention does not meet the stated requirement.

Configured local accounts and active login sessions are different records; tools such as who and w report current logged-in users. “Use who or w to inspect active sessions and separately consult account metadata for the list of created users” applies to that other condition. The reported evidence is an administrator provisions new student accounts but expects an existing employee's personal dotfiles to be copied automatically as templates into every home directory; this alternative would address the wrong dependency.

Directory owner, owning group and mode bits collectively determine ordinary discretionary access; changing one owner field alone is insufficient. “Review both group ownership and mode bits when modifying collaboration directories instead of treating one chown as complete authorization” would remedy that alternative situation, but it would not correct the present issue: for directories the execute bit governs path traversal, while directory read permission primarily permits listing entry names.

“Use ownership tools only on verified paths and avoid broad recursive changes outside the intended project tree” is the supported response when file ownership is filesystem metadata associated with user and group IDs; changing file contents does not change ownership. Here the decisive response is “Test directory traversal separately from directory listing before diagnosing access errors as missing file-read permissions”, so that different intervention does not meet the stated requirement.

The sticky bit on a shared writable directory restricts removal or renaming of entries by unrelated users, subject to ownership and privilege rules. “Protect shared writable directories with suitable sticky-bit behavior and test deletion ownership before offering multiuser temp space” applies to that other condition. The reported evidence is a learner grants read permission on a shared directory but removes its execute permission, after which colleagues can see directory names yet cannot enter it or open files; this alternative would address the wrong dependency.

Filesystem storage capacity and main memory statistics are separate resources; the free command reports memory and swap usage. “Use free with a readable display option to inspect available RAM and swap in the training session” would remedy that alternative situation, but it would not correct the present issue: hostnames and interface IP addresses are distinct; a system can have multiple network devices and IPv4 or IPv6 addresses.

“Read an appropriate process or system information entry under /proc without treating it as a long-term data store” is the supported response when the proc pseudo-filesystem exposes dynamic kernel and process information rather than a conventional persistent directory of ordinary documents. Here the decisive response is “Run the supported ip addr show command and select the address attached to the intended active network interface”, so that different intervention does not meet the stated requirement.

The /sys pseudo-filesystem exposes kernel device and subsystem attributes rather than ordinary personal data files. “Inspect supported read-only hardware attributes under /sys and modify device settings only through documented authorized interfaces” applies to that other condition. The reported evidence is a student needs the assigned IPv4 address of a training Linux computer but guesses it from its hostname and misses that multiple interfaces exist; this alternative would address the wrong dependency.

The learner correctly identifies the Linux kernel relationship while explaining why a desktop package manager is not built into a normal Android device. “Distinguish the shared kernel lineage from the separate Android application stack when selecting supported software or terminal tools” would remedy that alternative situation, but it would not correct the present issue: the developer identifies the guest operating system and performs a basic supported shell command without needing access to the physical cloud host.

“Install an authorized web server such as NGINX and configure a simple document root and reachable listener” is the supported response when a separate client fetches the expected static HTML response while the server process remains available without a local browser session. Here the decisive response is “Connect to the authorized Linux guest and use normal distribution identification and shell commands while respecting cloud-specific access controls”, so that different intervention does not meet the stated requirement.

The board starts the intended operating system, identifies its CPU architecture and permits the designed classroom programming exercises. “Choose an appropriate Raspberry Pi compatible Linux image and boot medium rather than applying an incompatible x86 installer” applies to that other condition. The reported evidence is a developer mistakes a Linux virtual machine running in a cloud account for a distinct operating system that does not share Linux shell and filesystem conventions with local machines; this alternative would address the wrong dependency.

The /etc/skel directory conventionally supplies default initial home-directory content for user creation, separate from arbitrary existing home files. “Configure approved generic starter files in /etc/skel and create a disposable test user with the appropriate home creation settings” would remedy that alternative situation, but it would not correct the present issue: the passwd utility performs an authorized password update using the system's account authentication mechanisms rather than editing identity metadata as plain text.

“Inspect id output and the account's current groups, then correct authorized membership and refresh the session where needed” is the supported response when effective group access depends on actual user and supplementary group identity information, which can be inspected with tools such as id. Here the decisive response is “Use passwd or the approved administrative reset workflow to change the appropriate account credential safely”, so that different intervention does not meet the stated requirement.

A Linux group is an account database entity with a group ID, not merely a label embedded in a file or directory name. “Create the approved group using groupadd or a supported account tool, then assign authorized members according to policy” applies to that other condition. The reported evidence is a learner changes the text inside /etc/passwd expecting to update their login password and then cannot authenticate with the intended new secret; this alternative would address the wrong dependency.

The cut utility can select delimited fields from each line when supplied with an appropriate field number and separator. “Use cut with the colon delimiter and the field corresponding to the desired username in the controlled sample” would remedy that alternative situation, but it would not correct the present issue: bzip2 and xz use different compression formats; similar purposes do not make their bitstreams interchangeable.

“Inspect the archive file list and extract into a new controlled directory rather than an unknown working location” is the supported response when tar extraction restores archived pathname entries relative to a chosen destination, so the current working directory and archive paths affect where files appear. Here the decisive response is “Identify the archive's true format and select the appropriate xz or bzip2 decompressor before restoring file contents”, so that different intervention does not meet the stated requirement.

The tar utility combines multiple files and directory entries into an archive, while a compressor such as gzip commonly processes individual streams or files. “Create a tar archive from the intended project directory with the appropriate archive-file and source arguments” applies to that other condition. The reported evidence is an operator attempts to decompress an .xz backup using bunzip2 because both tools reduce file size, producing an invalid compressed-data error; this alternative would address the wrong dependency.

A recipient can obtain the corresponding required source and license notices for the redistributed GPL-covered work. “Review the actual GPL version and comply with its source distribution and notice requirements when redistributing modified binaries” would remedy that alternative situation, but it would not correct the present issue: the selected desktop image has a documented vendor maintenance window compatible with the planned school replacement cycle.

“Identify the specific Linux Mint edition and its base repositories before selecting compatible desktop software and help instructions” is the supported response when the learner can describe which distribution family the installed edition uses and install a suitable package using its documented tools. Here the decisive response is “Choose a stable LTS distribution release when multi-year support and predictable upgrade windows are part of the deployment requirement”, so that different intervention does not meet the stated requirement.

The installed software is recorded by the RPM database and the package manager can display its version and dependency information. “Select a compatible packaged web-server build from configured RPM-based repositories and install it using the distribution's supported package manager” applies to that other condition. The reported evidence is a school is deploying classroom Linux desktops for several years but chooses a short-lived development release expecting the same maintenance lifespan as an Ubuntu LTS release; this alternative would address the wrong dependency.

A controlled memory load changes RAM utilization readings independently of how many ordinary files are deleted from disk. “Inspect memory availability and process usage using appropriate Linux monitoring commands before deciding whether the problem is RAM or disk” would remedy that alternative situation, but it would not correct the present issue: the expected NVMe disk is identified under its actual device naming scheme instead of being mistaken for a missing /dev/sd device.

“Inspect the appropriate authorized log file location and filter the recorded messages by the incident interval” is the supported response when the selected file contains the expected time-stamped test event while the service configuration remains a separate document. Here the decisive response is “Inspect available block devices and their partitions before selecting a particular drive for any educational demonstration”, so that different intervention does not meet the stated requirement.

After driver support is enabled, the expected network interface becomes visible to Linux network inspection tools. “Identify the hardware model and obtain a supported driver or compatible kernel module from a trusted distribution source” applies to that other condition. The reported evidence is a student assumes every solid-state drive appears as /dev/sda and cannot identify an NVMe device shown under a different Linux block device naming convention; this alternative would address the wrong dependency.

Bash can maintain an in-session command history, and persistent history behavior depends on shell configuration and session lifecycle. “Avoid typing passwords or tokens into interactive commands because shell history may retain sensitive parameters” would remedy that alternative situation, but it would not correct the present issue: shell word splitting treats unquoted spaces as argument separators; appropriate quoting preserves a path containing spaces as one parameter.

“Test environment visibility in child processes rather than assuming a local shell variable automatically becomes globally available” is the supported response when an ordinary shell variable is scoped to the current shell, while exported environment variables are passed to child processes. Here the decisive response is “Test shell scripts with whitespace-containing filenames and avoid assembling unquoted file paths from external input”, so that different intervention does not meet the stated requirement.

An interactive shell interprets typed command lines and can launch built-ins or available executables without compiling the command text into a program. “Distinguish interactive commands from scripts and compiled programs when diagnosing why a simple shell instruction will not run” applies to that other condition. The reported evidence is a student creates a directory named My Reports and then runs a command using the unquoted path, causing Bash to treat its two words as separate arguments; this alternative would address the wrong dependency.