100% Latest & Updated LPI 102-500 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 390
An embedded host runs correctly after NTP sync but later cold-boots with a badly wrong time before networking is available. Choose THREE measures that together correct the failure, demonstrate success and reduce recurrence.
- Persist RTC handling as part of maintenance for network-dependent clock systems.
- Configure an approved TCP rsyslog forwarding action and corresponding listener/TLS policy as needed.
- Interrupt and restore the receiver during test and verify transport and receipt.
- Read RTC and system time after sync, then cold-boot with networking isolated to check initial time.
- After verified synchronization, use an appropriate hwclock --systohc operation under the chosen UTC/local convention.
- Record journal priority conventions in operational runbooks.
Explanation
Correct Answers
A:Persist RTC handling as part of maintenance for network-dependent clock systems. It prevents repetition of the condition: The hardware clock did not receive the corrected system time and retains an old value.
D:Read RTC and system time after sync, then cold-boot with networking isolated to check initial time. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: The hardware clock did not receive the corrected system time and retains an old value.
E:After verified synchronization, use an appropriate hwclock --systohc operation under the chosen UTC/local convention. It corrects the mechanism identified in the scenario: The hardware clock did not receive the corrected system time and retains an old value.
Incorrect Answers
B:Configure an approved TCP rsyslog forwarding action and corresponding listener/TLS policy as needed. belongs to a situation where The single-@ rsyslog forwarding action denotes UDP while double-@@ denotes TCP in legacy action syntax. Here the evidence supports a different requirement: After verified synchronization, use an appropriate hwclock --systohc operation under the chosen UTC/local convention.
C:Interrupt and restore the receiver during test and verify transport and receipt. belongs to a situation where The single-@ rsyslog forwarding action denotes UDP while double-@@ denotes TCP in legacy action syntax. Here the evidence supports a different requirement: Read RTC and system time after sync, then cold-boot with networking isolated to check initial time.
F:That choice responds to a filter critical journal priority failure. In this incident, The hardware clock did not receive the corrected system time and retains an old value.
Question 391
Two different time synchronization daemons run simultaneously and repeatedly fight over system clock adjustment. Which diagnosis is supported by the observations?
- Competing NTP clients can apply conflicting clock discipline and confusing status reports.
- Without priority filtering the journal query mixes benign events with high-severity records.
- Traditional syslog severity selectors generally include the named level and more severe levels, so info includes many events.
- Destination lookup failure can defer mail regardless of MTA process health.
Explanation
Correct Answer
A:Competing NTP clients can apply conflicting clock discipline and confusing status reports. The observation is consistent with this mechanism; a targeted repair would be: Select one supported clock synchronization service and disable the redundant one.
Incorrect Answers
B:Without priority filtering the journal query mixes benign events with high-severity records. belongs to a situation where Without priority filtering the journal query mixes benign events with high-severity records. Here the evidence supports a different requirement: Competing NTP clients can apply conflicting clock discipline and confusing status reports.
C:Traditional syslog severity selectors generally include the named level and more severe levels, so info includes many events. could help with syslog selector priority semantics; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Inspect running time services and confirm one controlling daemon reports stable synchronization.
D:Destination lookup failure can defer mail regardless of MTA process health. That describes a different fault. Here, Competing NTP clients can apply conflicting clock discipline and confusing status reports.
Question 392
Two different time synchronization daemons run simultaneously and repeatedly fight over system clock adjustment. Which configuration approach is appropriate for this requirement?
- Configure an approved TCP rsyslog forwarding action and corresponding listener/TLS policy as needed.
- Use an authorized monitored destination mailbox and limit routing to policy-approved recipients.
- Emit a tagged test message with logger and trace it to the configured sink.
- Select one supported clock synchronization service and disable the redundant one.
Explanation
Correct Answer
D:Select one supported clock synchronization service and disable the redundant one. Unlike a broad workaround, it targets the observed cause: Competing NTP clients can apply conflicting clock discipline and confusing status reports.
Incorrect Answers
A: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: Inspect running time services and confirm one controlling daemon reports stable synchronization.
B:Local forwarding can disclose security and operational contents beyond the approved organizational boundary. That describes a different fault. Here, Competing NTP clients can apply conflicting clock discipline and confusing status reports.
C: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: Select one supported clock synchronization service and disable the redundant one.
Question 393
Two different time synchronization daemons run simultaneously and repeatedly fight over system clock adjustment. Which test would confirm the suspected Linux mechanism?
- Interrupt and restore the receiver during test and verify transport and receipt.
- Submit a local test message and verify queue handling and final delivery.
- Inspect running time services and confirm one controlling daemon reports stable synchronization.
- Generate a controlled error log and confirm lower-priority messages are excluded.
Explanation
Correct Answer
C:Inspect running time services and confirm one controlling daemon reports stable synchronization. It distinguishes a genuine correction from a superficial edit that has not addressed the underlying cause: Competing NTP clients can apply conflicting clock discipline and confusing status reports.
Incorrect Answers
A:That choice responds to a rsyslog tcp forwarding failure. In this incident, Competing NTP clients can apply conflicting clock discipline and confusing status reports.
B:A message composition client is not itself a mail transfer agent responsible for queuing and routing mail. That describes a different fault. Here, Competing NTP clients can apply conflicting clock discipline and confusing status reports.
D:Generate a controlled error log and confirm lower-priority messages are excluded. belongs to a situation where Without priority filtering the journal query mixes benign events with high-severity records. Here the evidence supports a different requirement: Inspect running time services and confirm one controlling daemon reports stable synchronization.
Question 394
Two different time synchronization daemons run simultaneously and repeatedly fight over system clock adjustment. Which repeatable check would reduce recurrence?
- Enforce a single supported time-discipline stack in host configuration.
- Specify transport reliability and security separately in centralized logging standards.
- Separate device fault recovery from queue acceptance in operational procedures.
- Make print destinations explicit in unattended workflows.
Explanation
Correct Answer
A:Enforce a single supported time-discipline stack in host configuration. This control detects or prevents the same mechanism before another incident.
Incorrect Answers
B:That choice responds to a rsyslog tcp forwarding failure. In this incident, Competing NTP clients can apply conflicting clock discipline and confusing status reports.
C:It would address printing halted by disabled printer rather than the present problem. The appropriate correction here is: Select one supported clock synchronization service and disable the redundant one.
D:That choice responds to a print to named destination failure. In this incident, Competing NTP clients can apply conflicting clock discipline and confusing status reports.
Question 395
Two different time synchronization daemons run simultaneously and repeatedly fight over system clock adjustment. Which TWO options provide a coherent remediation-and-test response to this incident?
- Search both sender and receiver logs for the unique tag and compare timestamps.
- Inspect running time services and confirm one controlling daemon reports stable synchronization.
- Specify transport reliability and security separately in centralized logging standards.
- Identify the installed MTA and handle the requested local alias without unrelated relay changes.
- Select one supported clock synchronization service and disable the redundant one.
Explanation
Correct Answers
B:Inspect running time services and confirm one controlling daemon reports stable synchronization. This measures the specific result of applying: Select one supported clock synchronization service and disable the redundant one.
E:Select one supported clock synchronization service and disable the redundant one. This is appropriate because Competing NTP clients can apply conflicting clock discipline and confusing status reports.
Incorrect Answers
A: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: Select one supported clock synchronization service and disable the redundant one.
C:Specify transport reliability and security separately in centralized logging standards. belongs to a situation where The single-@ rsyslog forwarding action denotes UDP while double-@@ denotes TCP in legacy action syntax. Here the evidence supports a different requirement: Enforce a single supported time-discipline stack in host configuration.
D:Identify the installed MTA and handle the requested local alias without unrelated relay changes. could help with mta configuration beyond exam scope; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Inspect running time services and confirm one controlling daemon reports stable synchronization.
Question 396
An administrator sees the correct time in date output and declares synchronization healthy, although the host is drifting. Which failure condition fits the evidence without assuming an unrelated fault?
- Journald and rsyslog are separate components; storage and forwarding rules determine whether entries are mirrored.
- Some MTAs require the aliases database to be rebuilt after editing the text file.
- A plausible wall-clock value is not evidence of upstream synchronization or bounded clock offset.
- An active MTA can hold messages in its queue when delivery is deferred or destination resolution fails.
Explanation
Correct Answer
C:A plausible wall-clock value is not evidence of upstream synchronization or bounded clock offset. The observation is consistent with this mechanism; a targeted repair would be: Query the active time client's synchronization, source and offset metrics rather than trusting date alone.
Incorrect Answers
A:This option assumes Journald and rsyslog are separate components; storage and forwarding rules determine whether entries are mirrored. The reported symptoms instead call for: Query the active time client's synchronization, source and offset metrics rather than trusting date alone.
B:That choice responds to a local mail alias activation failure. In this incident, A plausible wall-clock value is not evidence of upstream synchronization or bounded clock offset.
D:An active MTA can hold messages in its queue when delivery is deferred or destination resolution fails. That describes a different fault. Here, A plausible wall-clock value is not evidence of upstream synchronization or bounded clock offset.
Question 397
An administrator sees the correct time in date output and declares synchronization healthy, although the host is drifting. Which change most directly meets the stated requirement?
- Install or activate an approved MTA such as Postfix, Exim or Sendmail as policy requires.
- Query the active time client's synchronization, source and offset metrics rather than trusting date alone.
- Inspect printer enabled state and enable it after resolving the underlying physical issue.
- Inspect journald and rsyslog integration, applicable facilities and output rules rather than assuming identical stores.
Explanation
Correct Answer
B:Query the active time client's synchronization, source and offset metrics rather than trusting date alone. It is the direct response; verify the result by: Inspect timedatectl and chronyc tracking or the configured NTP client status over time.
Incorrect Answers
A:Install or activate an approved MTA such as Postfix, Exim or Sendmail as policy requires. belongs to a situation where A message composition client is not itself a mail transfer agent responsible for queuing and routing mail. Here the evidence supports a different requirement: Query the active time client's synchronization, source and offset metrics rather than trusting date alone.
C:The test for printing halted by disabled printer would be: Check queue drain after enabling and verify the previously pending job prints. The relevant acceptance check here is: Inspect timedatectl and chronyc tracking or the configured NTP client status over time.
D:This belongs to rsyslog journal coexistence, where Journald and rsyslog are separate components; storage and forwarding rules determine whether entries are mirrored. The current issue instead is: A plausible wall-clock value is not evidence of upstream synchronization or bounded clock offset.
Question 398
An administrator sees the correct time in date output and declares synchronization healthy, although the host is drifting. Which check would provide the strongest evidence that the fix worked?
- Trigger the test service and confirm its messages appear under the expected unit.
- Inspect timedatectl and chronyc tracking or the configured NTP client status over time.
- Print a known standard test page and examine CUPS logs for filter errors.
- Check returned timestamps against the known incident window and unit.
Explanation
Correct Answer
B:Inspect timedatectl and chronyc tracking or the configured NTP client status over time. This check is tied to the expected behavior rather than mere process uptime.
Incorrect Answers
A:That choice responds to a service-specific log query failure. In this incident, A plausible wall-clock value is not evidence of upstream synchronization or bounded clock offset.
C:This option assumes A wrong PPD/driver or filter conversion can create an unsuitable printer data stream. The reported symptoms instead call for: Query the active time client's synchronization, source and offset metrics rather than trusting date alone.
D:Check returned timestamps against the known incident window and unit. could help with systemd journal time window; it neither resolves nor demonstrates the current requirement. The distinguishing check is: Inspect timedatectl and chronyc tracking or the configured NTP client status over time.
Question 399
An administrator sees the correct time in date output and declares synchronization healthy, although the host is drifting. Which practice is most useful after the immediate repair succeeds?
- Alert on synchronization state and drift independently of local display formatting.
- Include verified offline journal extraction steps in recovery procedures.
- Do not infer MTA product identity solely from a compatible command name.
- Preserve stable service unit names and structured logging fields for diagnosis.
Explanation
Correct Answer
A:Alert on synchronization state and drift independently of local display formatting. The underlying risk is A plausible wall-clock value is not evidence of upstream synchronization or bounded clock offset.
Incorrect Answers
B:The test for rescue-system journal path would be: Check machine IDs and boot IDs to ensure displayed records come from the failed host. The relevant acceptance check here is: Inspect timedatectl and chronyc tracking or the configured NTP client status over time.
C:That choice responds to a sendmail compatibility command failure. In this incident, A plausible wall-clock value is not evidence of upstream synchronization or bounded clock offset.
D:This belongs to service-specific log query, where The systemd journal already stores structured unit metadata that can scope the search. The current issue instead is: A plausible wall-clock value is not evidence of upstream synchronization or bounded clock offset.
Question 400
An administrator sees the correct time in date output and declares synchronization healthy, although the host is drifting. Which THREE actions form a suitable remediation, verification and prevention plan? Select THREE.
- Alert on synchronization state and drift independently of local display formatting.
- Inspect timedatectl and chronyc tracking or the configured NTP client status over time.
- Do not infer MTA product identity solely from a compatible command name.
- Inspect journald and rsyslog integration, applicable facilities and output rules rather than assuming identical stores.
- Query the active time client's synchronization, source and offset metrics rather than trusting date alone.
- Inspect the executable provider and follow a test submission into the active queue.
Explanation
Correct Answers
A:Alert on synchronization state and drift independently of local display formatting. It preserves the corrective behavior established through: Query the active time client's synchronization, source and offset metrics rather than trusting date alone.
B:Inspect timedatectl and chronyc tracking or the configured NTP client status over time. It verifies that the targeted action (Query the active time client's synchronization, source and offset metrics rather than trusting date alone.) achieved its intended outcome.
E:Query the active time client's synchronization, source and offset metrics rather than trusting date alone. The change should be accepted only after this test: Inspect timedatectl and chronyc tracking or the configured NTP client status over time.
Incorrect Answers
C:This belongs to sendmail compatibility command, where Many MTAs provide a sendmail-compatible submission interface, independent of the actual daemon implementation. The current issue instead is: A plausible wall-clock value is not evidence of upstream synchronization or bounded clock offset.
D:The test for rsyslog journal coexistence would be: Emit a controlled event and trace whether it appears in both journal and the intended text log. The relevant acceptance check here is: Inspect timedatectl and chronyc tracking or the configured NTP client status over time.
F:Many MTAs provide a sendmail-compatible submission interface, independent of the actual daemon implementation. That describes a different fault. Here, A plausible wall-clock value is not evidence of upstream synchronization or bounded clock offset.
LPI Level 1 (102-500) Practice Tests