LPI 010-160 Bundle

The rmdir utility is intended for empty directories and refuses to remove a directory that still contains entries. “List the target directory, handle its contents through a separately approved process, then use rmdir when it is empty” would remedy that alternative situation, but it would not correct the present issue: for normal unquoted filename patterns, Bash pathname expansion substitutes matching directory entries before the command receives its arguments.

“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 “Quote a literal wildcard when text is intended, or use a scoped glob only when matching all eligible filenames is deliberate”, so that different intervention does not meet the stated requirement.

The ls long format displays file type, permission bits, ownership, sizes and other metadata not shown in a simple filename list. “Run ls -l against the intended path and read the file type and permission character groups correctly” applies to that other condition. The reported evidence is a student writes a command using *.txt and expects the shell to pass a literal asterisk to the program, but several matching text files are selected instead; this alternative would address the wrong dependency.

Manual pages are divided into numbered sections, so the same term can refer to different kinds of interfaces. “Open the applicable man section for the command-line utility or use the manual's section selection features” would remedy that alternative situation, but it would not correct the present issue: shell command names may resolve to aliases, functions, builtins or filesystem executables; a printed name alone does not identify the actual target.

“Use the built-in history display or an approved history navigation shortcut to locate and selectively rerun the intended command” is the supported response when bash can maintain an in-session command history, and persistent history behavior depends on shell configuration and session lifecycle. Here the decisive response is “Use the Bash type builtin to inspect how the command resolves before modifying a script or calling a different executable”, so that different intervention does not meet the stated requirement.

The shell searches PATH entries in order for commands that do not specify an explicit executable path. “Inspect the effective PATH and command resolution and invoke the intended executable with its full path or change the supported search order” applies to that other condition. The reported evidence is a trainee runs a command name that behaves differently from the executable documented in a tutorial because a shell alias has changed its meaning; this alternative would address the wrong dependency.

Command resolution reports the expected executable location and a test invocation produces the output of the intended program. “Inspect the effective PATH and command resolution and invoke the intended executable with its full path or change the supported search order” would remedy that alternative situation, but it would not correct the present issue: a harmless echo command displays the expected text immediately while an unavailable command yields an understandable shell lookup error.

“Export the needed variable in the parent shell before launching the child and confirm its value within the executed script” is the supported response when a newly started shell or script prints the intended PROJECT value while unrelated session state remains unchanged. Here the decisive response is “Enter the required command with valid syntax at the shell prompt and observe the resulting output or documented error”, so that different intervention does not meet the stated requirement.

The output shows the resolved home directory when double quoted and the literal variable name when single quoted. “Use double quotes around the requested variable expansion when the intention is to display its current value safely” applies to that other condition. The reported evidence is a learner enters the text of a shell command directly at a Bash prompt and assumes the text must first be saved as a compiled program before Linux can execute it; this alternative would address the wrong dependency.

This action addresses linux desktop gui and command line operating model, whose causal condition is: Linux systems can expose a command-line environment without a graphical desktop; the command interface is not evidence that the operating system is missing. The current scenario instead requires attention to: Hostnames and interface IP addresses are distinct; a system can have multiple network devices and IPv4 or IPv6 addresses.

This action addresses proc virtual filesystem reports running kernel state, whose causal condition is: The proc pseudo-filesystem exposes dynamic kernel and process information rather than a conventional persistent directory of ordinary documents. In this question the necessary remedy is “Run the supported ip addr show command and select the address attached to the intended active network interface”, which this alternative does not provide.

This action addresses sys virtual filesystem represents device information, whose causal condition is: The /sys pseudo-filesystem exposes kernel device and subsystem attributes rather than ordinary personal data files. The observed condition 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 mechanism addresses another problem.

Single quotes preserve most enclosed characters literally, while double quotes permit parameter expansion in Bash. “Use double quotes around the requested variable expansion when the intention is to display its current value safely” 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.

“Export the needed variable in the parent shell before launching the child and confirm its value within the executed script” 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 “Pass the pathname as a single double-quoted argument or use correct escaping when invoking the desired file command”, 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. “Enter the required command with valid syntax at the shell prompt and observe the resulting output or documented error” 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.

The top utility provides an interactive view of running tasks and CPU or memory activity that changes while the system runs. “Start top for the controlled workload and identify the process consuming the observed CPU resources” would remedy that alternative situation, but it would not correct the present issue: the /boot hierarchy typically contains bootloader and kernel startup files and is not intended as general user temporary storage.

“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 “Store personal work under an appropriate home or data directory and leave managed boot artifacts under their maintenance process”, 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 user sees /boot containing kernel-related files and assumes it is a good scratch space for a large video project; this alternative would address the wrong dependency.

This action addresses less interactive paging of long output, whose causal condition is: A pager such as less allows interactive navigation through long text without emitting the whole file as an uncontrolled screen dump. The current scenario instead requires attention to: Head selects leading lines, while tail selects trailing lines from a text stream or file.

This action addresses shebang selects interpreter for executable script, whose causal condition is: A shebang line at the beginning of an executable script can identify its intended interpreter for direct execution. In this question the necessary remedy is “Use tail with a suitable line count to inspect the latest stored lines and head when the first records are needed”, which this alternative does not provide.

This action addresses wc counts lines words and bytes distinctly, whose causal condition is: The wc options count different units: newline-terminated lines, whitespace-delimited words and bytes respectively. The observed condition is a student needs the newest events near the end of a long append-only log but repeatedly runs head and sees only the oldest lines; this mechanism addresses another problem.

Hostnames and interface IP addresses are distinct; a system can have multiple network devices and IPv4 or IPv6 addresses. “Inspect the interface and address family explicitly when recording network configuration for troubleshooting” would remedy that alternative situation, but it would not correct the present issue: filesystem storage capacity and main memory statistics are separate resources; the free command reports memory and swap usage.

“Measure resource use over an appropriate interval instead of equating a process name or configuration entry with current consumption” is the supported response when the top utility provides an interactive view of running tasks and CPU or memory activity that changes while the system runs. Here the decisive response is “Report memory and storage values with correct units and distinguish free memory from memory available after cache reclamation”, so that different intervention does not meet the stated requirement.

Executable files stored on disk are not the same as running processes; the ps command reports process information at the time of inspection. “Separate process-state evidence from software installation lists when interpreting performance and troubleshooting output” applies to that other condition. The reported evidence is a learner checks the size of /home and uses that number as a measure of remaining RAM available for programs, despite a separate free command showing pressure; this alternative would address the wrong dependency.

The hosts file provides local name-to-address mappings, while broader DNS lookups depend on the configured resolver and upstream name servers. “Document temporary hosts-file overrides and remove stale mappings before they mask correct DNS behavior later” would remedy that alternative situation, but it would not correct the present issue: an IP address alone does not prove an external route exists; the kernel routing table determines the next hop for off-subnet traffic.

“Test name resolution and packet connectivity independently rather than diagnosing both from one failed hostname command” is the supported response when IP reachability and hostname resolution are separate stages; direct numeric address success can coexist with DNS configuration failure. Here the decisive response is “Check destination routes in addition to interface addresses when investigating off-subnet connectivity failures”, so that different intervention does not meet the stated requirement.

The ss utility can show listening sockets and established connections, which are different from general filesystem or process listings. “Check socket binding and interface scope before altering firewall or external network policies in response to connection errors” applies to that other condition. The reported evidence is a workstation can reach local devices but fails to reach external networks, and the student checks only its interface address without inspecting routing; this alternative would address the wrong dependency.

The test server's listener appears with its local address and port while a deliberately stopped service no longer has that listener. “Inspect ss with appropriate listening and protocol flags and verify whether the expected local port is actually bound” would remedy that alternative situation, but it would not correct the present issue: the appropriate system device attribute is visible and explains how the kernel represents the attached hardware.

“Run the supported ip addr show command and select the address attached to the intended active network interface” is the supported response when the correct interface and its configured address are identified without relying on a guessed host name or stale note. Here the decisive response is “Inspect supported read-only hardware attributes under /sys and modify device settings only through documented authorized interfaces”, so that different intervention does not meet the stated requirement.

The user file resides in an intended writable data path and the existing boot configuration remains intact. “Store personal work under an appropriate home or data directory and leave managed boot artifacts under their maintenance process” applies to that other condition. The reported evidence is a beginner expects to edit a Linux hardware property by writing a normal user document into /sys and then assumes the entire directory is disposable; this alternative would address the wrong dependency.

The link resolves to its intended report when the target exists and deleting a disposable link leaves the original report present. “Create or inspect a symbolic link using ln -s and an appropriate listing, then distinguish removal of the link from removal of the target” would remedy that alternative situation, but it would not correct the present issue: the intended group can enter the authorized directory and open permitted files while unrelated accounts remain blocked.

“Use an appropriately authorized chown operation to set the intended owner and inspect the result with a long listing” is the supported response when the filename reports the new account as owner while the original document bytes remain unchanged after the metadata change. Here the decisive response is “Grant the minimum search or execute permission needed to traverse the intended directory and preserve appropriate protections on its files”, so that different intervention does not meet the stated requirement.

Two users can create their own temporary files, but an ordinary unrelated user cannot remove the other's protected entry. “Use the appropriate sticky-bit directory permissions for an approved shared temporary directory without making all individual files public” 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.