LPI 010-160 Practice Test 66
Question 650
A user wants a convenient alternate pathname to an existing configuration file. If the team ignores the correct Symbolic links with ln -s approach, which problem is the MOST relevant direct risk?
- Repairing permissions alone cannot recover a nonexistent target file.
- Copying the file creates an independent data copy rather than a path link.
- Running all applications as root increases the impact of mistakes and compromise.
- Assuming all temp files persist indefinitely can lose work.
Explanation
Correct Answer
B:Copying the file creates an independent data copy rather than a path link. Avoid the failure by following this action: Run `ln -s target linkname` to create a symbolic link.
Incorrect Answers
A:Repairing permissions alone cannot recover a nonexistent target file. That risk is associated with Dangling symbolic links; it is less directly tied to the task. The omitted Symbolic links with ln -s safeguard instead risks: copying the file creates an independent data copy rather than a path link.
C:That risk is associated with Root versus ordinary users; it is less directly tied to the task.
D:Assuming all temp files persist indefinitely can lose work. That risk is associated with /tmp and /var/tmp retention; it is less directly tied to the task. The omitted Symbolic links with ln -s safeguard instead risks: copying the file creates an independent data copy rather than a path link.
Question 651
A Linux user must send several files in one ZIP archive to a colleague on another operating system. If the team ignores the correct ZIP archives and unzip approach, which problem is the MOST relevant direct risk?
- Returning success after a failed critical command can mislead later automation.
- Missing compression leaves an uncompressed tar despite a .gz-looking filename.
- Sending bzip2 data to an unrelated decompressor can cause format errors.
- Using gzip alone on a directory does not produce the same multientry ZIP container.
Explanation
Correct Answer
D:Using gzip alone on a directory does not produce the same multientry ZIP container. Avoid the failure by following this action: Use `zip -r files.zip folder/` to create the archive and `unzip files.zip` to extract.
Incorrect Answers
A:That risk is associated with Exit code on script completion; it is less directly tied to the task.
B:Missing compression leaves an uncompressed tar despite a .gz-looking filename. That risk is associated with tar gzip combined compression; it is less directly tied to the task. The omitted ZIP archives and unzip safeguard instead risks: using gzip alone on a directory does not produce the same multientry ZIP container.
C:Sending bzip2 data to an unrelated decompressor can cause format errors. That risk is associated with bzip2 compressed streams; it is less directly tied to the task. The omitted ZIP archives and unzip safeguard instead risks: using gzip alone on a directory does not produce the same multientry ZIP container.
Question 652
A trainee sees entries such as `alex:x:1001:1001:...` and asks what the file contains. If the team ignores the correct /etc/passwd public account metadata approach, which problem is the MOST relevant direct risk?
- Treating a login-history command as a list of all installed users gives incorrect scope.
- Treating the `x` placeholder as the user's plaintext password misreads the file.
- Guessing permissions from displayed usernames alone can miss group membership.
- Misreading a group bit as an owner bit can lead to wrong access decisions.
Explanation
Correct Answer
B:Treating the `x` placeholder as the user's plaintext password misreads the file. Avoid the failure by following this action: Read `/etc/passwd` for account names, UIDs, GIDs, home directories and shells.
Incorrect Answers
A:That risk is associated with who w and last login activity; it is less directly tied to the task.
C:Guessing permissions from displayed usernames alone can miss group membership. That risk is associated with id UID and group identity; it is less directly tied to the task. The omitted /etc/passwd public account metadata safeguard instead risks: treating the `x` placeholder as the user's plaintext password misreads the file.
D:That risk is associated with ls -l permission string interpretation; it is less directly tied to the task. The omitted /etc/passwd public account metadata safeguard instead risks: treating the `x` placeholder as the user's plaintext password misreads the file.
Question 653
A script needs to save the output of `date` to a variable for later use. If the team ignores the correct Command substitution in scripts approach, which problem is the MOST relevant direct risk?
- Writing a command name as a string does not execute it.
- Compression is not automatically enabled by every tar archive creation.
- Confusing direct `./script.sh` execution with `bash script.sh` changes permission requirements.
- An unquoted expansion may split the path into two command arguments.
Explanation
Correct Answer
A:Writing a command name as a string does not execute it. Avoid the failure by following this action: Use command substitution such as `stamp=$(date)` and quote the result when needed.
Incorrect Answers
B:Compression is not automatically enabled by every tar archive creation. That risk is associated with Creating a tar archive; it is less directly tied to the task. The omitted Command substitution in scripts safeguard instead risks: writing a command name as a string does not execute it.
C:Confusing direct `./script.sh` execution with `bash script.sh` changes permission requirements. That risk is associated with Script invocation via bash; it is less directly tied to the task. The omitted Command substitution in scripts safeguard instead risks: writing a command name as a string does not execute it.
D:An unquoted expansion may split the path into two command arguments. That risk is associated with Quoting script argument expansion; it is less directly tied to the task. The omitted Command substitution in scripts safeguard instead risks: writing a command name as a string does not execute it.
Question 654
A team needs a shared Unix group for collaborating on project files. If the team ignores the correct groupadd new group approach, which problem is the MOST relevant direct risk?
- Creating a similarly named directory does not create group membership or identity.
- Creating a user does not necessarily provision a usable password login by itself.
- Assuming a user account exists because a home directory was manually created is unsafe.
- Assuming all temp files persist indefinitely can lose work.
Explanation
Correct Answer
A:Creating a similarly named directory does not create group membership or identity. Avoid the failure by following this action: Run `groupadd groupname` with appropriate privileges.
Incorrect Answers
B:Creating a user does not necessarily provision a usable password login by itself. That risk is associated with passwd setting account password; it is less directly tied to the task. The omitted groupadd new group safeguard instead risks: creating a similarly named directory does not create group membership or identity.
C:Assuming a user account exists because a home directory was manually created is unsafe. That risk is associated with useradd new local account; it is less directly tied to the task. The omitted groupadd new group safeguard instead risks: creating a similarly named directory does not create group membership or identity.
D:Assuming all temp files persist indefinitely can lose work. That risk is associated with /tmp and /var/tmp retention; it is less directly tied to the task. The omitted groupadd new group safeguard instead risks: creating a similarly named directory does not create group membership or identity.
Question 655
A background command is still running and an operator wants its process identifier. If the team ignores the correct ps process listing approach, which problem is the MOST relevant direct risk?
- Writing arbitrary data to a block device may overwrite actual storage.
- Mistaking runtime logs for boot images can cause administration errors.
- Reading disk capacity cannot identify all running processes.
- Keeping an end-of-life release can expose known defects without standard patches.
Explanation
Correct Answer
C:Reading disk capacity cannot identify all running processes. Avoid the failure by following this action: Run `ps` with suitable options for the relevant process set.
Incorrect Answers
A:Writing arbitrary data to a block device may overwrite actual storage. That risk is associated with /dev device nodes; it is less directly tied to the task. The omitted ps process listing safeguard instead risks: reading disk capacity cannot identify all running processes.
B:Mistaking runtime logs for boot images can cause administration errors. That risk is associated with /boot kernel startup files; it is less directly tied to the task. The omitted ps process listing safeguard instead risks: reading disk capacity cannot identify all running processes.
D:Keeping an end-of-life release can expose known defects without standard patches. That risk is associated with Distribution life cycle versus installed version; it is less directly tied to the task. The omitted ps process listing safeguard instead risks: reading disk capacity cannot identify all running processes.
Question 656
A student notices terminal and disk device nodes under `/dev`. If the team ignores the correct /dev device nodes approach, which problem is the MOST relevant direct risk?
- Writing arbitrary data to a block device may overwrite actual storage.
- Treating procfs entries as permanent backups can give misleading results.
- Replacing storage alone does not necessarily remedy insufficient working memory.
- Reading disk capacity cannot identify all running processes.
Explanation
Correct Answer
A:Writing arbitrary data to a block device may overwrite actual storage. Avoid the failure by following this action: Recognize `/dev` as the directory containing device nodes and related special files.
Incorrect Answers
B:Treating procfs entries as permanent backups can give misleading results. That risk is associated with /proc virtual process information; it is less directly tied to the task. The omitted /dev device nodes safeguard instead risks: writing arbitrary data to a block device may overwrite actual storage.
C:Replacing storage alone does not necessarily remedy insufficient working memory. That risk is associated with CPU and RAM responsibilities; it is less directly tied to the task. The omitted /dev device nodes safeguard instead risks: writing arbitrary data to a block device may overwrite actual storage.
D:Reading disk capacity cannot identify all running processes. That risk is associated with ps process listing; it is less directly tied to the task. The omitted /dev device nodes safeguard instead risks: writing arbitrary data to a block device may overwrite actual storage.
Question 657
A user edits a small shell script in the terminal using nano. If the team ignores the correct nano editor save and quit approach, which problem is the MOST relevant direct risk?
- A readable but non-executable script may require explicit interpreter invocation.
- Using a quoted literal glob as the loop source prevents normal pathname expansion.
- Using gzip alone on a directory does not produce the same multientry ZIP container.
- A viewer-only command does not save file modifications.
Explanation
Correct Answer
D:A viewer-only command does not save file modifications. Avoid the failure by following this action: Open the file with `nano filename`, edit, save and exit using nano's documented key shortcuts.
Incorrect Answers
A:A readable but non-executable script may require explicit interpreter invocation. That risk is associated with Script execute permission; it is less directly tied to the task. The omitted nano editor save and quit safeguard instead risks: a viewer-only command does not save file modifications.
B:Using a quoted literal glob as the loop source prevents normal pathname expansion. That risk is associated with Loop over matching filenames; it is less directly tied to the task. The omitted nano editor save and quit safeguard instead risks: a viewer-only command does not save file modifications.
C:Using gzip alone on a directory does not produce the same multientry ZIP container. That risk is associated with ZIP archives and unzip; it is less directly tied to the task. The omitted nano editor save and quit safeguard instead risks: a viewer-only command does not save file modifications.
Question 658
A school wants a dependable Linux desktop for scheduled exams rather than experimental releases. If the team ignores the correct Stable versus beta distribution releases approach, which problem is the MOST relevant direct risk?
- Replacing all shell automation with manually repeated clicks can be error-prone.
- Assuming every installed component has identical license terms gives incorrect compliance decisions.
- Using a beta build as a mission-critical default can expose unstable behavior.
- Reading only web-server logs can miss hardware detection errors.
Explanation
Correct Answer
C:Using a beta build as a mission-critical default can expose unstable behavior. Avoid the failure by following this action: Prefer a supported stable release for production and reserve beta builds for testing.
Incorrect Answers
A:Replacing all shell automation with manually repeated clicks can be error-prone. That risk is associated with GUI and command-line tradeoffs; it is less directly tied to the task. The omitted Stable versus beta distribution releases safeguard instead risks: using a beta build as a mission-critical default can expose unstable behavior.
B:That risk is associated with Linux and proprietary OS licensing models; it is less directly tied to the task. The omitted Stable versus beta distribution releases safeguard instead risks: using a beta build as a mission-critical default can expose unstable behavior.
D:Reading only web-server logs can miss hardware detection errors. That risk is associated with dmesg kernel messages; it is less directly tied to the task. The omitted Stable versus beta distribution releases safeguard instead risks: using a beta build as a mission-critical default can expose unstable behavior.
Question 659
A Linux administrator needs to find system-wide text configuration files. If the team ignores the correct /etc configuration files approach, which problem is the MOST relevant direct risk?
- Editing data in `/dev` does not replace system configuration files.
- Replacing all shell automation with manually repeated clicks can be error-prone.
- The wrong filesystem directory may hide important diagnostics.
- Mistaking sysfs for a persistent user-data directory can corrupt an investigation.
Explanation
Correct Answer
A:Editing data in `/dev` does not replace system configuration files. Avoid the failure by following this action: Inspect `/etc` and the service's documented configuration path.
Incorrect Answers
B:Replacing all shell automation with manually repeated clicks can be error-prone. That risk is associated with GUI and command-line tradeoffs; it is less directly tied to the task. The omitted /etc configuration files safeguard instead risks: editing data in `/dev` does not replace system configuration files.
C:The wrong filesystem directory may hide important diagnostics. That risk is associated with /var/log system messages; it is less directly tied to the task. The omitted /etc configuration files safeguard instead risks: editing data in `/dev` does not replace system configuration files.
D:Mistaking sysfs for a persistent user-data directory can corrupt an investigation. That risk is associated with /sys device and kernel interfaces; it is less directly tied to the task. The omitted /etc configuration files safeguard instead risks: editing data in `/dev` does not replace system configuration files.
Question 660
A small web application needs persistent relational tables and SQL queries. If the team ignores the correct MariaDB and MySQL data stores approach, which problem is the MOST relevant direct risk?
- Confusing a web server with an email client will not offer the desired desktop inbox.
- Treating the Android UI as a standard Linux desktop misstates application compatibility.
- Choosing an HTTP server alone does not provide relational tables.
- Selecting a document viewer does not provide the required image-editing tools.
Explanation
Correct Answer
C:Choosing an HTTP server alone does not provide relational tables. Avoid the failure by following this action: Install MariaDB or MySQL and create the required schema and user permissions.
Incorrect Answers
A:Confusing a web server with an email client will not offer the desired desktop inbox. That risk is associated with Thunderbird email client; it is less directly tied to the task. The omitted MariaDB and MySQL data stores safeguard instead risks: choosing an HTTP server alone does not provide relational tables.
B:Treating the Android UI as a standard Linux desktop misstates application compatibility. That risk is associated with Android Linux kernel relationship; it is less directly tied to the task. The omitted MariaDB and MySQL data stores safeguard instead risks: choosing an HTTP server alone does not provide relational tables.
D:Selecting a document viewer does not provide the required image-editing tools. That risk is associated with GIMP raster image editing; it is less directly tied to the task. The omitted MariaDB and MySQL data stores safeguard instead risks: choosing an HTTP server alone does not provide relational tables.