Pass LPI 102-500 Exam in First Attempt Easily
Real LPI 102-500 Exam Questions, Accurate & Verified Answers As Experienced in the Actual Test!

Verified by experts
3 products

You save $69.98

102-500 Premium Bundle

  • Premium File 120 Questions & Answers
  • Last Update: Nov 10, 2026
  • Training Course 126 Lectures
  • Study Guide 962 Pages
$79.99 $149.97

Purchase Individually

  • Premium File

    120 Questions & Answers
    Last Update: Nov 10, 2026

    $76.99
    $69.99
  • Training Course

    126 Lectures

    $43.99
    $39.99
  • Study Guide

    962 Pages

    $43.99
    $39.99

LPI Level 1 102-500 Practice Test 39

Question 380

A Linux troubleshooter is gathering specific evidence for this situation: A server loses journal messages after a reboot because it only uses volatile storage. Which check MOST directly diagnoses or confirms the technical condition described?

  1. Run logger with a unique tag and trace it through journal and rsyslog outputs.
  2. Check mailq and the MTA log entry for the test message ID.
  3. Run journalctl -u with the exact active service unit name.
  4. Review journald Storage settings, /var/log/journal and journalctl --list-boots.

Explanation

Correct Answer

D:

Review journald Storage settings, /var/log/journal and journalctl --list-boots. This check targets the relevant state for enabling persistent journald storage and directly assesses the observed behavior. The result should be evaluated against: Journal entries from a controlled prior boot are available after the next reboot.

Incorrect Answers

A:

Run logger with a unique tag and trace it through journal and rsyslog outputs. This check is relevant to testing a syslog pipeline with logger but not the most targeted diagnosis of enabling persistent journald storage. The specific check is: Review journald Storage settings, /var/log/journal and journalctl --list-boots.

B:

Check mailq and the MTA log entry for the test message ID. This check is relevant to checking queued outgoing email but not the most targeted diagnosis of enabling persistent journald storage. The specific check is: Review journald Storage settings, /var/log/journal and journalctl --list-boots.

C:

Run journalctl -u with the exact active service unit name. This check is relevant to filtering a service's systemd journal but not the most targeted diagnosis of enabling persistent journald storage. The specific check is: Review journald Storage settings, /var/log/journal and journalctl --list-boots.

Question 381

A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: A host's persistent systemd journal uses too much disk and the team proposes deleting arbitrary active files. Which step MOST directly corrects the specific problem described?

  1. Add or correct a facility-and-priority selector matching the service's actual syslog metadata.
  2. Submit the file using lpr with the approved destination printer and confirm the job ID.
  3. Use journalctl vacuum options and retention policy for archived journal data.
  4. Apply journalctl --since and --until around the actual outage window.

Explanation

Correct Answer

C:

Use journalctl vacuum options and retention policy for archived journal data. This targets the observed issue, limiting retained journal space safely, rather than a separate Linux configuration. Underlying behavior: Journalctl vacuuming applies retention limits to archived journal files. Verify the action by checking: Archived journal use falls within limits while current active journal integrity remains intact.

Incorrect Answers

A:

Add or correct a facility-and-priority selector matching the service's actual syslog metadata. This is an appropriate response to a different issue (selecting syslog facility and severity) but does not MOST directly address the explicit limiting retained journal space safely failure.

B:

Submit the file using lpr with the approved destination printer and confirm the job ID. This is an appropriate response to a different issue (submitting a print job through the lpd interface) but does not MOST directly address the explicit limiting retained journal space safely failure.

D:

Apply journalctl --since and --until around the actual outage window. This is an appropriate response to a different issue (filtering journal data by time range) but does not MOST directly address the explicit limiting retained journal space safely failure.

Question 382

A Linux team is checking the acceptance evidence for this specific situation: A host's persistent systemd journal uses too much disk and the team proposes deleting arbitrary active files. Which observation BEST confirms that this particular issue has been corrected?

  1. Archived journal use falls within limits while current active journal integrity remains intact.
  2. A new controlled journal event is ingested by the intended rsyslog rule and written to the expected file.
  3. The test tag appears at the expected receiver or log file with matching metadata.
  4. Timedatectl reports synchronization and timestamps agree with a trusted reference within policy tolerance.

Explanation

Correct Answer

A:

Archived journal use falls within limits while current active journal integrity remains intact. That evidence specifically demonstrates recovery from limiting retained journal space safely. The technical reason is: Journalctl vacuuming applies retention limits to archived journal files.

Incorrect Answers

B:

A new controlled journal event is ingested by the intended rsyslog rule and written to the expected file. This can validate understanding journald to rsyslog integration, but it does not establish that the described limiting retained journal space safely issue is fixed. The case-specific evidence is: Archived journal use falls within limits while current active journal integrity remains intact.

C:

The test tag appears at the expected receiver or log file with matching metadata. This can validate testing a syslog pipeline with logger, but it does not establish that the described limiting retained journal space safely issue is fixed. The case-specific evidence is: Archived journal use falls within limits while current active journal integrity remains intact.

D:

Timedatectl reports synchronization and timestamps agree with a trusted reference within policy tolerance. This can validate detecting system clock synchronization state, but it does not establish that the described limiting retained journal space safely issue is fixed. The case-specific evidence is: Archived journal use falls within limits while current active journal integrity remains intact.

Question 383

A Linux engineer reviews the underlying behavior in this particular case: A host's persistent systemd journal uses too much disk and the team proposes deleting arbitrary active files. Which technical behavior BEST explains this particular failure and its remedy?

  1. Volatile journal storage is lost on reboot, while persistent storage retains archived entries.
  2. Standard NTP time synchronization commonly exchanges datagrams over UDP port 123.
  3. Journal priority metadata supports severity-based filtering rather than grep-only text matching.
  4. Journalctl vacuuming applies retention limits to archived journal files.

Explanation

Correct Answer

D:

Journalctl vacuuming applies retention limits to archived journal files. This Linux behavior explains the observed symptoms and supports the precise remedy: Use journalctl vacuum options and retention policy for archived journal data.

Incorrect Answers

A:

Volatile journal storage is lost on reboot, while persistent storage retains archived entries. This describes another behavior (enabling persistent journald storage) and does not explain the stated limiting retained journal space safely failure. The operative behavior is: Journalctl vacuuming applies retention limits to archived journal files.

B:

Standard NTP time synchronization commonly exchanges datagrams over UDP port 123. This describes another behavior (understanding ntp service port usage) and does not explain the stated limiting retained journal space safely failure. The operative behavior is: Journalctl vacuuming applies retention limits to archived journal files.

C:

Journal priority metadata supports severity-based filtering rather than grep-only text matching. This describes another behavior (restricting journal results by priority) and does not explain the stated limiting retained journal space safely failure. The operative behavior is: Journalctl vacuuming applies retention limits to archived journal files.

Question 384

A Linux operating control has not corrected the following specific problem: A host's persistent systemd journal uses too much disk and the team proposes deleting arbitrary active files. Which outcome is the MOST directly associated operational risk if this problem remains?

  1. A broad network fix might expose services without resolving clock synchronization.
  2. Manual deletion may damage log retention and leave disk pressure unresolved.
  3. Incident evidence can disappear after the first remediation reboot.
  4. Investigators may diagnose the wrong machine and miss the actual boot failure.

Explanation

Correct Answer

B:

Manual deletion may damage log retention and leave disk pressure unresolved. This is the directly relevant consequence of leaving the limiting retained journal space safely problem unresolved. The appropriate preventive change is: Use journalctl vacuum options and retention policy for archived journal data.

Incorrect Answers

A:

A broad network fix might expose services without resolving clock synchronization. This consequence is connected to understanding ntp service port usage rather than the MOST direct exposure in the stated limiting retained journal space safely problem. The specific consequence is: Manual deletion may damage log retention and leave disk pressure unresolved.

C:

Incident evidence can disappear after the first remediation reboot. This consequence is connected to enabling persistent journald storage rather than the MOST direct exposure in the stated limiting retained journal space safely problem. The specific consequence is: Manual deletion may damage log retention and leave disk pressure unresolved.

D:

Investigators may diagnose the wrong machine and miss the actual boot failure. This consequence is connected to inspecting logs from an offline rescue filesystem rather than the MOST direct exposure in the stated limiting retained journal space safely problem. The specific consequence is: Manual deletion may damage log retention and leave disk pressure unresolved.

Question 385

A Linux troubleshooter is gathering specific evidence for this situation: A host's persistent systemd journal uses too much disk and the team proposes deleting arbitrary active files. Which check MOST directly diagnoses or confirms the technical condition described?

  1. Resolve the sendmail executable and trace one submission to the active MTA.
  2. Check journalctl --disk-usage and compare vacuum results with retained boot entries.
  3. Run journalctl -u with the exact active service unit name.
  4. Inspect /etc/logrotate.d, test logrotate -d and review rotated filenames.

Explanation

Correct Answer

B:

Check journalctl --disk-usage and compare vacuum results with retained boot entries. This check targets the relevant state for limiting retained journal space safely and directly assesses the observed behavior. The result should be evaluated against: Archived journal use falls within limits while current active journal integrity remains intact.

Incorrect Answers

A:

Resolve the sendmail executable and trace one submission to the active MTA. This check is relevant to understanding sendmail compatibility interfaces but not the most targeted diagnosis of limiting retained journal space safely. The specific check is: Check journalctl --disk-usage and compare vacuum results with retained boot entries.

C:

Run journalctl -u with the exact active service unit name. This check is relevant to filtering a service's systemd journal but not the most targeted diagnosis of limiting retained journal space safely. The specific check is: Check journalctl --disk-usage and compare vacuum results with retained boot entries.

D:

Inspect /etc/logrotate.d, test logrotate -d and review rotated filenames. This check is relevant to rotating high-volume application logs but not the most targeted diagnosis of limiting retained journal space safely. The specific check is: Check journalctl --disk-usage and compare vacuum results with retained boot entries.

Question 386

A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: A machine fails to boot and an analyst mounts its root filesystem on a rescue host but reads the rescue host's journal instead. Which step MOST directly corrects the specific problem described?

  1. Configure persistent systemd-journald storage with the supported setting and directory permissions.
  2. Query journalctl using the systemd service unit filter for the affected SSH service.
  3. Use journalctl --directory against the mounted machine's persistent journal directory.
  4. Submit the file using lpr with the approved destination printer and confirm the job ID.

Explanation

Correct Answer

C:

Use journalctl --directory against the mounted machine's persistent journal directory. This targets the observed issue, inspecting logs from an offline rescue filesystem, rather than a separate Linux configuration. Underlying behavior: Journalctl can open a designated external journal directory separately from the current host's logs. Verify the action by checking: The entries show the failed host's boot IDs and service failures rather than the rescue environment.

Incorrect Answers

A:

Configure persistent systemd-journald storage with the supported setting and directory permissions. This is an appropriate response to a different issue (enabling persistent journald storage) but does not MOST directly address the explicit inspecting logs from an offline rescue filesystem failure.

B:

Query journalctl using the systemd service unit filter for the affected SSH service. This is an appropriate response to a different issue (filtering a service's systemd journal) but does not MOST directly address the explicit inspecting logs from an offline rescue filesystem failure.

D:

Submit the file using lpr with the approved destination printer and confirm the job ID. This is an appropriate response to a different issue (submitting a print job through the lpd interface) but does not MOST directly address the explicit inspecting logs from an offline rescue filesystem failure.

Question 387

A Linux team is checking the acceptance evidence for this specific situation: A machine fails to boot and an analyst mounts its root filesystem on a rescue host but reads the rescue host's journal instead. Which observation BEST confirms that this particular issue has been corrected?

  1. Journal entries from a controlled prior boot are available after the next reboot.
  2. Chronyc shows a selected reliable source and a reducing measured clock offset.
  3. The result set omits informational entries but retains expected warnings and errors.
  4. The entries show the failed host's boot IDs and service failures rather than the rescue environment.

Explanation

Correct Answer

D:

The entries show the failed host's boot IDs and service failures rather than the rescue environment. That evidence specifically demonstrates recovery from inspecting logs from an offline rescue filesystem. The technical reason is: Journalctl can open a designated external journal directory separately from the current host's logs.

Incorrect Answers

A:

Journal entries from a controlled prior boot are available after the next reboot. This can validate enabling persistent journald storage, but it does not establish that the described inspecting logs from an offline rescue filesystem issue is fixed. The case-specific evidence is: The entries show the failed host's boot IDs and service failures rather than the rescue environment.

B:

Chronyc shows a selected reliable source and a reducing measured clock offset. This can validate checking chrony sources during drift, but it does not establish that the described inspecting logs from an offline rescue filesystem issue is fixed. The case-specific evidence is: The entries show the failed host's boot IDs and service failures rather than the rescue environment.

C:

The result set omits informational entries but retains expected warnings and errors. This can validate restricting journal results by priority, but it does not establish that the described inspecting logs from an offline rescue filesystem issue is fixed. The case-specific evidence is: The entries show the failed host's boot IDs and service failures rather than the rescue environment.

Question 388

A Linux engineer reviews the underlying behavior in this particular case: A machine fails to boot and an analyst mounts its root filesystem on a rescue host but reads the rescue host's journal instead. Which technical behavior BEST explains this particular failure and its remedy?

  1. Journalctl can open a designated external journal directory separately from the current host's logs.
  2. Volatile journal storage is lost on reboot, while persistent storage retains archived entries.
  3. Postfix, Exim and Sendmail can all act as mail transfer agents on Linux.
  4. Journalctl vacuuming applies retention limits to archived journal files.

Explanation

Correct Answer

A:

Journalctl can open a designated external journal directory separately from the current host's logs. This Linux behavior explains the observed symptoms and supports the precise remedy: Use journalctl --directory against the mounted machine's persistent journal directory.

Incorrect Answers

B:

Volatile journal storage is lost on reboot, while persistent storage retains archived entries. This describes another behavior (enabling persistent journald storage) and does not explain the stated inspecting logs from an offline rescue filesystem failure. The operative behavior is: Journalctl can open a designated external journal directory separately from the current host's logs.

C:

Postfix, Exim and Sendmail can all act as mail transfer agents on Linux. This describes another behavior (recognizing common mta implementations) and does not explain the stated inspecting logs from an offline rescue filesystem failure. The operative behavior is: Journalctl can open a designated external journal directory separately from the current host's logs.

D:

Journalctl vacuuming applies retention limits to archived journal files. This describes another behavior (limiting retained journal space safely) and does not explain the stated inspecting logs from an offline rescue filesystem failure. The operative behavior is: Journalctl can open a designated external journal directory separately from the current host's logs.

Question 389

A Linux operating control has not corrected the following specific problem: A machine fails to boot and an analyst mounts its root filesystem on a rescue host but reads the rescue host's journal instead. Which outcome is the MOST directly associated operational risk if this problem remains?

  1. Investigators may miss the cause amid unrelated host events.
  2. Important user notices may remain unread in the local spool.
  3. Central monitoring may be blind to incidents on isolated hosts.
  4. Investigators may diagnose the wrong machine and miss the actual boot failure.

Explanation

Correct Answer

D:

Investigators may diagnose the wrong machine and miss the actual boot failure. This is the directly relevant consequence of leaving the inspecting logs from an offline rescue filesystem problem unresolved. The appropriate preventive change is: Use journalctl --directory against the mounted machine's persistent journal directory.

Incorrect Answers

A:

Investigators may miss the cause amid unrelated host events. This consequence is connected to filtering a service's systemd journal rather than the MOST direct exposure in the stated inspecting logs from an offline rescue filesystem problem. The specific consequence is: Investigators may diagnose the wrong machine and miss the actual boot failure.

B:

Important user notices may remain unread in the local spool. This consequence is connected to configuring per-user email forwarding rather than the MOST direct exposure in the stated inspecting logs from an offline rescue filesystem problem. The specific consequence is: Investigators may diagnose the wrong machine and miss the actual boot failure.

C:

Central monitoring may be blind to incidents on isolated hosts. This consequence is connected to forwarding rsyslog to a central collector rather than the MOST direct exposure in the stated inspecting logs from an offline rescue filesystem problem. The specific consequence is: Investigators may diagnose the wrong machine and miss the actual boot failure.

Question 390

A Linux troubleshooter is gathering specific evidence for this situation: A machine fails to boot and an analyst mounts its root filesystem on a rescue host but reads the rescue host's journal instead. Which check MOST directly diagnoses or confirms the technical condition described?

  1. Check journalctl --since/--until arguments and the system clock configuration.
  2. Locate the mounted /var/log/journal directory and inspect its machine and boot IDs.
  3. Inspect ~/.forward, aliases and repeated recipient addresses in MTA log traces.
  4. Check journalctl --disk-usage and compare vacuum results with retained boot entries.

Explanation

Correct Answer

B:

Locate the mounted /var/log/journal directory and inspect its machine and boot IDs. This check targets the relevant state for inspecting logs from an offline rescue filesystem and directly assesses the observed behavior. The result should be evaluated against: The entries show the failed host's boot IDs and service failures rather than the rescue environment.

Incorrect Answers

A:

Check journalctl --since/--until arguments and the system clock configuration. This check is relevant to filtering journal data by time range but not the most targeted diagnosis of inspecting logs from an offline rescue filesystem. The specific check is: Locate the mounted /var/log/journal directory and inspect its machine and boot IDs.

C:

Inspect ~/.forward, aliases and repeated recipient addresses in MTA log traces. This check is relevant to preventing external forwarding loops but not the most targeted diagnosis of inspecting logs from an offline rescue filesystem. The specific check is: Locate the mounted /var/log/journal directory and inspect its machine and boot IDs.

D:

Check journalctl --disk-usage and compare vacuum results with retained boot entries. This check is relevant to limiting retained journal space safely but not the most targeted diagnosis of inspecting logs from an offline rescue filesystem. The specific check is: Locate the mounted /var/log/journal directory and inspect its machine and boot IDs.

LPI Level 1 (102-500) Practice Tests

Purchase Individually

  • Premium File

    120 Questions & Answers
    Last Update: Nov 10, 2026

    $76.99
    $69.99
  • Training Course

    126 Lectures

    $43.99
    $39.99
  • Study Guide

    962 Pages

    $43.99
    $39.99

SPECIAL OFFER: GET 10% OFF
This is ONE TIME OFFER

You save
10%

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

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

Please check your mailbox for a message from support@examlabs.com and follow the directions.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

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

  • Realistic exam simulation and exam editor with preview functions
  • Whole exam in a single file with several different question types
  • Customizable exam-taking mode & detailed score reports