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 34

Question 330

A Linux troubleshooter is gathering specific evidence for this situation: A server using chronyd drifts several seconds despite a configured NTP source list. Which check MOST directly diagnoses or confirms the technical condition described?

  1. Run chronyc sources -v and chronyc tracking and review network reachability.
  2. Inspect ntpq -p and the service journal for peer reachability errors.
  3. Inspect /etc/logrotate.d, test logrotate -d and review rotated filenames.
  4. Compare chronyc tracking before and after the controlled makestep action.

Explanation

Correct Answer

A:

Run chronyc sources -v and chronyc tracking and review network reachability. This check targets the relevant state for checking chrony sources during drift and directly assesses the observed behavior. The result should be evaluated against: Chronyc shows a selected reliable source and a reducing measured clock offset.

Incorrect Answers

B:

Inspect ntpq -p and the service journal for peer reachability errors. This check is relevant to verifying ntpd peers and reachability but not the most targeted diagnosis of checking chrony sources during drift. The specific check is: Run chronyc sources -v and chronyc tracking and review network reachability.

C:

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 checking chrony sources during drift. The specific check is: Run chronyc sources -v and chronyc tracking and review network reachability.

D:

Compare chronyc tracking before and after the controlled makestep action. This check is relevant to handling large initial time corrections but not the most targeted diagnosis of checking chrony sources during drift. The specific check is: Run chronyc sources -v and chronyc tracking and review network reachability.

Question 331

A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: After an administrator corrects system time, a dual-boot machine's hardware clock remains wrong and boot displays a time jump. Which step MOST directly corrects the specific problem described?

  1. Inspect and re-enable the printer or queue using supported CUPS administrative tools after correcting the cause.
  2. Use an authorized initial step correction such as chronyc makestep after confirming the reference source is trustworthy.
  3. Store the correct system time to the hardware clock using hwclock --systohc --utc with the agreed policy.
  4. Allow the approved NTP exchange on UDP port 123 between clients and the configured time servers.

Explanation

Correct Answer

C:

Store the correct system time to the hardware clock using hwclock --systohc --utc with the agreed policy. This targets the observed issue, synchronizing the hardware clock as utc, rather than a separate Linux configuration. Underlying behavior: The hardware clock and kernel-maintained system time are separate timekeeping mechanisms. Verify the action by checking: Hardware and system clock agree on UTC after a controlled reboot.

Incorrect Answers

A:

Inspect and re-enable the printer or queue using supported CUPS administrative tools after correcting the cause. This is an appropriate response to a different issue (diagnosing a paused cups queue) but does not MOST directly address the explicit synchronizing the hardware clock as utc failure.

B:

Use an authorized initial step correction such as chronyc makestep after confirming the reference source is trustworthy. This is an appropriate response to a different issue (handling large initial time corrections) but does not MOST directly address the explicit synchronizing the hardware clock as utc failure.

D:

Allow the approved NTP exchange on UDP port 123 between clients and the configured time servers. This is an appropriate response to a different issue (understanding ntp service port usage) but does not MOST directly address the explicit synchronizing the hardware clock as utc failure.

Question 332

A Linux team is checking the acceptance evidence for this specific situation: After an administrator corrects system time, a dual-boot machine's hardware clock remains wrong and boot displays a time jump. Which observation BEST confirms that this particular issue has been corrected?

  1. The client selects an authorized source and achieves the expected synchronization quality.
  2. Chronyc shows a selected reliable source and a reducing measured clock offset.
  3. A controlled recipient receives the intended subject and body through the local MTA.
  4. Hardware and system clock agree on UTC after a controlled reboot.

Explanation

Correct Answer

D:

Hardware and system clock agree on UTC after a controlled reboot. That evidence specifically demonstrates recovery from synchronizing the hardware clock as utc. The technical reason is: The hardware clock and kernel-maintained system time are separate timekeeping mechanisms.

Incorrect Answers

A:

The client selects an authorized source and achieves the expected synchronization quality. This can validate configuring chrony upstream references, but it does not establish that the described synchronizing the hardware clock as utc issue is fixed. The case-specific evidence is: Hardware and system clock agree on UTC after a controlled reboot.

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 synchronizing the hardware clock as utc issue is fixed. The case-specific evidence is: Hardware and system clock agree on UTC after a controlled reboot.

C:

A controlled recipient receives the intended subject and body through the local MTA. This can validate sending a basic command-line notification, but it does not establish that the described synchronizing the hardware clock as utc issue is fixed. The case-specific evidence is: Hardware and system clock agree on UTC after a controlled reboot.

Question 333

A Linux engineer reviews the underlying behavior in this particular case: After an administrator corrects system time, a dual-boot machine's hardware clock remains wrong and boot displays a time jump. Which technical behavior BEST explains this particular failure and its remedy?

  1. Standard NTP time synchronization commonly exchanges datagrams over UDP port 123.
  2. Journald collection and rsyslog file delivery can be distinct stages in the logging pipeline.
  3. The hardware clock and kernel-maintained system time are separate timekeeping mechanisms.
  4. Clock slewing corrects time gradually; an explicit step can correct a large offset immediately.

Explanation

Correct Answer

C:

The hardware clock and kernel-maintained system time are separate timekeeping mechanisms. This Linux behavior explains the observed symptoms and supports the precise remedy: Store the correct system time to the hardware clock using hwclock --systohc --utc with the agreed policy.

Incorrect Answers

A:

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 synchronizing the hardware clock as utc failure. The operative behavior is: The hardware clock and kernel-maintained system time are separate timekeeping mechanisms.

B:

Journald collection and rsyslog file delivery can be distinct stages in the logging pipeline. This describes another behavior (understanding journald to rsyslog integration) and does not explain the stated synchronizing the hardware clock as utc failure. The operative behavior is: The hardware clock and kernel-maintained system time are separate timekeeping mechanisms.

D:

Clock slewing corrects time gradually; an explicit step can correct a large offset immediately. This describes another behavior (handling large initial time corrections) and does not explain the stated synchronizing the hardware clock as utc failure. The operative behavior is: The hardware clock and kernel-maintained system time are separate timekeeping mechanisms.

Question 334

A Linux operating control has not corrected the following specific problem: After an administrator corrects system time, a dual-boot machine's hardware clock remains wrong and boot displays a time jump. Which outcome is the MOST directly associated operational risk if this problem remains?

  1. Boots may repeatedly start with incorrect time and disrupt scheduled tasks.
  2. Clock skew may persist despite an apparently installed NTP daemon.
  3. Investigators may diagnose the wrong machine and miss the actual boot failure.
  4. Transactions may be rejected while the initial clock offset remains excessive.

Explanation

Correct Answer

A:

Boots may repeatedly start with incorrect time and disrupt scheduled tasks. This is the directly relevant consequence of leaving the synchronizing the hardware clock as utc problem unresolved. The appropriate preventive change is: Store the correct system time to the hardware clock using hwclock --systohc --utc with the agreed policy.

Incorrect Answers

B:

Clock skew may persist despite an apparently installed NTP daemon. This consequence is connected to verifying ntpd peers and reachability rather than the MOST direct exposure in the stated synchronizing the hardware clock as utc problem. The specific consequence is: Boots may repeatedly start with incorrect time and disrupt scheduled tasks.

C:

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 synchronizing the hardware clock as utc problem. The specific consequence is: Boots may repeatedly start with incorrect time and disrupt scheduled tasks.

D:

Transactions may be rejected while the initial clock offset remains excessive. This consequence is connected to handling large initial time corrections rather than the MOST direct exposure in the stated synchronizing the hardware clock as utc problem. The specific consequence is: Boots may repeatedly start with incorrect time and disrupt scheduled tasks.

Question 335

A Linux troubleshooter is gathering specific evidence for this situation: After an administrator corrects system time, a dual-boot machine's hardware clock remains wrong and boot displays a time jump. Which check MOST directly diagnoses or confirms the technical condition described?

  1. Inspect ntpq -p and the service journal for peer reachability errors.
  2. Inspect timedatectl show and the currently active time-sync service state.
  3. Compare date -u and hwclock --show --utc before and after the update.
  4. Compare lpq results with lpstat queue information.

Explanation

Correct Answer

C:

Compare date -u and hwclock --show --utc before and after the update. This check targets the relevant state for synchronizing the hardware clock as utc and directly assesses the observed behavior. The result should be evaluated against: Hardware and system clock agree on UTC after a controlled reboot.

Incorrect Answers

A:

Inspect ntpq -p and the service journal for peer reachability errors. This check is relevant to verifying ntpd peers and reachability but not the most targeted diagnosis of synchronizing the hardware clock as utc. The specific check is: Compare date -u and hwclock --show --utc before and after the update.

B:

Inspect timedatectl show and the currently active time-sync service state. This check is relevant to detecting system clock synchronization state but not the most targeted diagnosis of synchronizing the hardware clock as utc. The specific check is: Compare date -u and hwclock --show --utc before and after the update.

D:

Compare lpq results with lpstat queue information. This check is relevant to listing a print queue using compatibility tools but not the most targeted diagnosis of synchronizing the hardware clock as utc. The specific check is: Compare date -u and hwclock --show --utc before and after the update.

Question 336

A Linux administrator supports a system covered by LPI exam 102-500, version 5.0: A remote office configures chronyd but only points it at an unreachable internal time server. Which step MOST directly corrects the specific problem described?

  1. Use journalctl with a suitable priority threshold, such as -p warning.
  2. Check ntpq peer and reachability information, then repair server access or selection.
  3. Inspect chronyc sources and tracking state, then repair the selected reachable reference sources.
  4. Specify reachable approved upstream servers or a pool in chrony configuration and verify access.

Explanation

Correct Answer

D:

Specify reachable approved upstream servers or a pool in chrony configuration and verify access. This targets the observed issue, configuring chrony upstream references, rather than a separate Linux configuration. Underlying behavior: NTP client configuration requires usable clock references rather than a daemon process alone. Verify the action by checking: The client selects an authorized source and achieves the expected synchronization quality.

Incorrect Answers

A:

Use journalctl with a suitable priority threshold, such as -p warning. This is an appropriate response to a different issue (restricting journal results by priority) but does not MOST directly address the explicit configuring chrony upstream references failure.

B:

Check ntpq peer and reachability information, then repair server access or selection. This is an appropriate response to a different issue (verifying ntpd peers and reachability) but does not MOST directly address the explicit configuring chrony upstream references failure.

C:

Inspect chronyc sources and tracking state, then repair the selected reachable reference sources. This is an appropriate response to a different issue (checking chrony sources during drift) but does not MOST directly address the explicit configuring chrony upstream references failure.

Question 337

A Linux team is checking the acceptance evidence for this specific situation: A remote office configures chronyd but only points it at an unreachable internal time server. Which observation BEST confirms that this particular issue has been corrected?

  1. NTP reachability and client synchronization recover without broadening unrelated access.
  2. Chronyc shows a selected reliable source and a reducing measured clock offset.
  3. The client selects an authorized source and achieves the expected synchronization quality.
  4. The specified job disappears while other users' queued jobs remain unchanged.

Explanation

Correct Answer

C:

The client selects an authorized source and achieves the expected synchronization quality. That evidence specifically demonstrates recovery from configuring chrony upstream references. The technical reason is: NTP client configuration requires usable clock references rather than a daemon process alone.

Incorrect Answers

A:

NTP reachability and client synchronization recover without broadening unrelated access. This can validate understanding ntp service port usage, but it does not establish that the described configuring chrony upstream references issue is fixed. The case-specific evidence is: The client selects an authorized source and achieves the expected synchronization quality.

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 configuring chrony upstream references issue is fixed. The case-specific evidence is: The client selects an authorized source and achieves the expected synchronization quality.

D:

The specified job disappears while other users' queued jobs remain unchanged. This can validate removing one cups print job safely, but it does not establish that the described configuring chrony upstream references issue is fixed. The case-specific evidence is: The client selects an authorized source and achieves the expected synchronization quality.

Question 338

A Linux engineer reviews the underlying behavior in this particular case: A remote office configures chronyd but only points it at an unreachable internal time server. Which technical behavior BEST explains this particular failure and its remedy?

  1. Chrony chooses and disciplines clock sources based on reachability and measured offset.
  2. Mail submission tools hand a message to local mail transport rather than guaranteeing final receipt.
  3. NTP configuration alone does not establish that peers are reachable or selected.
  4. NTP client configuration requires usable clock references rather than a daemon process alone.

Explanation

Correct Answer

D:

NTP client configuration requires usable clock references rather than a daemon process alone. This Linux behavior explains the observed symptoms and supports the precise remedy: Specify reachable approved upstream servers or a pool in chrony configuration and verify access.

Incorrect Answers

A:

Chrony chooses and disciplines clock sources based on reachability and measured offset. This describes another behavior (checking chrony sources during drift) and does not explain the stated configuring chrony upstream references failure. The operative behavior is: NTP client configuration requires usable clock references rather than a daemon process alone.

B:

Mail submission tools hand a message to local mail transport rather than guaranteeing final receipt. This describes another behavior (sending a basic command-line notification) and does not explain the stated configuring chrony upstream references failure. The operative behavior is: NTP client configuration requires usable clock references rather than a daemon process alone.

C:

NTP configuration alone does not establish that peers are reachable or selected. This describes another behavior (verifying ntpd peers and reachability) and does not explain the stated configuring chrony upstream references failure. The operative behavior is: NTP client configuration requires usable clock references rather than a daemon process alone.

Question 339

A Linux operating control has not corrected the following specific problem: A remote office configures chronyd but only points it at an unreachable internal time server. Which outcome is the MOST directly associated operational risk if this problem remains?

  1. Time drift can undermine authentication windows and distributed application consistency.
  2. An operator may falsely assume absence from a text log means no event occurred.
  3. Incorrect timestamps can invalidate event correlation across hosts.
  4. Unsynchronized hosts can disagree on security log event order.

Explanation

Correct Answer

D:

Unsynchronized hosts can disagree on security log event order. This is the directly relevant consequence of leaving the configuring chrony upstream references problem unresolved. The appropriate preventive change is: Specify reachable approved upstream servers or a pool in chrony configuration and verify access.

Incorrect Answers

A:

Time drift can undermine authentication windows and distributed application consistency. This consequence is connected to checking chrony sources during drift rather than the MOST direct exposure in the stated configuring chrony upstream references problem. The specific consequence is: Unsynchronized hosts can disagree on security log event order.

B:

An operator may falsely assume absence from a text log means no event occurred. This consequence is connected to understanding journald to rsyslog integration rather than the MOST direct exposure in the stated configuring chrony upstream references problem. The specific consequence is: Unsynchronized hosts can disagree on security log event order.

C:

Incorrect timestamps can invalidate event correlation across hosts. This consequence is connected to detecting system clock synchronization state rather than the MOST direct exposure in the stated configuring chrony upstream references problem. The specific consequence is: Unsynchronized hosts can disagree on security log event order.

Question 340

A Linux troubleshooter is gathering specific evidence for this situation: A remote office configures chronyd but only points it at an unreachable internal time server. Which check MOST directly diagnoses or confirms the technical condition described?

  1. Check firewall counters for UDP 123 and chrony or ntpd peer reachability.
  2. Inspect timedatectl show and the currently active time-sync service state.
  3. Inspect /etc/chrony.conf and chronyc sources along with UDP reachability.
  4. Inspect /etc/logrotate.d, test logrotate -d and review rotated filenames.

Explanation

Correct Answer

C:

Inspect /etc/chrony.conf and chronyc sources along with UDP reachability. This check targets the relevant state for configuring chrony upstream references and directly assesses the observed behavior. The result should be evaluated against: The client selects an authorized source and achieves the expected synchronization quality.

Incorrect Answers

A:

Check firewall counters for UDP 123 and chrony or ntpd peer reachability. This check is relevant to understanding ntp service port usage but not the most targeted diagnosis of configuring chrony upstream references. The specific check is: Inspect /etc/chrony.conf and chronyc sources along with UDP reachability.

B:

Inspect timedatectl show and the currently active time-sync service state. This check is relevant to detecting system clock synchronization state but not the most targeted diagnosis of configuring chrony upstream references. The specific check is: Inspect /etc/chrony.conf and chronyc sources along with UDP reachability.

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 configuring chrony upstream references. The specific check is: Inspect /etc/chrony.conf and chronyc sources along with UDP reachability.

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