LPI 010-160 Bundle

MariaDB and PostgreSQL are database management systems that maintain structured tables and queries, unlike a simple text editing application. “Classify software by its purpose and avoid substituting document editing tools for a persistent relational data service” would remedy that alternative situation, but it would not correct the present issue: NFS provides a network filesystem model that Linux clients can mount, while local copies do not stay synchronized automatically.

“Select the network file-sharing protocol based on client compatibility and permissions, not simply network connectivity” is the supported response when samba commonly implements SMB interoperability with Windows file-sharing clients, while NFS uses a different file-sharing protocol and ecosystem. Here the decisive response is “Protect NFS exports by client and filesystem permissions and avoid confusing a mounted share with independent duplicated files”, 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 two Linux laboratory computers need to mount one shared course directory, but the students assume that copying files manually after each change is the only option; this alternative would address the wrong dependency.

This action addresses tar extraction into an approved destination, whose causal condition is: Tar extraction restores archived pathname entries relative to a chosen destination, so the current working directory and archive paths affect where files appear. The current scenario instead requires attention to: A for loop iterates over supplied values, assigning each value to a loop variable before executing the body statements.

This action addresses positional parameters in bash script arguments, whose causal condition is: Bash positional parameters such as $1 are expanded by the shell unless quoting rules prevent expansion. In this question the necessary remedy is “Use a simple Bash for loop over the intended fixed sample list and quote each variable when printing or processing it”, which this alternative does not provide.

This action addresses executable bit required for direct shell script launch, whose causal condition is: Direct execution requires suitable executable permission on a regular file, while explicitly invoking Bash only needs permission to read its contents. The observed condition is an intern writes the same echo command ten times for ten filenames and asks how a basic Bash script could repeat one action over a defined list; this mechanism addresses another problem.

An id check inside the resulting shell reports the selected account while the original user's shell remains accessible on exit. “Use an approved su invocation to enter the intended authorized account and inspect the resulting identity before running commands” would remedy that alternative situation, but it would not correct the present issue: a file long listing shows restricted other bits and a different unapproved account can no longer read the test file.

“Use who or w to inspect active sessions and separately consult account metadata for the list of created users” is the supported response when the results identify a test logged-in session while inactive configured accounts are not falsely reported as connected. Here the decisive response is “Apply the intended symbolic chmod change to remove other-read access while retaining necessary owner and group permissions”, so that different intervention does not meet the stated requirement.

A long listing decodes to the intended owner, group and other permissions and an unauthorized account cannot modify the script. “Set a least-privilege numeric mode appropriate for the script's intended owner and authorized readers or executors” applies to that other condition. The reported evidence is a group project file is readable by every account although the team wants only its owner and group to read it, and an operator confuses permission characters; this alternative would address the wrong dependency.

ZIP is an archive format holding one or more entries, often compressed, rather than an ordinary text document. “Inspect ZIP contents before extraction and avoid overwriting unrelated files with an unfamiliar archive” would remedy that alternative situation, but it would not correct the present issue: the sort command orders text lines according to a selected comparison rule, allowing repeatable list ordering before analysis.

“Verify the intended stream is piped and be aware that stderr diagnostics are separate from ordinary standard output” is the supported response when a shell pipeline connects one command's standard output to the next command's standard input. Here the decisive response is “Use consistent sorting options and locale when relying on command-line comparisons of generated text”, so that different intervention does not meet the stated requirement.

The > redirection truncates or creates an output file, while >> appends to the existing file in a normal shell. “Review redirection operators before running commands against existing reports or log files containing irreplaceable data” applies to that other condition. The reported evidence is a trainee compares two text lists with identical names in different orders and concludes the lists contain different members because their lines do not align; this alternative would address the wrong dependency.

A shebang line at the beginning of an executable script can identify its intended interpreter for direct execution. “Place an appropriate supported Bash interpreter directive at the first line and confirm the path exists on the training system” would remedy that alternative situation, but it would not correct the present issue: head selects leading lines, while tail selects trailing lines from a text stream or file.

“Open the output in less and use supported navigation or search keys to inspect the desired section” is the supported response when a pager such as less allows interactive navigation through long text without emitting the whole file as an uncontrolled screen dump. Here the decisive response is “Use tail with a suitable line count to inspect the latest stored lines and head when the first records are needed”, so that different intervention does not meet the stated requirement.

The wc options count different units: newline-terminated lines, whitespace-delimited words and bytes respectively. “Select the appropriate wc count option for the specified measurement rather than treating all numeric outputs as interchangeable” applies to that other condition. The reported evidence 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 alternative would address the wrong dependency.

This action addresses default route found using ip route show, whose causal condition is: An IP address alone does not prove an external route exists; the kernel routing table determines the next hop for off-subnet traffic. The current scenario instead requires attention to: IP reachability and hostname resolution are separate stages; direct numeric address success can coexist with DNS configuration failure.

This action addresses hosts file versus dns resolver configuration, whose causal condition is: The hosts file provides local name-to-address mappings, while broader DNS lookups depend on the configured resolver and upstream name servers. In this question the necessary remedy is “Compare controlled numeric-address ping results against host or other name lookup output before changing routing”, which this alternative does not provide.

This action addresses ss displays current network socket listeners, whose causal condition is: The ss utility can show listening sockets and established connections, which are different from general filesystem or process listings. The observed condition is a technician successfully pings an IP address but cannot ping the intended hostname and concludes that all network connectivity is down; this mechanism addresses another problem.

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” 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.

“Set the intended owning group and suitable group permissions with authorized filesystem tools after confirming account memberships” is the supported response when directory owner, owning group and mode bits collectively determine ordinary discretionary access; changing one owner field alone is insufficient. 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.

The sticky bit on a shared writable directory restricts removal or renaming of entries by unrelated users, subject to ownership and privilege rules. “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.

A directory listing or file copy accesses the intended My Reports path without a missing-argument or nonexistent-path error. “Pass the pathname as a single double-quoted argument or use correct escaping when invoking the desired file command” would remedy that alternative situation, but it would not correct the present issue: a newly started shell or script prints the intended PROJECT value while unrelated session state remains unchanged.

“Enter the required command with valid syntax at the shell prompt and observe the resulting output or documented error” is the supported response when a harmless echo command displays the expected text immediately while an unavailable command yields an understandable shell lookup error. Here the decisive response is “Export the needed variable in the parent shell before launching the child and confirm its value within the executed script”, 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 sets PROJECT=lab in one Bash shell and starts a separate script but the script cannot read that value because it was never exported; this alternative would address the wrong dependency.

This action addresses find directory tree by filename pattern, whose causal condition is: A filesystem search utility such as find can traverse directories and filter entries by name and other supported properties. The current scenario instead requires attention to: Removing ordinary files and recursively removing directories are different operations, and recursive deletion can irreversibly delete many entries.

This action addresses cp copy retains original source file, whose causal condition is: The cp command copies file contents into another pathname, whereas mv relocates or renames the original directory entry. In this question the necessary remedy is “Inspect the exact directory contents and use the appropriate explicitly authorized recursive removal method only when the intended tree is confirmed”, which this alternative does not provide.

This action addresses mkdir nested directories requires parent handling, whose causal condition is: By default mkdir requires parent directories to exist; its supported parent-creation option can create the missing hierarchy. The observed condition is a trainee tries rm project to remove a nonempty directory and then attempts an unsafe wildcard command when the shell reports that the directory cannot be removed; this mechanism addresses another problem.

The shell can expand a leading tilde into the current user's configured home directory, avoiding assumptions about account names. “Use a supported tilde-based home path or the HOME variable appropriately when constructing a personal file location” would remedy that alternative situation, but it would not correct the present issue: by default mkdir requires parent directories to exist; its supported parent-creation option can create the missing hierarchy.

“Run find from the appropriate search root with a quoted name pattern and review matches before taking further action” is the supported response when a filesystem search utility such as find can traverse directories and filter entries by name and other supported properties. Here the decisive response is “Use mkdir -p for the desired nested directory path after checking where it will be created”, so that different intervention does not meet the stated requirement.

The cp command copies file contents into another pathname, whereas mv relocates or renames the original directory entry. “Use cp with a distinct destination pathname and confirm both source and backup copies exist” applies to that other condition. The reported evidence is a learner tries to create coursework/week1/scripts with a single mkdir command but receives an error because the intermediate coursework directory does not yet exist; this alternative would address the wrong dependency.

The /etc/passwd database commonly exposes account names and IDs while protected password hashes belong in a more restricted /etc/shadow database. “Inspect approved account metadata through standard account tools without attempting to reveal password hashes or weaken shadow permissions” would remedy that alternative situation, but it would not correct the present issue: a Linux group is an account database entity with a group ID, not merely a label embedded in a file or directory name.

“Run the supported user creation process with approved home directory and account defaults, then verify the new entry through account tools” is the supported response when creating a filesystem directory does not create a Unix user identity with a UID, account database entry and login settings. Here the decisive response is “Create the approved group using groupadd or a supported account tool, then assign authorized members according to policy”, so that different intervention does not meet the stated requirement.

The passwd utility performs an authorized password update using the system's account authentication mechanisms rather than editing identity metadata as plain text. “Use passwd or the approved administrative reset workflow to change the appropriate account credential safely” applies to that other condition. The reported evidence is a teacher wants several students to share access to a project folder and types the desired group name into a directory filename, expecting the group to exist; this alternative would address the wrong dependency.