IPv4 subnetting is one of the skills that turns networking theory into something operational. You need it to read an addressing plan, decide whether two hosts are local to each other, select an appropriate prefix, understand route summaries, interpret ACLs, and troubleshoot why a packet is being sent to a default gateway. For the Cisco 200-301 CCNA exam, subnetting is not an isolated math exercise; it is a foundation for routing, switching, services, and security.
As of October 2026, Cisco’s current 200-301 exam is CCNA v1.1, with Cisco announcing that v2.0 begins in February 2027. The subnetting skill remains fundamental either way. Candidates should therefore build the ability to reason from a prefix quickly instead of memorizing a few common masks and hoping the question fits them.
Think in network bits and host bits
An IPv4 address contains 32 bits. The subnet prefix tells you how many of those bits identify the network. A /24 uses 24 network bits and leaves 8 host bits. A /27 uses 27 network bits and leaves 5 host bits. Once you think in those terms, the relationships between prefix length, subnet size, and host capacity become much easier to derive.
The subnet mask is simply another representation of the prefix. A /24 is 255.255.255.0. A /26 is 255.255.255.192. A /28 is 255.255.255.240. For CCNA work, you should be able to move between prefix and dotted-decimal mask without needing a long calculation every time.
The most useful pattern is the block size in the “interesting” octet. If a mask has 192 in an octet, the block size is 64 because 256 – 192 = 64. Networks therefore begin at 0, 64, 128, and 192 in that octet. A mask value of 224 gives a block size of 32; 240 gives 16; 248 gives 8; 252 gives 4.
This shortcut works because valid subnet masks contain contiguous 1 bits followed by contiguous 0 bits. The block size is simply a faster way to locate the boundary created by those bits.
Find the network, broadcast, and usable range
Consider 192.168.10.77/27. A /27 mask is 255.255.255.224, so the block size in the last octet is 32. The subnet boundaries are 0, 32, 64, 96, and so on. The address 77 falls in the 64–95 block. That makes 192.168.10.64 the network address and 192.168.10.95 the broadcast address. Usable host addresses are 192.168.10.65 through 192.168.10.94.
The same method works when the interesting octet is not the last one. With 10.20.73.4/20, the mask is 255.255.240.0. The block size in the third octet is 16. The third-octet boundaries are 0, 16, 32, 48, 64, 80, and so on. Because 73 falls between 64 and 79, the network is 10.20.64.0 and the broadcast is 10.20.79.255.
Do not skip the network and broadcast addresses when checking capacity. Traditional IPv4 subnets reserve those addresses, so a /27 contains 32 total addresses but 30 conventional host addresses. For ordinary CCNA scenarios, the familiar formula 2^host-bits – 2 remains useful.
If you need a refresher on this exact reasoning pattern, the site’s IPv4 subnetting explanation is a useful companion to hands-on calculations.
Choose a subnet size from requirements
Many exam scenarios work in the opposite direction: instead of giving a prefix, they give a host requirement. Suppose a LAN needs 50 usable addresses. Five host bits provide 32 total addresses, which is too small. Six host bits provide 64 total addresses and 62 usable addresses, so the smallest suitable prefix is /26.
For 12 usable hosts, four host bits provide 16 total addresses and 14 usable addresses, so /28 is sufficient. For 120 hosts, seven host bits provide 128 total and 126 usable, so /25 works. The important habit is to choose the smallest subnet that satisfies the requirement unless the design deliberately reserves extra growth.
Variable-length subnet masking extends this idea. Different subnets can use different prefixes so address space is not wasted. A point-to-point or tiny management segment does not need the same prefix as a large user VLAN. In real designs, VLSM lets architects allocate prefixes according to actual demand.
For exam questions, read the wording carefully. “Needs 30 hosts” and “needs 30 addresses” are not necessarily the same. Cisco questions usually frame requirements around usable host addresses, so calculate accordingly.
Subnetting explains local-versus-remote forwarding
A host uses its own address and mask to decide whether a destination is on the local subnet. If it is local, the host resolves the destination’s Layer 2 address and sends the frame directly. If it is remote, the host sends the frame to its default gateway. The router then makes its own routing decision.
This is why a wrong subnet mask can break communication even when every device has a unique IP address. Two hosts can incorrectly believe they are on different networks, or one can believe a remote host is local and attempt resolution that will never succeed.
Subnetting also matters when reading a routing table. A router compares destination prefixes and uses longest-prefix match. A /27 route is more specific than a /24 route, so traffic matching both is forwarded according to the /27. Understanding prefix length therefore connects host addressing to routing behavior.
The broader network engineering certification landscape builds repeatedly on this same idea. Whether the platform is Cisco, cloud networking, or a firewall, prefix boundaries are part of nearly every routing and security decision.
Private IPv4 space and address planning
CCNA candidates should know why private IPv4 addressing exists and recognize the major RFC 1918 ranges: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. These ranges are used internally and are not routed directly across the public Internet.
Private addressing does not eliminate subnet design. Large enterprises often subdivide 10.0.0.0/8 into regional, site, function, and VLAN prefixes. Good plans make aggregation easier and reduce the chance of overlapping address space when networks merge or connect through VPNs.
Address planning also interacts with NAT, DHCP scopes, ACLs, route summarization, and troubleshooting. A poorly planned scheme can create long-term operational cost even if every individual subnet is mathematically valid.
A practical solving method
Under exam pressure, use a consistent sequence. First identify the prefix and interesting octet. Second determine the block size. Third locate the subnet boundary that contains the address. Fourth determine the next boundary; one address before it is the broadcast. Finally identify the usable range and, if needed, calculate capacity.
Write enough working to avoid mental slips. Candidates often lose points not because they do not understand subnetting, but because they jump straight to an answer and misread a boundary. A short, repeatable process is faster than trying to be clever.
It is also worth practicing mixed prefixes rather than only /24-to-/30 examples. Include /19, /20, /21, and other prefixes where the third octet changes. If every practice question changes only the fourth octet, your speed may disappear when the boundary moves.
Subnetting should become visual
The goal is not to recite formulas. The goal is to look at an address such as 172.16.142.10/20 and quickly see the block to which it belongs. With enough practice, prefixes become visual landmarks: /25 splits a /24 in half, /26 splits it into quarters, /27 into eighths, and so on.
That fluency helps with the rest of the CCNA syllabus. VLAN interfaces need appropriate prefixes. OSPF advertises networks and routes. ACLs match address ranges. Wireless controllers and management interfaces still depend on IP design. Troubleshooting almost always begins by verifying address, mask, gateway, and reachability.
Within the Cisco enterprise certification family, subnetting is one of the rare skills that remains useful from associate-level study through advanced routing and architecture. Treat it as a practical language of networking rather than a chapter to memorize once.
Use subnetting in troubleshooting scenarios
Subnetting becomes much easier to retain when every calculation has a networking consequence. Suppose a host is configured as 10.10.34.130/26 with a gateway of 10.10.34.129. The /26 boundaries in the final octet are 0, 64, 128, and 192, so the host and gateway are in the 128–191 subnet. That immediately tells you the pair is logically compatible before you investigate VLANs, ARP, or routing.
Now change the host mask to /25. The host still considers the gateway local, but it also considers addresses from 10.10.34.128 through 10.10.34.255 local. If the actual network was designed as two /26 subnets, the host may ARP for destinations that should have been sent to the gateway. This kind of mismatch produces symptoms that look random unless you inspect the prefix.
Route summaries use the same reasoning in reverse. When several contiguous networks share high-order bits, a router can sometimes advertise a shorter prefix that represents the group. Summarization reduces routing-table detail, but an overly broad summary can claim address space that does not actually exist behind the router. Subnet math therefore influences both endpoint troubleshooting and routing design.
Practice with packet paths, not only worksheets. Given a source, destination, mask, and routing table, decide whether the host ARPs locally, sends to a gateway, and which route the router selects. That is much closer to real CCNA reasoning than calculating fifty disconnected network addresses.