Study CompTIA 220-1201 Addressing, TCP/IP and SOHO Foundations: key concepts, common traps, and exam decision cues.
This is one of the highest-value A+ networking lessons because it turns a pile of IP facts into support logic. Core 1 wants you to know what a gateway, DNS server, DHCP scope, or private address actually does in a small network.
NAT: Network Address Translation, the process that lets many private devices share one public-facing address at the edge.
APIPA: Automatic private address in the
169.254.0.0/16range that often appears when DHCP configuration fails.
The exam usually wants you to:
| Item | What to remember |
|---|---|
| private IPv4 ranges | 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 |
| APIPA | 169.254.0.0/16, usually a DHCP failure clue |
| default gateway | where traffic leaves the local subnet |
| DNS server | resolves hostnames to IPs |
| DHCP | hands out IP configuration automatically |
| If the issue is… | Think first about… |
|---|---|
| valid local IP, but no outside access | default gateway, router, or upstream path |
| hostname fails but IP works | DNS |
self-assigned 169.254.x.x address |
DHCP |
| only one client fails while others work | client settings or local hardware first |
In SOHO questions, one router often handles many jobs:
That means one misconfiguration can break several user-visible services at once.
| Router role | Why it matters on Core 1 |
|---|---|
| wireless access point | client Wi-Fi association and security |
| DHCP service | automatic address assignment |
| NAT edge device | internet sharing for private hosts |
| basic firewall | common inbound and outbound filtering behavior |
That is why small-office troubleshooting can look broad at first. One misconfigured device may affect Wi-Fi, addressing, and internet access together.
1ipconfig /all
2ping 192.168.1.1
3nslookup example.com
What to notice:
ipconfig /all shows whether the IP settings look sanenslookup helps separate name-resolution issues from broader connectivity issuesA desktop can ping its default gateway and can browse a site by direct IP, but every hostname lookup fails. Another answer choice suggests replacing the Ethernet cable first because the network feels “unstable.”
The stronger answer usually:
169.254.x.x as a DHCP clue before chasing random cabling theoriesTCP/IP questions usually reward classifying the fault into addressing, routing, or name resolution. If you see 169.254.x.x, think failed DHCP. If the host can reach the gateway but websites fail by hostname, think DNS. If the issue is traffic leaving the subnet, think default gateway. A+ usually wants that simple separation before any deeper networking theory.