LPI 010-160 Practice Test 69
Question 680
An application stores short-lived scratch files and needs a conventional temporary area. If the team ignores the correct /tmp and /var/tmp retention approach, which problem is the MOST relevant direct risk?
- A world-writable directory without a sticky bit permits unwanted cross-user deletion.
- Assuming all temp files persist indefinitely can lose work.
- Editing a directory listing is not equivalent to managing group databases.
- Repairing permissions alone cannot recover a nonexistent target file.
Explanation
Correct Answer
B:Assuming all temp files persist indefinitely can lose work. Avoid the failure by following this action: Use temporary paths according to the distribution's retention policy; `/tmp` is often cleared sooner than `/var/tmp`.
Incorrect Answers
A:A world-writable directory without a sticky bit permits unwanted cross-user deletion. That risk is associated with Sticky bit shared directories; it is less directly tied to the task. The omitted /tmp and /var/tmp retention safeguard instead risks: assuming all temp files persist indefinitely can lose work.
C:Editing a directory listing is not equivalent to managing group databases. That risk is associated with /etc/group account membership records; it is less directly tied to the task. The omitted /tmp and /var/tmp retention safeguard instead risks: assuming all temp files persist indefinitely can lose work.
D: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 /tmp and /var/tmp retention safeguard instead risks: assuming all temp files persist indefinitely can lose work.
Question 681
A newly installed executable cannot be called by its bare name although it exists in `/opt/tools/bin`. If the team ignores the correct PATH and command discovery approach, which problem is the MOST relevant direct risk?
- Printing the unexpanded identifier does not display its value.
- A command outside PATH may require a qualified path.
- Using a log directory as the only documentation source can miss package instructions.
- Checking the status after additional commands can inspect the wrong operation.
Explanation
Correct Answer
B:A command outside PATH may require a qualified path. Avoid the failure by following this action: Add the executable directory to `PATH` or invoke the executable by its explicit path.
Incorrect Answers
A:Printing the unexpanded identifier does not display its value. That risk is associated with echo and shell variables; it is less directly tied to the task. The omitted PATH and command discovery safeguard instead risks: a command outside PATH may require a qualified path.
C:Using a log directory as the only documentation source can miss package instructions. That risk is associated with /usr/share/doc documentation directory; it is less directly tied to the task. The omitted PATH and command discovery safeguard instead risks: a command outside PATH may require a qualified path.
D:Checking the status after additional commands can inspect the wrong operation. That risk is associated with Exit status from previous command; it is less directly tied to the task. The omitted PATH and command discovery safeguard instead risks: a command outside PATH may require a qualified path.
Question 682
A student compares an application that computes slowly with one that runs out of working memory. If the team ignores the correct CPU and RAM responsibilities approach, which problem is the MOST relevant direct risk?
- Looking only at resolver configuration cannot reveal all assigned interface addresses.
- Replacing storage alone does not necessarily remedy insufficient working memory.
- Underpowered hardware can cause instability despite healthy software.
- Installing an unrelated user application does not replace missing kernel-level device support.
Explanation
Correct Answer
B:Replacing storage alone does not necessarily remedy insufficient working memory. Avoid the failure by following this action: Diagnose CPU capacity for computation and RAM capacity for active working data.
Incorrect Answers
A:Looking only at resolver configuration cannot reveal all assigned interface addresses. That risk is associated with ip addr show interface addresses; it is less directly tied to the task. The omitted CPU and RAM responsibilities safeguard instead risks: replacing storage alone does not necessarily remedy insufficient working memory.
C:Underpowered hardware can cause instability despite healthy software. That risk is associated with Power supply for components; it is less directly tied to the task. The omitted CPU and RAM responsibilities safeguard instead risks: replacing storage alone does not necessarily remedy insufficient working memory.
D:Installing an unrelated user application does not replace missing kernel-level device support. That risk is associated with Hardware drivers and kernel; it is less directly tied to the task. The omitted CPU and RAM responsibilities safeguard instead risks: replacing storage alone does not necessarily remedy insufficient working memory.
Question 683
A school evaluates an open-source application for handling student documents. If the team ignores the correct Privacy-conscious software selection approach, which problem is the MOST relevant direct risk?
- A padlock alone does not prove an unfamiliar domain is trustworthy.
- Typing a shell command into a browser search field does not execute it locally.
- Confusing a web server with an email client will not offer the desired desktop inbox.
- Installing untrusted code without reviewing access can expose files.
Explanation
Correct Answer
D:Installing untrusted code without reviewing access can expose files. Avoid the failure by following this action: Review application permissions, provenance, update policy and data-sharing settings.
Incorrect Answers
A:A padlock alone does not prove an unfamiliar domain is trustworthy. That risk is associated with Browser HTTPS and site verification; it is less directly tied to the task. The omitted Privacy-conscious software selection safeguard instead risks: installing untrusted code without reviewing access can expose files.
B:Typing a shell command into a browser search field does not execute it locally. That risk is associated with Graphical desktop versus command line; it is less directly tied to the task. The omitted Privacy-conscious software selection safeguard instead risks: installing untrusted code without reviewing access can expose files.
C: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 Privacy-conscious software selection safeguard instead risks: installing untrusted code without reviewing access can expose files.
Question 684
A training folder named `Project Files` must be used as one pathname argument. If the team ignores the correct Escaping spaces in shell paths approach, which problem is the MOST relevant direct risk?
- A nonexported shell-only variable is not automatically inherited by child programs.
- Noninteractive deletion can remove the wrong file without prompting.
- Quoting incorrectly can change text into expanded values.
- An unquoted spaced path is split into separate words and may make the command act on the wrong target.
Explanation
Correct Answer
D:An unquoted spaced path is split into separate words and may make the command act on the wrong target. Avoid the failure by following this action: Quote the entire path or escape its spaces, for example `cd "Project Files"`.
Incorrect Answers
A:That risk is associated with Exported environment variables; it is less directly tied to the task.
B:That risk is associated with rm interactive deletion; it is less directly tied to the task.
C:That risk is associated with Single versus double shell quotes; it is less directly tied to the task.
Question 685
A user wants to return to their login home directory from `/tmp`. If the team ignores the correct Home directory shorthand approach, which problem is the MOST relevant direct risk?
- Relative paths depend on the shell's starting directory.
- Confusing home with `/` changes the destination.
- Passing the wrong quoted form can make a command use a literal asterisk as a pathname.
- Plain `ls` on the top directory omits many descendants.
Explanation
Correct Answer
B:Confusing home with `/` changes the destination. Avoid the failure by following this action: Use `cd ~` or bare `cd` to return to the current user's home.
Incorrect Answers
A:Relative paths depend on the shell's starting directory. That risk is associated with Absolute filesystem paths; it is less directly tied to the task. The omitted Home directory shorthand safeguard instead risks: confusing home with `/` changes the destination.
C:Passing the wrong quoted form can make a command use a literal asterisk as a pathname. That risk is associated with Globbing versus literal pattern; it is less directly tied to the task. The omitted Home directory shorthand safeguard instead risks: confusing home with `/` changes the destination.
D:Plain `ls` on the top directory omits many descendants. That risk is associated with Recursive directory listings; it is less directly tied to the task. The omitted Home directory shorthand safeguard instead risks: confusing home with `/` changes the destination.
Question 686
A script tracks a successful task count and must increment an integer. If the team ignores the correct Bash arithmetic expansion approach, which problem is the MOST relevant direct risk?
- Treating `+` as string concatenation can produce the wrong count.
- Confusing regex star with shell glob star changes the intended matching semantics.
- An unquoted expansion may split the path into two command arguments.
- Without a suitable interpreter or execution method, a script may not run as intended.
Explanation
Correct Answer
A:Treating `+` as string concatenation can produce the wrong count. Avoid the failure by following this action: Use arithmetic expansion such as `count=$((count + 1))`.
Incorrect Answers
B:Confusing regex star with shell glob star changes the intended matching semantics. That risk is associated with Regular-expression dot and repetition; it is less directly tied to the task. The omitted Bash arithmetic expansion safeguard instead risks: treating `+` as string concatenation can produce the wrong count.
C: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 Bash arithmetic expansion safeguard instead risks: treating `+` as string concatenation can produce the wrong count.
D:Without a suitable interpreter or execution method, a script may not run as intended. That risk is associated with Shebang shell interpreter; it is less directly tied to the task. The omitted Bash arithmetic expansion safeguard instead risks: treating `+` as string concatenation can produce the wrong count.
Question 687
A script should process every `.log` file in its current directory. If the team ignores the correct Loop over matching filenames approach, which problem is the MOST relevant direct risk?
- Using a quoted literal glob as the loop source prevents normal pathname expansion.
- Typing text in command mode can trigger actions rather than insert characters.
- Compression is not automatically enabled by every tar archive creation.
- Without a suitable interpreter or execution method, a script may not run as intended.
Explanation
Correct Answer
A:Using a quoted literal glob as the loop source prevents normal pathname expansion. Avoid the failure by following this action: Use `for file in *.log; do . "$file" .; done` with quoted expansion.
Incorrect Answers
B:That risk is associated with vi insert mode and write quit; it is less directly tied to the task.
C: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 Loop over matching filenames safeguard instead risks: using a quoted literal glob as the loop source prevents normal pathname expansion.
D:That risk is associated with Shebang shell interpreter; it is less directly tied to the task. The omitted Loop over matching filenames safeguard instead risks: using a quoted literal glob as the loop source prevents normal pathname expansion.
Question 688
A learner knows a desired task but not the command name and wants to search manual descriptions. If the team ignores the correct Keyword manual search approach, which problem is the MOST relevant direct risk?
- Using `.` instead would refer to the current directory, not the parent.
- Using a process monitor does not display the command's manual.
- Assuming undocumented options exist can produce invalid command invocations.
- Guessing random command names may miss the indexed help.
Explanation
Correct Answer
D:Guessing random command names may miss the indexed help. Avoid the failure by following this action: Use `man -k keyword` or the equivalent `apropos keyword` when available.
Incorrect Answers
A:Using `.` instead would refer to the current directory, not the parent. That risk is associated with cd parent directory; it is less directly tied to the task. The omitted Keyword manual search safeguard instead risks: guessing random command names may miss the indexed help.
B:Using a process monitor does not display the command's manual. That risk is associated with man pages and sections; it is less directly tied to the task. The omitted Keyword manual search safeguard instead risks: guessing random command names may miss the indexed help.
C:Assuming undocumented options exist can produce invalid command invocations. That risk is associated with Command --help output; it is less directly tied to the task. The omitted Keyword manual search safeguard instead risks: guessing random command names may miss the indexed help.
Question 689
A student compares Android phones with GNU/Linux desktop distributions. If the team ignores the correct Android Linux kernel relationship approach, which problem is the MOST relevant direct risk?
- Debian-only package tools do not implement the host's supported RPM repository workflow.
- Choosing an HTTP server alone does not provide relational tables.
- Choosing an unsupported short-lived release can stop routine security updates.
- Treating the Android UI as a standard Linux desktop misstates application compatibility.
Explanation
Correct Answer
D:Treating the Android UI as a standard Linux desktop misstates application compatibility. Avoid the failure by following this action: Explain that Android uses the Linux kernel with an Android-specific userspace and application framework.
Incorrect Answers
A:Debian-only package tools do not implement the host's supported RPM repository workflow. That risk is associated with Red Hat enterprise package family; it is less directly tied to the task. The omitted Android Linux kernel relationship safeguard instead risks: treating the Android UI as a standard Linux desktop misstates application compatibility.
B:Choosing an HTTP server alone does not provide relational tables. That risk is associated with MariaDB and MySQL data stores; it is less directly tied to the task. The omitted Android Linux kernel relationship safeguard instead risks: treating the Android UI as a standard Linux desktop misstates application compatibility.
C:Choosing an unsupported short-lived release can stop routine security updates. That risk is associated with Ubuntu long-term support releases; it is less directly tied to the task. The omitted Android Linux kernel relationship safeguard instead risks: treating the Android UI as a standard Linux desktop misstates application compatibility.
Question 690
A service starts but another machine cannot reach its expected TCP port. If the team ignores the correct ss listening sockets approach, which problem is the MOST relevant direct risk?
- Writing to the whole disk instead of a partition can destroy partition metadata.
- A local hosts entry does not update global public DNS for other computers.
- Checking only IP assignment does not prove an application is listening.
- Confusing name resolution with ICMP masks the failing layer.
Explanation
Correct Answer
C:Checking only IP assignment does not prove an application is listening. Avoid the failure by following this action: Run `ss -ltn` and inspect the expected port and bound address.
Incorrect Answers
A:Writing to the whole disk instead of a partition can destroy partition metadata. That risk is associated with Linux block devices and partitions; it is less directly tied to the task. The omitted ss listening sockets safeguard instead risks: checking only IP assignment does not prove an application is listening.
B:A local hosts entry does not update global public DNS for other computers. That risk is associated with /etc/hosts local name entries; it is less directly tied to the task. The omitted ss listening sockets safeguard instead risks: checking only IP assignment does not prove an application is listening.
D:Confusing name resolution with ICMP masks the failing layer. That risk is associated with host DNS name lookup; it is less directly tied to the task. The omitted ss listening sockets safeguard instead risks: checking only IP assignment does not prove an application is listening.