LPI 102-500 Exam Dumps, Practice Test Questions

100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!

LPI 102-500 Premium Bundle
$79.97
$59.98

102-500 Premium Bundle

  • Premium File: 120 Questions & Answers. Last update: Nov 18, 2026
  • Training Course: 126 Video Lectures
  • Study Guide: 962 Pages
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

102-500 Premium Bundle

LPI 102-500 Premium Bundle
  • Premium File: 120 Questions & Answers. Last update: Nov 18, 2026
  • Training Course: 126 Video Lectures
  • Study Guide: 962 Pages
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
$79.97
$59.98

LPI 102-500 Practice Test 29

Question 280

A standard user receives permission denied from crontab even though the cron service is healthy. Select THREE measures that follow directly from the root cause and lifecycle risk.

  1. Run crontab -l as the test user and check the scheduler's access log.
  2. Manage cron permissions centrally rather than altering service credentials.
  3. Audit /etc/nsswitch.conf and NSS reachability before troubleshooting remote identities.
  4. Review the applicable allow/deny files and explicitly authorize the intended user under policy.
  5. Compare date output from the service and unchanged local-user shell.
  6. Set the service account shell to an approved nologin program and control other authentication paths.

Explanation

Correct Answers

A:

Run crontab -l as the test user and check the scheduler's access log. It verifies that the targeted action (Review the applicable allow/deny files and explicitly authorize the intended user under policy.) achieved its intended outcome.

B:

Manage cron permissions centrally rather than altering service credentials. This control detects or prevents the same mechanism before another incident.

D:

Review the applicable allow/deny files and explicitly authorize the intended user under policy. It corrects the mechanism identified in the scenario: Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.

Incorrect Answers

C:

This option assumes NSS can resolve users through sources other than the local passwd file. The reported symptoms instead call for: Review the applicable allow/deny files and explicitly authorize the intended user under policy.

E:

That choice responds to a timezone only for one process failure. In this incident, Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.

F:

That choice responds to a nonlogin service identity failure. In this incident, Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.

Question 281

A systemd timer shows next activation but the expected maintenance process never starts. Why does the reported configuration behave this way?

  1. A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.
  2. Password-aging fields alone do not enforce a hard account expiration date.
  3. usermod -G without -a replaces the entire supplementary group list.
  4. Password hash data should be protected in shadow rather than exposed with world-readable permissions.

Explanation

Correct Answer

A:

A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action. That cause connects the stated symptom to the corrective action: Correct the timer Unit target or provide the matching .service with an executable command.

Incorrect Answers

B:

That choice responds to a expire entire account on date failure. In this incident, A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.

C:

The test for supplementary group preservation would be: Run id username before and after the edit to verify both groups are present. The relevant acceptance check here is: Use systemctl list-timers and journalctl -u for the timer and service to verify activation.

D:

This option assumes Password hash data should be protected in shadow rather than exposed with world-readable permissions. The reported symptoms instead call for: Correct the timer Unit target or provide the matching .service with an executable command.

Question 282

A systemd timer shows next activation but the expected maintenance process never starts. Which remedial step follows from the observed mechanism?

  1. List locales with locale -a and generate/install the required locale through the distribution's mechanism.
  2. Correct the timer Unit target or provide the matching .service with an executable command.
  3. Convert from the known source encoding to UTF-8 using iconv with explicit -f and -t options.
  4. Use chage -M with the appropriate value and review minimum-age and warning settings.

Explanation

Correct Answer

B:

Correct the timer Unit target or provide the matching .service with an executable command. It corrects the mechanism identified in the scenario: A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.

Incorrect Answers

A:

List locales with locale -a and generate/install the required locale through the distribution's mechanism. could help with available locale not generated; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use systemctl list-timers and journalctl -u for the timer and service to verify activation.

C:

It would address character encoding conversion rather than the present problem. The appropriate correction here is: Correct the timer Unit target or provide the matching .service with an executable command.

D:

Use chage -M with the appropriate value and review minimum-age and warning settings. could help with password aging audit; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use systemctl list-timers and journalctl -u for the timer and service to verify activation.

Question 283

A systemd timer shows next activation but the expected maintenance process never starts. What diagnostic result would demonstrate the target behavior?

  1. Check stat permissions and run a controlled password authentication test.
  2. Inspect the locked password field and test that password authentication is denied.
  3. Use systemctl list-timers and journalctl -u for the timer and service to verify activation.
  4. Run locale and inspect LC_ALL plus category values before and after the change.

Explanation

Correct Answer

C:

Use systemctl list-timers and journalctl -u for the timer and service to verify activation. The test is evidence-based because the underlying failure was: A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.

Incorrect Answers

A:

The test for shadow file sensitivity would be: Check stat permissions and run a controlled password authentication test. The relevant acceptance check here is: Use systemctl list-timers and journalctl -u for the timer and service to verify activation.

B:

That choice responds to a lock password without destroying identity failure. In this incident, A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.

D:

Run locale and inspect LC_ALL plus category values before and after the change. belongs to a situation where LC_ALL overrides category-specific locale values and LANG fallback while it is set. Here the evidence supports a different requirement: Use systemctl list-timers and journalctl -u for the timer and service to verify activation.

Question 284

A systemd timer shows next activation but the expected maintenance process never starts. What operational safeguard addresses the root cause?

  1. Track skeleton revisions and plan explicit migrations for already provisioned homes.
  2. Deploy and test timer and service units as a linked pair.
  3. Require diffing the existing group list before any supplementary-group modification.
  4. Define category-specific locale requirements for programs exchanging numeric data.

Explanation

Correct Answer

B:

Deploy and test timer and service units as a linked pair. Sustained checks matter because A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.

Incorrect Answers

A:

This belongs to skeleton change is not retroactive, where The skeleton is copied at account home creation; it is not a live template for existing homes. The current issue instead is: A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.

C:

That choice responds to a supplementary group preservation failure. In this incident, A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.

D:

An all-category locale setting affects more than message translations, including numeric punctuation. That describes a different fault. Here, A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.

Question 285

A systemd timer shows next activation but the expected maintenance process never starts. Choose TWO case-specific steps: one that fixes the issue and one that proves the result.

  1. Use systemctl list-timers and journalctl -u for the timer and service to verify activation.
  2. Reserve LC_ALL overrides for narrow test commands and keep persistent locale policy explicit.
  3. Correct the timer Unit target or provide the matching .service with an executable command.
  4. Check locale output and an application-generated decimal value in the same process.
  5. Expire the account's current password with passwd -e or an equivalent chage setting.

Explanation

Correct Answers

A:

Use systemctl list-timers and journalctl -u for the timer and service to verify activation. This measures the specific result of applying: Correct the timer Unit target or provide the matching .service with an executable command.

C:

Correct the timer Unit target or provide the matching .service with an executable command. The change should be accepted only after this test: Use systemctl list-timers and journalctl -u for the timer and service to verify activation.

Incorrect Answers

B:

The test for lc_all overrides lang would be: Run locale and inspect LC_ALL plus category values before and after the change. The relevant acceptance check here is: Use systemctl list-timers and journalctl -u for the timer and service to verify activation.

D:

It would address locale category isolation rather than the present problem. The appropriate correction here is: Correct the timer Unit target or provide the matching .service with an executable command.

E:

This option assumes A normal password set does not always impose a mandatory first-login change. The reported symptoms instead call for: Correct the timer Unit target or provide the matching .service with an executable command.

Question 286

A daily systemd timer misses its scheduled time while a laptop is powered off and should run after the next boot. Which explanation most directly accounts for the failure in this environment?

  1. Deleting the account would also disrupt UID ownership records; locking the password is a narrower credential action.
  2. A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.
  3. The local-time database link is stale or references a zone file that is no longer valid.
  4. The password aging fields in the shadow database are not set to the approved maximum age.

Explanation

Correct Answer

B:

A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured. This is the explanation that justifies the specific remedy: Set Persistent=true for the OnCalendar timer when missed runs must be honored.

Incorrect Answers

A:

Deleting the account would also disrupt UID ownership records; locking the password is a narrower credential action. That describes a different fault. Here, A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.

C:

The local-time database link is stale or references a zone file that is no longer valid. belongs to a situation where The local-time database link is stale or references a zone file that is no longer valid. Here the evidence supports a different requirement: A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.

D:

The test for password aging audit would be: Run chage -l username to confirm maximum password age and future expiration schedule. The relevant acceptance check here is: Power down through one calendar boundary and confirm a catch-up activation after boot.

Question 287

A daily systemd timer misses its scheduled time while a laptop is powered off and should run after the next boot. What action should be planned as the next targeted correction?

  1. Use getent passwd username to query the host's configured name-service lookup chain.
  2. Set the correct system timezone using timedatectl set-timezone with the proper zone identifier.
  3. Set an account expiration with usermod -e or chage -E using the approved date.
  4. Set Persistent=true for the OnCalendar timer when missed runs must be honored.

Explanation

Correct Answer

D:

Set Persistent=true for the OnCalendar timer when missed runs must be honored. Unlike a broad workaround, it targets the observed cause: A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.

Incorrect Answers

A:

It would address look up ldap-mapped identity rather than the present problem. The appropriate correction here is: Set Persistent=true for the OnCalendar timer when missed runs must be honored.

B:

That choice responds to a system timezone persistent change failure. In this incident, A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.

C:

That choice responds to a expire entire account on date failure. In this incident, A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.

Question 288

A daily systemd timer misses its scheduled time while a laptop is powered off and should run after the next boot. What focused test would distinguish a real correction from a cosmetic change?

  1. Inspect the resolved /etc/localtime target and compare offset before and after.
  2. Power down through one calendar boundary and confirm a catch-up activation after boot.
  3. Compare id outputs and numeric ls -n owners on both hosts before granting access.
  4. Inspect getent passwd and attempt an interactive login in a controlled test.

Explanation

Correct Answer

B:

Power down through one calendar boundary and confirm a catch-up activation after boot. The test is evidence-based because the underlying failure was: A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.

Incorrect Answers

A:

It would address timezone database symlink rather than the present problem. The appropriate correction here is: Set Persistent=true for the OnCalendar timer when missed runs must be honored.

C:

Compare id outputs and numeric ls -n owners on both hosts before granting access. could help with uid collision after cloning; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Power down through one calendar boundary and confirm a catch-up activation after boot.

D:

An ordinary interactive login shell in /etc/passwd can permit shell access if credentials and policy allow. That describes a different fault. Here, A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.

Question 289

A daily systemd timer misses its scheduled time while a laptop is powered off and should run after the next boot. Which ongoing control would best reduce the chance of the issue returning?

  1. Choose character-versus-byte semantics explicitly in internationalized text tooling.
  2. Manage timezone selection declaratively instead of copying anonymous zone data.
  3. Document whether missed maintenance runs should be skipped, caught up or deduplicated.
  4. Reserve LC_ALL overrides for narrow test commands and keep persistent locale policy explicit.

Explanation

Correct Answer

C:

Document whether missed maintenance runs should be skipped, caught up or deduplicated. The underlying risk is A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.

Incorrect Answers

A:

Choose character-versus-byte semantics explicitly in internationalized text tooling. could help with utf-8 length versus byte length; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Power down through one calendar boundary and confirm a catch-up activation after boot.

B:

The test for timezone database symlink would be: Inspect the resolved /etc/localtime target and compare offset before and after. The relevant acceptance check here is: Power down through one calendar boundary and confirm a catch-up activation after boot.

D:

This belongs to lc_all overrides lang, where LC_ALL overrides category-specific locale values and LANG fallback while it is set. The current issue instead is: A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.

Question 290

A daily systemd timer misses its scheduled time while a laptop is powered off and should run after the next boot. Which THREE actions form a suitable remediation, verification and prevention plan? Select THREE.

  1. Document whether missed maintenance runs should be skipped, caught up or deduplicated.
  2. Record file encodings at interchange boundaries rather than guessing from appearance.
  3. Set Persistent=true for the OnCalendar timer when missed runs must be honored.
  4. Power down through one calendar boundary and confirm a catch-up activation after boot.
  5. List locales with locale -a and generate/install the required locale through the distribution's mechanism.
  6. Run chage -l username to confirm maximum password age and future expiration schedule.

Explanation

Correct Answers

A:

Document whether missed maintenance runs should be skipped, caught up or deduplicated. It preserves the corrective behavior established through: Set Persistent=true for the OnCalendar timer when missed runs must be honored.

C:

Set Persistent=true for the OnCalendar timer when missed runs must be honored. Unlike a broad workaround, it targets the observed cause: A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.

D:

Power down through one calendar boundary and confirm a catch-up activation after boot. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.

Incorrect Answers

B:

This option assumes The bytes use a different character encoding than the consumer expects. The reported symptoms instead call for: Set Persistent=true for the OnCalendar timer when missed runs must be honored.

E:

This belongs to available locale not generated, where The requested locale name may not be generated or installed locally. The current issue instead is: A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.

F:

Run chage -l username to confirm maximum password age and future expiration schedule. belongs to a situation where The password aging fields in the shadow database are not set to the approved maximum age. Here the evidence supports a different requirement: Power down through one calendar boundary and confirm a catch-up activation after boot.

LPI Level 1 (102-500) Practice Tests

UP

SPECIAL OFFER: GET 10% OFF

This is ONE TIME OFFER

ExamSnap Discount Offer
Enter Your Email Address to Receive Your 10% Off Discount Code

A confirmation link will be sent to this email address to verify your login. *We value your privacy. We will not rent or sell your email address.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your e-mail address below to get started with our interactive software demo of your free trial.

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.