Networking

Networking is nearly a quarter of Core 1 (23 percent), and it reads far more easily once you see the three layers stacked underneath it. Those three layers are this guide's own way of grouping the domain, not the protocol stack layers that Protocols and Ports teaches when it puts the two transports between the application and the network layer. First you name the parts: the protocols, the port numbers, and the radios that move data. Then you build a small network out of those parts, the kind an all-in-one router creates for a home or small office (SOHO, short for small office/home office). Then you wire and test the physical link with hand tools. Almost every question in this domain lives in exactly one of those layers, and the classic trap is to treat networking as one undifferentiated pile: answering a pure port-number recall item with a NAT or DHCP setup step, or reading a physical-connector question as if it were about Wi-Fi bands. Decide which layer the question is in first, and the right subtopic follows.

Protocols and Ports comes first because it is the vocabulary the rest of the domain speaks: TCP versus UDP (Transmission Control Protocol, which guarantees delivery, versus User Datagram Protocol, which just sends), the dozen-odd well-known port numbers, the encrypted sibling that should replace each cleartext protocol, and the Wi-Fi generations, bands, and short-range radios. Reach for it when a question names a service, a number, or a wireless technology. SOHO Networks is next, where you assemble those parts into a working network: the four settings every host needs (IP address, subnet mask, default gateway, and DNS, the Domain Name System), private addressing behind NAT (Network Address Translation), the all-in-one router, DHCP (Dynamic Host Configuration Protocol), WPA3 wireless security, and how you expose or reach a service through a port forward or a VPN (virtual private network). Networking Tools is last and the most physical: the crimpers, punchdown tools, testers, and probes that terminate, verify, and locate the actual cabling. Reach for it when the question shows a connector, a cable standard, or a test device.

Across this domain the exam rewards precision over raw capability. On a distance or connectivity question, pick the technology whose native range or role fits the scenario rather than the fastest one: NFC (near-field communication) for a tap, Bluetooth for a peripheral across a room, the 2.4 GHz band for reach. On a tool question, pick the single tool whose job the scenario asks for, terminate, verify, or locate, not the most capable meter on the bench. And when a legacy option and a modern one both technically function, choose the secure, current one: SSH over Telnet, HTTPS over HTTP, WPA3 over WPA2 or WEP, a reserved or static address for anything that must not move. Matching the stated requirement and defaulting to the safe choice settles most of the domain's close calls.