The answer is that the NTP daemon has recently started and has not yet synchronized. When ntpd initializes, it sets the stratum to 16 to indicate an unsynchronized state, and the ntpq -p output shows zero delay and offset because no valid time measurements have been computed yet. This is a normal transient condition; once the daemon contacts and synchronizes with an upstream server, the stratum drops below 16 and the delay/offset values become non-zero. On the LPIC-1 exam, this scenario tests your understanding of NTP’s startup behavior and the meaning of stratum levels—a common trap is misinterpreting these zero values as a network failure or server misconfiguration. Remember that stratum 16 is the “unsynchronized” flag, and zero delay/offset simply means no data has been collected. A helpful memory tip: think of stratum 16 as “stratum 1-6? No, it’s 16—still waiting for a time fix.”
LPIC-1 Administrative Tasks Practice Question
This LPIC-1 practice question tests your understanding of administrative tasks. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Refer to the exhibit.
# cat /etc/ntp.conf
server 0.pool.ntp.org iburst
server 1.pool.ntp.org iburst
# driftfile /var/lib/ntp/ntp.drift
restrict default kod nomodify notrap nopeer noquery
restrict -6 default kod nomodify notrap nopeer noquery
restrict 127.0.0.1
restrict -6 ::1
# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*0.pool.ntp.org .POOL. 16 p - 64 0 0.000 0.000 0.000
1.pool.ntp.org .POOL. 16 p - 64 0 0.000 0.000 0.000
Refer to the exhibit. An administrator runs 'ntpq -p' and sees the output shown. What is the most likely cause of the '16' stratum and '0.000' delay/offset?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Refer to the exhibit.
# cat /etc/ntp.conf
server 0.pool.ntp.org iburst
server 1.pool.ntp.org iburst
# driftfile /var/lib/ntp/ntp.drift
restrict default kod nomodify notrap nopeer noquery
restrict -6 default kod nomodify notrap nopeer noquery
restrict 127.0.0.1
restrict -6 ::1
# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*0.pool.ntp.org .POOL. 16 p - 64 0 0.000 0.000 0.000
1.pool.ntp.org .POOL. 16 p - 64 0 0.000 0.000 0.000
A
The NTP service is not running.
Why wrong: If the service were not running, ntpq -p would not return output.
B
The firewall is blocking UDP port 123.
Why wrong: While possible, the output shows servers are being polled (t=p), but reach is 0. More likely, NTP has just started.
C
The NTP daemon has recently started and has not yet synchronized.
The 'iburst' option causes rapid initial polls, but it still takes a few minutes for synchronization. The 0 reach and stratum 16 indicate no synchronization yet.
D
The restrict lines are blocking all NTP queries.
Why wrong: The restrict lines shown do not block local queries; they restrict remote clients.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The NTP daemon has recently started and has not yet synchronized.
The '16' stratum and '0.000' delay/offset values in the 'ntpq -p' output indicate that the NTP daemon has not yet synchronized with any time source. When ntpd starts, it initially sets the stratum to 16 (unsynchronized) and shows zero values for delay and offset until it completes the synchronization process. This is a normal transient state that resolves once the daemon successfully contacts and synchronizes with an NTP server.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The NTP service is not running.
Why it's wrong here
If the service were not running, ntpq -p would not return output.
✗
The firewall is blocking UDP port 123.
Why it's wrong here
While possible, the output shows servers are being polled (t=p), but reach is 0. More likely, NTP has just started.
✓
The NTP daemon has recently started and has not yet synchronized.
Why this is correct
The 'iburst' option causes rapid initial polls, but it still takes a few minutes for synchronization. The 0 reach and stratum 16 indicate no synchronization yet.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The restrict lines are blocking all NTP queries.
Why it's wrong here
The restrict lines shown do not block local queries; they restrict remote clients.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume a stratum of 16 and zero delay/offset indicate a firewall or service failure, but the correct interpretation is that the NTP daemon has just started and has not yet synchronized, which is a normal temporary state.
Trap categories for this question
Command / output trap
If the service were not running, ntpq -p would not return output.
Detailed technical explanation
How to think about this question
When ntpd starts, it enters a 'panic' state if the local clock is too far off, but under normal conditions it begins with stratum 16 and zero delay/offset until it receives a valid NTP response. The 'ntpq -p' command queries the NTP daemon's internal state variables; the delay and offset fields are populated only after the daemon has completed at least one round-trip measurement with a peer. In real-world scenarios, this output is common immediately after a system reboot or ntpd restart, and the daemon will typically synchronize within a few minutes if network connectivity and firewall rules are correct.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the LPIC-1 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Administrative Tasks — This question tests Administrative Tasks — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The NTP daemon has recently started and has not yet synchronized. — The '16' stratum and '0.000' delay/offset values in the 'ntpq -p' output indicate that the NTP daemon has not yet synchronized with any time source. When ntpd starts, it initially sets the stratum to 16 (unsynchronized) and shows zero values for delay and offset until it completes the synchronization process. This is a normal transient state that resolves once the daemon successfully contacts and synchronizes with an NTP server.
What should I do if I get this LPIC-1 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This LPIC-1 practice question is part of Courseiva's free LPI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the LPIC-1 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.