The correct configuration is the `ntp server 203.0.113.10 source Loopback0` command combined with `logging trap notifications`. This solves two distinct issues: the NTP client source interface must be explicitly set to Loopback0 because, by default, the router uses the outgoing interface’s IP address for NTP packets, which may not be routable back from the server, leaving the client stuck at stratum 16 (unsynchronized). For syslog, the trap level was likely set to `informational` (level 6), which floods the server with low-severity messages; changing it to `notifications` (level 5) captures only severity 0–5, ensuring critical alerts are not missed. 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` must match the interface used in the `ntp server` statement, or confusing syslog severity levels (lower number = higher severity). Memory tip: “Source your loopback for stable NTP, and trap notifications to cut the chatter.”
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.
Network Topology
You are connected to R1. Configure NTP client to synchronize with the NTP server at 203.0.113.10, using the loopback0 interface (192.168.1.1/32) as the source. Also configure syslog to send messages of severity level 5 (notifications) and below to the syslog server at 198.51.100.20. Currently, NTP shows stratum 16 (unsynchronized) and important syslog messages are being missed.
R1# show ntp status
Clock is unsynchronized, stratum 16, no reference clock
nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**10
reference time is 0.0.0.0 (00:00:00.000 UTC Mon Jan 1 2000)
clock offset is 0.0000 msec, root delay is 0.00 msec
root dispersion is 0.00 msec, peer dispersion is 0.00 msec
loopfilter state is 'CTRL' (Normal Controlled Loop)
R1# show run | section ntp
ntp server 203.0.113.10
R1# show run | include logging
logging host 198.51.100.20
no logging console
R1# show logging
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes)
Console logging: disabled
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 0 messages logged
Trap logging: level informational, 0 messages logged
Logging to 198.51.100.20 (udp port 514, audit disabled,
link up)
A
ntp server 203.0.113.10 source Loopback0
logging trap notifications
This configuration correctly specifies the NTP server with the source interface as Loopback0, ensuring consistent source IP for NTP packets. The 'logging trap notifications' command sets syslog severity to capture notifications (level 5) and above, filtering out lower-severity messages.
B
ntp server 203.0.113.10 source Loopback0
logging trap informational
Why wrong: This is incorrect because 'logging trap informational' sets the syslog trap level to informational (level 6), which includes all messages from level 6 and below, missing notifications (level 5) and above. The correct command is 'logging trap notifications'.
C
ntp server 203.0.113.10
logging trap notifications
Why wrong: This is incorrect because the NTP source interface is not specified. Without 'source Loopback0', the router uses the outgoing interface IP, which may not be reachable by the NTP server for replies, causing synchronization failure.
D
ntp server 203.0.113.10 source Loopback0
logging trap debugging
Why wrong: This is incorrect because 'logging trap debugging' sets the trap level to debugging (level 7), which captures all messages including very verbose debugging information, not just notifications and above. This would flood the syslog server with unnecessary messages.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
ntp server 203.0.113.10 source Loopback0
logging trap notifications
The NTP client is not synchronizing because the source interface is not specified; by default, the router uses the outgoing interface IP which may not be reachable by the NTP server for replies. Adding 'ntp source Loopback0' ensures NTP packets have a consistent source IP. The syslog trap level was set to 'informational' (level 6), which includes too many messages; to capture only notifications (level 5) and below (i.e., severity 0–5), change the trap level to 'notifications' using 'logging trap notifications'. This filters out lower-severity messages while retaining those that are notifications or more critical.
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 203.0.113.10 source Loopback0
logging trap notifications
Why this is correct
This configuration correctly specifies the NTP server with the source interface as Loopback0, ensuring consistent source IP for NTP packets. The 'logging trap notifications' command sets syslog severity to capture notifications (level 5) and above, filtering out lower-severity messages.
Related concept
Read the scenario before looking for a memorised answer.
✗
ntp server 203.0.113.10 source Loopback0
logging trap informational
Why it's wrong here
This is incorrect because 'logging trap informational' sets the syslog trap level to informational (level 6), which includes all messages from level 6 and below, missing notifications (level 5) and above. The correct command is 'logging trap notifications'.
✗
ntp server 203.0.113.10
logging trap notifications
Why it's wrong here
This is incorrect because the NTP source interface is not specified. Without 'source Loopback0', the router uses the outgoing interface IP, which may not be reachable by the NTP server for replies, causing synchronization failure.
✗
ntp server 203.0.113.10 source Loopback0
logging trap debugging
Why it's wrong here
This is incorrect because 'logging trap debugging' sets the trap level to debugging (level 7), which captures all messages including very verbose debugging information, not just notifications and above. This would flood the syslog server with unnecessary messages.
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 203.0.113.10 source Loopback0
logging trap notificationsCorrect answer▾
Why this is correct
This configuration correctly specifies the NTP server with the source interface as Loopback0, ensuring consistent source IP for NTP packets. The 'logging trap notifications' command sets syslog severity to capture notifications (level 5) and above, filtering out lower-severity messages.
✗ntp server 203.0.113.10 source Loopback0
logging trap informationalWrong answer — click to see why▾
Why this is wrong here
The trap level 'informational' captures messages of severity 6 and lower, but notifications are severity 5, which is higher and thus not included.
Why candidates choose this
Candidates may confuse the severity levels, thinking 'informational' includes notifications because it sounds broader, but in syslog, lower numbers indicate higher severity.
✗ntp server 203.0.113.10
logging trap notificationsWrong answer — click to see why▾
Why this is wrong here
The NTP source interface must be explicitly set to ensure the server can reply to the correct IP; omitting it can lead to unsynchronized state.
Why candidates choose this
Candidates might think the source interface is optional or that the router automatically uses a reachable IP, but in scenarios with multiple interfaces, specifying the source is critical.
✗ntp server 203.0.113.10 source Loopback0
logging trap debuggingWrong answer — click to see why▾
Why this is wrong here
The debugging level includes all severities, which is too broad; the requirement is to capture only notifications (level 5) and above, which requires 'notifications' level.
Why candidates choose this
Candidates might think 'debugging' captures everything including notifications, but it captures too much, and the question specifies only notifications and above, not all messages.
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
Command / output trap
This is incorrect because 'logging trap informational' sets the syslog trap level to informational (level 6), which includes all messages from level 6 and below, missing notifications (level 5) and above. The correct command is 'logging trap notifications'.
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 203.0.113.10 source Loopback0
logging trap notifications — The NTP client is not synchronizing because the source interface is not specified; by default, the router uses the outgoing interface IP which may not be reachable by the NTP server for replies. Adding 'ntp source Loopback0' ensures NTP packets have a consistent source IP. The syslog trap level was set to 'informational' (level 6), which includes too many messages; to capture only notifications (level 5) and below (i.e., severity 0–5), change the trap level to 'notifications' using 'logging trap notifications'. This filters out lower-severity messages while retaining those that are notifications or more critical.
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. Configure R1 as an NTP client to synchronize with NTP server 203.0.113.10, using its Loopback0 interface (192.168.1.1/32) as the source for NTP packets. Additionally, configure logging to syslog server 192.0.2.100 with a trap level that captures events from level 5 (notice) and above. The current configuration shows that NTP is not synchronized (stratum 16) and only debugging messages are being sent to the syslog server. Correct these issues so that R1 is synchronized and important system messages are logged.
hard
A.ntp server 203.0.113.10 source Loopback0
logging trap notifications
✓ B.ntp server 203.0.113.10
ntp source Loopback0
logging trap notifications
C.ntp server 203.0.113.10 source Loopback0
logging trap debugging
D.ntp server 203.0.113.10
logging host 192.0.2.100
logging trap notifications
Why B: The correct configuration is to add the NTP server with 'ntp server 203.0.113.10' and set the source interface separately with 'ntp source Loopback0'. For syslog, the command 'logging trap notifications' sets the trap level to 5 (notice), ensuring that critical and important messages are logged while excluding debugging output. Option A uses the combined 'ntp server ... source Loopback0' and does not match the separate source configuration required. Option C keeps logging at debugging level (7), which is too verbose. Option D lacks the NTP source configuration entirely.
Variation 2. You are connected to R1. Configure NTP client so that R1 synchronizes with the NTP server at 198.51.100.10, using its Loopback0 (10.0.0.1/32) as the source interface. Also configure syslog to send messages of severity 5 (notifications) and above to 192.0.2.20. The current configuration shows a misconfigured NTP server address and an incorrect logging trap level. Verify with 'show ntp status' (stratum should not be 16) and 'show logging'.
hard
✓ A.ntp server 198.51.100.10 source Loopback0
logging trap notifications
B.ntp server 198.51.100.10 source Loopback0
logging trap 4
C.ntp server 198.51.100.10
logging trap notifications
D.ntp server 203.0.113.5 source Loopback0
logging trap 7
Why A: The misconfigured NTP server address (203.0.113.5) and the debug-level logging trap (7) must be corrected to meet requirements. The correct commands are 'ntp server 198.51.100.10 source Loopback0' to use the specified server and Loopback0 as source, and 'logging trap notifications' (severity 5) to send only notifications and more severe messages. Option B is wrong because 'logging trap 4' sets the trap level to warning, which would not forward notifications. Option C misses the source interface, and Option D uses the wrong NTP server and an overly verbose trap level.
Variation 3. You are connected to R1 via the console. R1 should synchronize its clock with the NTP server 192.0.2.10 using its loopback0 interface (IP 10.0.0.1) as the source. Additionally, syslog messages of severity 'notification' (level 5) and above must be sent to the syslog server at 198.51.100.20. Currently, R1 shows NTP stratum 16 (unsynchronized) and syslog messages are not being forwarded. Identify and resolve the issues.
hard
✓ A.Add 'ntp server 192.0.2.10' and change 'logging trap informational' to 'logging trap notifications'.
B.Add 'ntp server 192.0.2.10' and change 'logging trap notifications' to 'logging trap informational'.
C.Add 'ntp server 192.0.2.10' and change 'logging trap notifications' to 'logging trap debugging'.
D.Add 'ntp server 192.0.2.10' and change 'logging trap informational' to 'logging trap emergencies'.
Why A: The NTP is unsynchronized because the 'ntp server' command is missing; only 'ntp source' is configured. Add 'ntp server 192.0.2.10' to point to the NTP server. The syslog trap level is set to 'informational' (level 6), which is too low—messages of level 5 (notification) are not sent because the trap level must be equal to or higher severity than the messages to be forwarded. Change the trap level to 'notifications' (level 5) to ensure level 0-5 messages are forwarded.
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.