In telemetry architecture, poor time synchronization primarily causes which outcome?

• A. Inability to access dashboards remotely.
• B. Inability to reliably correlate events across devices and compromise audit trails.
• C. Reduced power consumption.
• D. Inaccurate time stamps across devices and unreliable cross-device correlation.

Answer: (C)

Time synchronization ensures all devices share a common clock. When clocks drift, each device logs events using its own time reference, so timestamps become inconsistent. That makes it hard to order events correctly and to link related events across different devices. Audit trails rely on precise timing to show who did what and when; if times are off, those trails lose reliability. Dashboards may still display data, but the ability to correlate events across devices and trust the timing of those events is compromised. This issue is not about remote dashboard access or reducing power consumption. The primary outcome is inaccurate time stamps across devices and unreliable cross-device correlation.