Networking

CCNA Domain 4 Practice Test: IP Services Questions with Answers

IP Services is the smallest block of the CCNA 200-301 blueprint at 10 percent. It is also where people drop cheap points, because NAT, DHCP, NTP, SNMP, syslog, QoS, SSH and TFTP all look easy until a question shows real router output. This Domain 4 test gives you 30 CCNA IP Services practice questions per attempt from a 70-question bank, and every answer explains why it is right.

Original content from computingforgeeks.com - post 182309

Fifty of the questions come from the per-topic quizzes on the NAT, DHCP, NTP, SNMP and syslog, and QoS guides in this series. We wrote the other twenty: ten fill the gaps those quizzes left (DNS, the DHCP client, SSH and TFTP/FTP) and ten add depth to NAT, syslog, SNMP and QoS. The bank was checked in November 2026 against Cisco’s 200-301 v1.1 exam topics, and the output below comes from the Cisco IOS 15.2 lab routers behind those guides.

Take the Domain 4 practice test

Answer all 30 before you read any explanation. Then go back through every one, including the ones you got right. A correct guess on a NAT address question is worth nothing if you cannot say why it was correct, and the explanation is where that gap shows. Each retake gives you a different draw from the same 70 questions.

Loading quiz...

Scoring 85 percent or better on two or three different draws means IP Services is solid. Below that, the worked questions further down and the topic guides they link to are where to spend the next hour, because most misses in this domain come from the same half dozen traps.

Check what Domain 4 covers

Cisco lists nine IP Services topics in the official CCNA 200-301 v1.1 exam topics, and the verb on each one tells you how deep to go. “Configure and verify” means you should be able to type the commands and read the show output. “Explain” and “Describe” mean you need the concept, not the syntax.

TopicWhat Cisco asks forQuestions in the bank
4.1 Inside source NAT, static and poolsConfigure and verify14
4.2 NTP in client and server modeConfigure and verify10
4.3 Role of DHCP and DNSExplain4 DNS, plus the DHCP items below
4.4 SNMP in network operationsExplain7
4.5 Syslog facilities and severity levelsDescribe7
4.6 DHCP client and relayConfigure and verify11 DHCP in total
4.7 QoS per-hop behaviorExplain12
4.8 Remote access with SSHConfigure3
4.9 TFTP and FTPDescribe2

NAT carries the most questions for a reason: it’s a configure-and-verify topic with four address names that people mix up, so it rewards repetition.

SSH and TFTP/FTP are light here for different reasons. The Domain 5 test already covers VTY and SSH hardening, and the file transfer topic only asks you to describe the two protocols. If you want the full list of all six domains with their weights, the CCNA exam topics breakdown covers each one.

Use the bank as a study map

Every question in the bank is tagged by how its answer was checked. A lab item was confirmed on the GNS3 routers we used for the topic guides: we typed the command and read its output back. A documentation item was checked against Cisco documentation or the RFC that defines the protocol. That split matters when you plan your revision:

AreaQuestionsChecked on the labChecked against docs
NAT and PAT1477
QoS12012
DHCP server, relay and client1147
NTP1064
Syslog725
SNMP725
DNS422
SSH321
TFTP and FTP202
Total702545

Read the lab column as a hint about what kind of question you’ll face. NAT and NTP are heavy on lab items, so they test whether you can read a translation table or an association list, and the fix for misses there is time on a router, not more flashcards. QoS has no lab items at all because the topic is “explain”, so it’s pure terminology: DSCP values, the AF drop scheme, and the difference between policing and shaping.

Work through the questions people miss

These six are where most wrong answers in this domain land. Each one comes with the output that settles it, so you can see the answer on a router instead of taking our word for it.

Inside local versus inside global

The bank asks which address is the inside local in ip nat inside source static 192.168.20.20 203.0.113.10, and the answer is the first one, 192.168.20.20. “Local” means the address as seen from inside your network, “global” means as seen from outside, so the private address is always inside local. This translation table comes from the NAT lab router, running static NAT for one host and PAT for another:

R1# show ip nat translations
Pro Inside global      Inside local       Outside local      Outside global
icmp 203.0.113.9:1024  192.168.10.10:0    198.51.100.1:0     198.51.100.1:1024
icmp 203.0.113.10:0    192.168.20.20:0    198.51.100.1:0     198.51.100.1:0
--- 203.0.113.10       192.168.20.20      ---                ---

Each line of that table answers a different question in the bank, so read them one at a time:

  • Last line, no protocol or ports: the permanent static mapping
  • First line, port 1024 on the inside global: a PAT translation
  • Middle line: a live session riding the static entry

The static entry stays in the table even with no traffic flowing, which is why outside hosts can always reach 192.168.20.20 at 203.0.113.10. On the PAT line, 192.168.10.10 left as 203.0.113.9 with its ICMP identifier rewritten to 1024. That rewrite is how the router tells flows apart when many hosts share one public address.

A PAT pool that hands out nothing

One of the new questions comes straight from a mistake we made while building the NAT lab. The pool was first defined as ip nat pool PUBLIC 203.0.113.8 203.0.113.8 prefix-length 29, and every ping from the inside failed. Meanwhile the miss counter in show ip nat statistics kept climbing with zero addresses allocated.

The cause is that 203.0.113.8 is the network address of 203.0.113.8/29. A pool defined with a mask or prefix length will not hand out the network or broadcast address of that subnet, so this pool was empty. Moving it to 203.0.113.9 fixed the problem at once. If PAT looks configured but nothing translates, check the pool range against the mask before you touch the ACL.

Why a relayed DHCP lease shows Unknown

DHCP Discover is a broadcast, and routers don’t forward broadcasts, so a client on another subnet only reaches a central server when its gateway runs ip helper-address. You can see the result on the server. In the DHCP lab, R1 serves one LAN directly and a second LAN through a relay on R2:

R1# show ip dhcp binding
Bindings from all pools not associated with VRF:
IP address      Client-ID/              Lease expiration        Type       State      Interface
                Hardware address/
                User name
192.168.10.11   0063.6973.636f.2d63.    Jun 24 2026 03:46 AM    Automatic  Active     GigabitEthernet0/0
                6130.332e.3533.3231.
                2e30.3030.382d.4769.
                302f.30
192.168.20.11   0063.6973.636f.2d63.    Jun 24 2026 03:46 AM    Automatic  Active     Unknown
                6130.342e.3533.3364.
                2e30.3030.382d.4769.
                302f.30

The 192.168.10.11 lease names GigabitEthernet0/0 because that client sits on a connected segment. The 192.168.20.11 lease reads Unknown, because the request arrived as a unicast from the relay, not off a local wire.

The relay also explains how the server picked the right pool. R2 stamped each request with the address of the interface it arrived on, and the server matched that address to the 192.168.20.0/24 pool. Both clients in this lab ran ip address dhcp, the interface command that makes a router a DHCP client.

Stratum goes up one per NTP hop

Two numeric questions trip people here: the stratum a client ends up at, and the value that means “not synchronized”. The client is always one stratum below its server, and 16 means unsynchronized. On the NTP lab, R1 runs ntp master 3 and R2 points at it with ntp server 10.10.10.1:

R2# show ntp status
Clock is synchronized, stratum 4, reference is 10.10.10.1
nominal freq is 250.0000 Hz, actual freq is 249.9994 Hz, precision is 2**18
ntp uptime is 85100 (1/100 of seconds), resolution is 4016
reference time is EDED4392.45854048 (19:18:42.271 UTC Mon Jun 29 2026)
clock offset is 68.3901 msec, root delay is 8.00 msec
root dispersion is 92.25 msec, peer dispersion is 2.16 msec
system poll interval is 64, last update was 190 sec ago.
R2# show ntp associations

  address         ref clock       st   when   poll reach  delay  offset   disp
*~10.10.10.1      127.127.1.1      3     58     64   377  8.001  68.390  2.169
 * sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured

R2 reports stratum 4 because its server sits at stratum 3. In the association line, ~ means the server was configured by hand and * means R2 picked it as its sync source. A reach of 377 (octal for eight successful polls in a row) means the link is healthy.

The reference clock 127.127.1.1 is R1’s own hardware clock, which is what ntp master serves from. That is why R1 sits at exactly the stratum you gave it instead of one below an upstream server.

Read the severity inside a syslog message

Every Cisco log line carries its severity in the middle field of %FACILITY-SEVERITY-MNEMONIC, so you never have to guess. This is the buffer on the SNMP and syslog lab router after it started logging to a server at 10.20.20.50 and an interface came up:

R1# show logging
Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
    Buffer logging:  level informational, 5 messages logged
    Trap logging: level informational, 24 message lines logged
        Logging to 10.20.20.50  (udp port 514, link up),
              5 message lines logged
        Logging Source-Interface:       VRF Name:
        GigabitEthernet0/0

Log Buffer (32768 bytes):

*Jun 29 19:45:24.023: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0, changed state to up
*Jun 29 19:45:24.211: %SYS-5-CONFIG_I: Configured from console by console
*Jun 29 19:45:24.219: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 10.20.20.50 port 514 started - CLI initiated
*Jun 29 19:45:25.155: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up
*Jun 29 19:45:26.155: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to up

%LINK-3-UPDOWN is severity 3 (errors) even though the interface came up, which surprises most people. The line protocol message for the same event is severity 5 (notifications).

The trap level of informational means levels 0 through 6 go to the server and only debugging (7) stays local. Lower numbers are more severe, and a threshold always includes everything more severe than itself. That rule is the whole answer to the logging trap warnings question in the bank.

SSH keys need a domain name

IOS names its RSA key pair after the router’s fully qualified name, so crypto key generate rsa won’t run until you’ve set a hostname other than Router and an ip domain-name. The SSH lab shows where the name comes from:

The name for the keys will be: R1.lab.example.com

% The key modulus size is 2048 bits
% Generating 2048 bit RSA keys, keys will be non-exportable...
[OK] (elapsed time was 2 seconds)

Once the keys exist, show ip ssh confirms the server state on its first line:

SSH Enabled - version 2.0
Authentication timeout: 120 secs; Authentication retries: 3
Minimum expected Diffie Hellman key size : 1024 bits

That line proves the server is up, but it doesn’t prove Telnet is off. On classic IOS 15.x, as on these lab routers, the VTY lines keep accepting Telnet on TCP 23 until transport input ssh restricts them, and Telnet sends the password in clear text. Two of the new SSH questions turn on exactly that difference, so don’t stop at show ip ssh when you verify a device.

Study the areas the test exposed

Each area in this test has a hands-on guide with its own 10-question quiz, flashcards and a lab you can rebuild. Go to the one that matches your misses:

TFTP and FTP don’t have a guide of their own because the topic only asks you to describe them. The two facts that decide most questions are that TFTP runs on UDP 69 with no login and no directory listing (RFC 1350), while FTP runs on TCP with a username and password. For the commands from all of these guides on one page, keep the CCNA command cheat sheet open while you lab.

Move on to the other domain tests

IP Services is worth 10 percent, so don’t let it eat a week. Once you clear 85 percent on a few draws, switch to a domain you haven’t tested yet: Network Fundamentals, Network Access, IP Connectivity and Security Fundamentals each have a test built the same way, and Domain 6 has its own automation practice test. The CCNA practice questions hub lists every quiz in one place (its Domain 4 row read in progress until this test was ready), and the free CCNA labs give you the routers to rebuild any of the outputs above.

If you’d rather have one book that covers every domain end to end, the best CCNA books list compares the Odom and Lammle sets with the practice test books. We’re also building a CCNA prep pack from questions that aren’t published anywhere on the site:

Keep reading

Free CCNA 200-301 Practice Questions with Answers Networking Free CCNA 200-301 Practice Questions with Answers Configure Samba File Share on Debian 13 / 12 Debian Configure Samba File Share on Debian 13 / 12 WireGuard VPN Setup: Ubuntu 26.04/24.04, Debian 13, Rocky 10 Debian WireGuard VPN Setup: Ubuntu 26.04/24.04, Debian 13, Rocky 10 Best Networking Books: TCP/IP, Routing and Troubleshooting Books Best Networking Books: TCP/IP, Routing and Troubleshooting Omada Fusion Pro Behind a Router: Port Forwarding for LAN Access Networking Omada Fusion Pro Behind a Router: Port Forwarding for LAN Access How To Install Nagios on Ubuntu 24.04 (Noble Numbat) Monitoring How To Install Nagios on Ubuntu 24.04 (Noble Numbat)

Leave a Comment

Press ESC to close