Pass LPI 102-500 Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
LPI 102-500 Practice Test 28
Question 270
At fictional Harborview Library, the Linux identity and scheduled operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: A database rotation is intended for one specific maintenance window but is accidentally configured to recur every week. The decisive evidence is: The crontab schedule has recurring weekday fields and no one-time at job exists. Which paired action and independent proof BEST satisfies the requirement?
Explanation
Correct Answer
To close the incident, demonstrate that the test job runs in the agreed window and does not execute again on the following week. That addresses the crontab schedule has recurring weekday fields and no one-time at job exists and reflects the rule that at handles one-time deferred execution while cron expresses recurring schedules.
Incorrect Answers
A test that scoped correction: Select the approved timezone and validate the /etc/localtime mapping without changing actual UTC time. Independent acceptance: A known UTC instant displays the correct local wall time including the applicable daylight rules would not demonstrate closure of this condition. The needed proof is the test job runs in the agreed window and does not execute again on the following week.
Scoped correction: Preserve the home and owned data under approved policy before removing or locking the account. Independent acceptance: The user cannot authenticate and an authorized auditor can still access the required retained artifacts. That does not demonstrate the case-specific success condition: the test job runs in the agreed window and does not execute again on the following week. At handles one-time deferred execution while cron expresses recurring schedules.
Scoped correction: Assign a noninteractive shell or disable password login for the daemon account while preserving its required process rights. Independent acceptance: The backup daemon continues running and an interactive login attempt is rejected. That result does not test the original problem, identified by the crontab schedule has recurring weekday fields and no one-time at job exists. Recovery must show that the test job runs in the agreed window and does not execute again on the following week.
Question 271
At fictional Oakridge Services, the Linux identity and scheduled operations team is working while investigating an observed production-like support incident. The Linux scenario is: A database rotation is intended for one specific maintenance window but is accidentally configured to recur every week. The diagnostic evidence is: The crontab schedule has recurring weekday fields and no one-time at job exists. Which bounded step BEST resolves the described problem?
Explanation
Correct Answer
The crontab schedule has recurring weekday fields and no one-time at job exists. At handles one-time deferred execution while cron expresses recurring schedules. The case-specific correction is to use at for a vetted one-time task or a bounded timer that deactivates after execution. Preserve this constraint during the change: Confirm system clock and queue access before relying on any delayed execution.
Incorrect Answers
Another possible response is to select the approved timezone and validate the /etc/localtime mapping without changing actual UTC time. The case evidence instead shows that the crontab schedule has recurring weekday fields and no one-time at job exists. At handles one-time deferred execution while cron expresses recurring schedules.
Preserve the home and owned data under approved policy before removing or locking the account. This does not address the reported incident: a database rotation is intended for one specific maintenance window but is accidentally configured to recur every week. The crontab schedule has recurring weekday fields and no one-time at job exists. The case-specific correction is to use at for a vetted one-time task or a bounded timer that deactivates after execution.
One alternative would be to assign a noninteractive shell or disable password login for the daemon account while preserving its required process rights. The observed evidence instead shows that the crontab schedule has recurring weekday fields and no one-time at job exists. The more relevant correction is to use at for a vetted one-time task or a bounded timer that deactivates after execution.
Question 272
At fictional Oakridge Services, the Linux identity and scheduled operations team is working while investigating an observed production-like support incident. The Linux scenario is: A database rotation is intended for one specific maintenance window but is accidentally configured to recur every week. Which observation MOST directly supports the underlying diagnosis before any changes are made?
Explanation
Correct Answer
The crontab schedule has recurring weekday fields and no one-time at job exists. That observation distinguishes the reported incident because at handles one-time deferred execution while cron expresses recurring schedules. The appropriate response is to use at for a vetted one-time task or a bounded timer that deactivates after execution.
Incorrect Answers
A competing Linux diagnostic finding for Oakridge Services is: timedatectl shows the selected system zone differs from the required site zone while UTC offset is otherwise stable. It does not account for the observation the crontab schedule has recurring weekday fields and no one-time at job exists in the reported situation.
At Oakridge Services, another diagnostic finding is: The selected account deletion command includes home removal while backup and legal hold are incomplete. This would indicate another failure; here the crontab schedule has recurring weekday fields and no one-time at job exists. At handles one-time deferred execution while cron expresses recurring schedules.
At Oakridge Services, a different observation is: getent and shadow policy show an interactive shell and password authentication for a service-only identity. It concerns another dependency. This incident is distinguished by the crontab schedule has recurring weekday fields and no one-time at job exists. At handles one-time deferred execution while cron expresses recurring schedules.
Question 273
At fictional Oakridge Services, the Linux identity and scheduled operations team is working while investigating an observed production-like support incident. The Linux scenario is: A database rotation is intended for one specific maintenance window but is accidentally configured to recur every week. The proposed intervention is: Use at for a vetted one-time task or a bounded timer that deactivates after execution. Which independent result BEST demonstrates a successful correction?
Explanation
Correct Answer
Verify the change by checking that the test job runs in the agreed window and does not execute again on the following week. The original clue was the crontab schedule has recurring weekday fields and no one-time at job exists. The test is meaningful because at handles one-time deferred execution while cron expresses recurring schedules.
Incorrect Answers
At Oakridge Services, another acceptance finding might be: A known UTC instant displays the correct local wall time including the applicable daylight rules. That would still leave the reported failure unproven. An acceptance test must show that the test job runs in the agreed window and does not execute again on the following week.
At Oakridge Services, a different acceptance result would be: The user cannot authenticate and an authorized auditor can still access the required retained artifacts. It may validate a separate setting, but not the required action: use at for a vetted one-time task or a bounded timer that deactivates after execution. The required observation is the test job runs in the agreed window and does not execute again on the following week.
The independent acceptance evidence for Oakridge Services is: The backup daemon continues running and an interactive login attempt is rejected. The evidence relevant to this incident is the crontab schedule has recurring weekday fields and no one-time at job exists. Confirm the corresponding recovery result: The test job runs in the agreed window and does not execute again on the following week.
Question 274
At fictional Oakridge Services, the Linux identity and scheduled operations team is working while investigating an observed production-like support incident. The Linux scenario is: A database rotation is intended for one specific maintenance window but is accidentally configured to recur every week. The relevant evidence is: The crontab schedule has recurring weekday fields and no one-time at job exists. Which Linux administration principle MOST accurately explains the correct response?
Explanation
Correct Answer
The underlying rule is that at handles one-time deferred execution while cron expresses recurring schedules. The crontab schedule has recurring weekday fields and no one-time at job exists. A suitable correction is to use at for a vetted one-time task or a bounded timer that deactivates after execution.
Incorrect Answers
A competing Linux principle for Oakridge Services is: Timezone configuration controls display of instants and is separate from synchronization of system time. The decisive observation, the crontab schedule has recurring weekday fields and no one-time at job exists, requires a different explanation: at handles one-time deferred execution while cron expresses recurring schedules.
A different principle is: the relevant Linux system principle for Oakridge Services is: User account removal and user-owned filesystem data lifecycle are different administrative operations. The causal link actually supported by the crontab schedule has recurring weekday fields and no one-time at job exists is at handles one-time deferred execution while cron expresses recurring schedules.
A competing Linux principle for Oakridge Services is: Service identities should use narrowly scoped authentication and process permissions. However, it does not explain the crontab schedule has recurring weekday fields and no one-time at job exists. The applicable principle is that at handles one-time deferred execution while cron expresses recurring schedules.
Question 275
At fictional Oakridge Services, the Linux identity and scheduled operations team is working while investigating an observed production-like support incident. The Linux scenario is: A database rotation is intended for one specific maintenance window but is accidentally configured to recur every week. The decisive evidence is: The crontab schedule has recurring weekday fields and no one-time at job exists. Which paired action and independent proof BEST satisfies the requirement?
Explanation
Correct Answer
The acceptance evidence is the test job runs in the agreed window and does not execute again on the following week. This checks the intended outcome of use at for a vetted one-time task or a bounded timer that deactivates after execution. At handles one-time deferred execution while cron expresses recurring schedules.
Incorrect Answers
Even verifying scoped correction: Select the approved timezone and validate the /etc/localtime mapping without changing actual UTC time. Independent acceptance: A known UTC instant displays the correct local wall time including the applicable daylight rules leaves the reported failure unproven. An acceptance test must show that the test job runs in the agreed window and does not execute again on the following week.
The alternative outcome is scoped correction: Preserve the home and owned data under approved policy before removing or locking the account. Independent acceptance: The user cannot authenticate and an authorized auditor can still access the required retained artifacts. It may validate a separate setting, but not the required action: use at for a vetted one-time task or a bounded timer that deactivates after execution. The required observation is the test job runs in the agreed window and does not execute again on the following week.
Scoped correction: Assign a noninteractive shell or disable password login for the daemon account while preserving its required process rights. Independent acceptance: The backup daemon continues running and an interactive login attempt is rejected. The evidence relevant to this incident is the crontab schedule has recurring weekday fields and no one-time at job exists. Confirm the corresponding recovery result: The test job runs in the agreed window and does not execute again on the following week.
Question 276
At fictional Silverfield Finance, the Linux identity and scheduled operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: A weekly cleanup never executes after a host is powered off during its scheduled calendar trigger. The diagnostic evidence is: A systemd OnCalendar timer exists but does not have the required Persistent behavior. Which bounded step BEST resolves the described problem?
Explanation
Correct Answer
A weekly cleanup never executes after a host is powered off during its scheduled calendar trigger. The clue a systemd OnCalendar timer exists but does not have the required Persistent behavior supports the bounded action: Configure and enable an appropriate persistent systemd timer and validate its service unit and calendar event. Confirm that a controlled missed-schedule test runs after boot once and the timer next-run time is correct. Preserve this constraint during the change: Persistent timer semantics are not equivalent to replaying every missed schedule individually.
Incorrect Answers
Set the desired durable system zone or an explicit unit-level TZ environment according to policy. It could be useful for another problem, but it does not change a systemd OnCalendar timer exists but does not have the required Persistent behavior. The response needs to configure and enable an appropriate persistent systemd timer and validate its service unit and calendar event.
An alternative action is update the authorized account expiry and password aging settings according to the approved contract window. This incident instead involves a systemd OnCalendar timer exists but does not have the required Persistent behavior. Confirm the scoped change through a controlled missed-schedule test runs after boot once and the timer next-run time is correct.
Convert from the verified source encoding to UTF-8 using an explicit supported conversion and preserve original data. That would not correct the reported a systemd OnCalendar timer exists but does not have the required Persistent behavior. The supported response is to configure and enable an appropriate persistent systemd timer and validate its service unit and calendar event.
Question 277
At fictional Silverfield Finance, the Linux identity and scheduled operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: A weekly cleanup never executes after a host is powered off during its scheduled calendar trigger. Which observation MOST directly supports the underlying diagnosis before any changes are made?
Explanation
Correct Answer
A systemd OnCalendar timer exists but does not have the required Persistent behavior. Systemd timer persistence can catch missed calendar-based activations. This finding supports the targeted response: Configure and enable an appropriate persistent systemd timer and validate its service unit and calendar event.
Incorrect Answers
A competing Linux diagnostic finding for Silverfield Finance is: The shell has an ad hoc TZ variable while system timedatectl configuration remains unchanged. That finding does not isolate the reported issue: a weekly cleanup never executes after a host is powered off during its scheduled calendar trigger. The determining evidence is a systemd OnCalendar timer exists but does not have the required Persistent behavior.
At Silverfield Finance, that alternative suggests: chage output shows the account expiration date in the past, not merely password expiration. The actual diagnostic record shows a systemd OnCalendar timer exists but does not have the required Persistent behavior instead. The difference matters because systemd timer persistence can catch missed calendar-based activations.
At Silverfield Finance, another potential finding is: file and iconv checks show ISO-8859 data read as if it were already UTF-8. That would not establish the cause here. A systemd OnCalendar timer exists but does not have the required Persistent behavior. The case-specific correction is to configure and enable an appropriate persistent systemd timer and validate its service unit and calendar event.
Question 278
At fictional Silverfield Finance, the Linux identity and scheduled operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: A weekly cleanup never executes after a host is powered off during its scheduled calendar trigger. The proposed intervention is: Configure and enable an appropriate persistent systemd timer and validate its service unit and calendar event. Which independent result BEST demonstrates a successful correction?
Explanation
Correct Answer
A controlled missed-schedule test runs after boot once and the timer next-run time is correct. This measures whether the response corrected a systemd OnCalendar timer exists but does not have the required Persistent behavior rather than merely completing a configuration step.
Incorrect Answers
A separate test at Silverfield Finance could show: New process instances use the intended time zone and archived reports retain the correct timestamp interpretation. That would not demonstrate closure of this condition. The needed proof is a controlled missed-schedule test runs after boot once and the timer next-run time is correct.
The independent acceptance evidence for Silverfield Finance is: The contractor can sign in during the approved period but the account is denied after the recorded end date. That does not demonstrate the case-specific success condition: a controlled missed-schedule test runs after boot once and the timer next-run time is correct. Systemd timer persistence can catch missed calendar-based activations.
The independent acceptance evidence for Silverfield Finance is: A test name with accents survives import, search, and export without replacement characters. That result does not test the original problem, identified by a systemd OnCalendar timer exists but does not have the required Persistent behavior. Recovery must show that a controlled missed-schedule test runs after boot once and the timer next-run time is correct.
Question 279
At fictional Silverfield Finance, the Linux identity and scheduled operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: A weekly cleanup never executes after a host is powered off during its scheduled calendar trigger. The relevant evidence is: A systemd OnCalendar timer exists but does not have the required Persistent behavior. Which Linux administration principle MOST accurately explains the correct response?
Explanation
Correct Answer
Systemd timer persistence can catch missed calendar-based activations. The reported symptom arises where a systemd OnCalendar timer exists but does not have the required Persistent behavior. Address it through configure and enable an appropriate persistent systemd timer and validate its service unit and calendar event.
Incorrect Answers
At Silverfield Finance, another Linux system principle is: A process TZ environment override does not necessarily change the host system timezone. The present evidence is a systemd OnCalendar timer exists but does not have the required Persistent behavior, which instead follows from systemd timer persistence can catch missed calendar-based activations.
A competing Linux principle for Silverfield Finance is: Account expiry and password aging are distinct fields in Linux account policy. This describes another relationship, not the cause of a weekly cleanup never executes after a host is powered off during its scheduled calendar trigger. Systemd timer persistence can catch missed calendar-based activations.
At Silverfield Finance, a different Linux system principle is: Character encoding and locale settings determine how byte sequences map to text does not account for a systemd OnCalendar timer exists but does not have the required Persistent behavior. This case is governed by systemd timer persistence can catch missed calendar-based activations.
Question 280
At fictional Silverfield Finance, the Linux identity and scheduled operations team is working during a controlled system-configuration acceptance test. The Linux scenario is: A weekly cleanup never executes after a host is powered off during its scheduled calendar trigger. The decisive evidence is: A systemd OnCalendar timer exists but does not have the required Persistent behavior. Which paired action and independent proof BEST satisfies the requirement?
Explanation
Correct Answer
A controlled missed-schedule test runs after boot once and the timer next-run time is correct. Without that result, the finding a systemd OnCalendar timer exists but does not have the required Persistent behavior would remain unresolved.
Incorrect Answers
A test that scoped correction: Set the desired durable system zone or an explicit unit-level TZ environment according to policy. Independent acceptance: New process instances use the intended time zone and archived reports retain the correct timestamp interpretation would not demonstrate closure of this condition. The needed proof is a controlled missed-schedule test runs after boot once and the timer next-run time is correct.
Scoped correction: Update the authorized account expiry and password aging settings according to the approved contract window. Independent acceptance: The contractor can sign in during the approved period but the account is denied after the recorded end date. That does not demonstrate the case-specific success condition: a controlled missed-schedule test runs after boot once and the timer next-run time is correct. Systemd timer persistence can catch missed calendar-based activations.
Scoped correction: Convert from the verified source encoding to UTF-8 using an explicit supported conversion and preserve original data. Independent acceptance: A test name with accents survives import, search, and export without replacement characters. That result does not test the original problem, identified by a systemd OnCalendar timer exists but does not have the required Persistent behavior. Recovery must show that a controlled missed-schedule test runs after boot once and the timer next-run time is correct.
LPI Level 1 (102-500) Practice Tests
- LPI 102-500 Practice Test 26 - 10 Questions (Last Reviewed 22-Oct-2026)
- LPI 102-500 Practice Test 27 - 10 Questions (Last Reviewed 21-Oct-2026)
- LPI 102-500 Practice Test 28 - 10 Questions (Last Reviewed 20-Oct-2026)
- LPI 102-500 Practice Test 29 - 10 Questions (Last Reviewed 19-Oct-2026)
- LPI 102-500 Practice Test 30 - 10 Questions (Last Reviewed 18-Oct-2026)
