100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 280
A standard user receives permission denied from crontab even though the cron service is healthy. Select THREE measures that follow directly from the root cause and lifecycle risk.
- Run crontab -l as the test user and check the scheduler's access log.
- Manage cron permissions centrally rather than altering service credentials.
- Audit /etc/nsswitch.conf and NSS reachability before troubleshooting remote identities.
- Review the applicable allow/deny files and explicitly authorize the intended user under policy.
- Compare date output from the service and unchanged local-user shell.
- Set the service account shell to an approved nologin program and control other authentication paths.
Explanation
Correct Answers
A:Run crontab -l as the test user and check the scheduler's access log. It verifies that the targeted action (Review the applicable allow/deny files and explicitly authorize the intended user under policy.) achieved its intended outcome.
B:Manage cron permissions centrally rather than altering service credentials. This control detects or prevents the same mechanism before another incident.
D:Review the applicable allow/deny files and explicitly authorize the intended user under policy. It corrects the mechanism identified in the scenario: Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.
Incorrect Answers
C:This option assumes NSS can resolve users through sources other than the local passwd file. The reported symptoms instead call for: Review the applicable allow/deny files and explicitly authorize the intended user under policy.
E:That choice responds to a timezone only for one process failure. In this incident, Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.
F:That choice responds to a nonlogin service identity failure. In this incident, Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.
Question 281
A systemd timer shows next activation but the expected maintenance process never starts. Why does the reported configuration behave this way?
- A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.
- Password-aging fields alone do not enforce a hard account expiration date.
- usermod -G without -a replaces the entire supplementary group list.
- Password hash data should be protected in shadow rather than exposed with world-readable permissions.
Explanation
Correct Answer
A:A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action. That cause connects the stated symptom to the corrective action: Correct the timer Unit target or provide the matching .service with an executable command.
Incorrect Answers
B:That choice responds to a expire entire account on date failure. In this incident, A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.
C:The test for supplementary group preservation would be: Run id username before and after the edit to verify both groups are present. The relevant acceptance check here is: Use systemctl list-timers and journalctl -u for the timer and service to verify activation.
D:This option assumes Password hash data should be protected in shadow rather than exposed with world-readable permissions. The reported symptoms instead call for: Correct the timer Unit target or provide the matching .service with an executable command.
Question 282
A systemd timer shows next activation but the expected maintenance process never starts. Which remedial step follows from the observed mechanism?
- List locales with locale -a and generate/install the required locale through the distribution's mechanism.
- Correct the timer Unit target or provide the matching .service with an executable command.
- Convert from the known source encoding to UTF-8 using iconv with explicit -f and -t options.
- Use chage -M with the appropriate value and review minimum-age and warning settings.
Explanation
Correct Answer
B:Correct the timer Unit target or provide the matching .service with an executable command. It corrects the mechanism identified in the scenario: A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.
Incorrect Answers
A:List locales with locale -a and generate/install the required locale through the distribution's mechanism. could help with available locale not generated; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use systemctl list-timers and journalctl -u for the timer and service to verify activation.
C:It would address character encoding conversion rather than the present problem. The appropriate correction here is: Correct the timer Unit target or provide the matching .service with an executable command.
D:Use chage -M with the appropriate value and review minimum-age and warning settings. could help with password aging audit; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Use systemctl list-timers and journalctl -u for the timer and service to verify activation.
Question 283
A systemd timer shows next activation but the expected maintenance process never starts. What diagnostic result would demonstrate the target behavior?
- Check stat permissions and run a controlled password authentication test.
- Inspect the locked password field and test that password authentication is denied.
- Use systemctl list-timers and journalctl -u for the timer and service to verify activation.
- Run locale and inspect LC_ALL plus category values before and after the change.
Explanation
Correct Answer
C:Use systemctl list-timers and journalctl -u for the timer and service to verify activation. The test is evidence-based because the underlying failure was: A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.
Incorrect Answers
A:The test for shadow file sensitivity would be: Check stat permissions and run a controlled password authentication test. The relevant acceptance check here is: Use systemctl list-timers and journalctl -u for the timer and service to verify activation.
B:That choice responds to a lock password without destroying identity failure. In this incident, A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.
D:Run locale and inspect LC_ALL plus category values before and after the change. belongs to a situation where LC_ALL overrides category-specific locale values and LANG fallback while it is set. Here the evidence supports a different requirement: Use systemctl list-timers and journalctl -u for the timer and service to verify activation.
Question 284
A systemd timer shows next activation but the expected maintenance process never starts. What operational safeguard addresses the root cause?
- Track skeleton revisions and plan explicit migrations for already provisioned homes.
- Deploy and test timer and service units as a linked pair.
- Require diffing the existing group list before any supplementary-group modification.
- Define category-specific locale requirements for programs exchanging numeric data.
Explanation
Correct Answer
B:Deploy and test timer and service units as a linked pair. Sustained checks matter because A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.
Incorrect Answers
A:This belongs to skeleton change is not retroactive, where The skeleton is copied at account home creation; it is not a live template for existing homes. The current issue instead is: A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.
C:That choice responds to a supplementary group preservation failure. In this incident, A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.
D:An all-category locale setting affects more than message translations, including numeric punctuation. That describes a different fault. Here, A timer activates its associated .service unit; a wrong or missing unit mapping prevents the intended action.
Question 285
A systemd timer shows next activation but the expected maintenance process never starts. Choose TWO case-specific steps: one that fixes the issue and one that proves the result.
- Use systemctl list-timers and journalctl -u for the timer and service to verify activation.
- Reserve LC_ALL overrides for narrow test commands and keep persistent locale policy explicit.
- Correct the timer Unit target or provide the matching .service with an executable command.
- Check locale output and an application-generated decimal value in the same process.
- Expire the account's current password with passwd -e or an equivalent chage setting.
Explanation
Correct Answers
A:Use systemctl list-timers and journalctl -u for the timer and service to verify activation. This measures the specific result of applying: Correct the timer Unit target or provide the matching .service with an executable command.
C:Correct the timer Unit target or provide the matching .service with an executable command. The change should be accepted only after this test: Use systemctl list-timers and journalctl -u for the timer and service to verify activation.
Incorrect Answers
B:The test for lc_all overrides lang would be: Run locale and inspect LC_ALL plus category values before and after the change. The relevant acceptance check here is: Use systemctl list-timers and journalctl -u for the timer and service to verify activation.
D:It would address locale category isolation rather than the present problem. The appropriate correction here is: Correct the timer Unit target or provide the matching .service with an executable command.
E:This option assumes A normal password set does not always impose a mandatory first-login change. The reported symptoms instead call for: Correct the timer Unit target or provide the matching .service with an executable command.
Question 286
A daily systemd timer misses its scheduled time while a laptop is powered off and should run after the next boot. Which explanation most directly accounts for the failure in this environment?
- Deleting the account would also disrupt UID ownership records; locking the password is a narrower credential action.
- A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.
- The local-time database link is stale or references a zone file that is no longer valid.
- The password aging fields in the shadow database are not set to the approved maximum age.
Explanation
Correct Answer
B:A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured. This is the explanation that justifies the specific remedy: Set Persistent=true for the OnCalendar timer when missed runs must be honored.
Incorrect Answers
A:Deleting the account would also disrupt UID ownership records; locking the password is a narrower credential action. That describes a different fault. Here, A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.
C:The local-time database link is stale or references a zone file that is no longer valid. belongs to a situation where The local-time database link is stale or references a zone file that is no longer valid. Here the evidence supports a different requirement: A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.
D:The test for password aging audit would be: Run chage -l username to confirm maximum password age and future expiration schedule. The relevant acceptance check here is: Power down through one calendar boundary and confirm a catch-up activation after boot.
Question 287
A daily systemd timer misses its scheduled time while a laptop is powered off and should run after the next boot. What action should be planned as the next targeted correction?
- Use getent passwd username to query the host's configured name-service lookup chain.
- Set the correct system timezone using timedatectl set-timezone with the proper zone identifier.
- Set an account expiration with usermod -e or chage -E using the approved date.
- Set Persistent=true for the OnCalendar timer when missed runs must be honored.
Explanation
Correct Answer
D: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.
Incorrect Answers
A:It would address look up ldap-mapped identity rather than the present problem. The appropriate correction here is: Set Persistent=true for the OnCalendar timer when missed runs must be honored.
B:That choice responds to a system timezone persistent change failure. In this incident, A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.
C:That choice responds to a expire entire account on date failure. In this incident, A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.
Question 288
A daily systemd timer misses its scheduled time while a laptop is powered off and should run after the next boot. What focused test would distinguish a real correction from a cosmetic change?
- Inspect the resolved /etc/localtime target and compare offset before and after.
- Power down through one calendar boundary and confirm a catch-up activation after boot.
- Compare id outputs and numeric ls -n owners on both hosts before granting access.
- Inspect getent passwd and attempt an interactive login in a controlled test.
Explanation
Correct Answer
B:Power down through one calendar boundary and confirm a catch-up activation after boot. The test is evidence-based because the underlying failure was: A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.
Incorrect Answers
A:It would address timezone database symlink rather than the present problem. The appropriate correction here is: Set Persistent=true for the OnCalendar timer when missed runs must be honored.
C:Compare id outputs and numeric ls -n owners on both hosts before granting access. could help with uid collision after cloning; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Power down through one calendar boundary and confirm a catch-up activation after boot.
D:An ordinary interactive login shell in /etc/passwd can permit shell access if credentials and policy allow. That describes a different fault. Here, A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.
Question 289
A daily systemd timer misses its scheduled time while a laptop is powered off and should run after the next boot. Which ongoing control would best reduce the chance of the issue returning?
- Choose character-versus-byte semantics explicitly in internationalized text tooling.
- Manage timezone selection declaratively instead of copying anonymous zone data.
- Document whether missed maintenance runs should be skipped, caught up or deduplicated.
- Reserve LC_ALL overrides for narrow test commands and keep persistent locale policy explicit.
Explanation
Correct Answer
C:Document whether missed maintenance runs should be skipped, caught up or deduplicated. The underlying risk is A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.
Incorrect Answers
A:Choose character-versus-byte semantics explicitly in internationalized text tooling. could help with utf-8 length versus byte length; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Power down through one calendar boundary and confirm a catch-up activation after boot.
B: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: Power down through one calendar boundary and confirm a catch-up activation after boot.
D:This belongs to lc_all overrides lang, where LC_ALL overrides category-specific locale values and LANG fallback while it is set. The current issue instead is: A wall-clock timer does not necessarily catch up missed activations unless persistent semantics are configured.
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.
LPI Level 1 (102-500) Practice Tests