A BIG-IP Administrator configures three Network Time Protocol servers to keep the time of the devices in sync. Which tool should the administrator use to show the synchronization status with the Netwo

ntpdate manually steps or slews the system clock by contacting an NTP server, but it does not display the synchronization status or health of configured NTP peers.

The 'time' command measures the elapsed wall-clock and CPU time for a process execution and has no relationship to NTP or clock synchronization.

The correct tool on BIG-IP for checking NTP synchronization status queries each configured NTP peer and returns metrics such as stratum, delay, offset, and jitter, confirming whether the device is actively synchronized. Tools like ntpdate adjust the clock on demand but do not report ongoing peer synchronization state. This distinction is critical for administrators verifying that all three NTP servers are reachable and that the BIG-IP clock is tracking correctly.

The 'date' command displays or sets the local system date and time but provides no information about NTP peer reachability or synchronization state.