LPI 102-500 Practice Test 61
Question 600
A team maintaining a Linux host reports: A file server has an SGID binary in a writable application tree but auditors only inspect ordinary Unix read permissions. Which THREE elements together give the appropriate corrective action, direct diagnostic evidence and observable acceptance result? Select THREE answers.
- Combine local `ss` or `lsof` socket ownership checks with authorized nmap testing to identify exposed services and unnecessary listeners.
- Run carefully scoped `find` checks for -perm -4000 and -perm -2000, review file ownership, ACLs, package provenance and intended use.
- Only approved privileged executables retain special mode bits and exceptions have documented justification and monitoring.
- Assume executable files cannot gain extra privilege from mode bits and that a standard ls without permission details is sufficient for a SUID audit.
- Inspect `w`, `who`, `last`, `ulimit -a`, controlled process execution and any persistent limits configuration.
- Inventory files with SUID or SGID bits using a suitable `find` permission predicate, investigate ownership and remove unnecessary privilege through approved change control.
Explanation
Correct Answers
B:Most direct verification evidence: Run carefully scoped `find` checks for -perm -4000 and -perm -2000, review file ownership, ACLs, package provenance and intended use. Linux principle: SUID and SGID execution bits can change effective identity or group during program execution, so unexpected privileged binaries enlarge security risk.
C:Observable acceptance criterion: Only approved privileged executables retain special mode bits and exceptions have documented justification and monitoring. Linux principle: SUID and SGID execution bits can change effective identity or group during program execution, so unexpected privileged binaries enlarge security risk.
F:Recommended administrative action: Inventory files with SUID or SGID bits using a suitable `find` permission predicate, investigate ownership and remove unnecessary privilege through approved change control. Linux principle: SUID and SGID execution bits can change effective identity or group during program execution, so unexpected privileged binaries enlarge security risk.
Incorrect Answers
A:This alternative addresses Discovering exposed sockets and services, not the specific issue of Auditing privileged SUID and SGID executables: Combine local `ss` or `lsof` socket ownership checks with authorized nmap testing to identify exposed services and unnecessary listeners. Linux principle: SUID and SGID execution bits can change effective identity or group during program execution, so unexpected privileged binaries enlarge security risk. Appropriate response: Inventory files with SUID or SGID bits using a suitable `find` permission predicate, investigate ownership and remove unnecessary privilege through approved change control. Root-cause evidence: Run carefully scoped `find` checks for -perm -4000 and -perm -2000, review file ownership, ACLs, package provenance and intended use. Independent acceptance: Only approved privileged executables retain special mode bits and exceptions have documented justification and monitoring.
D:This shortcut is unsafe for the present Linux issue: Assume executable files cannot gain extra privilege from mode bits and that a standard ls without permission details is sufficient for a SUID audit. SUID and SGID execution bits can change effective identity or group during program execution, so unexpected privileged binaries enlarge security risk.
E:This alternative addresses Login history, active sessions and process limits, not the specific issue of Auditing privileged SUID and SGID executables: Inspect `w`, `who`, `last`, `ulimit -a`, controlled process execution and any persistent limits configuration.
Question 601
While verifying a Linux change request, an engineer finds: A service technician receives unrestricted root sudo when the job requires restarting exactly one system service. Which administrative step is the MOST appropriate way to resolve this issue? Select ONE best answer.
- Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation.
- Inventory files with SUID or SGID bits using a suitable `find` permission predicate, investigate ownership and remove unnecessary privilege through approved change control.
- Combine local `ss` or `lsof` socket ownership checks with authorized nmap testing to identify exposed services and unnecessary listeners.
- Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity.
Explanation
Correct Answer
D:Recommended administrative action: Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity.
Incorrect Answers
A:That option would use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation, but it addresses a different concern. Sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
B:This alternative addresses Auditing privileged SUID and SGID executables, not the specific issue of Sudoers least privilege and safe editing: Inventory files with SUID or SGID bits using a suitable `find` permission predicate, investigate ownership and remove unnecessary privilege through approved change control. Linux principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks. Appropriate response: Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity. Root-cause evidence: Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account. Independent acceptance: The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
C:This alternative addresses Discovering exposed sockets and services, not the specific issue of Sudoers least privilege and safe editing: Combine local `ss` or `lsof` socket ownership checks with authorized nmap testing to identify exposed services and unnecessary listeners. Linux principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks. Appropriate response: Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity. Root-cause evidence: Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account. Independent acceptance: The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
Question 602
A Linux administrator investigates the following system incident: A service technician receives unrestricted root sudo when the job requires restarting exactly one system service. Which Linux behavior or technical principle BEST explains why the issue occurs? Select ONE best answer.
- A service can bind locally or on external interfaces regardless of the operator's assumptions; local listener inventory and external reachability provide complementary evidence.
- hosts.allow and hosts.deny are legacy libwrap mechanisms that affect only applications using them; modern services may ignore these files entirely.
- Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation.
- sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
Explanation
Correct Answer
D:Relevant Linux operating principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
Incorrect Answers
A:This alternative addresses Discovering exposed sockets and services, not the specific issue of Sudoers least privilege and safe editing: A service can bind locally or on external interfaces regardless of the operator's assumptions; local listener inventory and external reachability provide complementary evidence. Linux principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks. Appropriate response: Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity. Root-cause evidence: Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account. Independent acceptance: The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
B:This alternative addresses TCP wrappers legacy access control and modern alternatives, not the specific issue of Sudoers least privilege and safe editing: hosts.allow and hosts.deny are legacy libwrap mechanisms that affect only applications using them; modern services may ignore these files entirely. Linux principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks. Appropriate response: Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity. Root-cause evidence: Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account. Independent acceptance: The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
C:That option would use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation, but it addresses a different concern. Independent acceptance: The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
Question 603
On a production Linux workstation or server, a technician observes: A service technician receives unrestricted root sudo when the job requires restarting exactly one system service. Which evidence or command result MOST directly tests the suspected root cause? Select ONE best answer.
- Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation.
- Run carefully scoped `find` checks for -perm -4000 and -perm -2000, review file ownership, ACLs, package provenance and intended use.
- Inspect `stat /etc/shadow`, attempt an unprivileged read, verify accounts through supported tools and review any unauthorized disclosure impact.
- Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account.
Explanation
Correct Answer
D:Most direct verification evidence: Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account.
Incorrect Answers
A:This shortcut is unsafe for the present Linux issue: Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation. It cannot establish a safe correction.
B:That option would run carefully scoped `find` checks for -perm -4000 and -perm -2000, review file ownership, ACLs, package provenance and intended use, but it addresses a different concern. Sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
C:That option would inspect `stat /etc/shadow`, attempt an unprivileged read, verify accounts through supported tools and review any unauthorized disclosure impact, but it addresses a different concern. Sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
Question 604
During an LPIC-1 practice lab, the operator encounters this condition: A service technician receives unrestricted root sudo when the job requires restarting exactly one system service. Which observed outcome BEST confirms a successful and properly scoped correction? Select ONE best answer.
- Clients recognize the correct unique server identity and unexpected key changes trigger investigation rather than silent acceptance.
- The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
- Ordinary users cannot read password hashes and the system still resolves account and login metadata correctly.
- Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation.
Explanation
Correct Answer
B:Observable acceptance criterion: The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
Incorrect Answers
A:This alternative addresses SSH server host keys and client trust decisions, not the specific issue of Sudoers least privilege and safe editing: Clients recognize the correct unique server identity and unexpected key changes trigger investigation rather than silent acceptance. Linux principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks. Appropriate response: Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity. Root-cause evidence: Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account. Independent acceptance: The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
C:This alternative addresses Shadow password file permissions and hash protection, not the specific issue of Sudoers least privilege and safe editing: Ordinary users cannot read password hashes and the system still resolves account and login metadata correctly. Linux principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks. Appropriate response: Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity. Root-cause evidence: Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account. Independent acceptance: The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
D:This shortcut is unsafe for the present Linux issue: Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation. sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
Question 605
A helpdesk escalation describes this Linux behavior: A service technician receives unrestricted root sudo when the job requires restarting exactly one system service. Which misleading assumption MOST directly contributes to this failure and should be rejected? Select ONE best answer.
- Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation.
- Assume whoami lists all active users on the host and that setting ulimit in one shell automatically applies to every existing login session.
- Assume adding a GPG signature automatically encrypts the file and that anyone possessing a public key can decrypt its ciphertext.
- Copy the private SSH key to authorized_keys on the server and make both key files world-readable to reduce login errors.
Explanation
Correct Answer
A:Reject this specific misconception: Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation. It incorrectly assumes behavior that conflicts with the observed Linux conditions.
Incorrect Answers
B:That option would assume whoami lists all active users on the host and that setting ulimit in one shell automatically applies to every existing login session, but it addresses a different concern. Sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
C:That option would assume adding a GPG signature automatically encrypts the file and that anyone possessing a public key can decrypt its ciphertext, but it addresses a different concern. Sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
D:This alternative addresses SSH user keys, authorized_keys and agent handling, not the specific issue of Sudoers least privilege and safe editing: Copy the private SSH key to authorized_keys on the server and make both key files world-readable to reduce login errors. Linux principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks. Appropriate response: Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity. Root-cause evidence: Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account. Independent acceptance: The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
Question 606
An operations handoff identifies this problem: An operator edits /etc/sudoers using an ordinary text editor and introduces a syntax error that prevents administrators from using sudo. Which administrative step is the MOST appropriate way to resolve this issue? Select ONE best answer.
- Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation.
- Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity.
- Use `who`, `w` and `last` to distinguish active from historical logins and apply appropriate shell or PAM resource limits with ulimit and policy.
- Identify the listening service and any associated systemd .socket activation unit, then disable or mask unnecessary network entry points according to policy.
Explanation
Correct Answer
B:Recommended administrative action: Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity.
Incorrect Answers
A:This shortcut is unsafe for the present Linux issue: Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation. It cannot establish a safe correction.
C:That option would use `who`, `w` and `last` to distinguish active from historical logins and apply appropriate shell or PAM resource limits with ulimit and policy, but it addresses a different concern. Sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
D:That option would identify the listening service and any associated systemd .socket activation unit, then disable or mask unnecessary network entry points according to policy, but it addresses a different concern. Sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
Question 607
A team maintaining a Linux host reports: An operator edits /etc/sudoers using an ordinary text editor and introduces a syntax error that prevents administrators from using sudo. Which Linux behavior or technical principle BEST explains why the issue occurs? Select ONE best answer.
- hosts.allow and hosts.deny are legacy libwrap mechanisms that affect only applications using them; modern services may ignore these files entirely.
- Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation.
- sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
- /etc/shadow exists to separate sensitive hashed password and aging data from the broadly readable identity fields of /etc/passwd.
Explanation
Correct Answer
C:Relevant Linux operating principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
Incorrect Answers
A:This alternative addresses TCP wrappers legacy access control and modern alternatives, not the specific issue of Sudoers least privilege and safe editing: hosts.allow and hosts.deny are legacy libwrap mechanisms that affect only applications using them; modern services may ignore these files entirely. Linux principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks. Appropriate response: Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity. Root-cause evidence: Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account. Independent acceptance: The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
B:This shortcut is unsafe for the present Linux issue: Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation. It cannot establish a safe correction. Linux principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
D:This alternative addresses Shadow password file permissions and hash protection, not the specific issue of Sudoers least privilege and safe editing: /etc/shadow exists to separate sensitive hashed password and aging data from the broadly readable identity fields of /etc/passwd. Linux principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks. Appropriate response: Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity. Root-cause evidence: Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account. Independent acceptance: The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
Question 608
While verifying a Linux change request, an engineer finds: An operator edits /etc/sudoers using an ordinary text editor and introduces a syntax error that prevents administrators from using sudo. Which evidence or command result MOST directly tests the suspected root cause? Select ONE best answer.
- Compare server host key fingerprint to an approved inventory, inspect /etc/ssh/ssh_host_* files and examine the user's known_hosts entry.
- Run carefully scoped `find` checks for -perm -4000 and -perm -2000, review file ownership, ACLs, package provenance and intended use.
- Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation.
- Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account.
Explanation
Correct Answer
D:Most direct verification evidence: Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account.
Incorrect Answers
A:That option would compare server host key fingerprint to an approved inventory, inspect /etc/ssh/ssh_host_* files and examine the user's known_hosts entry, but it addresses a different concern. Sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
B:This alternative addresses Auditing privileged SUID and SGID executables, not the specific issue of Sudoers least privilege and safe editing: Run carefully scoped `find` checks for -perm -4000 and -perm -2000, review file ownership, ACLs, package provenance and intended use.
C:This shortcut is unsafe for the present Linux issue: Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation. It cannot establish a safe correction. Linux principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks. Appropriate response: Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity. Root-cause evidence: Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account. Independent acceptance: The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
Question 609
A Linux administrator investigates the following system incident: An operator edits /etc/sudoers using an ordinary text editor and introduces a syntax error that prevents administrators from using sudo. Which observed outcome BEST confirms a successful and properly scoped correction? Select ONE best answer.
- The authorized client reaches only the intended remote service or graphical display without exposing the server's internal listening port publicly.
- The unwanted port no longer accepts connections after reboot while approved system services remain available.
- The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
- Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation.
Explanation
Correct Answer
C:Observable acceptance criterion: The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
Incorrect Answers
A:This alternative addresses SSH port forwarding and X11 tunnel purpose, not the specific issue of Sudoers least privilege and safe editing: The authorized client reaches only the intended remote service or graphical display without exposing the server's internal listening port publicly. Linux principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks. Appropriate response: Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity. Root-cause evidence: Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account. Independent acceptance: The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
B:This alternative addresses Disabling unnecessary systemd and socket-activated services, not the specific issue of Sudoers least privilege and safe editing: The unwanted port no longer accepts connections after reboot while approved system services remain available. Linux principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks. Appropriate response: Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity. Root-cause evidence: Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account. Independent acceptance: The user can perform only the authorized command and sudo policy remains syntactically valid with denied unrelated operations.
D:This shortcut is unsafe for the present Linux issue: Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation. sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
Question 610
On a production Linux workstation or server, a technician observes: An operator edits /etc/sudoers using an ordinary text editor and introduces a syntax error that prevents administrators from using sudo. Which TWO complementary steps provide the best corrective action and its most direct diagnostic verification? Select TWO answers.
- Inspect `w`, `who`, `last`, `ulimit -a`, controlled process execution and any persistent limits configuration.
- Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation.
- Identify the listening service and any associated systemd .socket activation unit, then disable or mask unnecessary network entry points according to policy.
- Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account.
- Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity.
Explanation
Correct Answers
D:Most direct verification evidence: Run `visudo -c`, inspect `/etc/sudoers` and `/etc/sudoers.d`, and use a controlled `sudo -l` test as the affected account. Linux principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
E:Recommended administrative action: Grant narrowly scoped sudo privileges using visudo or a validated sudoers.d fragment, then test as the intended identity. Linux principle: sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
Incorrect Answers
A:That option would inspect `w`, `who`, `last`, `ulimit -a`, controlled process execution and any persistent limits configuration, but it addresses a different concern. Sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
B:This shortcut is unsafe for the present Linux issue: Use `ALL=(ALL) NOPASSWD: ALL` for every support user and edit sudoers blindly with no syntax validation. sudo applies policy to which user may execute particular commands as another identity; unrestricted root privileges and unvalidated configuration edits are avoidable risks.
C:This alternative addresses Disabling unnecessary systemd and socket-activated services, not the specific issue of Sudoers least privilege and safe editing: Identify the listening service and any associated systemd .socket activation unit, then disable or mask unnecessary network entry points according to policy.
