The answer is to configure `ntp source Loopback0` and `logging trap critical`. The NTP client was failing to synchronize because the router was using the outgoing interface’s IP address, which may not be consistently reachable; specifying Loopback0 as the NTP source ensures a stable, routable IP for NTP packets. For syslog, the existing `logging trap debugging` sent all severity levels (0–7), but the requirement is to send only critical (severity 2) and higher—so `logging trap critical` filters out everything below that threshold. On the CCNA 200-301 v2 exam, this tests your ability to troubleshoot NTP synchronization and syslog filtering, often appearing in a “fix the configuration” scenario where you must spot the missing source interface and an overly permissive trap level. A common trap is confusing `logging trap` with `logging console`—remember, trap controls what is sent to the server, not what appears on the terminal. Memory tip: “Source for sync, trap for shrink”—the source stabilizes NTP, while the trap shrinks the syslog flood.
CCNA AI and Network Operations Practice Question
This 200-301 practice question tests your understanding of ai and network operations. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. 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.
Network Topology
You are connected to R1 via the console. R1 is a router acting as an NTP client to an external NTP server at 203.0.113.10. The NTP source interface must be Loopback0 (192.0.2.1/32). Additionally, configure R1 to send syslog messages of severity 'critical' and higher to a syslog server at 198.51.100.50. Currently, R1 shows 'Clock is unsynchronized, stratum 16'. Verify that NTP synchronizes and that only critical syslog messages are sent. The existing running configuration already has some NTP and syslog commands that need correction.
R1#show running-config | section ntp|logging
ntp server 203.0.113.10
logging host 198.51.100.50
logging trap debugging
!
interface Loopback0
ip address 192.0.2.1 255.255.255.255
!
R1#show ntp status
Clock is unsynchronized, stratum 16, no reference clock
nominal freq: 250.0000 Hz, actual freq: 250.0000 Hz, precision: 2**10
reference time: 0.0.0.0 00:00:00.000 UTC Mon Jan 1 2000
clock offset: 0.0000 msec, root delay: 0.00 msec
root dispersion: 0.00 msec, peer dispersion: 0.00 msec
loopfilter state: 'CTRL' (Normal Controlled), drift: 0.00000000 s/s
system poll interval: 64, last update was 0 sec ago.
R1#show ntp associations
address ref clock st when poll reach delay offset disp
*~203.0.113.10 .INIT. 16 - 64 0 0.00 0.00 16000.
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured
R1#show logging | include Logging
Syslog logging: enabled
Console logging: level debugging, 0 messages logged
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 0 messages logged
Trap logging: level debugging, 0 messages logged
Logging to 198.51.100.50 (udp port 514, audit disabled, link up),
2 messages logged, level debugging
A
Configure 'ntp source Loopback0' and 'logging trap critical'
The 'ntp source Loopback0' command ensures NTP packets use the stable Loopback0 interface IP, enabling synchronization. The 'logging trap critical' command restricts syslog messages to severity 2 (critical) and higher, meeting the requirement.
B
Configure 'ntp server 203.0.113.10 source Loopback0' and 'logging trap 2'
Why wrong: The 'ntp server' command does not support a 'source' keyword; the correct command is 'ntp source Loopback0'. Also, 'logging trap 2' is valid but less common; however, the primary error is the NTP command syntax.
C
Configure 'ntp source Loopback0' and 'logging trap 7'
Why wrong: While 'ntp source Loopback0' is correct, 'logging trap 7' sets the trap level to debugging (severity 7), which sends all syslog messages, not just critical and higher.
D
Configure 'ntp server 203.0.113.10' and 'logging host 198.51.100.50'
Why wrong: These commands are already present in the configuration; they do not address the missing NTP source interface or the incorrect logging trap level. The NTP source must be explicitly set, and the trap level must be changed from debugging to critical.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure 'ntp source Loopback0' and 'logging trap critical'
The NTP client was not synchronizing because the NTP source interface was not specified; the router uses the outgoing interface which may not be reachable or consistent. The 'ntp source Loopback0' command ensures NTP packets use a stable, routable IP address. For syslog, the logging trap was set to 'debugging', which sends all messages (severity 7). The requirement is to send only 'critical' (severity 2) and higher. The command 'logging trap critical' changes the filter. After both fixes, 'show ntp status' should show synchronized, stratum <16, and 'show logging' should show 'level critical' for trap logging.
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.
✓
Configure 'ntp source Loopback0' and 'logging trap critical'
Why this is correct
The 'ntp source Loopback0' command ensures NTP packets use the stable Loopback0 interface IP, enabling synchronization. The 'logging trap critical' command restricts syslog messages to severity 2 (critical) and higher, meeting the requirement.
Related concept
Read the scenario before looking for a memorised answer.
✗
Configure 'ntp server 203.0.113.10 source Loopback0' and 'logging trap 2'
Why it's wrong here
The 'ntp server' command does not support a 'source' keyword; the correct command is 'ntp source Loopback0'. Also, 'logging trap 2' is valid but less common; however, the primary error is the NTP command syntax.
✗
Configure 'ntp source Loopback0' and 'logging trap 7'
Why it's wrong here
While 'ntp source Loopback0' is correct, 'logging trap 7' sets the trap level to debugging (severity 7), which sends all syslog messages, not just critical and higher.
✗
Configure 'ntp server 203.0.113.10' and 'logging host 198.51.100.50'
Why it's wrong here
These commands are already present in the configuration; they do not address the missing NTP source interface or the incorrect logging trap level. The NTP source must be explicitly set, and the trap level must be changed from debugging to critical.
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.
✓Configure 'ntp source Loopback0' and 'logging trap critical'Correct answer▾
Why this is correct
The 'ntp source Loopback0' command ensures NTP packets use the stable Loopback0 interface IP, enabling synchronization. The 'logging trap critical' command restricts syslog messages to severity 2 (critical) and higher, meeting the requirement.
✗Configure 'ntp server 203.0.113.10 source Loopback0' and 'logging trap 2'Wrong answer — click to see why▾
Why this is wrong here
The NTP command syntax is incorrect; 'ntp server' does not accept a 'source' parameter. The correct approach is a separate 'ntp source' command.
Why candidates choose this
Candidates may think the source can be specified directly in the 'ntp server' command, similar to other protocols like 'tftp' or 'ftp'.
✗Configure 'ntp source Loopback0' and 'logging trap 7'Wrong answer — click to see why▾
Why this is wrong here
The logging trap level 7 corresponds to debugging, which is the most verbose level. The requirement is for critical (severity 2) and higher, so this would send too many messages.
Why candidates choose this
Candidates may confuse severity levels or think a higher number means more restrictive filtering, but in syslog, lower numbers are more severe.
✗Configure 'ntp server 203.0.113.10' and 'logging host 198.51.100.50'Wrong answer — click to see why▾
Why this is wrong here
The commands listed are already configured and do not fix the synchronization issue or the syslog filtering. The NTP source interface is missing, and the logging trap level is still debugging.
Why candidates choose this
Candidates might think that simply specifying the NTP server and syslog host is sufficient, overlooking the need for source interface and trap level configuration.
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.
Trap categories for this question
Keyword trap
The 'ntp server' command does not support a 'source' keyword; the correct command is 'ntp source Loopback0'. Also, 'logging trap 2' is valid but less common; however, the primary error is the NTP command syntax.
Command / output trap
The 'ntp server' command does not support a 'source' keyword; the correct command is 'ntp source Loopback0'. Also, 'logging trap 2' is valid but less common; however, the primary error is the NTP command syntax.
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: Configure 'ntp source Loopback0' and 'logging trap critical' — The NTP client was not synchronizing because the NTP source interface was not specified; the router uses the outgoing interface which may not be reachable or consistent. The 'ntp source Loopback0' command ensures NTP packets use a stable, routable IP address. For syslog, the logging trap was set to 'debugging', which sends all messages (severity 7). The requirement is to send only 'critical' (severity 2) and higher. The command 'logging trap critical' changes the filter. After both fixes, 'show ntp status' should show synchronized, stratum <16, and 'show logging' should show 'level critical' for trap logging.
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 →
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.