The answer is to configure 'ntp source Vlan100' and 'logging trap debugging' on R1. The NTP client fails to synchronize because no explicit source interface is set; without this, NTP packets may be sourced from a random interface IP, causing the server to reject them as untrusted. By specifying 'ntp source Vlan100', the client uses the correct SVI IP 192.168.1.1 for all NTP messages, allowing synchronization. For syslog, the default trap level is 'critical' (severity 3), which blocks debugging and informational messages; the command 'logging trap debugging' lowers the threshold to level 7, forwarding all system messages from debug upward. On the CCNA 200-301 v2 exam, this tests your understanding of NTP source interface requirements and syslog severity levels—a common trap is forgetting that NTP needs a consistent source IP for authentication or reachability, while syslog traps are often confused with the 'logging console' command. Memory tip: think "NTP needs a home (source interface), and syslog needs a lower trap to catch the bugs (debugging)."
CCNA AI and Network Operations Practice Question
This 200-301 practice question tests your understanding of ai and network operations. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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. The network operations center (NOC) has asked you to configure R1 as an NTP client of the NTP server at 192.0.2.10 (reachable via VLAN 100, SVI 192.168.1.1/24). They also need all system messages of level 'debug' (level 7) and higher forwarded to the syslog server at 203.0.113.50. The current configuration shows that NTP is not working (stratum 16) and syslog is only sending critical and higher messages. Fix both issues.
R1#show ntp status
Clock is unsynchronized, stratum 16, no reference clock
nominal freq is 250.00000 Hz, actual freq is 250.00000 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 ntp associations
address ref clock st when poll reach delay offset disp
*~0.0.0.0 0.0.0.0 16 - 64 0 0.00 0.00 16000.
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured
R1#show logging
Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
Console logging: level debugging, 0 messages logged
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 0 messages logged
Trap logging: level critical, 0 messages logged
Logging to: 203.0.113.50 (udp port 514, audit disabled, link up)
R1#show running-config | section ntp
ntp server 192.0.2.10
!
R1#show running-config | section logging
logging host 203.0.113.50
!
A
Configure 'ntp source Vlan100' and 'logging trap debugging'.
This is correct because 'ntp source Vlan100' ensures NTP packets are sourced from the VLAN 100 interface IP (192.168.1.1), which is reachable to the NTP server. 'logging trap debugging' sets the syslog trap level to debugging (severity 7), allowing all messages from debug and higher to be sent to the syslog server.
B
Configure 'ntp server 192.0.2.10' and 'logging trap 7'.
Why wrong: This is incorrect because 'ntp server 192.0.2.10' is already configured (implied by the scenario). The issue is the missing source interface, not the server command. 'logging trap 7' is not a valid command; the correct syntax is 'logging trap debugging' or 'logging trap 7' is not standard (though severity 7 is debugging, the keyword is preferred).
C
Configure 'ntp source Vlan100' and 'logging trap warnings'.
Why wrong: This is incorrect because 'logging trap warnings' sets the syslog trap level to warnings (severity 4), which filters out messages with severity lower than warnings (like notifications, informational, and debug). The NOC requires all messages up to debug level, so the trap level must be set to debugging.
D
Configure 'ntp update-calendar' and 'logging trap informational'.
Why wrong: This is incorrect because 'ntp update-calendar' updates the hardware calendar from NTP, but does not fix the source interface issue. 'logging trap informational' sets the trap level to informational (severity 6), which still excludes debug messages (severity 7).
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 Vlan100' and 'logging trap debugging'.
The NTP client is not synchronizing because there is no source interface specified; the NTP packets may be sourced from an unexpected interface and the server may ignore them. The solution is to configure 'ntp source Vlan100' to ensure NTP packets use the correct source IP. Additionally, the syslog trap level is set to 'critical', which filters out messages with severity lower than critical (like warnings, errors, etc.). The NOC requires all messages up to debug level; therefore, change the logging trap level to 'debugging' with 'logging trap debugging'.
Key principle: A trunk being up does not mean the VLAN is allowed across it. Always verify the allowed VLAN list and whether the VLAN exists on both switches.
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 Vlan100' and 'logging trap debugging'.
Why this is correct
This is correct because 'ntp source Vlan100' ensures NTP packets are sourced from the VLAN 100 interface IP (192.168.1.1), which is reachable to the NTP server. 'logging trap debugging' sets the syslog trap level to debugging (severity 7), allowing all messages from debug and higher to be sent to the syslog server.
Related concept
Access ports place end devices into a single VLAN.
✗
Configure 'ntp server 192.0.2.10' and 'logging trap 7'.
Why it's wrong here
This is incorrect because 'ntp server 192.0.2.10' is already configured (implied by the scenario). The issue is the missing source interface, not the server command. 'logging trap 7' is not a valid command; the correct syntax is 'logging trap debugging' or 'logging trap 7' is not standard (though severity 7 is debugging, the keyword is preferred).
✗
Configure 'ntp source Vlan100' and 'logging trap warnings'.
Why it's wrong here
This is incorrect because 'logging trap warnings' sets the syslog trap level to warnings (severity 4), which filters out messages with severity lower than warnings (like notifications, informational, and debug). The NOC requires all messages up to debug level, so the trap level must be set to debugging.
✗
Configure 'ntp update-calendar' and 'logging trap informational'.
Why it's wrong here
This is incorrect because 'ntp update-calendar' updates the hardware calendar from NTP, but does not fix the source interface issue. 'logging trap informational' sets the trap level to informational (severity 6), which still excludes debug messages (severity 7).
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 Vlan100' and 'logging trap debugging'.Correct answer▾
Why this is correct
This is correct because 'ntp source Vlan100' ensures NTP packets are sourced from the VLAN 100 interface IP (192.168.1.1), which is reachable to the NTP server. 'logging trap debugging' sets the syslog trap level to debugging (severity 7), allowing all messages from debug and higher to be sent to the syslog server.
✗Configure 'ntp server 192.0.2.10' and 'logging trap 7'.Wrong answer — click to see why▾
Why this is wrong here
The specific factual error: 'logging trap 7' is not a valid Cisco IOS command; the correct command uses the keyword 'debugging'. Also, the NTP server command alone does not fix the source interface issue.
Why candidates choose this
Candidates might think adding the NTP server command again will fix synchronization, or they may incorrectly use the numeric severity level without the keyword.
✗Configure 'ntp source Vlan100' and 'logging trap warnings'.Wrong answer — click to see why▾
Why this is wrong here
The specific factual error: 'logging trap warnings' only sends messages with severity 0-4, missing severity 5-7 (notifications, informational, debug).
Why candidates choose this
Candidates may confuse 'warnings' with a higher severity level, not realizing that debug is the lowest severity and requires the 'debugging' keyword.
✗Configure 'ntp update-calendar' and 'logging trap informational'.Wrong answer — click to see why▾
Why this is wrong here
The specific factual error: 'ntp update-calendar' is not needed for NTP synchronization; the source interface is the key missing piece. 'logging trap informational' does not include debug messages.
Why candidates choose this
Candidates may think updating the calendar is necessary for NTP to work, or they may believe informational is the lowest level, not realizing debug is lower.
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: an active trunk can still block the VLAN you need
A trunk being up does not prove every VLAN is crossing it. Check allowed VLAN lists, native VLAN mismatch, VLAN existence and access-port assignment.
Trap categories for this question
Keyword trap
This is incorrect because 'ntp server 192.0.2.10' is already configured (implied by the scenario). The issue is the missing source interface, not the server command. 'logging trap 7' is not a valid command; the correct syntax is 'logging trap debugging' or 'logging trap 7' is not standard (though severity 7 is debugging, the keyword is preferred).
Command / output trap
This is incorrect because 'ntp server 192.0.2.10' is already configured (implied by the scenario). The issue is the missing source interface, not the server command. 'logging trap 7' is not a valid command; the correct syntax is 'logging trap debugging' or 'logging trap 7' is not standard (though severity 7 is debugging, the keyword is preferred).
Scenario analysis trap
This is incorrect because 'ntp server 192.0.2.10' is already configured (implied by the scenario). The issue is the missing source interface, not the server command. 'logging trap 7' is not a valid command; the correct syntax is 'logging trap debugging' or 'logging trap 7' is not standard (though severity 7 is debugging, the keyword is preferred).
Detailed technical explanation
How to think about this question
VLAN questions usually combine access-port and trunking clues. The key is to identify whether the issue is local to one switchport, caused by the trunk, or caused by the VLAN not existing where it needs to exist.
KKey Concepts to Remember
Access ports place end devices into a single VLAN.
Trunk ports carry multiple VLANs between switches.
Allowed VLAN lists decide which VLANs can cross a trunk.
Native VLAN mismatch can create confusing symptoms.
TExam Day Tips
→Use show vlan brief to verify access VLANs.
→Use show interfaces trunk to verify trunk state and allowed VLANs.
→Do not treat every same-VLAN issue as a routing problem.
Key takeaway
A trunk being up does not mean the VLAN is allowed across it. Always verify the allowed VLAN list and whether the VLAN exists on both switches.
Real-world example
How this comes up in practice
A help-desk technician troubleshoots why a newly connected PC cannot reach shared printers on the same floor. The cable is good, the switch port is active, but the PC is in VLAN 20 and the printers are in VLAN 10. The uplink trunk only allows VLAN 10. A trunk being up does not mean every VLAN crosses it.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this 200-301 question in full detail.
Review VLAN allowed lists, native VLAN mismatch detection, and how to verify VLAN membership with show vlan brief and show interfaces trunk. Then practise related 200-301 questions on switching, trunking, and access-port configuration.
AI and Network Operations — This question tests AI and Network Operations — Access ports place end devices into a single VLAN..
What is the correct answer to this question?
The correct answer is: Configure 'ntp source Vlan100' and 'logging trap debugging'. — The NTP client is not synchronizing because there is no source interface specified; the NTP packets may be sourced from an unexpected interface and the server may ignore them. The solution is to configure 'ntp source Vlan100' to ensure NTP packets use the correct source IP. Additionally, the syslog trap level is set to 'critical', which filters out messages with severity lower than critical (like warnings, errors, etc.). The NOC requires all messages up to debug level; therefore, change the logging trap level to 'debugging' with 'logging trap debugging'.
What should I do if I get this 200-301 question wrong?
Review VLAN allowed lists, native VLAN mismatch detection, and how to verify VLAN membership with show vlan brief and show interfaces trunk. Then practise related 200-301 questions on switching, trunking, and access-port configuration.
What is the key concept behind this question?
Access ports place end devices into a single VLAN.
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.