A /27 subnet uses the mask 255.255.255.224 and contains 32 IPv4 addresses, with 30 available for devices after network and broadcast addresses are reserved. That makes it a close fit for a small server network, while larger subnet masks may leave many addresses unused.

Multiple Choice

A server administrator needs to configure a server on a network that will have no more than 30 available IP addresses. Which of the following subnet addresses will be the most efficient for this network?

The subnet mask 255.255.255.224, which corresponds to a CIDR notation of /27, effectively creates a subnet that allows for precisely 30 usable IP addresses. This configuration provides a total of 32 IP addresses in the subnet, but two of those addresses—one for the network and one for the broadcast—are reserved. Therefore, the actual number of usable addresses for devices is 30, which fits the requirement of the server administrator perfectly. This subnetting approach is optimal for a network that does not require more than 30 IP addresses, as it minimizes waste of IP address space. Each of the other subnet masks provided would either allocate too many addresses or not accommodate the needed addresses efficiently. For instance, with a subnet mask of 255.255.255.0, there would be 254 usable addresses, which is excessive for a network of this size. Similarly, 255.255.255.128 offers 126 usable addresses and 255.255.255.192 allows for 62 usable addresses—both options lead to unnecessary allocation of more addresses than required. The choice of a subnet mask must always consider not only the current needs but also future scalability. However, in this specific case, using

Why a /27 Subnet Fits a Small Server Network

A small server network doesn’t need a huge pool of addresses. If it has room for no more than 30 devices, assigning hundreds of IP addresses can waste valuable address space. A subnet mask of 255.255.255.224, also written as /27, is a close fit: it provides 32 total IPv4 addresses, of which 30 are normally available for devices.

That balance matters in server administration. A well-sized subnet is easier to document, manage, and protect. It also leaves more of an organization’s address space available for other networks, such as storage systems, management interfaces, or employee devices.

The numbers behind a /27

An IPv4 address contains 32 bits, usually shown as four decimal numbers called octets. A subnet mask marks which bits identify the network and which bits can identify hosts within that network.

In CIDR notation, the slash number tells how many bits belong to the network portion. A /27 uses 27 network bits, leaving five bits for addresses within the subnet.

Five host bits allow:

2⁵ = 32 total addresses

In a typical IPv4 subnet, two of those addresses have special roles:

  • The network address identifies the subnet itself.

  • The broadcast address lets a device send a message to all hosts on the subnet.

So the usual usable-host calculation is:

32 total addresses − 2 reserved addresses = 30 usable addresses

That’s why 255.255.255.224 can serve a small network with up to 30 devices, while avoiding the much larger address pool created by a broader subnet.

What the mask looks like in binary

The decimal mask can seem a little abstract, so it helps to look at its final octet in binary:

255.255.255.224

11111111.11111111.11111111.11100000

Each 1 marks a network bit; each 0 marks a host bit. In the last octet, the first three bits are part of the network, leaving five bits for host addresses.

The mask also sets the size of each subnet block. Since the final octet is 224, subtracting it from 256 gives a block size of 32. Subnets in that octet therefore begin at intervals of 32: for example, 0, 32, 64, 96, and so on.

Consider the subnet 192.168.10.64/27. Its address range runs from 192.168.10.64 through 192.168.10.95. The first address, 192.168.10.64, is the network address; the last, 192.168.10.95, is the broadcast address. The addresses between them can be assigned to devices.

This kind of boundary arithmetic is useful when setting up a server VLAN or checking whether two devices belong to the same subnet. A device with the wrong mask might treat a nearby system as remote—or try to reach a remote system directly. Small configuration errors can make a network feel mysteriously unreliable.

Why a larger subnet may be wasteful

A /24 mask, or 255.255.255.0, leaves eight host bits. That creates 256 total addresses, with 254 typically usable. For a network that needs only 30, this is a much larger pool than necessary.

A /25, or 255.255.255.128, provides 128 total addresses and 126 usable ones. A /26, or 255.255.255.192, provides 64 total and 62 usable. Both can support a 30-device network, but each reserves a larger block of address space than a /27.

The difference may not feel important on one isolated subnet. Across a large organization, though, address blocks add up. A data center might have separate subnets for application servers, database servers, backup systems, monitoring tools, and out-of-band management. Giving every small group a /24 can leave gaps and make the address plan harder to maintain.

A smaller subnet can also make network boundaries clearer. If a group of management devices lives in its own subnet, administrators can apply firewall rules and access controls specifically to that group. Subnetting doesn’t provide security by itself, but it gives network design a useful structure.

Address capacity is not the only consideration

Thirty usable addresses is a tidy fit, but it leaves little room if the device count grows. A network may include more than physical servers: virtual machines, network appliances, load balancers, monitoring interfaces, and other devices may each need an address. Some infrastructure services may also use reserved addresses under an organization’s plan.

That means administrators should count the whole subnet population, not just the machines described as “servers.” They should also consider expected growth. If the network may soon need 35 addresses, a /27 won’t be enough; the next larger common subnet, a /26, provides 62 usable addresses.

There’s a trade-off here. A subnet that’s too large wastes address space, while one that’s too small can force a disruptive redesign later. The right size depends on both current requirements and a realistic view of what might be added. A simple inventory—servers, gateways, virtual machines, and network services—can prevent a lot of guesswork.

How subnetting supports server operations

Subnets are building blocks in a network design. They help divide systems into logical groups, even when those systems share the same physical switches. A VLAN, for example, can place a set of servers into a distinct Layer 2 network, while an IP subnet defines the address range used by that group. The two concepts often work together, but they are not the same thing.

When a server sends traffic to an address outside its subnet, it usually forwards that traffic to a default gateway. If the server’s IP address, subnet mask, and gateway don’t agree, communication can fail in confusing ways. The server may still reach devices on its local subnet but fail to contact services elsewhere.

Documentation helps keep these details straight. A network plan can record the subnet in CIDR notation, its address range, its gateway, and its intended use. For instance, noting “192.168.10.64/27 — application servers — gateway 192.168.10.65” is clearer than listing a mask alone. Consistent records become especially valuable when several administrators share responsibility for a server environment.

A small subnet, chosen deliberately

For a network that needs up to 30 usable IPv4 addresses, 255.255.255.224 (/27) provides the closest standard subnet size. It creates 32 total addresses, with the network and broadcast addresses reserved, leaving 30 for hosts.

The broader lesson is simple: subnet size should follow the number of devices that need addresses, with a sensible allowance for growth. A /27 isn’t automatically right for every small server group, but it’s a strong fit when the requirement is genuinely capped at 30. Count the devices, understand the reserved addresses, and keep the address plan clear. Those modest steps make a server network easier to run—and much easier to troubleshoot when something goes sideways.