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 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.
R1#show running-config | include ntp|logging
logging host 192.0.2.100
logging trap debugging
!
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
ntp uptime is 0 minutes, resolution 4000 ms
reference time is 0x00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)
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 'NC' (No Connection)
R1#show ntp associations
address ref clock st when poll reach delay offset disp
*~0.0.0.0 .INIT. 16 - 64 0 0.000 0.000 16000.
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured
A
ntp server 203.0.113.10 source Loopback0
logging trap notifications
Why wrong: This command sequence correctly configures R1 as an NTP client with the specified server and source interface, and sets the syslog trap level to 5 (notifications), which captures events at level 5 and above (including critical, alerts, and emergencies).
B
ntp server 203.0.113.10
ntp source Loopback0
logging trap notifications
Correctly configures NTP server with 'ntp server 203.0.113.10' and sets the NTP source interface separately using 'ntp source Loopback0'. Logging trap is set to notifications (level 5), meeting all requirements.
C
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 7, which captures all messages including debugging. The requirement is to capture events from level 5 (notice) and above, which means level 5 and higher (0-5). Debugging is level 7, which is too low (actually higher number means lower severity? In syslog, lower numbers are more severe. Level 5 is notice, level 7 is debug. So 'logging trap debugging' captures level 7 and above, which includes all levels, but the requirement is to capture level 5 and above, which is more restrictive. Actually, 'logging trap debugging' captures level 7 and above, meaning it includes debugging and all lower severity (higher number) messages? Wait, Cisco trap levels: 0=emergencies, 1=alerts, 2=critical, 3=errors, 4=warnings, 5=notifications, 6=informational, 7=debugging. When you set 'logging trap debugging', it means you want to capture messages at level 7 and above (i.e., levels 0-7). That is too broad; the requirement is to capture level 5 and above (0-5). So this would include informational and debugging, which are not required. Also, the current issue is that only debugging messages are being sent, which suggests the trap level is set to debugging, so this option would not change the behavior.
D
ntp server 203.0.113.10
logging host 192.0.2.100
logging trap notifications
Why wrong: This is incorrect because it does not specify the source interface for NTP packets. The NTP server command is missing the 'source Loopback0' keyword, so NTP packets will use the outgoing interface IP as the source, which may not be the Loopback0 address. Additionally, the logging host command is already configured (the question states logging to 192.0.2.100 is already set up), so this option redundantly adds it, but the main error is the missing NTP source.
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
ntp source Loopback0
logging trap notifications
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.
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 it's wrong here
This command sequence correctly configures R1 as an NTP client with the specified server and source interface, and sets the syslog trap level to 5 (notifications), which captures events at level 5 and above (including critical, alerts, and emergencies).
When this WOULD be correct
This configuration is used when you need to synchronize time with an NTP server and ensure that only important system messages (level 5 and above) are sent to a syslog server.
✓
ntp server 203.0.113.10
ntp source Loopback0
logging trap notifications
Why this is correct
Correctly configures NTP server with 'ntp server 203.0.113.10' and sets the NTP source interface separately using 'ntp source Loopback0'. Logging trap is set to notifications (level 5), meeting all requirements.
Related concept
Read the scenario before looking for a memorised answer.
✗
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 7, which captures all messages including debugging. The requirement is to capture events from level 5 (notice) and above, which means level 5 and higher (0-5). Debugging is level 7, which is too low (actually higher number means lower severity? In syslog, lower numbers are more severe. Level 5 is notice, level 7 is debug. So 'logging trap debugging' captures level 7 and above, which includes all levels, but the requirement is to capture level 5 and above, which is more restrictive. Actually, 'logging trap debugging' captures level 7 and above, meaning it includes debugging and all lower severity (higher number) messages? Wait, Cisco trap levels: 0=emergencies, 1=alerts, 2=critical, 3=errors, 4=warnings, 5=notifications, 6=informational, 7=debugging. When you set 'logging trap debugging', it means you want to capture messages at level 7 and above (i.e., levels 0-7). That is too broad; the requirement is to capture level 5 and above (0-5). So this would include informational and debugging, which are not required. Also, the current issue is that only debugging messages are being sent, which suggests the trap level is set to debugging, so this option would not change the behavior.
✗
ntp server 203.0.113.10
logging host 192.0.2.100
logging trap notifications
Why it's wrong here
This is incorrect because it does not specify the source interface for NTP packets. The NTP server command is missing the 'source Loopback0' keyword, so NTP packets will use the outgoing interface IP as the source, which may not be the Loopback0 address. Additionally, the logging host command is already configured (the question states logging to 192.0.2.100 is already set up), so this option redundantly adds it, but the main error is the missing NTP source.
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
ntp source Loopback0
logging trap notificationsCorrect answer▾
Why this is correct
Correctly configures NTP server with 'ntp server 203.0.113.10' and sets the NTP source interface separately using 'ntp source Loopback0'. Logging trap is set to notifications (level 5), meeting all requirements.
✗ntp server 203.0.113.10 source Loopback0
logging trap notificationsWrong answer — click to see why▾
Why this is wrong here
Uses 'ntp server ... source Loopback0' instead of the required separate 'ntp source Loopback0' command.
★ When this WOULD be the correct answer
This configuration is used when you need to synchronize time with an NTP server and ensure that only important system messages (level 5 and above) are sent to a syslog server.
✗ntp server 203.0.113.10 source Loopback0
logging trap debuggingWrong answer — click to see why▾
Why this is wrong here
Setting the trap level to 'debugging' captures all syslog messages, including debugging, which is the current problem. The requirement is to capture only level 5 and above, so the correct level is 'notifications'.
Why candidates choose this
Candidates might confuse the trap level direction: they might think 'debugging' captures only debug messages, but it actually captures all messages because it is the highest level.
✗ntp server 203.0.113.10
logging host 192.0.2.100
logging trap notificationsWrong answer — click to see why▾
Why this is wrong here
The NTP server command lacks the 'source' keyword to specify Loopback0 as the source interface. Without this, the NTP source IP will be the IP of the interface used to reach the server, which may not be 192.168.1.1.
Why candidates choose this
Candidates might think that the source interface is optional or that the NTP server command alone is sufficient, but the question explicitly requires using Loopback0 as the source.
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 it does not specify the source interface for NTP packets. The NTP server command is missing the 'source Loopback0' keyword, so NTP packets will use the outgoing interface IP as the source, which may not be the Loopback0 address. Additionally, the logging host command is already configured (the question states logging to 192.0.2.100 is already set up), so this option redundantly adds it, but the main error is the missing NTP source.
Command / output trap
This command sequence correctly configures R1 as an NTP client with the specified server and source interface, and sets the syslog trap level to 5 (notifications), which captures events at level 5 and above (including critical, alerts, and emergencies).
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
ntp source Loopback0
logging trap notifications — 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.
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.