100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 270
A server needs a maintenance command once tonight, not repeated daily or every boot. Select THREE measures that follow directly from the root cause and lifecycle risk.
- Schedule account renames as identity migrations with rollback and service-owner review.
- Use atq to confirm the pending job and check completion after the scheduled time.
- Use at for bounded one-time work and remove expired scheduler artifacts after review.
- Assign unique approved UIDs and reconcile affected file ownership after checking shared storage.
- Compare timedatectl status and date output with date -u.
- Queue the command using at with a concrete future time and check scheduler access rules.
Explanation
Correct Answers
B:Use atq to confirm the pending job and check completion after the scheduled time. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: A recurring cron entry would repeat a one-off maintenance action unnecessarily.
C:Use at for bounded one-time work and remove expired scheduler artifacts after review. It makes the outcome of the targeted repair (Queue the command using at with a concrete future time and check scheduler access rules.) repeatable.
F:Queue the command using at with a concrete future time and check scheduler access rules. It corrects the mechanism identified in the scenario: A recurring cron entry would repeat a one-off maintenance action unnecessarily.
Incorrect Answers
A:It would address ownership after username rename rather than the present problem. The appropriate correction here is: Queue the command using at with a concrete future time and check scheduler access rules.
D:The test for uid collision after cloning would be: Compare id outputs and numeric ls -n owners on both hosts before granting access. The relevant acceptance check here is: Use atq to confirm the pending job and check completion after the scheduled time.
E:Compare timedatectl status and date output with date -u. belongs to a situation where The configured timezone, not NTP synchronization, determines local-time presentation. Here the evidence supports a different requirement: Use atq to confirm the pending job and check completion after the scheduled time.
Question 271
An operator accidentally queues a destructive one-time job under at but has not executed it. Why does the reported configuration behave this way?
- usermod -G without -a replaces the entire supplementary group list.
- LC_ALL overrides category-specific locale values and LANG fallback while it is set.
- Deleting an account without the remove-home option may leave home and mailbox artifacts.
- A queued at job persists until it runs or is explicitly removed.
Explanation
Correct Answer
D:A queued at job persists until it runs or is explicitly removed. A good follow-up is to test this explanation through: Run atq again to verify the removed job no longer appears.
Incorrect Answers
A:It would address supplementary group preservation rather than the present problem. The appropriate correction here is: Identify the queued job with atq and remove its specific job number using atrm.
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: Run atq again to verify the removed job no longer appears.
C:Deleting an account without the remove-home option may leave home and mailbox artifacts. belongs to a situation where Deleting an account without the remove-home option may leave home and mailbox artifacts. Here the evidence supports a different requirement: A queued at job persists until it runs or is explicitly removed.
Question 272
An operator accidentally queues a destructive one-time job under at but has not executed it. Which remedial step follows from the observed mechanism?
- Use a character-aware operation with an explicit UTF-8 locale rather than treating raw bytes as graphemes.
- For approved disposable test accounts, use userdel -r and separately check non-home data.
- Invoke the reporting command with TZ=UTC or set the service's own environment accordingly.
- Identify the queued job with atq and remove its specific job number using atrm.
Explanation
Correct Answer
D:Identify the queued job with atq and remove its specific job number using atrm. This is appropriate because A queued at job persists until it runs or is explicitly removed.
Incorrect Answers
A:This option assumes UTF-8 encodes some characters as multiple bytes, so byte counts and character counts can differ. The reported symptoms instead call for: Identify the queued job with atq and remove its specific job number using atrm.
B:The test for remove account and managed home would be: Confirm getent passwd no longer resolves the account and its intended home path was removed. The relevant acceptance check here is: Run atq again to verify the removed job no longer appears.
C:That choice responds to a timezone only for one process failure. In this incident, A queued at job persists until it runs or is explicitly removed.
Question 273
An operator accidentally queues a destructive one-time job under at but has not executed it. What focused test would distinguish a real correction from a cosmetic change?
- Compare getent and direct /etc/passwd results for the same network identity.
- Run atq again to verify the removed job no longer appears.
- Create one new account and compare it with an older account to establish the copy boundary.
- Check stat permissions and run a controlled password authentication test.
Explanation
Correct Answer
B:Run atq again to verify the removed job no longer appears. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: A queued at job persists until it runs or is explicitly removed.
Incorrect Answers
A:The test for look up ldap-mapped identity would be: Compare getent and direct /etc/passwd results for the same network identity. The relevant acceptance check here is: Run atq again to verify the removed job no longer appears.
C:It would address skeleton change is not retroactive rather than the present problem. The appropriate correction here is: Identify the queued job with atq and remove its specific job number using atrm.
D:Check stat permissions and run a controlled password authentication test. could help with shadow file sensitivity; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Run atq again to verify the removed job no longer appears.
Question 274
An operator accidentally queues a destructive one-time job under at but has not executed it. What should the team standardize to prevent similar incidents?
- Audit /etc/nsswitch.conf and NSS reachability before troubleshooting remote identities.
- Use scoped timezone overrides for service-specific reporting requirements.
- Track skeleton revisions and plan explicit migrations for already provisioned homes.
- Require peer review of high-impact one-time scheduled operations.
Explanation
Correct Answer
D:Require peer review of high-impact one-time scheduled operations. It prevents repetition of the condition: A queued at job persists until it runs or is explicitly removed.
Incorrect Answers
A:NSS can resolve users through sources other than the local passwd file. That describes a different fault. Here, A queued at job persists until it runs or is explicitly removed.
B:Use scoped timezone overrides for service-specific reporting requirements. could help with timezone only for one process; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Run atq again to verify the removed job no longer appears.
C:The skeleton is copied at account home creation; it is not a live template for existing homes. That describes a different fault. Here, A queued at job persists until it runs or is explicitly removed.
Question 275
An operator accidentally queues a destructive one-time job under at but has not executed it. Which TWO measures belong together as the direct correction and a discriminating verification? Select TWO.
- Compare id outputs and numeric ls -n owners on both hosts before granting access.
- Treat initial credential change and full account expiration as separate identity controls.
- Identify the queued job with atq and remove its specific job number using atrm.
- Run atq again to verify the removed job no longer appears.
- Plan a coordinated usermod -l and -d -m change with home-path and service references checked.
Explanation
Correct Answers
C:Identify the queued job with atq and remove its specific job number using atrm. This is appropriate because A queued at job persists until it runs or is explicitly removed.
D:Run atq again to verify the removed job no longer appears. This measures the specific result of applying: Identify the queued job with atq and remove its specific job number using atrm.
Incorrect Answers
A:It would address uid collision after cloning rather than the present problem. The appropriate correction here is: Identify the queued job with atq and remove its specific job number using atrm.
B:That choice responds to a expire password at next login failure. In this incident, A queued at job persists until it runs or is explicitly removed.
E:usermod -l changes the login name but does not automatically move every home pathname. That describes a different fault. Here, A queued at job persists until it runs or is explicitly removed.
Question 276
A standard user receives permission denied from crontab even though the cron service is healthy. Which explanation most directly accounts for the failure in this environment?
- The configured timezone, not NTP synchronization, determines local-time presentation.
- Password-aging fields alone do not enforce a hard account expiration date.
- Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.
- An ordinary interactive login shell in /etc/passwd can permit shell access if credentials and policy allow.
Explanation
Correct Answer
C:Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules. Addressing the cause requires: Review the applicable allow/deny files and explicitly authorize the intended user under policy.
Incorrect Answers
A:The test for system timezone persistent change would be: Compare timedatectl status and date output with date -u. The relevant acceptance check here is: Run crontab -l as the test user and check the scheduler's access log.
B:Password-aging fields alone do not enforce a hard account expiration date. could help with expire entire account on date; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Run crontab -l as the test user and check the scheduler's access log.
D:An ordinary interactive login shell in /etc/passwd can permit shell access if credentials and policy allow. belongs to a situation where An ordinary interactive login shell in /etc/passwd can permit shell access if credentials and policy allow. Here the evidence supports a different requirement: Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.
Question 277
A standard user receives permission denied from crontab even though the cron service is healthy. What should the administrator do to correct this behavior?
- Review the applicable allow/deny files and explicitly authorize the intended user under policy.
- Set the intended primary group with usermod -g while retaining necessary supplemental groups.
- Use a character-aware operation with an explicit UTF-8 locale rather than treating raw bytes as graphemes.
- Use useradd with home creation enabled or provision the home securely with correct ownership.
Explanation
Correct Answer
A:Review the applicable allow/deny files and explicitly authorize the intended user under policy. Unlike a broad workaround, it targets the observed cause: Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.
Incorrect Answers
B:Set the intended primary group with usermod -g while retaining necessary supplemental groups. belongs to a situation where The primary GID, not the complete supplementary group list, normally determines the default file group. Here the evidence supports a different requirement: Review the applicable allow/deny files and explicitly authorize the intended user under policy.
C:This belongs to utf-8 length versus byte length, where UTF-8 encodes some characters as multiple bytes, so byte counts and character counts can differ. The current issue instead is: Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.
D:That choice responds to a create home for new local account failure. In this incident, Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.
Question 278
A standard user receives permission denied from crontab even though the cron service is healthy. Which check would provide the strongest evidence that the fix worked?
- Inspect getent passwd and attempt an interactive login in a controlled test.
- Compare id outputs and numeric ls -n owners on both hosts before granting access.
- Run crontab -l as the test user and check the scheduler's access log.
- Create one new account and compare it with an older account to establish the copy boundary.
Explanation
Correct Answer
C:Run crontab -l as the test user and check the scheduler's access log. The test is evidence-based because the underlying failure was: Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.
Incorrect Answers
A:This belongs to nonlogin service identity, where An ordinary interactive login shell in /etc/passwd can permit shell access if credentials and policy allow. The current issue instead is: Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.
B:That choice responds to a uid collision after cloning failure. In this incident, Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.
D:The skeleton is copied at account home creation; it is not a live template for existing homes. That describes a different fault. Here, Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.
Question 279
A standard user receives permission denied from crontab even though the cron service is healthy. What longer-term control best supports this requirement?
- Manage cron permissions centrally rather than altering service credentials.
- Treat timezone selection and accurate UTC clock synchronization as separate operations.
- Maintain centralized UID/GID allocation for cloned and networked Linux systems.
- Manage timezone selection declaratively instead of copying anonymous zone data.
Explanation
Correct Answer
A:Manage cron permissions centrally rather than altering service credentials. Sustained checks matter because Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.
Incorrect Answers
B:That choice responds to a system timezone persistent change failure. In this incident, Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.
C:Unix file ownership is keyed to numeric UID and GID rather than display login names. That describes a different fault. Here, Cron access can be restricted by /etc/cron.allow or /etc/cron.deny according to implementation rules.
D:It would address timezone database symlink rather than the present problem. The appropriate correction here is: Review the applicable allow/deny files and explicitly authorize the intended user under policy.
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.
LPI Level 1 (102-500) Practice Tests