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 38

Question 370

A dual-boot workstation periodically shifts time after reboot because Linux and the other OS disagree about the RTC basis. Which THREE actions form a suitable remediation, verification and prevention plan? Select THREE.

  1. Document the RTC standard across dual-boot images to avoid repeated time offsets.
  2. Send test mail to every alias and inspect headers/queue for a finite route.
  3. Escalate transport policy and mail security rearchitecture to the appropriate mail-service owner.
  4. Enable persistent journald storage and provision the appropriate /var/log/journal location and settings.
  5. Establish a consistent hardware-clock convention, preferably RTC in UTC where supported, and set timedatectl policy.
  6. Compare hwclock -r with date -u after a clean shutdown and reboot.

Explanation

Correct Answers

A:

Document the RTC standard across dual-boot images to avoid repeated time offsets. This control detects or prevents the same mechanism before another incident.

E:

Establish a consistent hardware-clock convention, preferably RTC in UTC where supported, and set timedatectl policy. It addresses the root cause, while Document the RTC standard across dual-boot images to avoid repeated time offsets. reduces future recurrence.

F:

Compare hwclock -r with date -u after a clean shutdown and reboot. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: The systems interpret the hardware RTC using different UTC versus localtime assumptions.

Incorrect Answers

B:

Send test mail to every alias and inspect headers/queue for a finite route. belongs to a situation where Circular aliases can cause indefinite recursion or be rejected by the MTA. Here the evidence supports a different requirement: Compare hwclock -r with date -u after a clean shutdown and reboot.

C:

Escalate transport policy and mail security rearchitecture to the appropriate mail-service owner. could help with mta configuration beyond exam scope; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Compare hwclock -r with date -u after a clean shutdown and reboot.

D:

This option assumes The systemd journal may be stored only in runtime storage, which disappears at reboot. The reported symptoms instead call for: Establish a consistent hardware-clock convention, preferably RTC in UTC where supported, and set timedatectl policy.

Question 371

A new host reports NTP synchronized=no, and chronyc sources lists no reachable time source. Which mechanism best explains the difference between expectation and result?

  1. A plain journalctl query in the rescue OS reads that OS's journal, not the mounted system's stored logs.
  2. An active MTA can hold messages in its queue when delivery is deferred or destination resolution fails.
  3. The time synchronization daemon lacks a usable upstream source or cannot reach it.
  4. Without priority filtering the journal query mixes benign events with high-severity records.

Explanation

Correct Answer

C:

The time synchronization daemon lacks a usable upstream source or cannot reach it. This is the explanation that justifies the specific remedy: Configure an approved reachable chrony server or pool and permit its required NTP traffic.

Incorrect Answers

A:

A plain journalctl query in the rescue OS reads that OS's journal, not the mounted system's stored logs. That describes a different fault. Here, The time synchronization daemon lacks a usable upstream source or cannot reach it.

B:

The test for inspect pending mail delivery would be: Compare queue entries and age before and after resolving a known delivery fault. The relevant acceptance check here is: Inspect chronyc sources -v and chronyc tracking until a valid selected source appears.

D:

This option assumes Without priority filtering the journal query mixes benign events with high-severity records. The reported symptoms instead call for: Configure an approved reachable chrony server or pool and permit its required NTP traffic.

Question 372

A new host reports NTP synchronized=no, and chronyc sources lists no reachable time source. Which configuration approach is appropriate for this requirement?

  1. Configure an approved reachable chrony server or pool and permit its required NTP traffic.
  2. Query journalctl -u service-name with a suitable time range instead of scanning arbitrary text.
  3. Run newaliases or the MTA's supported alias database rebuild after updating /etc/aliases.
  4. Configure an approved TCP rsyslog forwarding action and corresponding listener/TLS policy as needed.

Explanation

Correct Answer

A:

Configure an approved reachable chrony server or pool and permit its required NTP traffic. Unlike a broad workaround, it targets the observed cause: The time synchronization daemon lacks a usable upstream source or cannot reach it.

Incorrect Answers

B:

Query journalctl -u service-name with a suitable time range instead of scanning arbitrary text. belongs to a situation where The systemd journal already stores structured unit metadata that can scope the search. Here the evidence supports a different requirement: Configure an approved reachable chrony server or pool and permit its required NTP traffic.

C:

This option assumes Some MTAs require the aliases database to be rebuilt after editing the text file. The reported symptoms instead call for: Configure an approved reachable chrony server or pool and permit its required NTP traffic.

D:

This belongs to rsyslog tcp forwarding, where The single-@ rsyslog forwarding action denotes UDP while double-@@ denotes TCP in legacy action syntax. The current issue instead is: The time synchronization daemon lacks a usable upstream source or cannot reach it.

Question 373

A new host reports NTP synchronized=no, and chronyc sources lists no reachable time source. How should the administrator verify the required behavior?

  1. Inspect chronyc sources -v and chronyc tracking until a valid selected source appears.
  2. Emit a controlled event and trace whether it appears in both journal and the intended text log.
  3. Check queue drain after enabling and verify the previously pending job prints.
  4. Run logrotate in debug/test mode and verify ownership, rotation and application write behavior.

Explanation

Correct Answer

A:

Inspect chronyc sources -v and chronyc tracking until a valid selected source appears. The test is evidence-based because the underlying failure was: The time synchronization daemon lacks a usable upstream source or cannot reach it.

Incorrect Answers

B:

This option assumes Journald and rsyslog are separate components; storage and forwarding rules determine whether entries are mirrored. The reported symptoms instead call for: Configure an approved reachable chrony server or pool and permit its required NTP traffic.

C:

This option assumes A queue can accept jobs without forwarding them to a disabled printer device. The reported symptoms instead call for: Configure an approved reachable chrony server or pool and permit its required NTP traffic.

D:

The test for logrotate retention would be: Run logrotate in debug/test mode and verify ownership, rotation and application write behavior. The relevant acceptance check here is: Inspect chronyc sources -v and chronyc tracking until a valid selected source appears.

Question 374

A new host reports NTP synchronized=no, and chronyc sources lists no reachable time source. Which ongoing control would best reduce the chance of the issue returning?

  1. Keep sufficient persistent boot history for post-crash investigation.
  2. Treat system-mail aliases as controlled data-flow configuration.
  3. Monitor source reachability and measured offset, not just whether the daemon process is running.
  4. Treat alias database rebuild and delivery tests as part of change procedures.

Explanation

Correct Answer

C:

Monitor source reachability and measured offset, not just whether the daemon process is running. It prevents repetition of the condition: The time synchronization daemon lacks a usable upstream source or cannot reach it.

Incorrect Answers

A:

Keep sufficient persistent boot history for post-crash investigation. belongs to a situation where journalctl defaults to the current boot unless another boot is selected. Here the evidence supports a different requirement: Monitor source reachability and measured offset, not just whether the daemon process is running.

B:

That choice responds to a confidential forwarding mistake failure. In this incident, The time synchronization daemon lacks a usable upstream source or cannot reach it.

D:

Treat alias database rebuild and delivery tests as part of change procedures. could help with local mail alias activation; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Inspect chronyc sources -v and chronyc tracking until a valid selected source appears.

Question 375

A new host reports NTP synchronized=no, and chronyc sources lists no reachable time source. Choose TWO case-specific steps: one that fixes the issue and one that proves the result.

  1. Check both queue acceptance and printer enabled state during incidents.
  2. Send a test message to root and confirm it reaches the authorized duty destination.
  3. Use journalctl --since and --until with explicit times for the investigation interval.
  4. Inspect chronyc sources -v and chronyc tracking until a valid selected source appears.
  5. Configure an approved reachable chrony server or pool and permit its required NTP traffic.

Explanation

Correct Answers

D:

Inspect chronyc sources -v and chronyc tracking until a valid selected source appears. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: The time synchronization daemon lacks a usable upstream source or cannot reach it.

E:

Configure an approved reachable chrony server or pool and permit its required NTP traffic. The change should be accepted only after this test: Inspect chronyc sources -v and chronyc tracking until a valid selected source appears.

Incorrect Answers

A:

This option assumes The queue may be configured to reject incoming jobs independently of whether the device is enabled. The reported symptoms instead call for: Configure an approved reachable chrony server or pool and permit its required NTP traffic.

B:

This belongs to local mail alias activation, where Some MTAs require the aliases database to be rebuilt after editing the text file. The current issue instead is: The time synchronization daemon lacks a usable upstream source or cannot reach it.

C:

It would address systemd journal time window rather than the present problem. The appropriate correction here is: Configure an approved reachable chrony server or pool and permit its required NTP traffic.

Question 376

A virtual machine's clock is several minutes behind and the application cannot tolerate the long correction while chrony slowly slews it. Which mechanism best explains the difference between expectation and result?

  1. Removing a specific queued print job is distinct from disabling or purging a printer.
  2. A successful daemon restart does not prove that a message reaches its intended local or remote destination.
  3. The time client is correcting a large offset gradually rather than stepping it under approved conditions.
  4. The systemd journal may be stored only in runtime storage, which disappears at reboot.

Explanation

Correct Answer

C:

The time client is correcting a large offset gradually rather than stepping it under approved conditions. This is the explanation that justifies the specific remedy: Use an explicitly approved chrony makestep policy or one-time step after evaluating application sensitivity.

Incorrect Answers

A:

This belongs to remove one queued print job, where Removing a specific queued print job is distinct from disabling or purging a printer. The current issue instead is: The time client is correcting a large offset gradually rather than stepping it under approved conditions.

B:

The test for test syslog pipeline with logger would be: Search both sender and receiver logs for the unique tag and compare timestamps. The relevant acceptance check here is: Watch chronyc tracking offset before and after intervention and confirm stable synchronization.

D:

This option assumes The systemd journal may be stored only in runtime storage, which disappears at reboot. The reported symptoms instead call for: Use an explicitly approved chrony makestep policy or one-time step after evaluating application sensitivity.

Question 377

A virtual machine's clock is several minutes behind and the application cannot tolerate the long correction while chrony slowly slews it. Which configuration approach is appropriate for this requirement?

  1. Use an authorized monitored destination mailbox and limit routing to policy-approved recipients.
  2. Use an explicitly approved chrony makestep policy or one-time step after evaluating application sensitivity.
  3. Point journalctl at the mounted journal directory or file using supported --directory/--file options.
  4. Run newaliases or the MTA's supported alias database rebuild after updating /etc/aliases.

Explanation

Correct Answer

B:

Use an explicitly approved chrony makestep policy or one-time step after evaluating application sensitivity. It is the direct response; verify the result by: Watch chronyc tracking offset before and after intervention and confirm stable synchronization.

Incorrect Answers

A:

That choice responds to a confidential forwarding mistake failure. In this incident, The time client is correcting a large offset gradually rather than stepping it under approved conditions.

C:

The test for rescue-system journal path would be: Check machine IDs and boot IDs to ensure displayed records come from the failed host. The relevant acceptance check here is: Watch chronyc tracking offset before and after intervention and confirm stable synchronization.

D:

It would address local mail alias activation rather than the present problem. The appropriate correction here is: Use an explicitly approved chrony makestep policy or one-time step after evaluating application sensitivity.

Question 378

A virtual machine's clock is several minutes behind and the application cannot tolerate the long correction while chrony slowly slews it. Which test would confirm the suspected Linux mechanism?

  1. Watch chronyc tracking offset before and after intervention and confirm stable synchronization.
  2. Send a controlled message to the local user and verify receipt at the forward destination.
  3. Interrupt and restore the receiver during test and verify transport and receipt.
  4. Measure journal disk usage before and after vacuuming and ensure recent events remain.

Explanation

Correct Answer

A:

Watch chronyc tracking offset before and after intervention and confirm stable synchronization. The test is evidence-based because the underlying failure was: The time client is correcting a large offset gradually rather than stepping it under approved conditions.

Incorrect Answers

B:

The test for forward mail for one user would be: Send a controlled message to the local user and verify receipt at the forward destination. The relevant acceptance check here is: Watch chronyc tracking offset before and after intervention and confirm stable synchronization.

C:

Interrupt and restore the receiver during test and verify transport and receipt. belongs to a situation where The single-@ rsyslog forwarding action denotes UDP while double-@@ denotes TCP in legacy action syntax. Here the evidence supports a different requirement: Watch chronyc tracking offset before and after intervention and confirm stable synchronization.

D:

The test for retire old journal safely would be: Measure journal disk usage before and after vacuuming and ensure recent events remain. The relevant acceptance check here is: Watch chronyc tracking offset before and after intervention and confirm stable synchronization.

Question 379

A virtual machine's clock is several minutes behind and the application cannot tolerate the long correction while chrony slowly slews it. Which repeatable check would reduce recurrence?

  1. Review alias graphs for cycles during mail-routing changes.
  2. Monitor rotated log sizes and retention alongside application load.
  3. Include large startup clock offsets in workload risk checks and clock policy.
  4. Review forwarding loops and sensitive-message exposure before enabling user-level redirects.

Explanation

Correct Answer

C:

Include large startup clock offsets in workload risk checks and clock policy. It prevents repetition of the condition: The time client is correcting a large offset gradually rather than stepping it under approved conditions.

Incorrect Answers

A:

This option assumes Circular aliases can cause indefinite recursion or be rejected by the MTA. The reported symptoms instead call for: Use an explicitly approved chrony makestep policy or one-time step after evaluating application sensitivity.

B:

The test for logrotate retention would be: Run logrotate in debug/test mode and verify ownership, rotation and application write behavior. The relevant acceptance check here is: Watch chronyc tracking offset before and after intervention and confirm stable synchronization.

D:

This option assumes Global aliases are not required for a per-account redirect supported by ~/.forward. The reported symptoms instead call for: Use an explicitly approved chrony makestep policy or one-time step after evaluating application sensitivity.

Question 380

A virtual machine's clock is several minutes behind and the application cannot tolerate the long correction while chrony slowly slews it. Which THREE actions form a suitable remediation, verification and prevention plan? Select THREE.

  1. Use an explicitly approved chrony makestep policy or one-time step after evaluating application sensitivity.
  2. Include large startup clock offsets in workload risk checks and clock policy.
  3. Inspect lpstat -o or lpq for queue state and job identifiers.
  4. Send a test message to root and confirm it reaches the authorized duty destination.
  5. Keep sufficient persistent boot history for post-crash investigation.
  6. Watch chronyc tracking offset before and after intervention and confirm stable synchronization.

Explanation

Correct Answers

A:

Use an explicitly approved chrony makestep policy or one-time step after evaluating application sensitivity. This is appropriate because The time client is correcting a large offset gradually rather than stepping it under approved conditions.

B:

Include large startup clock offsets in workload risk checks and clock policy. The underlying risk is The time client is correcting a large offset gradually rather than stepping it under approved conditions.

F:

Watch chronyc tracking offset before and after intervention and confirm stable synchronization. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: The time client is correcting a large offset gradually rather than stepping it under approved conditions.

Incorrect Answers

C:

Inspect lpstat -o or lpq for queue state and job identifiers. belongs to a situation where Connectivity alone does not indicate whether jobs are pending, held or blocked in the print scheduler. Here the evidence supports a different requirement: Use an explicitly approved chrony makestep policy or one-time step after evaluating application sensitivity.

D:

This belongs to local mail alias activation, where Some MTAs require the aliases database to be rebuilt after editing the text file. The current issue instead is: The time client is correcting a large offset gradually rather than stepping it under approved conditions.

E:

This option assumes journalctl defaults to the current boot unless another boot is selected. The reported symptoms instead call for: Use an explicitly approved chrony makestep policy or one-time step after evaluating application sensitivity.

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.