LPI 010-160 Practice Test 63
Question 620
A beginner needs a simple test of ICMP reachability to a known host. If the team ignores the correct ping reachability testing approach, which problem is the MOST relevant direct risk?
- Missing a default route can prevent off-subnet connectivity.
- Firewalls may block ICMP even when application services work.
- Checking only IP assignment does not prove an application is listening.
- Mistaking sysfs for a persistent user-data directory can corrupt an investigation.
Explanation
Correct Answer
B:Firewalls may block ICMP even when application services work. Avoid the failure by following this action: Run `ping` against the intended IP or hostname where ICMP is allowed.
Incorrect Answers
A:Missing a default route can prevent off-subnet connectivity. That risk is associated with ip route show default gateway; it is less directly tied to the task. The omitted ping reachability testing safeguard instead risks: firewalls may block ICMP even when application services work.
C:Checking only IP assignment does not prove an application is listening. That risk is associated with ss listening sockets; it is less directly tied to the task. The omitted ping reachability testing safeguard instead risks: firewalls may block ICMP even when application services work.
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 ping reachability testing safeguard instead risks: firewalls may block ICMP even when application services work.
Question 621
A user is authorized to open a shell as a different local account. If the team ignores the correct su switching user identity approach, which problem is the MOST relevant direct risk?
- Guessing permissions from displayed usernames alone can miss group membership.
- Misunderstanding the mask may expose newly created data.
- Treating the `x` placeholder as the user's plaintext password misreads the file.
- Assuming su without authorization grants elevated access can lead to authentication failure.
Explanation
Correct Answer
D:Assuming su without authorization grants elevated access can lead to authentication failure. Avoid the failure by following this action: Use `su - targetuser` where authorized and provide authentication as required.
Incorrect Answers
A: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 su switching user identity safeguard instead risks: assuming su without authorization grants elevated access can lead to authentication failure.
B:Misunderstanding the mask may expose newly created data. That risk is associated with umask default permission reduction; it is less directly tied to the task. The omitted su switching user identity safeguard instead risks: assuming su without authorization grants elevated access can lead to authentication failure.
C:Treating the `x` placeholder as the user's plaintext password misreads the file. That risk is associated with /etc/passwd public account metadata; it is less directly tied to the task. The omitted su switching user identity safeguard instead risks: assuming su without authorization grants elevated access can lead to authentication failure.
Question 622
A student needs to inspect a file's owner, group, size and permissions. If the team ignores the correct ls -l file metadata approach, which problem is the MOST relevant direct risk?
- Noninteractive deletion can remove the wrong file without prompting.
- Missing dotfiles from a default listing does not imply they were deleted.
- Confusing `pwd` with `cd` can move the shell rather than reporting its location.
- Choosing a recursive option does not alone guarantee long-format columns.
Explanation
Correct Answer
D:Choosing a recursive option does not alone guarantee long-format columns. Avoid the failure by following this action: Run `ls -l` on the requested path.
Incorrect Answers
A:Noninteractive deletion can remove the wrong file without prompting. That risk is associated with rm interactive deletion; it is less directly tied to the task. The omitted ls -l file metadata safeguard instead risks: choosing a recursive option does not alone guarantee long-format columns.
B:Missing dotfiles from a default listing does not imply they were deleted. That risk is associated with Hidden dotfiles and ls -a; it is less directly tied to the task. The omitted ls -l file metadata safeguard instead risks: choosing a recursive option does not alone guarantee long-format columns.
C:Confusing `pwd` with `cd` can move the shell rather than reporting its location. That risk is associated with pwd current directory; it is less directly tied to the task. The omitted ls -l file metadata safeguard instead risks: choosing a recursive option does not alone guarantee long-format columns.
Question 623
A security auditor must explain why ordinary users cannot view stored password hashes. If the team ignores the correct /etc/shadow protected credentials approach, which problem is the MOST relevant direct risk?
- Making shadow data world-readable exposes password hashes for offline attack.
- Misreading a group bit as an owner bit can lead to wrong access decisions.
- Lack of sudo permission is not fixed by adding a shell alias alone.
- Treating a login-history command as a list of all installed users gives incorrect scope.
Explanation
Correct Answer
A:Making shadow data world-readable exposes password hashes for offline attack. Avoid the failure by following this action: Recognize `/etc/shadow` as a protected repository for password hashes and password-aging data.
Incorrect Answers
B:Misreading a group bit as an owner bit can lead to wrong access decisions. That risk is associated with ls -l permission string interpretation; it is less directly tied to the task. The omitted /etc/shadow protected credentials safeguard instead risks: making shadow data world-readable exposes password hashes for offline attack.
C:Lack of sudo permission is not fixed by adding a shell alias alone. That risk is associated with sudo authorized privilege elevation; it is less directly tied to the task. The omitted /etc/shadow protected credentials safeguard instead risks: making shadow data world-readable exposes password hashes for offline attack.
D:Treating a login-history command as a list of all installed users gives incorrect scope. That risk is associated with who w and last login activity; it is less directly tied to the task. The omitted /etc/shadow protected credentials safeguard instead risks: making shadow data world-readable exposes password hashes for offline attack.
Question 624
An administrator needs to compress a large text export with the xz format. If the team ignores the correct xz compression tools approach, which problem is the MOST relevant direct risk?
- Writing a command name as a string does not execute it.
- Treating unrelated archive extensions as equivalent may fail decoding.
- Treating gzip alone as a directory archiver is incorrect.
- Sending bzip2 data to an unrelated decompressor can cause format errors.
Explanation
Correct Answer
B:Treating unrelated archive extensions as equivalent may fail decoding. Avoid the failure by following this action: Use `xz` for compression and `unxz` or `xz -d` for decompression.
Incorrect Answers
A:Writing a command name as a string does not execute it. That risk is associated with Command substitution in scripts; it is less directly tied to the task. The omitted xz compression tools safeguard instead risks: treating unrelated archive extensions as equivalent may fail decoding.
C:Treating gzip alone as a directory archiver is incorrect. That risk is associated with gzip compression and gunzip; it is less directly tied to the task. The omitted xz compression tools safeguard instead risks: treating unrelated archive extensions as equivalent may fail decoding.
D: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 xz compression tools safeguard instead risks: treating unrelated archive extensions as equivalent may fail decoding.
Question 625
A writer wants to rename `draft.md` to `final.md` without retaining both names. If the team ignores the correct mv rename and relocation approach, which problem is the MOST relevant direct risk?
- Creating a directory instead of a file changes the expected object type.
- Copying only one file will not preserve child directories.
- Using `cp` leaves the original behind when a move was required.
- Using a log directory as the only documentation source can miss package instructions.
Explanation
Correct Answer
C:Using `cp` leaves the original behind when a move was required. Avoid the failure by following this action: Use `mv` with the original and destination paths.
Incorrect Answers
A:Creating a directory instead of a file changes the expected object type. That risk is associated with touch empty files and timestamps; it is less directly tied to the task. The omitted mv rename and relocation safeguard instead risks: using `cp` leaves the original behind when a move was required.
B:Copying only one file will not preserve child directories. That risk is associated with cp -r directory trees; it is less directly tied to the task. The omitted mv rename and relocation safeguard instead risks: using `cp` leaves the original behind when a move was required.
D: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 mv rename and relocation safeguard instead risks: using `cp` leaves the original behind when a move was required.
Question 626
Newly created files should not be accessible to all local users by default. If the team ignores the correct umask default permission reduction approach, which problem is the MOST relevant direct risk?
- Choosing 644 would allow other users to read the report.
- Making shadow data world-readable exposes password hashes for offline attack.
- Assuming file write permission is sufficient for deletion leads to mistaken access analysis.
- Misunderstanding the mask may expose newly created data.
Explanation
Correct Answer
D:Misunderstanding the mask may expose newly created data. Avoid the failure by following this action: Configure a suitable `umask` to clear unwanted default permissions.
Incorrect Answers
A:Choosing 644 would allow other users to read the report. That risk is associated with chmod octal mode 640; it is less directly tied to the task. The omitted umask default permission reduction safeguard instead risks: misunderstanding the mask may expose newly created data.
B:Making shadow data world-readable exposes password hashes for offline attack. That risk is associated with /etc/shadow protected credentials; it is less directly tied to the task. The omitted umask default permission reduction safeguard instead risks: misunderstanding the mask may expose newly created data.
C:Assuming file write permission is sufficient for deletion leads to mistaken access analysis. That risk is associated with Directory write and delete rights; it is less directly tied to the task. The omitted umask default permission reduction safeguard instead risks: misunderstanding the mask may expose newly created data.
Question 627
A project directory should become a compressed `.tar.gz` backup. If the team ignores the correct tar gzip combined compression approach, which problem is the MOST relevant direct risk?
- Missing compression leaves an uncompressed tar despite a .gz-looking filename.
- Using gzip alone on a directory does not produce the same multientry ZIP container.
- Returning success after a failed critical command can mislead later automation.
- Treating gzip alone as a directory archiver is incorrect.
Explanation
Correct Answer
A:Missing compression leaves an uncompressed tar despite a .gz-looking filename. Avoid the failure by following this action: Run `tar -czf project.tar.gz project/` to create gzip-compressed tar.
Incorrect Answers
B: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 tar gzip combined compression safeguard instead risks: missing compression leaves an uncompressed tar despite a .gz-looking filename.
C:Returning success after a failed critical command can mislead later automation. That risk is associated with Exit code on script completion; it is less directly tied to the task. The omitted tar gzip combined compression safeguard instead risks: missing compression leaves an uncompressed tar despite a .gz-looking filename.
D:Treating gzip alone as a directory archiver is incorrect. That risk is associated with gzip compression and gunzip; it is less directly tied to the task. The omitted tar gzip combined compression safeguard instead risks: missing compression leaves an uncompressed tar despite a .gz-looking filename.
Question 628
An automation runner checks a script's result and should stop after a fatal error. If the team ignores the correct Exit code on script completion approach, which problem is the MOST relevant direct risk?
- Treating unrelated archive extensions as equivalent may fail decoding.
- Confusing direct `./script.sh` execution with `bash script.sh` changes permission requirements.
- An unquoted expansion may split the path into two command arguments.
- Returning success after a failed critical command can mislead later automation.
Explanation
Correct Answer
D:Returning success after a failed critical command can mislead later automation. Avoid the failure by following this action: Use `exit 0` for successful completion and a nonzero exit code for a failure.
Incorrect Answers
A:Treating unrelated archive extensions as equivalent may fail decoding. That risk is associated with xz compression tools; it is less directly tied to the task. The omitted Exit code on script completion safeguard instead risks: returning success after a failed critical command can mislead later automation.
B: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 Exit code on script completion safeguard instead risks: returning success after a failed critical command can mislead later automation.
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 Exit code on script completion safeguard instead risks: returning success after a failed critical command can mislead later automation.
Question 629
A lab chooses openSUSE for a Linux workstation and needs an appropriate software-management approach. If the team ignores the correct SUSE and openSUSE distributions approach, which problem is the MOST relevant direct risk?
- A generic desktop image for the wrong processor architecture may not boot.
- Treating the Android UI as a standard Linux desktop misstates application compatibility.
- Treating openSUSE and SUSE Enterprise as identical support contracts creates lifecycle mistakes.
- Typing a shell command into a browser search field does not execute it locally.
Explanation
Correct Answer
C:Treating openSUSE and SUSE Enterprise as identical support contracts creates lifecycle mistakes. Avoid the failure by following this action: Recognize openSUSE and SUSE as related Linux distributions with their supported RPM-based package tooling.
Incorrect Answers
A:A generic desktop image for the wrong processor architecture may not boot. That risk is associated with Raspberry Pi Linux deployment; it is less directly tied to the task. The omitted SUSE and openSUSE distributions safeguard instead risks: treating openSUSE and SUSE Enterprise as identical support contracts creates lifecycle mistakes.
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 SUSE and openSUSE distributions safeguard instead risks: treating openSUSE and SUSE Enterprise as identical support contracts creates lifecycle mistakes.
D:That risk is associated with Graphical desktop versus command line; it is less directly tied to the task. The omitted SUSE and openSUSE distributions safeguard instead risks: treating openSUSE and SUSE Enterprise as identical support contracts creates lifecycle mistakes.
Question 630
A student wants to see all `.txt` files using filename pattern expansion. If the team ignores the correct Globbing versus literal pattern approach, which problem is the MOST relevant direct risk?
- Listing `/var/log` is not equivalent to the user's current history list.
- Passing the wrong quoted form can make a command use a literal asterisk as a pathname.
- Assuming undocumented options exist can produce invalid command invocations.
- Checking the status after additional commands can inspect the wrong operation.
Explanation
Correct Answer
B:Passing the wrong quoted form can make a command use a literal asterisk as a pathname. Avoid the failure by following this action: Use `*.txt` unquoted for matching filenames and quote it when literal text is intended.
Incorrect Answers
A:That risk is associated with Shell history recall; it is less directly tied to the task.
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 Globbing versus literal pattern safeguard instead risks: passing the wrong quoted form can make a command use a literal asterisk as a pathname.
D:That risk is associated with Exit status from previous command; it is less directly tied to the task.