How to Get a 5 in AP Networking

What we have for Networking

Everything below is free to work through and is organised against the same units as the official course framework, so you can go straight to the unit you are weakest in.

Score data

AP Networking is a new enough course that we do not have a published national score distribution to show you, and we would rather say so than invent one. Once the College Board releases distributions for this exam, this section will show them.

The 5 units of AP Networking

Unit names and exam weights follow the published course framework. Weights are the share of the multiple-choice section each unit is worth, so they tell you exactly where to spend time: Unit 1 (Network Foundations), Unit 2 (Network Infrastructure), Unit 3 (Network Services) are worth roughly 0–0% between them.

A unit-by-unit study order

Work the units in framework order for your first pass — later units in Networking lean on earlier ones — then let your error log, not the unit numbers, drive the review phase. Each row below opens the first lesson of that unit.

1. 1Network FoundationsPilot of the exam · 3 lessons · starts with “Network Models and Encapsulation”
2. 2Network InfrastructurePilot of the exam · 3 lessons · starts with “Switching and VLANs”
3. 3Network ServicesPilot of the exam · 3 lessons · starts with “DNS, DHCP, and Address Translation”
4. 4Network OperationsPilot of the exam · 3 lessons · starts with “Monitoring, Baselines, and Documentation”
5. 5Network SecurityPilot of the exam · 3 lessons · starts with “Segmentation, Firewalls, and Zero Trust”

On exam day

The exam-specific warnings our Networking lessons flag as you go.

• For a scenario about **layered network communication**, identify the decisive evidence before naming a response. A defensible conclusion here is: The application data remains conceptually the same while lower-layer framing changes from link to link.
• For a scenario about **IPv4 addressing and subnet boundaries**, identify the decisive evidence before naming a response. A defensible conclusion here is: A router must move the packet between the two /24 networks.
• For a scenario about **local media, switching, and performance measures**, identify the decisive evidence before naming a response. A defensible conclusion here is: The evidence points to wireless quality, not insufficient advertised internet bandwidth.
• For a scenario about **Layer 2 forwarding and logical segmentation**, identify the decisive evidence before naming a response. A defensible conclusion here is: VLANs provide segmentation, but policy at the routed boundary determines what communication is allowed.
• For a scenario about **routing tables, next hops, and path decisions**, identify the decisive evidence before naming a response. A defensible conclusion here is: The router forwards through gateway B using the /24 route.
• For a scenario about **wireless design, channels, roaming, and capacity**, identify the decisive evidence before naming a response. A defensible conclusion here is: Treat this as a capacity and airtime problem, then validate the redesign under realistic load.
• For a scenario about **core network services**, identify the decisive evidence before naming a response. A defensible conclusion here is: Investigate DHCP and local connectivity before blaming name resolution.
• For a scenario about **TCP, UDP, ports, and application dependencies**, identify the decisive evidence before naming a response. A defensible conclusion here is: Different parts of one application can choose different transports based on their requirements.
• For a scenario about **virtual networks, redundancy, and shared responsibility**, identify the decisive evidence before naming a response. A defensible conclusion here is: Multiple front-end servers do not make the whole service resilient when a critical shared dependency is singular.
• For a scenario about **observable and supportable network operations**, identify the decisive evidence before naming a response. A defensible conclusion here is: Convert the vague symptom into measured scope, then compare evidence across the path.

Everything for Networking, in order of use

Frequently asked questions