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 All timekeeping depends on one retired fixed address that no longer responds. and needs Configure a supported pool directive and verify successful synchronization.

This fix is aimed at The operator assumes every configured source is selected even though most are unreachable. and would be relevant if A time-source investigation needs evidence of which chrony server is currently selected. The incident instead states All timekeeping depends on one retired fixed address that no longer responds. and needs Configure a supported pool directive and verify successful synchronization.

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 All timekeeping depends on one retired fixed address that no longer responds. and needs Configure a supported pool directive and verify successful synchronization.

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: Restore correct NTP/chrony clock discipline on the unsynchronized host before debugging certificate age.

Configure server or pool directives in the active chrony.conf and restart/reload chronyd appropriately. That operation is designed for the different case: An administrator needs to add approved chrony time sources to a host that uses chronyd. It does not perform the specific action required here: Restore correct NTP/chrony clock discipline on the unsynchronized host before debugging certificate age.

Synchronize the hardware clock from the known-correct system clock with hwclock --systohc, respecting the site's UTC convention. That operation is designed for the different case: A server's hardware RTC drifts away from the correct time stored in the Linux system clock. It does not perform the specific action required here: Restore correct NTP/chrony clock discipline on the unsynchronized host before debugging certificate age.

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 Restore correct NTP/chrony clock discipline on the unsynchronized host before debugging certificate age. satisfies the stated condition.

This explains another Linux operation, namely Configure server or pool directives in the active chrony.conf and restart/reload chronyd appropriately., where chronyd reads its configured upstream NTP sources to discipline the local clock. It does not explain why Restore correct NTP/chrony clock discipline on the unsynchronized host before debugging certificate age. satisfies the stated condition.

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 Restore correct NTP/chrony clock discipline on the unsynchronized host before debugging certificate age. satisfies the stated condition.

That observation checks A small deployment needs multiple DNS-discovered public time servers with changing individual hosts. In this scenario it does not demonstrate Restore correct NTP/chrony clock discipline on the unsynchronized host before debugging certificate age.; the relevant evidence must establish Both nodes report synchronized time and the same certificate passes normal not-before/not-after checks.

That observation checks A time-source investigation needs evidence of which chrony server is currently selected. In this scenario it does not demonstrate Restore correct NTP/chrony clock discipline on the unsynchronized host before debugging certificate age.; the relevant evidence must establish Both nodes report synchronized time and the same certificate passes normal not-before/not-after checks.

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 Restore correct NTP/chrony clock discipline on the unsynchronized host before debugging certificate age.; the relevant evidence must establish Both nodes report synchronized time and the same certificate passes normal not-before/not-after checks.

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 clock is several hours ahead yet certificates are reissued rather than fixing time. The current requirement calls for a different check.

That symptom concerns An administrator needs to add approved chrony time sources to a host that uses chronyd. This concerns a separate requirement, not the one being tested. The relevant failure is The clock is several hours ahead yet certificates are reissued rather than fixing time. The current requirement calls for a different check.

That symptom concerns A small deployment needs multiple DNS-discovered public time servers with changing individual hosts. This concerns a separate requirement, not the one being tested. The relevant failure is The clock is several hours ahead yet certificates are reissued rather than fixing time. The current requirement calls for a different check.

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 clock is several hours ahead yet certificates are reissued rather than fixing time. and needs Correct the node clock and verify time synchronization before making certificate changes.

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 The clock is several hours ahead yet certificates are reissued rather than fixing time. and needs Correct the node clock and verify time synchronization before making certificate changes.

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 clock is several hours ahead yet certificates are reissued rather than fixing time. and needs Correct the node clock and verify time synchronization before making certificate changes.

Set SystemMaxUse in the active journald.conf storage configuration. That operation is designed for the different case: A host must limit the space that persistent systemd journal files can occupy. It does not perform the specific action required here: Run journalctl -u service-name with the exact systemd unit name.

Run journalctl --since 'yesterday 18:00' with appropriate local-time interpretation. That operation is designed for the different case: An admin must inspect log activity only since yesterday at 18:00. It does not perform the specific action required here: Run journalctl -u service-name with the exact systemd unit name.

Configure an rsyslog forwarding action using the supported TCP transport, such as *.* @@loghost:514. That operation is designed for the different case: A syslog administrator must send local rsyslog messages to a central collector over TCP rather than UDP. It does not perform the specific action required here: Run journalctl -u service-name with the exact systemd unit name.

This explains another Linux operation, namely Add a suitable logrotate policy under /etc/logrotate.d/ and test its configuration., where logrotate applies per-log size/time rules, rotates files and can compress retained copies. It does not explain why Run journalctl -u service-name with the exact systemd unit name. satisfies the stated condition.

This explains another Linux operation, namely Use journalctl --vacuum-time=7d or --vacuum-size=... on archived journal files, as policy permits., where Journal vacuum operations remove eligible archived files; active files may require rotation first. It does not explain why Run journalctl -u service-name with the exact systemd unit name. satisfies the stated condition.

This explains another Linux operation, namely Enable persistent journal storage through Storage=persistent and a suitable /var/log/journal configuration., where Persistent journald storage retains records on disk, while volatile storage under /run is lost at reboot. It does not explain why Run journalctl -u service-name with the exact systemd unit name. satisfies the stated condition.

That observation checks An incident responder needs journal records at warning severity or higher but not informational noise. In this scenario it does not demonstrate Run journalctl -u service-name with the exact systemd unit name.; the relevant evidence must establish The resulting output includes the target service errors and excludes unrelated services.

That observation checks A web server's large log file needs periodic rotation, compression and retention. In this scenario it does not demonstrate Run journalctl -u service-name with the exact systemd unit name.; the relevant evidence must establish The resulting output includes the target service errors and excludes unrelated services.

That observation checks A script should emit a tagged diagnostic entry through the system's logging facility rather than merely printing to stdout. In this scenario it does not demonstrate Run journalctl -u service-name with the exact systemd unit name.; the relevant evidence must establish The resulting output includes the target service errors and excludes unrelated services.

This fix is aimed at The operator greps for the word error and misses critical messages with other text. and would be relevant if An incident responder needs journal records at warning severity or higher but not informational noise. The incident instead states A full journal dump hides the failure among unrelated application messages. and needs Filter journal entries by the failing systemd unit.

This fix is aimed at Only current-boot logs are visible after every reboot despite an incident-retention requirement. and would be relevant if A host loses systemd journal records across a reboot because storage is volatile. The incident instead states A full journal dump hides the failure among unrelated application messages. and needs Filter journal entries by the failing systemd unit.

This fix is aimed at The responder runs journalctl with no path and sees only the investigation machine's logs. and would be relevant if A responder has an offline copy of a host's journal directory and wants to inspect it without booting that host. The incident instead states A full journal dump hides the failure among unrelated application messages. and needs Filter journal entries by the failing systemd unit.

Set SystemMaxUse in the active journald.conf storage configuration. That operation is designed for the different case: A host must limit the space that persistent systemd journal files can occupy. It does not perform the specific action required here: Use journalctl -p warning (or an equivalent explicit priority range).

Use journalctl --vacuum-time=7d or --vacuum-size=... on archived journal files, as policy permits. That operation is designed for the different case: A systemd journal fills its configured disk quota and old archived journal data should be pruned. It does not perform the specific action required here: Use journalctl -p warning (or an equivalent explicit priority range).

Run journalctl --since 'yesterday 18:00' with appropriate local-time interpretation. That operation is designed for the different case: An admin must inspect log activity only since yesterday at 18:00. It does not perform the specific action required here: Use journalctl -p warning (or an equivalent explicit priority range).