Courseiva

CCNA Ntp Questions

22 questions · Ntp topic · All types, answers revealed

1
PBQhard

You are connected to R1, a branch router that must synchronize time with the NTP server at 198.51.100.1 (reachable via G0/0) and send critical syslog messages (severity 0-4) to the logging server at 203.0.113.10. The current configuration has NTP pointing to a wrong server and syslog set to debug level, flooding the server. Correct the NTP server, set the NTP source interface to Loopback0 (10.10.10.1/32), and adjust the syslog trap level so that only emergencies through warnings are logged.

Hints

  • •Remove the incorrect NTP server before adding the correct one.
  • •Use the 'ntp source' command to specify the Loopback interface.
  • •The logging trap level 'warnings' corresponds to severity 4.
A.no ntp server 192.0.2.1; ntp server 198.51.100.1; ntp source Loopback0; logging trap warnings
B.ntp server 198.51.100.1 source G0/0; logging trap errors
C.ntp server 192.0.2.1 source Loopback0; logging trap warnings
D.ntp server 198.51.100.1 source Loopback0; logging trap debugging
AnswerA
solution
! R1
configure terminal
no ntp server 192.0.2.1
ntp server 198.51.100.1
ntp source Loopback0
logging trap warnings
end

Why this answer

The router points to the wrong NTP server (192.0.2.1: reach 0, stratum 16, unsynchronized). Remove it and configure the correct server 198.51.100.1, with Loopback0 as the NTP source interface (ntp source Loopback0, or the source keyword on the ntp server command). The syslog trap level is debugging (7), which sends every message; 'logging trap warnings' (level 4) sends only emergencies through warnings (severity 0-4).

Verify with show ntp associations, show ntp status and show running-config | include logging trap.

Exam trap

Watch out for two separate configuration items: NTP and syslog. Ensure you update both the NTP server IP and source interface, and set the correct syslog trap level. Common traps include forgetting to change the NTP server IP, using the wrong source interface, or setting the wrong syslog severity level.

Why the other options are wrong

B

The source interface must be Loopback0 for consistency, and the trap level should be warnings (4) to include warnings.

C

The NTP server address must be updated to 198.51.100.1; 192.0.2.1 is the misconfigured server.

D

The trap level should be warnings (4), not debugging (7). Debugging sends all messages, flooding the server.

2
MCQhard

A network engineer notices that the system clock on a Cisco IOS-XE router is incorrect, causing syslog timestamps to be unreliable. The router is configured as an NTP client of the server 192.168.1.10, and no NTP authentication is configured on either side. The exhibit shows the output gathered on the router. What is the most likely cause of the problem?

A.The NTP server is using TCP instead of UDP for NTP communication.
B.The router has no route to the NTP server 192.168.1.10.
C.The NTP server has a higher stratum level than the router's local clock, so the router ignores it.
D.NTP authentication is misconfigured on the router.
AnswerB

The reach value of 0 in 'show ntp associations' means no NTP response has been received. 'show ip route 192.168.1.10' returns '% Network not in table' and the ping fails, so the router cannot send NTP requests to the server. Adding a route fixes it.

Why this answer

The association table shows 192.168.1.10 as configured (~) but with reach 0 and no response ever received (ref clock .INIT., stratum 16, 'never updated'). The routing table has no entry for 192.168.1.10 and the ping fails, so the NTP requests (UDP 123) never reach the server. The fix is to add a route to the server's subnet.

The server is not using TCP, a stratum difference does not prevent packet exchange, and no authentication is configured.

Exam trap

Cisco often tests the misconception that NTP uses TCP or that authentication is the primary cause of synchronization failure, when in fact the most common issue is simple network reachability or firewall blocking of UDP port 123.

Why the other options are wrong

C

The NTP server having a higher stratum level than the local clock does not prevent synchronization outright; the router will still attempt to sync if the server is reachable and authenticates, so this is not the most likely cause.

3
MCQhard

Router R1 is configured as an NTP client of the server 192.0.2.1, but it does not synchronize. There is no firewall between R1 and 192.0.2.1 and no NTP authentication is configured. Based on the exhibit, what is the most likely cause?

A.The NTP server at 192.0.2.1 is not configured as a peer on R1.
B.Router R1 does not have a route to reach 192.0.2.1.
C.The NTP server at 192.0.2.1 is not using NTP version 4.
D.The NTP server at 192.0.2.1 has a firewall blocking NTP traffic.
AnswerB

'show ip route 192.0.2.1' returns '% Network not in table'. Without a route R1 cannot send NTP requests, so reach stays 0 and the clock remains unsynchronized at stratum 16.

Why this answer

The association to 192.0.2.1 is configured (~) but has reach 0 and the system 'never updated'. 'show ip route 192.0.2.1' returns '% Network not in table', so R1 has no route to the server and its NTP requests cannot be sent. With no firewall in the path, the missing route is the most likely cause.

Exam trap

Cisco often tests the misconception that NTP configuration alone ensures synchronization, but the trap here is that candidates overlook the prerequisite of IP reachability, assuming the ntp server command handles routing automatically.

Why the other options are wrong

A

Configuring the server as a peer is unnecessary for an NTP client; the client uses the ntp server command.

C

NTP version incompatibility does not prevent synchronization because devices negotiate versions automatically.

D

The problem states there is no firewall, so this cannot be the cause.

4
Drag & Dropmedium

Drag and drop the following steps into the correct order to configure an IOS-XE device as an NTP client and send its syslog messages with correct timestamps to a remote server: time source first, then timestamps, then remote logging, then verification.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

All commands are global configuration commands, so global configuration mode comes first. The time source is configured first so the clock becomes accurate, then log timestamps are enabled, then the remote syslog server is configured, and show ntp status and show logging verify the result.

Exam trap

A common trap is to think that NTP must be configured before syslog (or vice versa). The required first step is entering global configuration mode; after that, the order of NTP server and logging host commands can vary, but all required steps must be completed before verification.

5
Multi-Selecteasy

A company wants all routers and switches to use a common time source so log timestamps line up during incident review. Which two statements about NTP are correct?

Select 2 answers
A.It helps synchronize device clocks
B.Consistent time improves correlation of syslog and other event data
C.It advertises Layer 3 reachability between routers
D.It encrypts data traffic between endpoints by default
AnswersA, B

NTP uses a hierarchical stratum model to distribute UTC time from authoritative sources down to client routers and switches, typically over UDP port 123. Each device adjusts its local clock gradually to eliminate drift and jitter, converging on a mutually consistent time reference. This is the core synchronization mechanism that makes a common time base possible across all networking devices.

Why this answer

NTP (Network Time Protocol) is used to synchronize device clocks (option A) so that event timestamps are consistent across network devices, which improves correlation of syslog and other event data (option B). Option C is incorrect because NTP does not advertise Layer 3 reachability; that is a function of routing protocols like OSPF or EIGRP. Option D is incorrect because NTP does not encrypt data traffic by default; it only synchronizes time and does not provide encryption.

Exam trap

A common exam trap is mistaking NTP for a routing or security protocol. Some candidates incorrectly believe NTP advertises Layer 3 reachability like routing protocols (e.g., OSPF or EIGRP) or that it encrypts data traffic by default. This confusion arises because NTP is often mentioned alongside other network services, but its sole purpose is to synchronize device clocks.

Selecting options related to routing or encryption when the question focuses on time synchronization leads to incorrect answers. Understanding that NTP only aligns time across devices helps avoid this trap.

Why the other options are wrong

C

This option is incorrect because advertising Layer 3 reachability is the role of routing protocols like OSPF or EIGRP, not NTP, which only synchronizes time.

D

This option is incorrect as NTP does not encrypt data traffic by default; it is a time synchronization protocol and does not provide encryption services.

6
MCQmedium

Why is NTP especially valuable when a network uses centralized Syslog servers?

A.Because synchronized clocks make log timestamps easier to correlate across devices
B.Because NTP converts Syslog into a routing protocol
C.Because NTP automatically creates DHCP pools
D.Because NTP eliminates the need for a Syslog server
AnswerA

When all network devices reference the same authoritative NTP source, their log timestamps are expressed in the same time scale, so an administrator can accurately sequence events across routers, switches, and firewalls during troubleshooting. Centralized log correlation depends on consistent timestamps; without NTP, even devices with identical configurations can drift, making a single incident appear to happen at different times or in the wrong order. NTP therefore makes centralized logging meaningful by providing a common temporal reference.

Why this answer

NTP is especially valuable because centralized logs are much easier to interpret when device clocks are synchronized. In plain language, if multiple routers and switches send messages to one logging server but each device believes a different time, the event sequence becomes confusing. NTP helps align those clocks so the timestamps in the logs are consistent and the team can reconstruct incidents more accurately.

This is a practical operations concept rather than a syntax question. Syslog solves the collection problem, and NTP solves the time-correlation problem. Together they make logs more useful than either one alone. That is why the best answer focuses on timestamp consistency rather than on routing, VLAN, or NAT behavior.

Exam trap

A common exam trap is selecting an answer that incorrectly attributes routing or DHCP functions to NTP, such as thinking NTP converts Syslog into a routing protocol or automatically creates DHCP pools. These options confuse NTP’s fundamental role in time synchronization with unrelated network services. Another trap is assuming NTP eliminates the need for a Syslog server, which is false because NTP only provides accurate timestamps; it does not collect or store logs.

Understanding that NTP’s value lies in timestamp consistency, not in changing or replacing other protocols, is critical to avoid these mistakes.

Why the other options are wrong

B

Incorrect because NTP does not convert Syslog into a routing protocol; NTP’s function is strictly time synchronization, unrelated to routing protocols.

C

Incorrect because NTP does not create DHCP pools; DHCP pool creation is unrelated to time synchronization and is managed by DHCP services.

D

Incorrect because NTP does not eliminate the need for a Syslog server; it complements Syslog by providing accurate timestamps but does not replace log collection.

7
PBQmedium

You are connected to R1, an NTP client that should synchronize its clock with NTP server 192.168.1.100 (timezone UTC-5 is already configured). Configure R1 as an NTP client and send messages of severity informational (6) and more severe to the console and the logging buffer.

Network Topology
G0/0192.168.1.1/24LANR1NTP server

Hints

  • •Use ntp server command to point to the NTP server.
  • •Logging level 6 corresponds to informational.
  • •Buffered and console logging commands are separate.
A.ntp server 192.168.1.100 logging console informational logging buffered informational
B.ntp peer 192.168.1.100 logging console informational logging buffered informational
C.ntp server 192.168.1.100 logging console 5 logging buffered 5
D.ntp server 192.168.1.100 logging trap informational
AnswerA
solution
! R1
ntp server 192.168.1.100
logging console informational
logging buffered informational

Why this answer

ntp server 192.168.1.100 makes R1 an NTP client. NTP synchronization messages are logged at informational level, so the console and buffer must be set to informational (6) with logging console informational and logging buffered informational. ntp peer configures symmetric mode, a lower level such as 5 hides the messages, and logging trap affects only the syslog server.

Exam trap

200-301 often tests the difference between numeric and keyword logging levels; candidates may assume they are interchangeable, but the question may require a specific format.

Why the other options are wrong

B

ntp peer is not client mode.

C

Level 5 excludes informational messages.

D

logging trap does not affect the console or buffer.

8
MCQmedium

The playbook in the exhibit is run twice against switches that already have the NTP server configured. What is the expected result on the second run?

A.The task reports ok and makes no change because the line already exists
B.The switch adds a duplicate ntp server entry
C.The play fails because the line already exists
D.The switch reloads to apply the line
AnswerA

Idempotent module behavior.

Why this answer

The ios_config module compares the requested lines with the running configuration and only sends missing lines. When the line already exists, the task reports ok with no change. This idempotent behavior lets a playbook be rerun safely.

Why the other options are wrong

B

A duplicate is not created.

C

It is treated as already compliant.

D

A reload is not part of ios_config.

9
MCQmedium

Why is NTP especially valuable when a company uses a centralized Syslog server?

A.It synchronizes device clocks so centralized log timestamps can be correlated accurately.
B.It assigns the Syslog server its IP address.
C.It replaces the need for Syslog entirely.
D.It encrypts all Syslog messages automatically.
AnswerA

Syslog entries carry only local device clocks, so unsynchronised clocks make correlating events across devices impossible. NTP aligns all devices to a common time source, giving the centralised Syslog server consistent timestamps for accurate forensic and troubleshooting timelines.

Why this answer

NTP is especially valuable because it aligns device clocks, which makes centralized log timestamps much easier to interpret. In practical terms, if devices disagree on time, the combined log stream becomes harder to trust and correlate. NTP improves the timeline accuracy of operational and security analysis.

This is why NTP and Syslog are often discussed together. One centralizes events, and the other makes those events easier to line up correctly.

Exam trap

A common exam trap is to confuse NTP’s role with other network functions such as IP addressing or encryption. Some candidates incorrectly think NTP assigns IP addresses to devices or encrypts Syslog messages. This misunderstanding leads to selecting options that describe unrelated functions.

NTP’s sole purpose is to synchronize clocks across devices, enabling accurate timestamping of logs. Misinterpreting this can cause candidates to overlook the critical importance of time alignment in centralized logging environments, which is the core reason NTP is valuable when using a centralized Syslog server.

Why the other options are wrong

B

Incorrect because NTP does not assign IP addresses; IP addressing is handled by DHCP or manual configuration, not time synchronization protocols.

C

Incorrect because NTP does not replace Syslog; NTP provides time synchronization, while Syslog collects and centralizes log messages from devices.

D

Incorrect because NTP does not encrypt Syslog messages; encryption requires separate protocols such as TLS or IPsec, not time synchronization services.

10
PBQhard

You are connected to R1, a branch router. The NTP server 203.0.113.10 accepts requests only from R1's Loopback0 address (192.168.1.1/32), and the syslog server is 198.51.100.20. R1 currently shows 'Clock is unsynchronized, stratum 16'. Configure R1 to use Loopback0 as its NTP source so it can synchronize, and make sure syslog messages of severity informational (level 6) and more severe are sent to the syslog server.

Network Topology
G0/010.0.0.2/30linkR1R2

Hints

  • •The server is configured but reach is 0: the requests leave with the wrong source address, because the server only accepts 192.168.1.1.
  • •'ntp source Loopback0' makes NTP packets use the loopback address.
  • •'logging trap warnings' only sends levels 0-4; informational is level 6.
A.Configure 'ntp source Loopback0' and 'logging trap informational'.
B.Configure 'ntp server 203.0.113.10 source Loopback0' and 'logging trap warnings'.
C.Configure 'ntp source Loopback0' and 'logging trap notifications'.
D.Configure 'ntp source Loopback0' and 'logging host 198.51.100.20' without changing the trap level.
AnswerA
solution
! R1
configure terminal
ntp source Loopback0
logging trap informational
end
write memory

Why this answer

The NTP association is configured but reach is 0 and the clock is unsynchronized because R1 sources its requests from the outgoing interface address instead of Loopback0, which is the only address the server accepts. ntp source Loopback0 fixes this. Separately, logging trap warnings only sends severity 0-4 messages, so informational (level 6) messages are not sent; logging trap informational sends levels 0-6 to the syslog server.

Exam trap

Trap: Candidates may confuse the 'ntp server' command syntax with the global 'ntp source' command, or assume the default syslog trap level already includes informational messages. Remember: NTP source is set globally, and syslog trap levels must be explicitly configured to match the required severity.

Why the other options are wrong

B

logging trap warnings excludes informational messages.

C

notifications is more restrictive than informational.

D

The trap level must be changed.

11
MCQmedium

Why is centralized logging especially useful when combined with NTP?

A.Because synchronized clocks make centralized log timelines easier to analyze accurately.
B.Because NTP assigns the Syslog server its IP address.
C.Because Syslog replaces authentication when NTP is present.
D.Because centralized logging blocks unauthorized traffic automatically.
AnswerA

Synchronised clocks via NTP ensure that log timestamps across all network devices share a common time reference, eliminating drift that would otherwise scatter events from the same incident across different points in a centralised log timeline. This temporal alignment satisfies the constraint of accurate forensic reconstruction, as analysts can correlate events from routers, switches, and servers without manual offset correction.

Why this answer

Centralized logging is much more useful when device clocks are synchronized because the timestamps can be correlated properly. In practical terms, collecting messages in one place is valuable, but if one router thinks it is 9:00 and another thinks it is 9:17, the event sequence becomes confusing. NTP solves that time-alignment problem.

This is a common operations best practice. Syslog provides the central visibility, and NTP makes the timeline trustworthy.

Exam trap

A common exam trap is to mistakenly believe that NTP provides IP addressing or security functions such as blocking unauthorized traffic. Some may also incorrectly assume that syslog replaces authentication mechanisms when NTP is present. These misconceptions arise because candidates confuse the distinct roles of NTP and syslog.

NTP strictly synchronizes time, while syslog collects logs. Neither assigns IP addresses nor enforces access control. Understanding this separation is crucial to avoid selecting incorrect answers that attribute unrelated functions to NTP or centralized logging.

Why the other options are wrong

B

Option B is incorrect because NTP does not assign IP addresses to syslog servers or any devices. IP addressing is handled by DHCP or manual configuration, not by NTP.

C

Option C is incorrect because syslog does not replace authentication mechanisms. NTP and syslog are unrelated to access control or authentication processes in Cisco networks.

D

Option D is incorrect because centralized logging improves visibility into network events but does not block unauthorized traffic. Traffic enforcement is managed by firewalls, ACLs, or other security features.

12
Matchingmedium

Drag and drop the syslog severity levels and NTP concepts on the left to their correct descriptions on the right.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Emergency: system is unusable

Debugging: detailed debug messages

Reference clock (e.g., atomic clock or GPS)

Unsynchronized or maximum usable stratum

Configures an IOS-XE device as an NTP client

Displays NTP synchronization state and stratum

Why these pairings

Syslog severity levels range from 0 (Emergency) to 7 (Debug), with 0 being the most critical. NTP stratum indicates clock accuracy: stratum 0 is the reference clock, stratum 1 is directly connected to a reference, and so on up to stratum 15, which is the maximum usable synchronized stratum. Stratum 16 means the device is unsynchronized.

The ntp server command configures a device as a client, and show ntp status displays synchronization state and current stratum.

Exam trap

Be careful not to confuse the severity order of syslog levels: lower numbers (0) are more severe, higher numbers (7) are less severe. Also, remember that NTP stratum numbers work inversely to accuracy: lower stratum numbers indicate higher accuracy, with Stratum 0 being the most accurate reference clock.

13
MCQmedium

Why is NTP especially useful when devices send logs to a centralized Syslog server?

A.It helps align device clocks so centralized log timestamps can be correlated more accurately.
B.It assigns the Syslog server an IP address.
C.It replaces the need for a Syslog server.
D.It encrypts every Syslog message automatically.
AnswerA

Network Time Protocol synchronizes the system clocks of routers, switches, and servers, so each device reports the same timestamp for concurrent events. When centralized log correlation combines Syslog outputs from multiple devices, consistent time references enable security analysts to reconstruct the exact sequence of actions and pinpoint root causes. Without NTP alignment, clock drift would cause misleading log ordering and obscure real threats.

Why this answer

NTP is especially useful because synchronized clocks make the log timestamps more meaningful and easier to correlate. In plain language, if each device thinks the current time is different, the sequence of events in the centralized log becomes confusing. NTP helps align time across devices so the logs tell a more accurate story.

This is an operational best practice. Syslog collects the messages, and NTP makes their timing consistent. The correct answer is the one focused on timestamp correlation.

Exam trap

Avoid confusing NTP's function with security or data optimization features; focus on its role in time synchronization.

Why the other options are wrong

B

NTP is a protocol for clock synchronization, not for IP address assignment. IP addresses are assigned via DHCP or static configuration, and NTP operates at the application layer to synchronize time over the network. Therefore, NTP does not assign IP addresses to any device, including Syslog servers.

C

NTP and Syslog serve entirely different purposes. NTP synchronizes clocks, while Syslog is a protocol for sending log messages to a centralized server. NTP cannot replace Syslog because it does not collect, store, or forward log messages.

Both are often used together but are independent services.

D

NTP does not provide encryption for Syslog messages or any other data. NTP is solely responsible for time synchronization and does not include security features like encryption. Syslog messages are typically sent in clear text unless additional security measures like TLS or SSH are implemented.

14
PBQhard

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'.

Hints

  • •Check the NTP server address in running-config; it points to the wrong IP.
  • •Set the NTP source interface to Loopback0 so requests use the specified address.
  • •'logging trap debugging' sends every severity, including debug; change it to notifications (level 5) so only levels 0-5 are sent.
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
AnswerA
solution
! R1
configure terminal
no ntp server 203.0.113.5
ntp server 198.51.100.10
ntp source Loopback0
no logging trap debugging
logging trap notifications
end
write memory

Why this answer

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.

Exam trap

Candidates often confuse the numeric severity levels with the keyword equivalents for logging trap. Also, they may forget to specify the source interface for NTP, assuming the router will use the loopback automatically. Always verify that the NTP source interface is explicitly configured when required.

Why the other options are wrong

B

logging trap 4 sets the severity to warning (4), so it does not include notifications (5).

C

The missing source interface causes NTP to use an incorrect source address, likely resulting in unsynchronized status.

D

The NTP server address is incorrect and 'logging trap 7' sends all debug messages instead of limiting to notifications and above.

15
Multi-Selectmedium

Which two statements accurately describe why NTP and Syslog are often configured together?

Select 2 answers
A.Syslog provides event visibility, while NTP helps keep timestamps consistent across devices.
B.Consistent time improves the usefulness of centralized logs and event correlation.
C.NTP replaces the need for any event logging.
D.Syslog automatically assigns the NTP server address to all devices.
E.Both services can be used only on routers, not switches.
AnswersA, B

Syslog is a client/server protocol that forwards network device log messages to a central collector, giving administrators event visibility. NTP synchronizes device clocks so every logged event has a consistent, reliable timestamp. They work together because syslog provides the audit trail while NTP makes the timestamps in that trail trustworthy.

Why this answer

NTP and Syslog are often configured together because logs become much more useful when the device clocks are aligned. In practical terms, Syslog provides the event messages, while NTP helps ensure that the timestamps on those messages are consistent across the environment. That makes troubleshooting and incident analysis more reliable.

This is a very practical operations concept and comes up often in real troubleshooting workflows.

Exam trap

A common exam trap is selecting the option that NTP replaces the need for event logging or that Syslog automatically configures NTP server addresses. Candidates might confuse time synchronization with logging functionality, but NTP only provides accurate time, not event data. Similarly, Syslog collects logs but does not manage NTP settings.

Misunderstanding these roles can lead to incorrect answers, as the two services complement each other but serve distinct purposes in network management.

Why the other options are wrong

C

This option is incorrect because NTP only synchronizes time and does not replace the need for event logging, which is handled by Syslog or other logging mechanisms.

D

This option is incorrect because Syslog does not configure NTP server addresses or manage time synchronization; these are separate configuration tasks.

E

This option is incorrect because both NTP and Syslog are widely used on various network devices, including routers and switches, not limited to routers alone.

16
Matchingmedium

Drag and drop the syslog and NTP items on the left to the correct descriptions on the right.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Alert: immediate action needed

Notification: normal but significant condition

Reference clock (e.g., atomic clock or GPS)

NTP client synchronized to a stratum 1 server

Configures the device as an NTP client

Displays syslog messages in the buffer

Why these pairings

Each item is correctly paired with its description: A identifies the syslog facility (the source of the log), B indicates syslog severity (urgency level), C correctly describes an NTP server (time source), and D correctly describes an NTP client (time requester). These are foundational definitions for syslog and NTP operations.

Exam trap

Watch out for confusing syslog severity levels with facility types. Also, ensure you correctly match the NTP client and server roles in the context of time synchronization.

17
MCQhard

Refer to the exhibit. A network administrator is troubleshooting an NTP synchronization issue on R1. The router is configured with the command ntp server 10.1.1.100, but the clock remains unsynchronized. The administrator issues the show ntp status command. What is the most likely cause of the problem?

A.The NTP authentication key configured on R1 does not match the one on the server.
B.The system time on R1 is set to an epoch that is too far from the server's time, causing NTP to refuse to synchronize.
C.The NTP service is not enabled on R1; the 'ntp server' command only defines a server but does not start the NTP process.
D.The router cannot reach the NTP server 10.1.1.100 at UDP port 123 due to a routing issue or an access list.
AnswerD

The exhibit clearly shows 'no reference clock' and stratum 16, which indicates that R1 has not received any NTP packets from the configured server. This is a classic symptom of network unreachability—the router’s NTP requests are not making it to the server or responses are not coming back, often caused by a missing route or an ACL filtering UDP 123.

Why this answer

The `show ntp status` output would show the clock as unsynchronized if R1 cannot communicate with the NTP server at 10.1.1.100. NTP uses UDP port 123, and a routing issue or an access list blocking this port would prevent the exchange of NTP packets, leaving the clock unsynchronized. The `ntp server` command configures R1 as a client to request synchronization, but it does not guarantee reachability.

Exam trap

Cisco often tests the misconception that the `ntp server` command alone is insufficient and that an additional 'ntp enable' command is needed, but in reality, the client process is automatically started by the `ntp server` command.

Why the other options are wrong

A

Candidates often confuse unsynchronized status with authentication issues, but authentication failures do not prevent reception of packets; they just discard them after arrival.

B

A common myth is that NTP cannot sync if the clocks are too far apart. While extreme offsets may delay sync, they do not prevent the router from hearing the server, so the reference clock field would still show the server’s IP or clock ID.

C

Some candidates mistakenly believe that a separate 'ntp enable' command is required. In IOS, configuring an ntp server automatically enables NTP, so the service is active.

18
Multi-Selectmedium

Which two statements about NTP are correct? (Choose two.)

Select 2 answers
A.Accurate time helps correlate log messages across multiple devices.
B.NTP replaces the need for DNS in enterprise networks.
C.NTP synchronizes clocks between network devices and time sources.
D.NTP is used to negotiate EtherChannel parameters.
AnswersA, C

When network devices have synchronized time, their logs can be aligned to a common timeline, allowing an administrator to trace a single event across multiple routers, switches, and firewalls. Without synchronized time, an attacker or a fault can be obscured by skewed timestamps. This correlation is fundamental to efficient incident response and root-cause analysis.

Why this answer

NTP synchronizes time across devices, which is important for logging, certificates, and event correlation.

Exam trap

A common exam trap is mistaking NTP for a service that replaces DNS or manages link aggregation like EtherChannel. Some candidates incorrectly believe NTP handles domain name resolution or negotiates EtherChannel parameters because these are also fundamental network services. However, NTP’s sole purpose is to synchronize time across devices.

Selecting options that confuse NTP with DNS or EtherChannel leads to incorrect answers. Understanding that NTP only manages time synchronization helps avoid this trap and ensures accurate selection of correct options related to time correlation and clock synchronization.

Why the other options are wrong

B

This option is incorrect because NTP does not replace DNS. DNS resolves domain names to IP addresses, while NTP only synchronizes time across devices.

D

This option is incorrect because NTP does not negotiate EtherChannel parameters. EtherChannel negotiation is handled by protocols like PAgP or LACP, unrelated to time synchronization.

19
Multi-Selectmedium

Which two statements accurately describe common uses of NTP in network operations?

Select 2 answers
A.It helps align device clocks across the network.
B.It improves the reliability of event timelines and log correlation.
C.It replaces the need for Syslog.
D.It assigns IP addresses to hosts.
E.It provides WLAN encryption.
AnswersA, B

NTP synchronises device clocks to a common reference time source, satisfying the requirement to align clocks across the network. Accurate, consistent timestamps are essential for correlating syslog and SNMP events, validating certificate lifetimes, and interpreting time-based ACLs, so this statement accurately describes a core operational use.

Why this answer

Option A is correct because NTP (Network Time Protocol) synchronizes the clocks of network devices to a common time reference, typically a stratum-0/1 source, keeping routers, switches, and servers aligned within milliseconds. Option B is correct because accurate, consistent timestamps from NTP make event timelines reliable and enable log correlation across multiple devices, which is essential for troubleshooting, SIEM analysis, and forensic investigations. The unmarked options do not belong: NTP does not replace Syslog (C), which is a separate logging/transport mechanism; it does not assign IP addresses (D), which is the role of DHCP; and it does not provide WLAN encryption (E), which is handled by protocols such as WPA2/WPA3.

Exam trap

A frequent exam trap is assuming that NTP performs functions beyond time synchronization, such as replacing Syslog or assigning IP addresses. Candidates might incorrectly select options suggesting NTP handles logging or DHCP tasks because these services are all related to network management. However, NTP’s sole purpose is to synchronize device clocks.

Confusing NTP with DHCP or Syslog overlooks their distinct roles and can lead to selecting incorrect answers. Understanding that NTP supports but does not replace logging or address assignment is crucial to avoid this trap.

Why the other options are wrong

C

This option is incorrect because NTP does not replace Syslog; Syslog is responsible for logging events, while NTP only synchronizes time.

D

This option is incorrect because IP address assignment is handled by DHCP, not NTP, which only manages time synchronization.

E

This option is incorrect because NTP has no role in providing WLAN encryption; encryption is managed by wireless security protocols like WPA2 or WPA3.

20
Multi-Selectmedium

Which TWO statements correctly describe NTP stratum levels and syslog severity levels in a Cisco IOS-XE environment?

Select 2 answers
A.An NTP stratum value of 1 indicates a higher accuracy than a stratum value of 3.
B.A syslog severity level of 5 (notice) is more severe than a level of 4 (warning).
C.The 'ntp server' command under global configuration configures the device as an NTP client.
D.Syslog severity level 0 (emergency) indicates a normal operational message.
E.NTP stratum 0 is assigned to devices that are directly connected to an authoritative time source.
AnswersA, C

NTP stratum defines the distance from a reference clock in a hierarchy. Stratum 0 is the authoritative time source (e.g., GPS or atomic clock), stratum 1 is a device directly synchronized to that source, and stratum 3 is two hops away from stratum 1. Each hop introduces potential network delay and jitter, so a lower stratum value indicates closer proximity to the reference clock and consequently higher time accuracy. Therefore, stratum 1 is indeed more accurate than stratum 3.

Why this answer

A lower NTP stratum number indicates higher accuracy; stratum 1 is directly synchronized to a precise reference clock (e.g., GPS) and is thus more accurate than stratum 3, which is two hops away. Option C is correct because the 'ntp server' command configures a device to synchronize its clock to a specified NTP server, making it an NTP client. Option B is incorrect: syslog severity level 4 (warning) is more severe than level 5 (notice) because lower severity numbers indicate higher severity.

Option D is incorrect: severity level 0 (emergency) is the most severe level, indicating a system-wide critical event, not a normal operational message. Option E is incorrect: NTP stratum 0 is assigned to an authoritative time source itself (e.g., atomic clock), not to devices directly connected to it; devices connected to stratum 0 sources are stratum 1.

Exam trap

Candidates often mistakenly equate lower syslog severity numbers with lower importance, not realizing that a smaller number means a higher severity; similarly, they may think higher NTP stratum numbers mean higher accuracy.

Why the other options are wrong

B

Syslog severity levels use inverse numbering: level 4 (warning) is more severe than level 5 (notice), so the statement is false.

D

Syslog level 0 (emergency) is the highest severity, indicating a catastrophic system failure, not a normal operational message.

E

NTP stratum 0 is the reference clock itself; devices synchronized directly to it are stratum 1, not stratum 0.

21
MCQmedium

Exhibit: A branch router receives time from an NTP server, but the show output marks the server with a tilde instead of an asterisk. What does that mean?

A.That server is the current system clock source
B.The server is reachable but not the one currently selected for synchronization
C.NTP authentication has disabled the server permanently
D.The router is acting as an NTP master for that server
AnswerB

In show ntp associations, the leading character shows the peer's status: an asterisk (*) marks the peer the router is synchronized to (system peer), a plus (+) marks a good candidate, and a tilde (~) marks a configured peer. Here the tilde server (192.0.2.50) is reachable (reach 377) but is not the system peer, because the router has selected 198.51.100.20 (stratum 1, GPS), marked with *. So the tilde server is not the current clock source.

Why this answer

In Cisco NTP output, the asterisk (*) indicates the current synchronization source. The tilde (~) specifically means the server is statically configured and reachable but has not been selected for synchronization. This differs from the plus sign (+), which denotes a candidate for synchronization.

Therefore, the router is not using that server as its active time source.

Exam trap

Be careful not to confuse the tilde (~) with the asterisk (*) or other symbols that indicate different statuses in NTP output.

Why the other options are wrong

A

In NTP, an asterisk (*) indicates the selected time source, while a tilde (~) means the server is reachable but not selected. Option A describes the asterisk, not the tilde.

C

A tilde (~) indicates the server is reachable but not synchronized; a permanently disabled server due to authentication would show a period (.) or not appear at all.

D

In the context of NTP, a tilde (~) indicates the server is reachable but not selected as the synchronization source. The router acting as an NTP master would be indicated by the 'master' command or stratum level, not by the tilde symbol.

22
MCQhard

A switch shows a clock that is several minutes off from other devices even though an NTP server has been configured. Which issue is the most likely cause?

A.The NTP server is unsynchronized or unreachable
B.The device must run Syslog before NTP can sync
C.NTP requires a trunk port on the management VLAN
D.The clock can sync only if DNS is configured
AnswerA

NTP clients trust time only from a server that is both reachable and itself synchronized to a reference clock. When the server is unreachable (e.g., UDP 123 is filtered) or its stratum is too high because it lost its upstream source, the switch discards the NTP packets and retains the local clock, which drifts after several minutes. The remedy is to verify the server's stratum and reachability before adjusting anything else.

Why this answer

NTP requires IP reachability to the time source. If the NTP server is unreachable due to routing or ACL issues, the switch falls back to its local clock, causing drift. Option A is correct.

Option B is wrong because Syslog has no effect on NTP synchronization. Option C is incorrect because NTP does not require a trunk port; it can operate over any VLAN with IP connectivity. Option D is false because DNS is only needed if the NTP server is specified by hostname; the server can be reached by IP address without DNS.

Exam trap

A common mistake is thinking that unrelated services like Syslog, trunk ports, or DNS are prerequisites for NTP; only IP connectivity to a synchronized NTP server matters.

Why the other options are wrong

B

Syslog and NTP are independent protocols; Syslog does not need to run before NTP can synchronize.

C

NTP works over any IP network; there is no requirement for a trunk port on the management VLAN.

D

DNS is only needed if the NTP server is referenced by hostname rather than IP address; many configurations use IP addresses directly.

Ready to test yourself?

Try a timed practice session using only Ntp questions.