McAfee Secure

LPI 010-160 Bundle

Exam Code: 010-160

Exam Name Linux Essentials Certificate Exam, version 1.6

Certification Provider: LPI

Corresponding Certification: Linux Essentials

LPI 010-160 Bundle $44.99

100% LPI 010-160 Guaranteed Success With Testking Training Materials

Get Real 010-160 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    010-160 Questions & Answers

    80 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual 010-160 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • 010-160 Video Course

    010-160 Training Course

    78 Video Lectures

    010-160 Video Course is developed by LPI Professionals to help you pass the 010-160 exam.

    Description

    This course will improve your knowledge and skills required to pass Linux Essentials Certificate Exam, version 1.6 exam.
  • Study Guide

    010-160 Study Guide

    364 PDF Pages

    Developed by industry experts, this 364-page guide spells out in painstaking detail all of the information you need to ace 010-160 exam.

Linux Essentials Certificate Exam, version 1.6 (010-160) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    80 Questions

    $124.99
  • 010-160 Video Course

    Training Course

    78 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    364 PDF Pages

    $29.99

LPI 010-160 Practice Test 51

Question 500

A Linux user needs to resolve this problem: A shared Linux workstation is used by several students and one proposes performing all routine tasks under the root account. What measurable result should the technician look for?

  1. Routine document edits succeed as a standard user while restricted system files remain protected.
  2. The approved command completes and the following ordinary shell continues under the user's normal identity.
  3. The username and UID appear in /etc/passwd but direct shadow access by an ordinary user is denied.
  4. id shows the intended effective user in the switched session and restores the prior identity after exit.

Explanation

Correct Answer

A:

Routine document edits succeed as a standard user while restricted system files remain protected. This is specific evidence for the stated requirement. The explanation is: The root account bypasses many ordinary permission protections, increasing consequences of mistakes. The required action is: Use a separate normal user account for everyday work and elevate only specific approved commands when necessary.

Incorrect Answers

B:

That observation would verify a different mechanism: Sudo can run a specified command with elevated effective privileges under local policy while retaining a normal user workflow. It would not establish whether the present failure was corrected, because the root account bypasses many ordinary permission protections, increasing consequences of mistakes. Test “Routine document edits succeed as a standard user while restricted system files remain protected” instead.

C:

“The username and UID appear in /etc/passwd but direct shadow access by an ordinary user is denied” tests the technical condition: Password hashes are commonly separated from generally readable account metadata for access protection. The current control has another acceptance boundary: The root account bypasses many ordinary permission protections, increasing consequences of mistakes. Its direct evidence is “Routine document edits succeed as a standard user while restricted system files remain protected”.

D:

This test can succeed without resolving the cause described here. It addresses: Su starts a shell or command under another user account when authentication and policy allow it. The relevant causal dependency is: The root account bypasses many ordinary permission protections, increasing consequences of mistakes. The required validation is “Routine document edits succeed as a standard user while restricted system files remain protected”.

Question 501

A helpdesk colleague describes this Linux behavior: A shared Linux workstation is used by several students and one proposes performing all routine tasks under the root account. Which ongoing practice reduces recurrence of this issue?

  1. Document service-account purposes before editing local account databases.
  2. Review permitted sudo commands and audit privileged operations.
  3. Teach least privilege and avoid long-lived administrative sessions for normal tasks.
  4. Verify identity and group membership before changing directory permissions.

Explanation

Correct Answer

C:

Teach least privilege and avoid long-lived administrative sessions for normal tasks. This practice reduces recurrence of the same problem. Technical reason: The root account bypasses many ordinary permission protections, increasing consequences of mistakes. A controlled repeat test should show: Routine document edits succeed as a standard user while restricted system files remain protected.

Incorrect Answers

A:

This safeguard maintains a different technical control: Document service-account purposes before editing local account databases. The recurring risk here is governed by: Teach least privilege and avoid long-lived administrative sessions for normal tasks. The relevant review is “Teach least privilege and avoid long-lived administrative sessions for normal tasks”.

B:

“Review permitted sudo commands and audit privileged operations” is a sensible check for: Review permitted sudo commands and audit privileged operations. It is not the prevention measure for the current dependency: Teach least privilege and avoid long-lived administrative sessions for normal tasks. The closer guardrail is “Teach least privilege and avoid long-lived administrative sessions for normal tasks”.

D:

That review tracks a separate failure mechanism: Verify identity and group membership before changing directory permissions. The question requires sustained control over: Teach least privilege and avoid long-lived administrative sessions for normal tasks. The corresponding safeguard is “Teach least privilege and avoid long-lived administrative sessions for normal tasks”.

Question 502

While using Linux in a small organization, the following occurs: A student finds account names in /etc/passwd and assumes every user's password hash is stored there in readable form. Which specific action BEST resolves the stated problem?

  1. Use a separate normal user account for everyday work and elevate only specific approved commands when necessary.
  2. Recognize system and service accounts separately from ordinary login accounts before taking action.
  3. Use sudo for the one authorized administrative command rather than an unrestricted long-lived root session.
  4. Inspect account information through approved tools and recognize /etc/shadow as the protected password-hash database on typical systems.

Explanation

Correct Answer

D:

Inspect account information through approved tools and recognize /etc/shadow as the protected password-hash database on typical systems. This directly addresses the reported situation. Why it works: Password hashes are commonly separated from generally readable account metadata for access protection. Acceptance evidence: The username and UID appear in /etc/passwd but direct shadow access by an ordinary user is denied.

Incorrect Answers

A:

The proposed action focuses on a control governed by: Use a separate normal user account for everyday work and elevate only specific approved commands when necessary. In this question the binding condition is: Inspect account information through approved tools and recognize /etc/shadow as the protected password-hash database on typical systems. Applying “Inspect account information through approved tools and recognize /etc/shadow as the protected password-hash database on typical systems” addresses that specific cause instead.

B:

“Recognize system and service accounts separately from ordinary login accounts before taking action” acts on a neighboring technical dependency: Recognize system and service accounts separately from ordinary login accounts before taking action. It does not resolve the stated condition, whose causal mechanism is: Inspect account information through approved tools and recognize /etc/shadow as the protected password-hash database on typical systems. The required action is “Inspect account information through approved tools and recognize /etc/shadow as the protected password-hash database on typical systems”.

C:

This option would change the part of the system described by: Use sudo for the one authorized administrative command rather than an unrestricted long-lived root session. The reported behavior instead arises because inspect account information through approved tools and recognize /etc/shadow as the protected password-hash database on typical systems. The direct remediation is “Inspect account information through approved tools and recognize /etc/shadow as the protected password-hash database on typical systems”.

Question 503

A user working at a Linux terminal reports: A student finds account names in /etc/passwd and assumes every user's password hash is stored there in readable form. Which statement most accurately describes the cause?

  1. Unix-like access decisions use numeric user and group identities, not just friendly display names.
  2. Login history is recorded separately from a snapshot of processes currently running.
  3. System accounts can own files or run services without being intended for interactive login.
  4. Password hashes are commonly separated from generally readable account metadata for access protection.

Explanation

Correct Answer

D:

Password hashes are commonly separated from generally readable account metadata for access protection. This explains the stated Linux behavior. The corresponding safe action is: Inspect account information through approved tools and recognize /etc/shadow as the protected password-hash database on typical systems. Confirm it with: The username and UID appear in /etc/passwd but direct shadow access by an ordinary user is denied.

Incorrect Answers

A:

The alternative mechanism is: Unix-like access decisions use numeric user and group identities, not just friendly display names. The present evidence instead rests on: Password hashes are commonly separated from generally readable account metadata for access protection.

B:

The offered principle concerns: Login history is recorded separately from a snapshot of processes currently running. That is not what the current scenario establishes. Its controlling mechanism is: Password hashes are commonly separated from generally readable account metadata for access protection.

C:

System accounts can own files or run services without being intended for interactive login. That principle governs the offered alternative, but the facts in this question are explained by: Password hashes are commonly separated from generally readable account metadata for access protection. The two technical dependencies must be distinguished.

Question 504

During an introductory open-source workshop, the task is: A student finds account names in /etc/passwd and assumes every user's password hash is stored there in readable form. Which finding would validate the selected approach?

  1. id shows the intended effective user in the switched session and restores the prior identity after exit.
  2. The username and UID appear in /etc/passwd but direct shadow access by an ordinary user is denied.
  3. A known prior login appears in the available history even after that session terminates.
  4. A test login appears in who and disappears after it logs out while group membership remains unchanged.

Explanation

Correct Answer

B:

The username and UID appear in /etc/passwd but direct shadow access by an ordinary user is denied. This is specific evidence for the stated requirement. The explanation is: Password hashes are commonly separated from generally readable account metadata for access protection. The required action is: Inspect account information through approved tools and recognize /etc/shadow as the protected password-hash database on typical systems.

Incorrect Answers

A:

The alternative measures an outcome associated with: Su starts a shell or command under another user account when authentication and policy allow it. It does not verify the stated failure. Here password hashes are commonly separated from generally readable account metadata for access protection. Confirm “The username and UID appear in /etc/passwd but direct shadow access by an ordinary user is denied”.

C:

“A known prior login appears in the available history even after that session terminates” tests the technical condition: Login history is recorded separately from a snapshot of processes currently running. The current control has another acceptance boundary: Password hashes are commonly separated from generally readable account metadata for access protection. Its direct evidence is “The username and UID appear in /etc/passwd but direct shadow access by an ordinary user is denied”.

D:

This test can succeed without resolving the cause described here. It addresses: Session commands report logged-in terminals and users; group databases describe membership independently of activity. The relevant causal dependency is: Password hashes are commonly separated from generally readable account metadata for access protection. The required validation is “The username and UID appear in /etc/passwd but direct shadow access by an ordinary user is denied”.

Question 505

A new Linux operator is assigned this task: A student finds account names in /etc/passwd and assumes every user's password hash is stored there in readable form. What should an instructor recommend for subsequent exercises?

  1. Document service-account purposes before editing local account databases.
  2. Teach least privilege and avoid long-lived administrative sessions for normal tasks.
  3. Review permitted sudo commands and audit privileged operations.
  4. Never copy or disclose password hashes when troubleshooting account metadata.

Explanation

Correct Answer

D:

Never copy or disclose password hashes when troubleshooting account metadata. This practice reduces recurrence of the same problem. Technical reason: Password hashes are commonly separated from generally readable account metadata for access protection. A controlled repeat test should show: The username and UID appear in /etc/passwd but direct shadow access by an ordinary user is denied.

Incorrect Answers

A:

Document service-account purposes before editing local account databases. That explains why “Document service-account purposes before editing local account databases” is useful for its own dependency, but the present failure follows a different constraint: Never copy or disclose password hashes when troubleshooting account metadata. The targeted correction is “Never copy or disclose password hashes when troubleshooting account metadata”.

B:

The proposed action focuses on a control governed by: Teach least privilege and avoid long-lived administrative sessions for normal tasks. In this question the binding condition is: Never copy or disclose password hashes when troubleshooting account metadata. Applying “Never copy or disclose password hashes when troubleshooting account metadata” addresses that specific cause instead.

C:

“Review permitted sudo commands and audit privileged operations” acts on a neighboring technical dependency: Review permitted sudo commands and audit privileged operations. It does not resolve the stated condition, whose causal mechanism is: Never copy or disclose password hashes when troubleshooting account metadata. The required action is “Never copy or disclose password hashes when troubleshooting account metadata”.

Question 506

A Linux user needs to resolve this problem: A support technician wants to know who is currently logged in, but reads a static group file and reports all group members as active sessions. Which command or choice meets the stated need?

  1. Use a separate normal user account for everyday work and elevate only specific approved commands when necessary.
  2. Use su appropriately to switch user identity, and distinguish it from running one command through sudo.
  3. Use who or w to inspect current sessions rather than relying on /etc/group.
  4. Use last to review available login records, recognizing retention and logging limitations.

Explanation

Correct Answer

C:

Use who or w to inspect current sessions rather than relying on /etc/group. This directly addresses the reported situation. Why it works: Session commands report logged-in terminals and users; group databases describe membership independently of activity. Acceptance evidence: A test login appears in who and disappears after it logs out while group membership remains unchanged.

Incorrect Answers

A:

The proposed action focuses on a control governed by: Use a separate normal user account for everyday work and elevate only specific approved commands when necessary. In this question the binding condition is: Use who or w to inspect current sessions rather than relying on /etc/group. Applying “Use who or w to inspect current sessions rather than relying on /etc/group” addresses that specific cause instead.

B:

“Use su appropriately to switch user identity, and distinguish it from running one command through sudo” acts on a neighboring technical dependency: Use su appropriately to switch user identity, and distinguish it from running one command through sudo. It does not resolve the stated condition, whose causal mechanism is: Use who or w to inspect current sessions rather than relying on /etc/group. The required action is “Use who or w to inspect current sessions rather than relying on /etc/group”.

D:

Use last to review available login records, recognizing retention and logging limitations. That explains why “Use last to review available login records, recognizing retention and logging limitations” is useful for its own dependency, but the present failure follows a different constraint: Use who or w to inspect current sessions rather than relying on /etc/group. The targeted correction is “Use who or w to inspect current sessions rather than relying on /etc/group”.

Question 507

A helpdesk colleague describes this Linux behavior: A support technician wants to know who is currently logged in, but reads a static group file and reports all group members as active sessions. Why does the recommended action work?

  1. System accounts can own files or run services without being intended for interactive login.
  2. Unix-like access decisions use numeric user and group identities, not just friendly display names.
  3. Session commands report logged-in terminals and users; group databases describe membership independently of activity.
  4. Password hashes are commonly separated from generally readable account metadata for access protection.

Explanation

Correct Answer

C:

Session commands report logged-in terminals and users; group databases describe membership independently of activity. This explains the stated Linux behavior. The corresponding safe action is: Use who or w to inspect current sessions rather than relying on /etc/group. Confirm it with: A test login appears in who and disappears after it logs out while group membership remains unchanged.

Incorrect Answers

A:

The alternative mechanism is: System accounts can own files or run services without being intended for interactive login. The present evidence instead rests on: Session commands report logged-in terminals and users; group databases describe membership independently of activity.

B:

The offered principle concerns: Unix-like access decisions use numeric user and group identities, not just friendly display names. That is not what the current scenario establishes. Its controlling mechanism is: Session commands report logged-in terminals and users; group databases describe membership independently of activity.

D:

The alternate statement is relevant when password hashes are commonly separated from generally readable account metadata for access protection. Here the root condition follows: Session commands report logged-in terminals and users; group databases describe membership independently of activity. It is not the same causal explanation.

Question 508

During a beginner Linux practical, the following issue occurs: A support technician wants to know who is currently logged in, but reads a static group file and reports all group members as active sessions. Which observation would BEST verify that the problem was resolved?

  1. The daemon's configured process UID matches its service account even though no interactive session is expected.
  2. A test login appears in who and disappears after it logs out while group membership remains unchanged.
  3. The username and UID appear in /etc/passwd but direct shadow access by an ordinary user is denied.
  4. Routine document edits succeed as a standard user while restricted system files remain protected.

Explanation

Correct Answer

B:

A test login appears in who and disappears after it logs out while group membership remains unchanged. This is specific evidence for the stated requirement. The explanation is: Session commands report logged-in terminals and users; group databases describe membership independently of activity. The required action is: Use who or w to inspect current sessions rather than relying on /etc/group.

Incorrect Answers

A:

The alternative measures an outcome associated with: System accounts can own files or run services without being intended for interactive login. It does not verify the stated failure. Here session commands report logged-in terminals and users; group databases describe membership independently of activity. Confirm “A test login appears in who and disappears after it logs out while group membership remains unchanged”.

C:

“The username and UID appear in /etc/passwd but direct shadow access by an ordinary user is denied” tests the technical condition: Password hashes are commonly separated from generally readable account metadata for access protection. The current control has another acceptance boundary: Session commands report logged-in terminals and users; group databases describe membership independently of activity. Its direct evidence is “A test login appears in who and disappears after it logs out while group membership remains unchanged”.

D:

This test can succeed without resolving the cause described here. It addresses: The root account bypasses many ordinary permission protections, increasing consequences of mistakes. The relevant causal dependency is: Session commands report logged-in terminals and users; group databases describe membership independently of activity. The required validation is “A test login appears in who and disappears after it logs out while group membership remains unchanged”.

Question 509

A technician working on a classroom Linux system finds: A support technician wants to know who is currently logged in, but reads a static group file and reports all group members as active sessions. What preventive habit belongs in the runbook?

  1. Maintain appropriate authentication log retention and time synchronization.
  2. Separate current-session monitoring from account-directory inventory.
  3. Document service-account purposes before editing local account databases.
  4. Review permitted sudo commands and audit privileged operations.

Explanation

Correct Answer

B:

Separate current-session monitoring from account-directory inventory. This practice reduces recurrence of the same problem. Technical reason: Session commands report logged-in terminals and users; group databases describe membership independently of activity. A controlled repeat test should show: A test login appears in who and disappears after it logs out while group membership remains unchanged.

Incorrect Answers

A:

This safeguard maintains a different technical control: Maintain appropriate authentication log retention and time synchronization. The recurring risk here is governed by: Separate current-session monitoring from account-directory inventory. The relevant review is “Separate current-session monitoring from account-directory inventory”.

C:

The alternate safeguard protects a separate dependency: Document service-account purposes before editing local account databases. For this failure the continuing exposure is: Separate current-session monitoring from account-directory inventory. Maintain “Separate current-session monitoring from account-directory inventory” instead.

D:

That review tracks a separate failure mechanism: Review permitted sudo commands and audit privileged operations. The question requires sustained control over: Separate current-session monitoring from account-directory inventory. The corresponding safeguard is “Separate current-session monitoring from account-directory inventory”.

Question 510

A user working at a Linux terminal reports: A security reviewer wants historical evidence of a previous interactive login and a junior technician checks only a current-process list. What should the learner do to satisfy the requirement?

  1. Inspect account information through approved tools and recognize /etc/shadow as the protected password-hash database on typical systems.
  2. Use last to review available login records, recognizing retention and logging limitations.
  3. Use a separate normal user account for everyday work and elevate only specific approved commands when necessary.
  4. Use sudo for the one authorized administrative command rather than an unrestricted long-lived root session.

Explanation

Correct Answer

B:

Use last to review available login records, recognizing retention and logging limitations. This directly addresses the reported situation. Why it works: Login history is recorded separately from a snapshot of processes currently running. Acceptance evidence: A known prior login appears in the available history even after that session terminates.

Incorrect Answers

A:

The proposed action focuses on a control governed by: Inspect account information through approved tools and recognize /etc/shadow as the protected password-hash database on typical systems. In this question the binding condition is: Use last to review available login records, recognizing retention and logging limitations. Applying “Use last to review available login records, recognizing retention and logging limitations” addresses that specific cause instead.

C:

This option would change the part of the system described by: Use a separate normal user account for everyday work and elevate only specific approved commands when necessary. The reported behavior instead arises because use last to review available login records, recognizing retention and logging limitations. The direct remediation is “Use last to review available login records, recognizing retention and logging limitations”.

D:

Use sudo for the one authorized administrative command rather than an unrestricted long-lived root session. That explains why “Use sudo for the one authorized administrative command rather than an unrestricted long-lived root session” is useful for its own dependency, but the present failure follows a different constraint: Use last to review available login records, recognizing retention and logging limitations. The targeted correction is “Use last to review available login records, recognizing retention and logging limitations”.