The answer is to configure `ntp source Loopback0` and `logging trap notifications`. The NTP source command forces all NTP packets to use the loopback0 IP (10.0.0.1) as the origin, ensuring the server sees a consistent, reachable address for replies—without it, the router uses the egress interface’s IP, which may not be routable back. For syslog, the default trap level is debugging (level 7), which sends everything; changing it to notifications (level 5) filters out lower-severity messages like debug and informational, saving bandwidth. On the CCNA 200-301 v2 exam, this tests your ability to troubleshoot NTP synchronization and syslog filtering, two common real-world misconfigurations. A common trap is forgetting that `ntp source` is a global command, not applied per server, and that syslog severity levels are inverse (lower number = higher severity). Memory tip: NTP needs a stable source, so think “Loopback for stable sync”; for syslog, remember “trap notifications” stops the debug chatter.
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 console. The NTP server 198.51.100.10 is already configured on R1, but R1 is not synchronizing because the NTP packets are sourced from the wrong interface. Configure R1 to source NTP packets from its loopback0 interface (IP 10.0.0.1/32). Additionally, configure syslog logging to the remote server 203.0.113.5, ensuring that only messages at severity 'notifications' (level 5) and above are sent. The current configuration shows that syslog is sending all messages (including debug-level) to the server, wasting bandwidth. Fix both issues.
R1# show running-config | section ntp|logging
ntp server 198.51.100.10
logging host 203.0.113.5
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
*~198.51.100.10 .INIT. 16 - 1024 0 0.0 0.0 16000.
~ (synchronized), * (candidate), # (selected), + (peer), - (outlier)
R1# show logging
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited)
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 message lines logged
Logging to 203.0.113.5 (udp port 514, audit disabled)
0 message lines logged
A
Configure 'ntp source Loopback0' and 'logging trap notifications'.
This is correct because 'ntp source Loopback0' ensures NTP packets are sourced from the loopback interface, providing a consistent source IP for the NTP server to reply to. 'logging trap notifications' sets the syslog trap level to 'notifications' (severity 5), filtering out lower-severity messages like debug (7) and informational (6).
B
Configure 'ntp server 198.51.100.10 source Loopback0' and 'logging trap warnings'.
Why wrong: This is incorrect because the 'ntp server' command does not support the 'source' keyword; the source interface is configured separately with 'ntp source'. Also, 'logging trap warnings' sets the level to 'warnings' (severity 4), which includes messages below 'notifications' (severity 5), so it does not meet the requirement of only sending notifications and above.
C
Configure 'ntp source Loopback0' and 'logging trap debugging'.
Why wrong: This is incorrect because 'logging trap debugging' sets the syslog trap level to 'debugging' (severity 7), which sends all messages including debug-level, wasting bandwidth. The requirement is to send only notifications (level 5) and above, which requires 'logging trap notifications'.
D
Configure 'ntp server 198.51.100.10' and 'logging trap notifications'.
Why wrong: This is incorrect because while the syslog configuration is correct, the NTP configuration lacks the 'ntp source Loopback0' command. Without specifying the source interface, NTP packets will use the outgoing interface's IP address, which may not be reachable by the server or may cause synchronization issues if the interface goes down.
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 notifications'.
The NTP client is not synchronizing because the NTP packets are not sourced from an interface that the server can reach and reply to; the default source is the outgoing interface, but the server sees a different source IP. The `ntp server 198.51.100.10` command is already configured (not shown), so you only need to specify the source interface with `ntp source Loopback0`. Also, the syslog trap level is set to 'debugging', which sends all messages; change it to 'notifications' to filter out lower-severity messages. After these changes, verify with 'show ntp status' (should show stratum less than 16 and 'synchronized') and 'show ntp associations' (should show a reach count > 0 and a valid ref clock). Check syslog with 'show logging' to confirm trap level is 'notifications'.
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 notifications'.
Why this is correct
This is correct because 'ntp source Loopback0' ensures NTP packets are sourced from the loopback interface, providing a consistent source IP for the NTP server to reply to. 'logging trap notifications' sets the syslog trap level to 'notifications' (severity 5), filtering out lower-severity messages like debug (7) and informational (6).
Related concept
Read the scenario before looking for a memorised answer.
✗
Configure 'ntp server 198.51.100.10 source Loopback0' and 'logging trap warnings'.
Why it's wrong here
This is incorrect because the 'ntp server' command does not support the 'source' keyword; the source interface is configured separately with 'ntp source'. Also, 'logging trap warnings' sets the level to 'warnings' (severity 4), which includes messages below 'notifications' (severity 5), so it does not meet the requirement of only sending notifications and above.
✗
Configure 'ntp source Loopback0' and 'logging trap debugging'.
Why it's wrong here
This is incorrect because 'logging trap debugging' sets the syslog trap level to 'debugging' (severity 7), which sends all messages including debug-level, wasting bandwidth. The requirement is to send only notifications (level 5) and above, which requires 'logging trap notifications'.
✗
Configure 'ntp server 198.51.100.10' and 'logging trap notifications'.
Why it's wrong here
This is incorrect because while the syslog configuration is correct, the NTP configuration lacks the 'ntp source Loopback0' command. Without specifying the source interface, NTP packets will use the outgoing interface's IP address, which may not be reachable by the server or may cause synchronization issues if the interface goes down.
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 notifications'.Correct answer▾
Why this is correct
This is correct because 'ntp source Loopback0' ensures NTP packets are sourced from the loopback interface, providing a consistent source IP for the NTP server to reply to. 'logging trap notifications' sets the syslog trap level to 'notifications' (severity 5), filtering out lower-severity messages like debug (7) and informational (6).
✗Configure 'ntp server 198.51.100.10 source Loopback0' and 'logging trap warnings'.Wrong answer — click to see why▾
Why this is wrong here
The specific factual error: The 'ntp server' command cannot specify a source interface; that is done with 'ntp source'. Additionally, 'warnings' (level 4) is more severe than 'notifications' (level 5), but the requirement is to send only notifications and above, which includes levels 0-5. 'warnings' includes levels 0-4, missing level 5 (notifications).
Why candidates choose this
Candidates might think the source can be specified directly in the 'ntp server' command, similar to other protocols, and may confuse syslog severity levels, thinking 'warnings' is higher than 'notifications'.
✗Configure 'ntp source Loopback0' and 'logging trap debugging'.Wrong answer — click to see why▾
Why this is wrong here
The specific factual error: 'logging trap debugging' sends all syslog messages (levels 0-7), which is the default and does not filter out lower-severity messages. The correct level for notifications and above is 'notifications' (level 5).
Why candidates choose this
Candidates may mistakenly think 'debugging' is the correct level for notifications, or they may not realize that the default is already 'debugging' and that they need to change it to a higher severity level.
✗Configure 'ntp server 198.51.100.10' and 'logging trap notifications'.Wrong answer — click to see why▾
Why this is wrong here
The specific factual error: The NTP client is not configured to source packets from Loopback0. The 'ntp server' command alone does not set the source interface; an additional 'ntp source' command is required.
Why candidates choose this
Candidates may think that simply specifying the NTP server is enough, or they may assume the source is automatically the loopback if it is the only interface. However, the default source is the outgoing interface, not the loopback.
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
This is incorrect because the 'ntp server' command does not support the 'source' keyword; the source interface is configured separately with 'ntp source'. Also, 'logging trap warnings' sets the level to 'warnings' (severity 4), which includes messages below 'notifications' (severity 5), so it does not meet the requirement of only sending notifications and above.
Command / output trap
This is incorrect because the 'ntp server' command does not support the 'source' keyword; the source interface is configured separately with 'ntp source'. Also, 'logging trap warnings' sets the level to 'warnings' (severity 4), which includes messages below 'notifications' (severity 5), so it does not meet the requirement of only sending notifications and above.
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 notifications'. — The NTP client is not synchronizing because the NTP packets are not sourced from an interface that the server can reach and reply to; the default source is the outgoing interface, but the server sees a different source IP. The `ntp server 198.51.100.10` command is already configured (not shown), so you only need to specify the source interface with `ntp source Loopback0`. Also, the syslog trap level is set to 'debugging', which sends all messages; change it to 'notifications' to filter out lower-severity messages. After these changes, verify with 'show ntp status' (should show stratum less than 16 and 'synchronized') and 'show ntp associations' (should show a reach count > 0 and a valid ref clock). Check syslog with 'show logging' to confirm trap level is 'notifications'.
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.