An organization that collects logs from multiple servers notices that newly added hosts produce mismatched timestamps compared to existing servers. The new hosts do not contact the established clock system that other servers use. Which modification fixes the inconsistency?
Use an additional external reference and alternate the updates between both sources
Point each new server to the same time service used by the other servers
Stop synchronization on the older servers and rely on new default settings
Set the clock by hand on all new hosts whenever mismatches occur
In centralized environments, time coordination typically relies on a standard protocol such as Network Time Protocol (NTP). Making all servers point to the same clock source guarantees consistent timestamps and accurate event correlation. Turning off synchronization or introducing extra sources complicates alignment. Manually matching clocks is prone to oversight and drifts again over time.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is NTP and why is it important for servers?
Open an interactive chat with Bash
What are the consequences of mismatched timestamps in server logs?
Open an interactive chat with Bash
How does introducing multiple time sources complicate synchronization?