A switch shows a clock that is several minutes off from other devices even though an NTP server has been configured. Which issue is the most likely cause?
Exhibit
show ntp associations address ref clock st when poll reach delay offset disp *~10.10.50.5 .INIT. 16 - 64 0 0.000 0.000 16000 Configured server: 10.10.50.5
Trap 1: The device must run Syslog before NTP can sync
Syslog is unrelated.
Trap 2: NTP requires a trunk port on the management VLAN
NTP needs IP reachability, not a trunk specifically.
Trap 3: The clock can sync only if DNS is configured
NTP uses IP connectivity; DNS is optional if using addresses.
- A
The NTP server is unsynchronized or unreachable
This is correct because NTP requires a reachable, synchronized time source. If the server is unreachable or not synchronized, the switch cannot update its clock, leading to drift.
- B
The device must run Syslog before NTP can sync
Why wrong: Syslog is unrelated.
- C
NTP requires a trunk port on the management VLAN
Why wrong: NTP needs IP reachability, not a trunk specifically.
- D
The clock can sync only if DNS is configured
Why wrong: NTP uses IP connectivity; DNS is optional if using addresses.