Pass Your LPI 102-500 Exam Easy!

This fix is aimed at The clock is several hours ahead yet certificates are reissued rather than fixing time. and would be relevant if Two Linux nodes disagree about certificate validity because one has synchronized time and the other does not. The incident instead states The system clock is corrected by NTP but the RTC still carries the old value across reboot. and needs Write the corrected time to the hardware clock using the intended UTC/localtime convention.

This fix is aimed at Only an obsolete ntp.conf file was edited, so the running chronyd still uses its old sources. and would be relevant if An administrator needs to add approved chrony time sources to a host that uses chronyd. The incident instead states The system clock is corrected by NTP but the RTC still carries the old value across reboot. and needs Write the corrected time to the hardware clock using the intended UTC/localtime convention.

This fix is aimed at The team runs chronyc on a host with ntpd only and receives no chronyd response. and would be relevant if A legacy host uses ntpd and the admin needs to view peer delay, offset and reachability. The incident instead states The system clock is corrected by NTP but the RTC still carries the old value across reboot. and needs Write the corrected time to the hardware clock using the intended UTC/localtime convention.

Restore correct NTP/chrony clock discipline on the unsynchronized host before debugging certificate age. That operation is designed for the different case: Two Linux nodes disagree about certificate validity because one has synchronized time and the other does not. It does not perform the specific action required here: Configure server or pool directives in the active chrony.conf and restart/reload chronyd appropriately.

Use an approved pool.ntp.org pool directive with appropriate chrony/ntpd pool syntax. That operation is designed for the different case: A small deployment needs multiple DNS-discovered public time servers with changing individual hosts. It does not perform the specific action required here: Configure server or pool directives in the active chrony.conf and restart/reload chronyd appropriately.

Use ntpq -p to inspect NTP peer associations where ntpd exposes that interface. That operation is designed for the different case: A legacy host uses ntpd and the admin needs to view peer delay, offset and reachability. It does not perform the specific action required here: Configure server or pool directives in the active chrony.conf and restart/reload chronyd appropriately.

This explains another Linux operation, namely Synchronize the hardware clock from the known-correct system clock with hwclock --systohc, respecting the site's UTC convention., where hwclock explicitly reads or writes the hardware real-time clock independently of the running system clock. It does not explain why Configure server or pool directives in the active chrony.conf and restart/reload chronyd appropriately. satisfies the stated condition.

This explains another Linux operation, namely Restore correct NTP/chrony clock discipline on the unsynchronized host before debugging certificate age., where Certificate validity checks depend on the current instant; a clock far in the past or future can cause false failures. It does not explain why Configure server or pool directives in the active chrony.conf and restart/reload chronyd appropriately. satisfies the stated condition.

This explains another Linux operation, namely Use ntpq -p to inspect NTP peer associations where ntpd exposes that interface., where ntpq queries the traditional NTP daemon for peer state and selection indicators. It does not explain why Configure server or pool directives in the active chrony.conf and restart/reload chronyd appropriately. satisfies the stated condition.

That observation checks A systemd Linux host has the wrong system date even though its timezone setting is correct. In this scenario it does not demonstrate Configure server or pool directives in the active chrony.conf and restart/reload chronyd appropriately.; the relevant evidence must establish chronyc sources reports approved reachable sources with usable measurements.

That observation checks Two Linux nodes disagree about certificate validity because one has synchronized time and the other does not. In this scenario it does not demonstrate Configure server or pool directives in the active chrony.conf and restart/reload chronyd appropriately.; the relevant evidence must establish chronyc sources reports approved reachable sources with usable measurements.

That observation checks A legacy host uses ntpd and the admin needs to view peer delay, offset and reachability. In this scenario it does not demonstrate Configure server or pool directives in the active chrony.conf and restart/reload chronyd appropriately.; the relevant evidence must establish chronyc sources reports approved reachable sources with usable measurements.

That symptom concerns A time-source investigation needs evidence of which chrony server is currently selected. This concerns a separate requirement, not the one being tested. The relevant failure is Only an obsolete ntp.conf file was edited, so the running chronyd still uses its old sources. The current requirement calls for a different check.

That symptom concerns A server's hardware RTC drifts away from the correct time stored in the Linux system clock. This concerns a separate requirement, not the one being tested. The relevant failure is Only an obsolete ntp.conf file was edited, so the running chronyd still uses its old sources. The current requirement calls for a different check.

That symptom concerns A systemd Linux host has the wrong system date even though its timezone setting is correct. This concerns a separate requirement, not the one being tested. The relevant failure is Only an obsolete ntp.conf file was edited, so the running chronyd still uses its old sources. The current requirement calls for a different check.

This fix is aimed at The system clock is corrected by NTP but the RTC still carries the old value across reboot. and would be relevant if A server's hardware RTC drifts away from the correct time stored in the Linux system clock. The incident instead states Only an obsolete ntp.conf file was edited, so the running chronyd still uses its old sources. and needs Change the configuration file actually read by chronyd and validate source reachability.

This fix is aimed at The clock is several hours ahead yet certificates are reissued rather than fixing time. and would be relevant if Two Linux nodes disagree about certificate validity because one has synchronized time and the other does not. The incident instead states Only an obsolete ntp.conf file was edited, so the running chronyd still uses its old sources. and needs Change the configuration file actually read by chronyd and validate source reachability.

This fix is aimed at The administrator changes the timezone to hide a several-minute clock error. and would be relevant if A systemd Linux host has the wrong system date even though its timezone setting is correct. The incident instead states Only an obsolete ntp.conf file was edited, so the running chronyd still uses its old sources. and needs Change the configuration file actually read by chronyd and validate source reachability.

Use an approved pool.ntp.org pool directive with appropriate chrony/ntpd pool syntax. That operation is designed for the different case: A small deployment needs multiple DNS-discovered public time servers with changing individual hosts. It does not perform the specific action required here: Run chronyc sources -v and inspect the source-selection marker and reachability.

Use ntpq -p to inspect NTP peer associations where ntpd exposes that interface. That operation is designed for the different case: A legacy host uses ntpd and the admin needs to view peer delay, offset and reachability. It does not perform the specific action required here: Run chronyc sources -v and inspect the source-selection marker and reachability.

Use timedatectl or the appropriate privileged date mechanism to set the system clock, then restore NTP sync. That operation is designed for the different case: A systemd Linux host has the wrong system date even though its timezone setting is correct. It does not perform the specific action required here: Run chronyc sources -v and inspect the source-selection marker and reachability.

This explains another Linux operation, namely Use an approved pool.ntp.org pool directive with appropriate chrony/ntpd pool syntax., where A pool can resolve to a rotating set of time servers and improves source diversity over a hardcoded single address. It does not explain why Run chronyc sources -v and inspect the source-selection marker and reachability. satisfies the stated condition.

This explains another Linux operation, namely Use ntpq -p to inspect NTP peer associations where ntpd exposes that interface., where ntpq queries the traditional NTP daemon for peer state and selection indicators. It does not explain why Run chronyc sources -v and inspect the source-selection marker and reachability. satisfies the stated condition.

This explains another Linux operation, namely Use timedatectl or the appropriate privileged date mechanism to set the system clock, then restore NTP sync., where The real-time system clock and the timezone describe different things; changing the timezone cannot repair a wrong UTC instant. It does not explain why Run chronyc sources -v and inspect the source-selection marker and reachability. satisfies the stated condition.

That observation checks A server's hardware RTC drifts away from the correct time stored in the Linux system clock. In this scenario it does not demonstrate Run chronyc sources -v and inspect the source-selection marker and reachability.; the relevant evidence must establish An expected source has reachable samples and a selection marker in chronyc output.

That observation checks Two Linux nodes disagree about certificate validity because one has synchronized time and the other does not. In this scenario it does not demonstrate Run chronyc sources -v and inspect the source-selection marker and reachability.; the relevant evidence must establish An expected source has reachable samples and a selection marker in chronyc output.

That observation checks A legacy host uses ntpd and the admin needs to view peer delay, offset and reachability. In this scenario it does not demonstrate Run chronyc sources -v and inspect the source-selection marker and reachability.; the relevant evidence must establish An expected source has reachable samples and a selection marker in chronyc output.

That symptom concerns Two Linux nodes disagree about certificate validity because one has synchronized time and the other does not. This concerns a separate requirement, not the one being tested. The relevant failure is The operator assumes every configured source is selected even though most are unreachable. The current requirement calls for a different check.

That symptom concerns A server's hardware RTC drifts away from the correct time stored in the Linux system clock. This concerns a separate requirement, not the one being tested. The relevant failure is The operator assumes every configured source is selected even though most are unreachable. The current requirement calls for a different check.

That symptom concerns A legacy host uses ntpd and the admin needs to view peer delay, offset and reachability. This concerns a separate requirement, not the one being tested. The relevant failure is The operator assumes every configured source is selected even though most are unreachable. The current requirement calls for a different check.

This fix is aimed at The administrator changes the timezone to hide a several-minute clock error. and would be relevant if A systemd Linux host has the wrong system date even though its timezone setting is correct. The incident instead states The operator assumes every configured source is selected even though most are unreachable. and needs Use chronyc sources or tracking to identify the selected reference and failed reachability.

This fix is aimed at The clock is several hours ahead yet certificates are reissued rather than fixing time. and would be relevant if Two Linux nodes disagree about certificate validity because one has synchronized time and the other does not. The incident instead states The operator assumes every configured source is selected even though most are unreachable. and needs Use chronyc sources or tracking to identify the selected reference and failed reachability.

This fix is aimed at All timekeeping depends on one retired fixed address that no longer responds. and would be relevant if A small deployment needs multiple DNS-discovered public time servers with changing individual hosts. The incident instead states The operator assumes every configured source is selected even though most are unreachable. and needs Use chronyc sources or tracking to identify the selected reference and failed reachability.