What's changed: Initial version
3.4Networking (OSI/TCP-IP, IP Addressing/Subnet Calculation/CIDR, Routing, DNS/DHCP, Transmission-Time Calculations, Wireless LAN, SDN/QoS)
Learn the OSI basic reference model, which layers communication conceptually, and the practical standard TCP/IP; the structure of an IP address and calculating network splits using a subnet mask and CIDR notation; routing, which selects a path; DNS for name resolution and DHCP for automatic IP assignment; protocols such as HTTP/HTTPS, SMTP, POP, and IMAP; calculating transmission time from a line's bit rate (bps); wireless LAN standards and encryption; and SDN and QoS — with an emphasis on calculation problems, at Applied Information Technology Engineer depth.
Networking is one of the areas within the AP exam's technology domain where calculation problems concentrate most heavily. Deriving host and network counts from a subnet mask, and deriving transmission time from a line's bit rate and utilization, matter less as memorized formulas and more as something you can derive by understanding the structure of binary numbers and how bit counts relate. Alongside this, the correspondence between OSI layers and TCP/IP, and the differing roles of representative protocols, are also tested as situational judgments.
3.4.1The OSI reference model, TCP/IP, and address design
- The OSI basic reference model is a conceptual model splitting communication functions into seven layers (physical, data link, network, transport, session, presentation, application). TCP/IP is the four-layer (network interface, internet, transport, application) protocol suite actually used on the internet; IP corresponds to the OSI network layer, and TCP/UDP correspond to the transport layer.
- An IP address consists of a network portion and a host portion. A subnet mask is a bit string indicating how much is the network portion (e.g.,
255.255.255.0means the upper 24 bits are the network portion). CIDR notation writes the number of network-portion bits after a slash, as in192.168.1.0/24. If the host portion hashbits, the number of assignable hosts = 2^h - 2 (all-0s is the network address and all-1s is the broadcast address, neither assignable, hence subtracting 2). - When further splitting an existing
/24network, increasing the number of network-portion bits increases the number of subnets while decreasing the number of hosts per subnet. With the resulting bit count asn(originally 24), the relationship is: number of subnets = 2^(n-24), hosts per subnet = 2^(32-n) - 2.
3.4.2Routing, DNS/DHCP, protocols, and transmission-time calculation
- Routing is the process by which a router looks at the destination IP address and decides which path to forward to next (judged via the routing table, using longest-match). DNS is the mechanism for name resolution, converting a domain name into an IP address. DHCP is the protocol that automatically assigns an IP address and related settings when a device starts up.
- HTTP is the plaintext protocol for fetching web pages; HTTPS is HTTP encrypted with TLS. SMTP handles sending mail; POP downloads mail from the server to the device and deletes it there (offline-centric); IMAP manages mail on the server itself (easier to keep in sync across multiple devices).
- The basic transmission-time formula: transmission time (seconds) = data volume (bits) / effective transfer rate (bits/second). The effective transfer rate is found as line speed x line utilization (if no utilization is given, use the line speed as-is). If the data volume is given in bytes, multiply by 8 to convert to bits before calculating.
- Wireless LAN refers to the IEEE 802.11 family of standards (newer standards are faster; encryption schemes such as WPA3 secure them). SDN (Software-Defined Networking) centrally manages network devices' control functions in software. QoS (Quality of Service) controls priority and bandwidth by traffic type, ensuring the quality of delay-sensitive traffic such as voice and video.
The staples: assignable hosts = 2^h - 2; number of subnets = 2^(n-24) (when splitting from a /24); transmission time = data volume (bits) / (line speed x utilization); POP downloads and deletes, IMAP manages mail on the server. At the AP level, compound problems combining subnet calculation and transmission-time calculation are classic (e.g., finding how long it takes to transfer a given file size over a resulting subnet). Mixing up units (bits vs. bytes, decimal vs. binary prefixes) is the single biggest source of lost points, so always confirm units before calculating.
Consider a requirement to split the head office's 192.168.1.0/24 network into eight independent subnets, one per department. Since eight subnets are needed, the minimum additional bit count a satisfying 2^a >= 8 is 3 bits, making the resulting network portion 24+3 = 27 bits (/27). Here, the number of subnets = 2^(27-24) = 8 (as required), and since the host portion is 32-27 = 5 bits, the number of hosts = 2^5 - 2 = 30 per subnet. If each department has at most around 25 devices, this /27 split satisfies the requirement. Next, consider transferring an 8MB (megabyte) design drawing from each department's file server to the head office's backup server. The line speed is 10Mbps, but since it is shared with other traffic, the line utilization is 80%. Converting the data volume to bits: 8MB x 8 = 64 megabits; the effective transfer rate is 10Mbps x 0.8 = 8 megabits/second, so transmission time = 64 megabits / 8 megabits/second = 8 seconds (checking: 8 megabits/second x 8 seconds = 64 megabits, which matches). If this transfer instead ran over a dedicated 10Mbps line at 100% utilization, the transmission time would shorten to 64 megabits / 10 megabits/second = 6.4 seconds, but that would halt other traffic, so if delay-sensitive traffic such as voice calls needs to coexist, a more realistic design uses QoS to control priority, allocating file transfer only the remaining bandwidth. Finally, IP addresses are auto-assigned via DHCP within each resulting subnet, and communication between departments is routed according to the router's routing table. If the subnets need to be split further in the future, changing /27 to /28 would double the number of subnets (2^(28-24) = 16), but the hosts per subnet would be halved to 2^(32-28) - 2 = 14, so the design must account for the basic tradeoff that finer splitting sacrifices the number of devices each subnet can hold.
| CIDR | Host bits | Assignable hosts (2^h - 2) |
|---|---|---|
| /24 | 8 | 254 |
| /27 | 5 | 30 |
| /28 | 4 | 14 |
Trap: "Calculate host count as 2^h" is wrong — the network address and broadcast address cannot be assigned to a device, so 2 must always be subtracted (2^h - 2). "Line speed = effective transfer rate" is also wrong: whenever a line utilization is given, it must be multiplied in (do not assume 100%). "Data volume can be used as-is in bits" is wrong too: a data volume given in bytes (MB, GB, etc.) must be multiplied by 8 to convert to bits before plugging it into the transmission-time formula. Forgetting a unit conversion is the single most common source of lost points.
3.4.3Section summary
- Hosts = 2^h - 2; number of subnets = 2^(n-24) (when splitting from a /24). Extending the network portion sacrifices host capacity
- Transmission time = data volume (bits) / (line speed x utilization). Convert bytes to bits by x8, and always confirm and apply the utilization
- POP = download and delete; IMAP = server-side management. QoS prioritizes delay-sensitive traffic; SDN centrally manages control in software
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. You want to split the `192.168.1.0/24` network evenly into 8 per-department subnets. Which combination of resulting CIDR notation and hosts per subnet is correct?
Q2. An 8MB file is transferred over a line with a speed of 10Mbps and a utilization of 80%. What is the correct transmission time (calculate using 1MB = 8 megabits)?
Q3. You want mail to stay synced across multiple devices at all times, with mail classified and managed on the server. Which protocol fits best?

