LPI 010-160 Bundle

The permitted administrator completes a controlled system configuration change while an ordinary test account remains unable to alter it. “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: two users can create their own temporary files, but an ordinary unrelated user cannot remove the other's protected entry.

“Set the intended owning group and suitable group permissions with authorized filesystem tools after confirming account memberships” is the supported response when an approved group member can create a disposable test file while a nonmember remains unable to write in the shared directory. Here the decisive response is “Use the appropriate sticky-bit directory permissions for an approved shared temporary directory without making all individual files public”, so that different intervention does not meet the stated requirement.

The intended group can enter the authorized directory and open permitted files while unrelated accounts remain blocked. “Grant the minimum search or execute permission needed to traverse the intended directory and preserve appropriate protections on its files” applies to that other condition. The reported evidence is a training machine offers a shared writable temporary directory and one student is able to delete another student's files despite not owning them; this alternative would address the wrong dependency.

This action addresses passwd changes authentication password for account, whose causal condition is: The passwd utility performs an authorized password update using the system's account authentication mechanisms rather than editing identity metadata as plain text. The current scenario instead requires attention to: File ownership is filesystem metadata associated with user and group IDs; changing file contents does not change ownership.

This action addresses directory execute permission controls traversal, whose causal condition is: For directories the execute bit governs path traversal, while directory read permission primarily permits listing entry names. In this question the necessary remedy is “Use an appropriately authorized chown operation to set the intended owner and inspect the result with a long listing”, which this alternative does not provide.

This action addresses sticky bit prevents unrelated users deleting shared temp files, whose causal condition is: The sticky bit on a shared writable directory restricts removal or renaming of entries by unrelated users, subject to ownership and privilege rules. The observed condition is an administrator needs to transfer responsibility for a project file to another account but edits the first line of the file to contain the new person's username; this mechanism addresses another problem.

This action addresses useradd creates account with intended home directory, whose causal condition is: Creating a filesystem directory does not create a Unix user identity with a UID, account database entry and login settings. The current scenario instead requires attention to: Sudo can authorize and log selected privileged commands under a named user account without distributing a shared root login secret.

This action addresses su changes execution user context, whose causal condition is: The su utility can start a shell under another account, so effective identity and login-environment details can differ from the caller's previous session. In this question the necessary remedy is “Run only the approved administrative command through sudo under the user's authorized policy rather than exposing root credentials”, which this alternative does not provide.

This action addresses root account privilege differs from standard user, whose causal condition is: A normal account and the root superuser have different default privileges, and protected system changes require authorized elevated access. The observed condition is a help-desk trainee needs to update one protected file and considers sharing the system's root password with every team member for convenience; this mechanism addresses another problem.

The delivered product retains necessary license notices without falsely claiming that a BSD component alone mandates publishing unrelated proprietary code. “Inspect the actual license terms, preserve required notices and attribute the permissively licensed component appropriately” would remedy that alternative situation, but it would not correct the present issue: the teacher successfully edits both example file types and saves the results in an agreed compatible format.

“Configure a controlled Samba share with an intended access policy and test it from an authorized Windows workstation” is the supported response when the Windows user opens the shared Linux directory through SMB and an unauthorized account cannot read private files. Here the decisive response is “Install an appropriate LibreOffice package and open a sample document and spreadsheet in the intended desktop environment”, so that different intervention does not meet the stated requirement.

A file placed in the authorized export becomes visible through the client mount without a manual second copy. “Provide a properly authorized NFS export and mount it on the intended client using the documented share path” applies to that other condition. The reported evidence is a teacher wants to edit documents and spreadsheets on Linux but installs a command-line image converter because both are listed as open source packages; this alternative would address the wrong dependency.

A separate client fetches the expected static HTML response while the server process remains available without a local browser session. “Install an authorized web server such as NGINX and configure a simple document root and reachable listener” would remedy that alternative situation, but it would not correct the present issue: a controlled installation uses the appropriate distribution package manager and successfully resolves dependencies from the intended trusted repositories.

“Choose a stable LTS distribution release when multi-year support and predictable upgrade windows are part of the deployment requirement” is the supported response when the selected desktop image has a documented vendor maintenance window compatible with the planned school replacement cycle. Here the decisive response is “Identify the installed distribution and use its supported package manager and repositories instead of assuming apt is universal”, 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 new Linux learner finds an Ubuntu tutorial using the apt command but applies the same instructions verbatim to a Red Hat family server, where apt is not installed and packages have different names; 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: the ls long format displays file type, permission bits, ownership, sizes and other metadata not shown in a simple filename list.

“Test path navigation with a harmless working directory before using parent-relative paths in destructive commands” is the supported response when relative .. refers to the parent of the current directory, while a leading slash restarts path resolution at the root directory. Here the decisive response is “Inspect metadata with long listings before modifying permissions or assuming an entry with a familiar extension is executable”, so that different intervention does not meet the stated requirement.

The shell can expand a leading tilde into the current user's configured home directory, avoiding assumptions about account names. “Test path construction under multiple accounts rather than hard-coding one person's home directory into shared shell commands” applies to that other condition. The reported evidence is a user sees only filenames in standard ls output but needs to distinguish an executable file from a directory and inspect its access permissions; this alternative would address the wrong dependency.

This action addresses grep regular expression star repeats preceding token, whose causal condition is: In basic regular expressions, the asterisk repeats the immediately preceding expression zero or more times rather than acting as a generic arbitrary suffix. The current scenario instead requires attention to: In basic regular expressions, an unescaped dot matches a single character, and bracket expressions can select a defined character set.

This action addresses grep matches lines containing target text, whose causal condition is: Grep filters input by a pattern and prints matching lines, making it suitable for locating occurrences in text files. In this question the necessary remedy is “Use an appropriate regular expression in grep and quote the pattern so the shell does not transform it first”, which this alternative does not provide.

This action addresses zip and unzip preserve a multi-file exchange, whose causal condition is: ZIP is an archive format holding one or more entries, often compressed, rather than an ordinary text document. The observed condition is a trainee searches a code list for entries such as cat and cot but uses a fixed-string search for c.t and expects the dot to match any character; this mechanism addresses another problem.

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” would remedy that alternative situation, but it would not correct the present issue: an interactive shell interprets typed command lines and can launch built-ins or available executables without compiling the command text into a program.

“Pass the pathname as a single double-quoted argument or use correct escaping when invoking the desired file command” is the supported response when shell word splitting treats unquoted spaces as argument separators; appropriate quoting preserves a path containing spaces as one parameter. 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.

An ordinary shell variable is scoped to the current shell, while exported environment variables are passed to child processes. “Export the needed variable in the parent shell before launching the child and confirm its value within the executed script” 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 absolute path starts at filesystem root, whose causal condition is: A path without a leading slash is interpreted relative to the current working directory rather than from the filesystem root. The current scenario instead requires attention to: A filesystem search utility such as find can traverse directories and filter entries by name and other supported properties.

This action addresses rm directory tree versus file removal semantics, whose causal condition is: Removing ordinary files and recursively removing directories are different operations, and recursive deletion can irreversibly delete many entries. In this question the necessary remedy is “Run find from the appropriate search root with a quoted name pattern and review matches before taking further action”, which this alternative does not provide.

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. The observed condition is a student knows a text file is under a large course tree but recursively opens every directory by hand instead of searching its name; this mechanism addresses another problem.

A symbolic link is a filesystem entry that refers to another pathname and can exist independently of the continued existence of its target. “Check link destinations before using recursive file operations and avoid treating a broken symlink as a missing directory entry” would remedy that alternative situation, but it would not correct the present issue: the su utility can start a shell under another account, so effective identity and login-environment details can differ from the caller's previous session.

“Keep password hash storage restricted and distinguish public identity metadata from secret authentication material” is the supported response when the /etc/passwd database commonly exposes account names and IDs while protected password hashes belong in a more restricted /etc/shadow database. Here the decisive response is “Confirm active identity and shell environment after using su, particularly before modifying files belonging to another account”, so that different intervention does not meet the stated requirement.

A normal account and the root superuser have different default privileges, and protected system changes require authorized elevated access. “Use standard-user sessions for ordinary work and limit root-level changes to justified tasks with reviewable audit context” applies to that other condition. The reported evidence is a trainee uses su to switch to another local account but assumes the current shell always retains their original effective user identity and home environment; this alternative would address the wrong dependency.

The authorized test user can authenticate with the new password while the former credential is rejected according to system policy. “Use passwd or the approved administrative reset workflow to change the appropriate account credential safely” would remedy that alternative situation, but it would not correct the present issue: an approved group member can create a disposable test file while a nonmember remains unable to write in the shared directory.

“Grant the minimum search or execute permission needed to traverse the intended directory and preserve appropriate protections on its files” is the supported response when the intended group can enter the authorized directory and open permitted files while unrelated accounts remain blocked. Here the decisive response is “Set the intended owning group and suitable group permissions with authorized filesystem tools after confirming account memberships”, so that different intervention does not meet the stated requirement.

The filename reports the new account as owner while the original document bytes remain unchanged after the metadata change. “Use an appropriately authorized chown operation to set the intended owner and inspect the result with a long listing” applies to that other condition. The reported evidence is a team directory is intended for one working group but an administrator changes only the owner name and assumes every other group member automatically gets write access; this alternative would address the wrong dependency.