100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 290
A daily systemd timer misses its scheduled time while a laptop is powered off and should run after the next boot. Which THREE actions form a suitable remediation, verification and prevention plan? Select THREE.
- Document whether missed maintenance runs should be skipped, caught up or deduplicated.
- Record file encodings at interchange boundaries rather than guessing from appearance.
- Set Persistent=true for the OnCalendar timer when missed runs must be honored.
- Power down through one calendar boundary and confirm a catch-up activation after boot.
- List locales with locale -a and generate/install the required locale through the distribution's mechanism.
- Run chage -l username to confirm maximum password age and future expiration schedule.
Explanation
Correct Answers
A:Document whether missed maintenance runs should be skipped, caught up or deduplicated. It preserves the corrective behavior established through: Set Persistent=true for the OnCalendar timer when missed runs must be honored.
C:Set Persistent=true for the OnCalendar timer when missed runs must be honored. Unlike a broad workaround, it targets the observed cause: A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.
D:Power down through one calendar boundary and confirm a catch-up activation after boot. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.
Incorrect Answers
B:This option assumes The bytes use a different character encoding than the consumer expects. The reported symptoms instead call for: Set Persistent=true for the OnCalendar timer when missed runs must be honored.
E:This belongs to available locale not generated, where The requested locale name may not be generated or installed locally. The current issue instead is: A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.
F:Run chage -l username to confirm maximum password age and future expiration schedule. belongs to a situation where The password aging fields in the shadow database are not set to the approved maximum age. Here the evidence supports a different requirement: Power down through one calendar boundary and confirm a catch-up activation after boot.
Question 291
A job that must run at 03:15 each weekday uses an OnBootSec timer and instead runs relative to reboot time. What underlying Linux behavior should the administrator identify first?
- Password-aging fields alone do not enforce a hard account expiration date.
- Monotonic timers measure elapsed time rather than matching calendar dates and weekdays.
- The account creation procedure did not provision its home path and default skeleton files.
- Deleting an account without the remove-home option may leave home and mailbox artifacts.
Explanation
Correct Answer
B:Monotonic timers measure elapsed time rather than matching calendar dates and weekdays. The administrator should distinguish this from unrelated symptoms by checking: Inspect systemd-analyze calendar output and the next trigger from systemctl list-timers.
Incorrect Answers
A:It would address expire entire account on date rather than the present problem. The appropriate correction here is: Use OnCalendar with the appropriate weekday/time expression in the timer unit.
C:The account creation procedure did not provision its home path and default skeleton files. belongs to a situation where The account creation procedure did not provision its home path and default skeleton files. Here the evidence supports a different requirement: Monotonic timers measure elapsed time rather than matching calendar dates and weekdays.
D:Deleting an account without the remove-home option may leave home and mailbox artifacts. That describes a different fault. Here, Monotonic timers measure elapsed time rather than matching calendar dates and weekdays.
Question 292
A job that must run at 03:15 each weekday uses an OnBootSec timer and instead runs relative to reboot time. What action should be planned as the next targeted correction?
- Expire the account's current password with passwd -e or an equivalent chage setting.
- Apply reviewed updates separately to existing accounts or distribute a managed dotfile policy.
- Use a character-aware operation with an explicit UTF-8 locale rather than treating raw bytes as graphemes.
- Use OnCalendar with the appropriate weekday/time expression in the timer unit.
Explanation
Correct Answer
D:Use OnCalendar with the appropriate weekday/time expression in the timer unit. It corrects the mechanism identified in the scenario: Monotonic timers measure elapsed time rather than matching calendar dates and weekdays.
Incorrect Answers
A:The test for expire password at next login would be: Review chage -l for password expiration and perform a controlled first login. The relevant acceptance check here is: Inspect systemd-analyze calendar output and the next trigger from systemctl list-timers.
B:The test for skeleton change is not retroactive would be: Create one new account and compare it with an older account to establish the copy boundary. The relevant acceptance check here is: Inspect systemd-analyze calendar output and the next trigger from systemctl list-timers.
C:Use a character-aware operation with an explicit UTF-8 locale rather than treating raw bytes as graphemes. could help with utf-8 length versus byte length; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Inspect systemd-analyze calendar output and the next trigger from systemctl list-timers.
Question 293
A job that must run at 03:15 each weekday uses an OnBootSec timer and instead runs relative to reboot time. Which check would provide the strongest evidence that the fix worked?
- Run the parser under two installed locales and compare successful machine-readable results.
- Inspect systemd-analyze calendar output and the next trigger from systemctl list-timers.
- Run id and create a test file to observe its default group ownership.
- Compare known accented characters and inspect conversion errors before importing.
Explanation
Correct Answer
B:Inspect systemd-analyze calendar output and the next trigger from systemctl list-timers. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
Incorrect Answers
A:Run the parser under two installed locales and compare successful machine-readable results. belongs to a situation where Locale-dependent human-readable output changes with language settings, so the parser is fragile. Here the evidence supports a different requirement: Inspect systemd-analyze calendar output and the next trigger from systemctl list-timers.
C:This belongs to primary group correction, where The primary GID, not the complete supplementary group list, normally determines the default file group. The current issue instead is: Monotonic timers measure elapsed time rather than matching calendar dates and weekdays.
D:Compare known accented characters and inspect conversion errors before importing. belongs to a situation where The bytes use a different character encoding than the consumer expects. Here the evidence supports a different requirement: Inspect systemd-analyze calendar output and the next trigger from systemctl list-timers.
Question 294
A job that must run at 03:15 each weekday uses an OnBootSec timer and instead runs relative to reboot time. What operational safeguard addresses the root cause?
- Choose calendar versus monotonic schedules from the actual business requirement.
- Reserve LC_ALL overrides for narrow test commands and keep persistent locale policy explicit.
- Manage timezone selection declaratively instead of copying anonymous zone data.
- Treat timezone selection and accurate UTC clock synchronization as separate operations.
Explanation
Correct Answer
A:Choose calendar versus monotonic schedules from the actual business requirement. This control detects or prevents the same mechanism before another incident.
Incorrect Answers
B:It would address lc_all overrides lang rather than the present problem. The appropriate correction here is: Use OnCalendar with the appropriate weekday/time expression in the timer unit.
C:The test for timezone database symlink would be: Inspect the resolved /etc/localtime target and compare offset before and after. The relevant acceptance check here is: Inspect systemd-analyze calendar output and the next trigger from systemctl list-timers.
D:The test for system timezone persistent change would be: Compare timedatectl status and date output with date -u. The relevant acceptance check here is: Inspect systemd-analyze calendar output and the next trigger from systemctl list-timers.
Question 295
A job that must run at 03:15 each weekday uses an OnBootSec timer and instead runs relative to reboot time. Which TWO options provide a coherent remediation-and-test response to this incident?
- Set the correct system timezone using timedatectl set-timezone with the proper zone identifier.
- Use OnCalendar with the appropriate weekday/time expression in the timer unit.
- Compare id outputs and numeric ls -n owners on both hosts before granting access.
- Inspect systemd-analyze calendar output and the next trigger from systemctl list-timers.
- Treat initial credential change and full account expiration as separate identity controls.
Explanation
Correct Answers
B:Use OnCalendar with the appropriate weekday/time expression in the timer unit. Unlike a broad workaround, it targets the observed cause: Monotonic timers measure elapsed time rather than matching calendar dates and weekdays.
D:Inspect systemd-analyze calendar output and the next trigger from systemctl list-timers. This check is tied to the expected behavior rather than mere process uptime.
Incorrect Answers
A:Set the correct system timezone using timedatectl set-timezone with the proper zone identifier. could help with system timezone persistent change; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Inspect systemd-analyze calendar output and the next trigger from systemctl list-timers.
C:It would address uid collision after cloning rather than the present problem. The appropriate correction here is: Use OnCalendar with the appropriate weekday/time expression in the timer unit.
E:Treat initial credential change and full account expiration as separate identity controls. belongs to a situation where A normal password set does not always impose a mandatory first-login change. Here the evidence supports a different requirement: Choose calendar versus monotonic schedules from the actual business requirement.
Question 296
A cron script writes its output to the wrong location because it assumes the interactive current directory. Which mechanism best explains the difference between expectation and result?
- The bytes use a different character encoding than the consumer expects.
- Scheduled jobs do not inherit the caller's working directory from an earlier terminal session.
- Unix file ownership is keyed to numeric UID and GID rather than display login names.
- The account creation procedure did not provision its home path and default skeleton files.
Explanation
Correct Answer
B:Scheduled jobs do not inherit the caller's working directory from an earlier terminal session. That cause connects the stated symptom to the corrective action: Use absolute paths or explicitly cd into a validated task directory before writing.
Incorrect Answers
A:The bytes use a different character encoding than the consumer expects. could help with character encoding conversion; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Run under a neutral working directory and locate the generated output exactly.
C:This belongs to uid collision after cloning, where Unix file ownership is keyed to numeric UID and GID rather than display login names. The current issue instead is: Scheduled jobs do not inherit the caller's working directory from an earlier terminal session.
D:This option assumes The account creation procedure did not provision its home path and default skeleton files. The reported symptoms instead call for: Use absolute paths or explicitly cd into a validated task directory before writing.
Question 297
A cron script writes its output to the wrong location because it assumes the interactive current directory. Which remedial step follows from the observed mechanism?
- Use absolute paths or explicitly cd into a validated task directory before writing.
- Use usermod -aG docker username and preserve the other supplementary memberships.
- Convert from the known source encoding to UTF-8 using iconv with explicit -f and -t options.
- Set an account expiration with usermod -e or chage -E using the approved date.
Explanation
Correct Answer
A:Use absolute paths or explicitly cd into a validated task directory before writing. The change should be accepted only after this test: Run under a neutral working directory and locate the generated output exactly.
Incorrect Answers
B:This belongs to supplementary group preservation, where usermod -G without -a replaces the entire supplementary group list. The current issue instead is: Scheduled jobs do not inherit the caller's working directory from an earlier terminal session.
C:That choice responds to a character encoding conversion failure. In this incident, Scheduled jobs do not inherit the caller's working directory from an earlier terminal session.
D:The test for expire entire account on date would be: Check chage -l and attempt a controlled login after the expiration boundary. The relevant acceptance check here is: Run under a neutral working directory and locate the generated output exactly.
Question 298
A cron script writes its output to the wrong location because it assumes the interactive current directory. What diagnostic result would demonstrate the target behavior?
- Run under a neutral working directory and locate the generated output exactly.
- Compare getent and direct /etc/passwd results for the same network identity.
- Check chage -l and attempt a controlled login after the expiration boundary.
- Compare id outputs and numeric ls -n owners on both hosts before granting access.
Explanation
Correct Answer
A:Run under a neutral working directory and locate the generated output exactly. The observation confirms the diagnosis or falsifies it before declaring the incident resolved.
Incorrect Answers
B:Compare getent and direct /etc/passwd results for the same network identity. could help with look up ldap-mapped identity; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Run under a neutral working directory and locate the generated output exactly.
C:The test for expire entire account on date would be: Check chage -l and attempt a controlled login after the expiration boundary. The relevant acceptance check here is: Run under a neutral working directory and locate the generated output exactly.
D:That choice responds to a uid collision after cloning failure. In this incident, Scheduled jobs do not inherit the caller's working directory from an earlier terminal session.
Question 299
A cron script writes its output to the wrong location because it assumes the interactive current directory. What should the team standardize to prevent similar incidents?
- Provision required locales in the host image before assigning them to users.
- Use scoped timezone overrides for service-specific reporting requirements.
- Make scheduled scripts independent of the launching session's current directory.
- Treat timezone selection and accurate UTC clock synchronization as separate operations.
Explanation
Correct Answer
C:Make scheduled scripts independent of the launching session's current directory. The underlying risk is Scheduled jobs do not inherit the caller's working directory from an earlier terminal session.
Incorrect Answers
A:The test for available locale not generated would be: Run locale -a and a test locale-sensitive command after installation. The relevant acceptance check here is: Run under a neutral working directory and locate the generated output exactly.
B:Use scoped timezone overrides for service-specific reporting requirements. belongs to a situation where Timezone conversion for one process can be controlled with TZ, independent of system-wide settings. Here the evidence supports a different requirement: Make scheduled scripts independent of the launching session's current directory.
D:It would address system timezone persistent change rather than the present problem. The appropriate correction here is: Use absolute paths or explicitly cd into a validated task directory before writing.
Question 300
A cron script writes its output to the wrong location because it assumes the interactive current directory. Select THREE measures that follow directly from the root cause and lifecycle risk.
- Use passwd -l for the local password and separately review other authentication methods such as SSH keys.
- Run locale -a and a test locale-sensitive command after installation.
- Include password-aging fields in regular privileged-identity policy audits.
- Make scheduled scripts independent of the launching session's current directory.
- Use absolute paths or explicitly cd into a validated task directory before writing.
- Run under a neutral working directory and locate the generated output exactly.
Explanation
Correct Answers
D:Make scheduled scripts independent of the launching session's current directory. Sustained checks matter because Scheduled jobs do not inherit the caller's working directory from an earlier terminal session.
E:Use absolute paths or explicitly cd into a validated task directory before writing. Unlike a broad workaround, it targets the observed cause: Scheduled jobs do not inherit the caller's working directory from an earlier terminal session.
F:Run under a neutral working directory and locate the generated output exactly. It verifies that the targeted action (Use absolute paths or explicitly cd into a validated task directory before writing.) achieved its intended outcome.
Incorrect Answers
A:The test for lock password without destroying identity would be: Inspect the locked password field and test that password authentication is denied. The relevant acceptance check here is: Run under a neutral working directory and locate the generated output exactly.
B:This belongs to available locale not generated, where The requested locale name may not be generated or installed locally. The current issue instead is: Scheduled jobs do not inherit the caller's working directory from an earlier terminal session.
C:Include password-aging fields in regular privileged-identity policy audits. belongs to a situation where The password aging fields in the shadow database are not set to the approved maximum age. Here the evidence supports a different requirement: Make scheduled scripts independent of the launching session's current directory.
LPI Level 1 (102-500) Practice Tests