In a multi-step time synchronization troubleshooting scenario, what is the correct order of steps?

• A. 2, 3, 1
• B. 3, 2, 1
• C. 1, 2, 3
• D. 1, 3, 2

Answer: (A)

When diagnosing time synchronization, you want to anchor the process on a valid reference clock first. If the time source itself isn’t reachable or is incorrect, no amount of local tweaking will yield correct times on the endpoints. So you start by verifying the time source and the network path to it. Once you’ve confirmed a reachable, trustworthy reference, the next step is to check that the synchronization service (such as NTP or PTP) is properly configured and running on the devices, and that there are no firewall or policy blocks preventing the service from talking to the reference. Only after the reference and the service are confirmed do you verify the actual clocks on the end systems to ensure they have synchronized to the correct time. This logical flow—reference first, service second, end clocks third—matches the sequence 2, 3, 1 and explains why it’s the best order.