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 43

Question 420

An incident responder needs only error-severity or worse journal events, not informational service chatter. Select THREE measures that follow directly from the root cause and lifecycle risk.

  1. Create a valid ~/.forward file under the user's home with appropriate permissions and delivery policy.
  2. Record journal priority conventions in operational runbooks.
  3. Use package and service inspection plus one local delivery test.
  4. Use journalctl -p err to include error and more severe messages.
  5. Review alias graphs for cycles during mail-routing changes.
  6. Generate a controlled error log and confirm lower-priority messages are excluded.

Explanation

Correct Answers

B:

Record journal priority conventions in operational runbooks. The underlying risk is Without priority filtering the journal query mixes benign events with high-severity records.

D:

Use journalctl -p err to include error and more severe messages. Unlike a broad workaround, it targets the observed cause: Without priority filtering the journal query mixes benign events with high-severity records.

F:

Generate a controlled error log and confirm lower-priority messages are excluded. The test is evidence-based because the underlying failure was: Without priority filtering the journal query mixes benign events with high-severity records.

Incorrect Answers

A:

This belongs to forward mail for one user, where Global aliases are not required for a per-account redirect supported by ~/.forward. The current issue instead is: Without priority filtering the journal query mixes benign events with high-severity records.

C:

That choice responds to a mta configuration beyond exam scope failure. In this incident, Without priority filtering the journal query mixes benign events with high-severity records.

E:

The test for avoid alias loop would be: Send test mail to every alias and inspect headers/queue for a finite route. The relevant acceptance check here is: Generate a controlled error log and confirm lower-priority messages are excluded.

Question 421

A machine crashes during startup and is then successfully rebooted, obscuring which boot generated the failure. What underlying Linux behavior should the administrator identify first?

  1. journalctl defaults to the current boot unless another boot is selected.
  2. The hardware clock did not receive the corrected system time and retains an old value.
  3. DNS resolution failure prevents the NTP client from reaching a hostname-configured time source.
  4. Global aliases are not required for a per-account redirect supported by ~/.forward.

Explanation

Correct Answer

A:

journalctl defaults to the current boot unless another boot is selected. The observation is consistent with this mechanism; a targeted repair would be: Use journalctl -b -1 to examine the preceding boot, assuming its journal was retained.

Incorrect Answers

B:

This belongs to sync rtc from verified system clock, where The hardware clock did not receive the corrected system time and retains an old value. The current issue instead is: journalctl defaults to the current boot unless another boot is selected.

C:

This belongs to ntp pool name resolution, where DNS resolution failure prevents the NTP client from reaching a hostname-configured time source. The current issue instead is: journalctl defaults to the current boot unless another boot is selected.

D:

Global aliases are not required for a per-account redirect supported by ~/.forward. That describes a different fault. Here, journalctl defaults to the current boot unless another boot is selected.

Question 422

A machine crashes during startup and is then successfully rebooted, obscuring which boot generated the failure. What should the administrator do to correct this behavior?

  1. Run newaliases or the MTA's supported alias database rebuild after updating /etc/aliases.
  2. Use journalctl -b -1 to examine the preceding boot, assuming its journal was retained.
  3. Set the appropriate timezone rather than falsifying the synchronized UTC clock.
  4. Inspect CUPS queue acceptance status and enable acceptance using the supported administrative command.

Explanation

Correct Answer

B:

Use journalctl -b -1 to examine the preceding boot, assuming its journal was retained. This is appropriate because journalctl defaults to the current boot unless another boot is selected.

Incorrect Answers

A:

It would address local mail alias activation rather than the present problem. The appropriate correction here is: Use journalctl -b -1 to examine the preceding boot, assuming its journal was retained.

C:

This belongs to ntp clock versus timezone, where NTP synchronizes the system clock; the configured timezone controls the local-time rendering. The current issue instead is: journalctl defaults to the current boot unless another boot is selected.

D:

This belongs to cups accepts no new jobs, where The queue may be configured to reject incoming jobs independently of whether the device is enabled. The current issue instead is: journalctl defaults to the current boot unless another boot is selected.

Question 423

A machine crashes during startup and is then successfully rebooted, obscuring which boot generated the failure. How should the administrator verify the required behavior?

  1. Compare journalctl --list-boots with the selected boot's timestamps.
  2. Compare lpstat -d with the chosen explicit queue and verify the test document routing.
  3. Watch chronyc tracking offset before and after intervention and confirm stable synchronization.
  4. Inspect chronyc sources -v and chronyc tracking until a valid selected source appears.

Explanation

Correct Answer

A:

Compare journalctl --list-boots with the selected boot's timestamps. This measures the specific result of applying: Use journalctl -b -1 to examine the preceding boot, assuming its journal was retained.

Incorrect Answers

B:

This belongs to print to named destination, where Without an explicit destination, lpr typically uses the configured default printer selection. The current issue instead is: journalctl defaults to the current boot unless another boot is selected.

C:

This option assumes The time client is correcting a large offset gradually rather than stepping it under approved conditions. The reported symptoms instead call for: Use journalctl -b -1 to examine the preceding boot, assuming its journal was retained.

D:

That choice responds to a chrony not synchronized failure. In this incident, journalctl defaults to the current boot unless another boot is selected.

Question 424

A machine crashes during startup and is then successfully rebooted, obscuring which boot generated the failure. Which repeatable check would reduce recurrence?

  1. Keep sufficient persistent boot history for post-crash investigation.
  2. Document the RTC standard across dual-boot images to avoid repeated time offsets.
  3. Treat system-mail aliases as controlled data-flow configuration.
  4. Enforce a single supported time-discipline stack in host configuration.

Explanation

Correct Answer

A:

Keep sufficient persistent boot history for post-crash investigation. It prevents repetition of the condition: journalctl defaults to the current boot unless another boot is selected.

Incorrect Answers

B:

Document the RTC standard across dual-boot images to avoid repeated time offsets. could help with hardware clock stored in utc; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Compare journalctl --list-boots with the selected boot's timestamps.

C:

Treat system-mail aliases as controlled data-flow configuration. belongs to a situation where Local forwarding can disclose security and operational contents beyond the approved organizational boundary. Here the evidence supports a different requirement: Keep sufficient persistent boot history for post-crash investigation.

D:

Competing NTP clients can apply conflicting clock discipline and confusing status reports. That describes a different fault. Here, journalctl defaults to the current boot unless another boot is selected.

Question 425

A machine crashes during startup and is then successfully rebooted, obscuring which boot generated the failure. Which TWO measures belong together as the direct correction and a discriminating verification? Select TWO.

  1. Use journalctl -b -1 to examine the preceding boot, assuming its journal was retained.
  2. Check queue drain after enabling and verify the previously pending job prints.
  3. Configure multiple policy-approved NTP servers or a suitable pool and verify source selection behavior.
  4. Enforce a single supported time-discipline stack in host configuration.
  5. Compare journalctl --list-boots with the selected boot's timestamps.

Explanation

Correct Answers

A:

Use journalctl -b -1 to examine the preceding boot, assuming its journal was retained. This is appropriate because journalctl defaults to the current boot unless another boot is selected.

E:

Compare journalctl --list-boots with the selected boot's timestamps. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.

Incorrect Answers

B:

Check queue drain after enabling and verify the previously pending job prints. belongs to a situation where A queue can accept jobs without forwarding them to a disabled printer device. Here the evidence supports a different requirement: Compare journalctl --list-boots with the selected boot's timestamps.

C:

The test for chrony source trust and failover would be: Take the primary source offline in a test and inspect peer selection and offset stability. The relevant acceptance check here is: Compare journalctl --list-boots with the selected boot's timestamps.

D:

Competing NTP clients can apply conflicting clock discipline and confusing status reports. That describes a different fault. Here, journalctl defaults to the current boot unless another boot is selected.

Question 426

A heavily logged host is running out of disk space in the journal directory, and a technician wants to delete random active journal files. Which failure condition fits the evidence without assuming an unrelated fault?

  1. A plausible wall-clock value is not evidence of upstream synchronization or bounded clock offset.
  2. Manual deletion of active journal files can corrupt useful evidence or race with journald.
  3. The time client is correcting a large offset gradually rather than stepping it under approved conditions.
  4. An active MTA can hold messages in its queue when delivery is deferred or destination resolution fails.

Explanation

Correct Answer

B:

Manual deletion of active journal files can corrupt useful evidence or race with journald. A good follow-up is to test this explanation through: Measure journal disk usage before and after vacuuming and ensure recent events remain.

Incorrect Answers

A:

A plausible wall-clock value is not evidence of upstream synchronization or bounded clock offset. could help with date display cannot prove sync; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Measure journal disk usage before and after vacuuming and ensure recent events remain.

C:

That choice responds to a clock slewing on startup failure. In this incident, Manual deletion of active journal files can corrupt useful evidence or race with journald.

D:

This belongs to inspect pending mail delivery, where An active MTA can hold messages in its queue when delivery is deferred or destination resolution fails. The current issue instead is: Manual deletion of active journal files can corrupt useful evidence or race with journald.

Question 427

A heavily logged host is running out of disk space in the journal directory, and a technician wants to delete random active journal files. Which intervention addresses the specific problem with the least unrelated change?

  1. Repair DNS resolution and then allow or trigger an approved queue retry.
  2. Identify the job and remove its ID with lprm or a CUPS equivalent.
  3. Use supported journalctl vacuum-size or vacuum-time controls, with retention requirements considered.
  4. Establish a consistent hardware-clock convention, preferably RTC in UTC where supported, and set timedatectl policy.

Explanation

Correct Answer

C:

Use supported journalctl vacuum-size or vacuum-time controls, with retention requirements considered. It corrects the mechanism identified in the scenario: Manual deletion of active journal files can corrupt useful evidence or race with journald.

Incorrect Answers

A:

It would address mail queue after dns fault rather than the present problem. The appropriate correction here is: Use supported journalctl vacuum-size or vacuum-time controls, with retention requirements considered.

B:

The test for remove one queued print job would be: Use lpq or lpstat -o to verify that job disappeared while unrelated jobs remain. The relevant acceptance check here is: Measure journal disk usage before and after vacuuming and ensure recent events remain.

D:

It would address hardware clock stored in utc rather than the present problem. The appropriate correction here is: Use supported journalctl vacuum-size or vacuum-time controls, with retention requirements considered.

Question 428

A heavily logged host is running out of disk space in the journal directory, and a technician wants to delete random active journal files. What focused test would distinguish a real correction from a cosmetic change?

  1. Measure journal disk usage before and after vacuuming and ensure recent events remain.
  2. Print a known standard test page and examine CUPS logs for filter errors.
  3. Inspect running time services and confirm one controlling daemon reports stable synchronization.
  4. Compare hwclock -r with date -u after a clean shutdown and reboot.

Explanation

Correct Answer

A:

Measure journal disk usage before and after vacuuming and ensure recent events remain. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.

Incorrect Answers

B:

Print a known standard test page and examine CUPS logs for filter errors. belongs to a situation where A wrong PPD/driver or filter conversion can create an unsuitable printer data stream. Here the evidence supports a different requirement: Measure journal disk usage before and after vacuuming and ensure recent events remain.

C:

This belongs to ntp service conflict, where Competing NTP clients can apply conflicting clock discipline and confusing status reports. The current issue instead is: Manual deletion of active journal files can corrupt useful evidence or race with journald.

D:

This belongs to hardware clock stored in utc, where The systems interpret the hardware RTC using different UTC versus localtime assumptions. The current issue instead is: Manual deletion of active journal files can corrupt useful evidence or race with journald.

Question 429

A heavily logged host is running out of disk space in the journal directory, and a technician wants to delete random active journal files. Which ongoing control would best reduce the chance of the issue returning?

  1. Alert on synchronization state and drift independently of local display formatting.
  2. Set documented journald size and retention limits rather than emergency manual deletion.
  3. Monitor source reachability and measured offset, not just whether the daemon process is running.
  4. Include DNS dependencies when monitoring time synchronization.

Explanation

Correct Answer

B:

Set documented journald size and retention limits rather than emergency manual deletion. This control detects or prevents the same mechanism before another incident.

Incorrect Answers

A:

A plausible wall-clock value is not evidence of upstream synchronization or bounded clock offset. That describes a different fault. Here, Manual deletion of active journal files can corrupt useful evidence or race with journald.

C:

Monitor source reachability and measured offset, not just whether the daemon process is running. belongs to a situation where The time synchronization daemon lacks a usable upstream source or cannot reach it. Here the evidence supports a different requirement: Set documented journald size and retention limits rather than emergency manual deletion.

D:

It would address ntp pool name resolution rather than the present problem. The appropriate correction here is: Use supported journalctl vacuum-size or vacuum-time controls, with retention requirements considered.

Question 430

A heavily logged host is running out of disk space in the journal directory, and a technician wants to delete random active journal files. Which THREE case-specific steps cover immediate repair, test evidence and sustained control?

  1. Include resolver reachability in MTA monitoring and delivery smoke tests.
  2. Use supported journalctl vacuum-size or vacuum-time controls, with retention requirements considered.
  3. Repair DNS reachability or configure an approved resolvable/internal NTP source.
  4. Measure journal disk usage before and after vacuuming and ensure recent events remain.
  5. Set documented journald size and retention limits rather than emergency manual deletion.
  6. Submit one labeled test job and observe it transition through the queue.

Explanation

Correct Answers

B:

Use supported journalctl vacuum-size or vacuum-time controls, with retention requirements considered. It corrects the mechanism identified in the scenario: Manual deletion of active journal files can corrupt useful evidence or race with journald.

D:

Measure journal disk usage before and after vacuuming and ensure recent events remain. It verifies that the targeted action (Use supported journalctl vacuum-size or vacuum-time controls, with retention requirements considered.) achieved its intended outcome.

E:

Set documented journald size and retention limits rather than emergency manual deletion. It prevents repetition of the condition: Manual deletion of active journal files can corrupt useful evidence or race with journald.

Incorrect Answers

A:

This option assumes Destination lookup failure can defer mail regardless of MTA process health. The reported symptoms instead call for: Use supported journalctl vacuum-size or vacuum-time controls, with retention requirements considered.

C:

DNS resolution failure prevents the NTP client from reaching a hostname-configured time source. That describes a different fault. Here, Manual deletion of active journal files can corrupt useful evidence or race with journald.

F:

This option assumes Connectivity alone does not indicate whether jobs are pending, held or blocked in the print scheduler. The reported symptoms instead call for: Use supported journalctl vacuum-size or vacuum-time controls, with retention requirements considered.

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.