100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 470
A local /etc/aliases change routes root mail to the duty mailbox only on paper; new messages still go to root. Which THREE case-specific steps cover immediate repair, test evidence and sustained control?
- Print a known standard test page and examine CUPS logs for filter errors.
- Design time-source redundancy and restrict untrusted NTP servers.
- Use journalctl -p err to include error and more severe messages.
- Send a test message to root and confirm it reaches the authorized duty destination.
- Run newaliases or the MTA's supported alias database rebuild after updating /etc/aliases.
- Treat alias database rebuild and delivery tests as part of change procedures.
Explanation
Correct Answers
D:Send a test message to root and confirm it reaches the authorized duty destination. It verifies that the targeted action (Run newaliases or the MTA's supported alias database rebuild after updating /etc/aliases.) achieved its intended outcome.
E:Run newaliases or the MTA's supported alias database rebuild after updating /etc/aliases. It is the direct response; verify the result by: Send a test message to root and confirm it reaches the authorized duty destination.
F:Treat alias database rebuild and delivery tests as part of change procedures. This control detects or prevents the same mechanism before another incident.
Incorrect Answers
A:It would address cups driver and filter mismatch rather than the present problem. The appropriate correction here is: Run newaliases or the MTA's supported alias database rebuild after updating /etc/aliases.
B:The test for chrony source trust and failover would be: Take the primary source offline in a test and inspect peer selection and offset stability. The relevant acceptance check here is: Send a test message to root and confirm it reaches the authorized duty destination.
C:The test for filter critical journal priority would be: Generate a controlled error log and confirm lower-priority messages are excluded. The relevant acceptance check here is: Send a test message to root and confirm it reaches the authorized duty destination.
Question 471
A local account needs messages forwarded to an approved mailbox without changing the global alias map. Which mechanism best explains the difference between expectation and result?
- Global aliases are not required for a per-account redirect supported by ~/.forward.
- A successful daemon restart does not prove that a message reaches its intended local or remote destination.
- The time client is correcting a large offset gradually rather than stepping it under approved conditions.
- The hardware clock did not receive the corrected system time and retains an old value.
Explanation
Correct Answer
A:Global aliases are not required for a per-account redirect supported by ~/.forward. Addressing the cause requires: Create a valid ~/.forward file under the user's home with appropriate permissions and delivery policy.
Incorrect Answers
B:This option assumes A successful daemon restart does not prove that a message reaches its intended local or remote destination. The reported symptoms instead call for: Create a valid ~/.forward file under the user's home with appropriate permissions and delivery policy.
C:The test for clock slewing on startup would be: Watch chronyc tracking offset before and after intervention and confirm stable synchronization. The relevant acceptance check here is: Send a controlled message to the local user and verify receipt at the forward destination.
D:The hardware clock did not receive the corrected system time and retains an old value. could help with sync rtc from verified system clock; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Send a controlled message to the local user and verify receipt at the forward destination.
Question 472
A local account needs messages forwarded to an approved mailbox without changing the global alias map. What should the administrator do to correct this behavior?
- Review the printer model and configure an appropriate CUPS driver/filter chain for that device.
- Configure multiple policy-approved NTP servers or a suitable pool and verify source selection behavior.
- Establish a consistent hardware-clock convention, preferably RTC in UTC where supported, and set timedatectl policy.
- Create a valid ~/.forward file under the user's home with appropriate permissions and delivery policy.
Explanation
Correct Answer
D:Create a valid ~/.forward file under the user's home with appropriate permissions and delivery policy. It addresses the root cause, while Review forwarding loops and sensitive-message exposure before enabling user-level redirects. reduces future recurrence.
Incorrect Answers
A:A wrong PPD/driver or filter conversion can create an unsuitable printer data stream. That describes a different fault. Here, Global aliases are not required for a per-account redirect supported by ~/.forward.
B:It would address chrony source trust and failover rather than the present problem. The appropriate correction here is: Create a valid ~/.forward file under the user's home with appropriate permissions and delivery policy.
C:The systems interpret the hardware RTC using different UTC versus localtime assumptions. That describes a different fault. Here, Global aliases are not required for a per-account redirect supported by ~/.forward.
Question 473
A local account needs messages forwarded to an approved mailbox without changing the global alias map. What diagnostic result would demonstrate the target behavior?
- Send a controlled message to the local user and verify receipt at the forward destination.
- Measure journal disk usage before and after vacuuming and ensure recent events remain.
- Trigger the test service and confirm its messages appear under the expected unit.
- Run logrotate in debug/test mode and verify ownership, rotation and application write behavior.
Explanation
Correct Answer
A:Send a controlled message to the local user and verify receipt at the forward destination. This check is tied to the expected behavior rather than mere process uptime.
Incorrect Answers
B:This belongs to retire old journal safely, where Manual deletion of active journal files can corrupt useful evidence or race with journald. The current issue instead is: Global aliases are not required for a per-account redirect supported by ~/.forward.
C:Trigger the test service and confirm its messages appear under the expected unit. belongs to a situation where The systemd journal already stores structured unit metadata that can scope the search. Here the evidence supports a different requirement: Send a controlled message to the local user and verify receipt at the forward destination.
D:Without logrotate or equivalent rotation, log files can grow until disk capacity is exhausted. That describes a different fault. Here, Global aliases are not required for a per-account redirect supported by ~/.forward.
Question 474
A local account needs messages forwarded to an approved mailbox without changing the global alias map. Which repeatable check would reduce recurrence?
- Make print destinations explicit in unattended workflows.
- Set documented journald size and retention limits rather than emergency manual deletion.
- Monitor source reachability and measured offset, not just whether the daemon process is running.
- Review forwarding loops and sensitive-message exposure before enabling user-level redirects.
Explanation
Correct Answer
D:Review forwarding loops and sensitive-message exposure before enabling user-level redirects. It prevents repetition of the condition: Global aliases are not required for a per-account redirect supported by ~/.forward.
Incorrect Answers
A:Without an explicit destination, lpr typically uses the configured default printer selection. That describes a different fault. Here, Global aliases are not required for a per-account redirect supported by ~/.forward.
B:Set documented journald size and retention limits rather than emergency manual deletion. could help with retire old journal safely; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Send a controlled message to the local user and verify receipt at the forward destination.
C:Monitor source reachability and measured offset, not just whether the daemon process is running. could help with chrony not synchronized; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Send a controlled message to the local user and verify receipt at the forward destination.
Question 475
A local account needs messages forwarded to an approved mailbox without changing the global alias map. Which TWO measures belong together as the direct correction and a discriminating verification? Select TWO.
- Monitor source reachability and measured offset, not just whether the daemon process is running.
- Send a controlled message to the local user and verify receipt at the forward destination.
- Inspect chronyc sources -v and chronyc tracking until a valid selected source appears.
- Create a valid ~/.forward file under the user's home with appropriate permissions and delivery policy.
- Repair DNS reachability or configure an approved resolvable/internal NTP source.
Explanation
Correct Answers
B:Send a controlled message to the local user and verify receipt at the forward destination. This measures the specific result of applying: Create a valid ~/.forward file under the user's home with appropriate permissions and delivery policy.
D:Create a valid ~/.forward file under the user's home with appropriate permissions and delivery policy. This is appropriate because Global aliases are not required for a per-account redirect supported by ~/.forward.
Incorrect Answers
A:The test for chrony not synchronized would be: Inspect chronyc sources -v and chronyc tracking until a valid selected source appears. The relevant acceptance check here is: Send a controlled message to the local user and verify receipt at the forward destination.
C:This option assumes The time synchronization daemon lacks a usable upstream source or cannot reach it. The reported symptoms instead call for: Create a valid ~/.forward file under the user's home with appropriate permissions and delivery policy.
E:DNS resolution failure prevents the NTP client from reaching a hostname-configured time source. That describes a different fault. Here, Global aliases are not required for a per-account redirect supported by ~/.forward.
Question 476
A monitoring alert reports delayed mail but the operator has not inspected whether messages remain queued. Which failure condition fits the evidence without assuming an unrelated fault?
- A plain journalctl query in the rescue OS reads that OS's journal, not the mounted system's stored logs.
- An active MTA can hold messages in its queue when delivery is deferred or destination resolution fails.
- Without logrotate or equivalent rotation, log files can grow until disk capacity is exhausted.
- A successful daemon restart does not prove that a message reaches its intended local or remote destination.
Explanation
Correct Answer
B:An active MTA can hold messages in its queue when delivery is deferred or destination resolution fails. A good follow-up is to test this explanation through: Compare queue entries and age before and after resolving a known delivery fault.
Incorrect Answers
A:A plain journalctl query in the rescue OS reads that OS's journal, not the mounted system's stored logs. belongs to a situation where A plain journalctl query in the rescue OS reads that OS's journal, not the mounted system's stored logs. Here the evidence supports a different requirement: An active MTA can hold messages in its queue when delivery is deferred or destination resolution fails.
C:The test for logrotate retention would be: Run logrotate in debug/test mode and verify ownership, rotation and application write behavior. The relevant acceptance check here is: Compare queue entries and age before and after resolving a known delivery fault.
D:It would address test syslog pipeline with logger rather than the present problem. The appropriate correction here is: Inspect the mail queue with mailq or the MTA's equivalent before attempting broad changes.
Question 477
A monitoring alert reports delayed mail but the operator has not inspected whether messages remain queued. What should the administrator do to correct this behavior?
- Select one supported clock synchronization service and disable the redundant one.
- Inspect the mail queue with mailq or the MTA's equivalent before attempting broad changes.
- Query journalctl -u service-name with a suitable time range instead of scanning arbitrary text.
- Configure an approved TCP rsyslog forwarding action and corresponding listener/TLS policy as needed.
Explanation
Correct Answer
B:Inspect the mail queue with mailq or the MTA's equivalent before attempting broad changes. It is the direct response; verify the result by: Compare queue entries and age before and after resolving a known delivery fault.
Incorrect Answers
A:Competing NTP clients can apply conflicting clock discipline and confusing status reports. That describes a different fault. Here, An active MTA can hold messages in its queue when delivery is deferred or destination resolution fails.
C:The test for service-specific log query would be: Trigger the test service and confirm its messages appear under the expected unit. The relevant acceptance check here is: Compare queue entries and age before and after resolving a known delivery fault.
D:Configure an approved TCP rsyslog forwarding action and corresponding listener/TLS policy as needed. could help with rsyslog tcp forwarding; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Compare queue entries and age before and after resolving a known delivery fault.
Question 478
A monitoring alert reports delayed mail but the operator has not inspected whether messages remain queued. Which observation should be used for acceptance testing?
- Emit a controlled event and trace whether it appears in both journal and the intended text log.
- Measure journal disk usage before and after vacuuming and ensure recent events remain.
- Take the primary source offline in a test and inspect peer selection and offset stability.
- Compare queue entries and age before and after resolving a known delivery fault.
Explanation
Correct Answer
D:Compare queue entries and age before and after resolving a known delivery fault. The test is evidence-based because the underlying failure was: An active MTA can hold messages in its queue when delivery is deferred or destination resolution fails.
Incorrect Answers
A:That choice responds to a rsyslog journal coexistence failure. In this incident, An active MTA can hold messages in its queue when delivery is deferred or destination resolution fails.
B:The test for retire old journal safely would be: Measure journal disk usage before and after vacuuming and ensure recent events remain. The relevant acceptance check here is: Compare queue entries and age before and after resolving a known delivery fault.
C:Take the primary source offline in a test and inspect peer selection and offset stability. belongs to a situation where The clock service lacks sufficient reachable, approved fallback time sources. Here the evidence supports a different requirement: Compare queue entries and age before and after resolving a known delivery fault.
Question 479
A monitoring alert reports delayed mail but the operator has not inspected whether messages remain queued. What should the team standardize to prevent similar incidents?
- Monitor deferred-message count and delivery latency, not just MTA uptime.
- Monitor rotated log sizes and retention alongside application load.
- Design time-source redundancy and restrict untrusted NTP servers.
- Alert on synchronization state and drift independently of local display formatting.
Explanation
Correct Answer
A:Monitor deferred-message count and delivery latency, not just MTA uptime. This control detects or prevents the same mechanism before another incident.
Incorrect Answers
B:The test for logrotate retention would be: Run logrotate in debug/test mode and verify ownership, rotation and application write behavior. The relevant acceptance check here is: Compare queue entries and age before and after resolving a known delivery fault.
C:That choice responds to a chrony source trust and failover failure. In this incident, An active MTA can hold messages in its queue when delivery is deferred or destination resolution fails.
D:This option assumes A plausible wall-clock value is not evidence of upstream synchronization or bounded clock offset. The reported symptoms instead call for: Inspect the mail queue with mailq or the MTA's equivalent before attempting broad changes.
Question 480
A monitoring alert reports delayed mail but the operator has not inspected whether messages remain queued. Which THREE case-specific steps cover immediate repair, test evidence and sustained control?
- Use journalctl --since and --until with explicit times for the investigation interval.
- Compare queue entries and age before and after resolving a known delivery fault.
- Run logrotate in debug/test mode and verify ownership, rotation and application write behavior.
- Set documented journald size and retention limits rather than emergency manual deletion.
- Monitor deferred-message count and delivery latency, not just MTA uptime.
- Inspect the mail queue with mailq or the MTA's equivalent before attempting broad changes.
Explanation
Correct Answers
B:Compare queue entries and age before and after resolving a known delivery fault. It verifies that the targeted action (Inspect the mail queue with mailq or the MTA's equivalent before attempting broad changes.) achieved its intended outcome.
E:Monitor deferred-message count and delivery latency, not just MTA uptime. It preserves the corrective behavior established through: Inspect the mail queue with mailq or the MTA's equivalent before attempting broad changes.
F:Inspect the mail queue with mailq or the MTA's equivalent before attempting broad changes. It addresses the root cause, while Monitor deferred-message count and delivery latency, not just MTA uptime. reduces future recurrence.
Incorrect Answers
A:Use journalctl --since and --until with explicit times for the investigation interval. could help with systemd journal time window; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Compare queue entries and age before and after resolving a known delivery fault.
C:Without logrotate or equivalent rotation, log files can grow until disk capacity is exhausted. That describes a different fault. Here, An active MTA can hold messages in its queue when delivery is deferred or destination resolution fails.
D:That choice responds to a retire old journal safely failure. In this incident, An active MTA can hold messages in its queue when delivery is deferred or destination resolution fails.
LPI Level 1 (102-500) Practice Tests