The correct commands are `ntp server 198.51.100.1 source Loopback0` and `logging trap warnings`. This fixes two critical issues: the NTP client was pointing to an unreachable server (192.0.2.1), leaving the router at stratum 16 and unable to synchronize, while the syslog trap level was set to debugging (level 7), flooding the logging server with every message. By specifying the correct NTP server and sourcing from Loopback0, you ensure consistent reachability and stable time synchronization, a key requirement for accurate logging and authentication in a CCNA network. On the CCNA 200-301 v2 exam, this tests your ability to configure NTP client settings and filter syslog severity levels—a common trap is confusing the `logging trap` keyword with the severity name (e.g., `warnings` for level 4) versus the numeric value. Remember: NTP needs a reachable source and server, while syslog trap levels are inclusive from 0 up to the level you set. A quick memory tip: "Warnings (4) and above" means emergencies (0) through warnings (4) are logged.
CCNA AI and Network Operations Practice Question
This 200-301 practice question tests your understanding of ai and network operations. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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
R1#show running-config | include ntp|logging
ntp server 192.0.2.1
logging host 203.0.113.10
logging trap debugging
!
R1#show ntp status
Clock is unsynchronized, stratum 16, no reference clock
R1#show ntp associations
address ref clock st when poll reach delay offset disp
*~192.0.2.1 .INIT. 16 - 64 0 0.0 0.0 0.0
~198.51.100.1 .INIT. 16 - 64 0 0.0 0.0 0.0
You are connected to R1, a branch router that must synchronize time with the NTP server at 198.51.100.1 (reachable via G0/0) and send critical syslog messages (severity 0-4) to the logging server at 203.0.113.10. The current configuration has NTP pointing to a wrong server and syslog set to debug level, flooding the server. Correct the NTP server, set the NTP source interface to Loopback0 (10.10.10.1/32), and adjust the syslog trap level so that only emergencies through warnings are logged.
R1#show running-config | include ntp|logging
ntp server 192.0.2.1
logging host 203.0.113.10
logging trap debugging
!
R1#show ntp status
Clock is unsynchronized, stratum 16, no reference clock
R1#show ntp associations
address ref clock st when poll reach delay offset disp
*~192.0.2.1 .INIT. 16 - 64 0 0.0 0.0 0.0
~198.51.100.1 .INIT. 16 - 64 0 0.0 0.0 0.0
A
ntp server 198.51.100.1 source Loopback0; logging trap warnings
This command sets the NTP server to the correct IP (198.51.100.1) with Loopback0 as the source interface, and changes the syslog trap level to warnings (severity 4), which logs messages with severity 0-4 (emergencies through warnings).
B
ntp server 198.51.100.1 source G0/0; logging trap errors
Why wrong: This is incorrect because the source interface should be Loopback0, not G0/0, and the syslog trap level 'errors' (severity 3) only logs severities 0-3, missing warnings (severity 4).
C
ntp server 192.0.2.1 source Loopback0; logging trap warnings
Why wrong: This is incorrect because the NTP server IP is still the wrong one (192.0.2.1), which is unreachable. The correct server is 198.51.100.1.
D
ntp server 198.51.100.1 source Loopback0; logging trap debugging
Why wrong: This is incorrect because the syslog trap level is set to debugging (severity 7), which sends all messages, including debug-level messages. The requirement is to log only severities 0-4 (emergencies through warnings).
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
ntp server 198.51.100.1 source Loopback0; logging trap warnings
The NTP server was misconfigured to 192.0.2.1, which is unreachable, leaving the router at stratum 16. The correct NTP server is 198.51.100.1, so the ntp server command must be updated. The source interface should be Loopback0 for reachability consistency. The syslog trap level was set to debugging (level 7), which sends all messages; it should be changed to warnings (level 4) to filter only severity 0-4. Verification includes checking NTP synchronization and syslog configuration.
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.
✓
ntp server 198.51.100.1 source Loopback0; logging trap warnings
Why this is correct
This command sets the NTP server to the correct IP (198.51.100.1) with Loopback0 as the source interface, and changes the syslog trap level to warnings (severity 4), which logs messages with severity 0-4 (emergencies through warnings).
Related concept
Read the scenario before looking for a memorised answer.
✗
ntp server 198.51.100.1 source G0/0; logging trap errors
Why it's wrong here
This is incorrect because the source interface should be Loopback0, not G0/0, and the syslog trap level 'errors' (severity 3) only logs severities 0-3, missing warnings (severity 4).
✗
ntp server 192.0.2.1 source Loopback0; logging trap warnings
Why it's wrong here
This is incorrect because the NTP server IP is still the wrong one (192.0.2.1), which is unreachable. The correct server is 198.51.100.1.
✗
ntp server 198.51.100.1 source Loopback0; logging trap debugging
Why it's wrong here
This is incorrect because the syslog trap level is set to debugging (severity 7), which sends all messages, including debug-level messages. The requirement is to log only severities 0-4 (emergencies through warnings).
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 200-301 exam frequently reuses these exact scenarios with slightly different constraints.
✓ntp server 198.51.100.1 source Loopback0; logging trap warningsCorrect answer▾
Why this is correct
This command sets the NTP server to the correct IP (198.51.100.1) with Loopback0 as the source interface, and changes the syslog trap level to warnings (severity 4), which logs messages with severity 0-4 (emergencies through warnings).
✗ntp server 198.51.100.1 source G0/0; logging trap errorsWrong answer — click to see why▾
Why this is wrong here
The source interface must be Loopback0 for consistency, and the trap level should be warnings (4) to include warnings.
Why candidates choose this
Candidates might think G0/0 is the correct source since it's the interface that reaches the NTP server, but using a loopback ensures reachability even if G0/0 goes down.
✗ntp server 192.0.2.1 source Loopback0; logging trap warningsWrong answer — click to see why▾
Why this is wrong here
The NTP server address must be updated to 198.51.100.1; 192.0.2.1 is the misconfigured server.
Why candidates choose this
Candidates might forget to change the NTP server IP and only adjust the source interface and syslog level.
✗ntp server 198.51.100.1 source Loopback0; logging trap debuggingWrong answer — click to see why▾
Why this is wrong here
The trap level should be warnings (4), not debugging (7). Debugging sends all messages, flooding the server.
Why candidates choose this
Candidates might confuse the logging levels or think debugging is needed for troubleshooting, but the question explicitly requires only severities 0-4.
Analysis generated from the official 200-301blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
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.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→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 200-301 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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this 200-301 question in full detail.
Identify which 200-301 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
AI and Network Operations — This question tests AI and Network Operations — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: ntp server 198.51.100.1 source Loopback0; logging trap warnings — The NTP server was misconfigured to 192.0.2.1, which is unreachable, leaving the router at stratum 16. The correct NTP server is 198.51.100.1, so the ntp server command must be updated. The source interface should be Loopback0 for reachability consistency. The syslog trap level was set to debugging (level 7), which sends all messages; it should be changed to warnings (level 4) to filter only severity 0-4. Verification includes checking NTP synchronization and syslog configuration.
What should I do if I get this 200-301 question wrong?
Identify which 200-301 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You are connected to R1, a branch router connected to a central NTP server at 203.0.113.10 and a syslog server at 198.51.100.20. Configure R1 as an NTP client using its Loopback0 interface (192.168.1.1/32) as the source, and ensure syslog messages of severity 'informational' and above are sent to the syslog server. Currently, R1 shows 'Clock is unsynchronized, stratum 16'. Identify and fix the NTP issue, then apply the syslog configuration.
hard
✓ A.Configure 'ntp source Loopback0' and 'logging trap informational'.
B.Configure 'ntp server 203.0.113.10 source Loopback0' and 'logging trap warnings'.
C.Configure 'ntp source Loopback0' and 'logging trap debugging'.
D.Configure 'ntp source Loopback0' and 'logging host 198.51.100.20' without changing the trap level.
Why A: The NTP client was configured but the source interface was not specified, causing the router to use a default source that may not be reachable. Additionally, the syslog trap level was set to 'warnings' (severity 4), which filters out informational (severity 6) messages. To fix: configure 'ntp source Loopback0' to use a consistent source IP, and change 'logging trap informational' to allow all messages severity 6 and above.
Last reviewed: Jun 6, 2026
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.
This 200-301 practice question is part of Courseiva's free Cisco 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 200-301 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.