How to Get a 5 in AP Networking

What we have for Networking

Everything below is free to work through and is organized 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.

What a 5 in Networking takes

The specific habits that separate a 5 from a 3 on this exam, drawn from the scoring patterns for Networking.

• Show the arithmetic on any subnetting question. 2^n − 2 written out earns the point that a bare answer does not.
• When a symptom is "local works, external fails", say what that rules OUT as well as what it rules in — proving the endpoints are fine is half the diagnosis.
• For each diagnostic tool you name, state what a pass and a fail would each tell you. A tool with no stated interpretation earns nothing.
• Do not describe TCP as simply "better" than UDP. Every answer that treats reliability as a universal good misses the point real-time traffic is making.

The 5 units of AP Networking

Unit names follow the published course framework. Networking is one of the courses whose framework does not weight units against the exam, so there is no “heaviest unit” to chase — spread your time by where your own errors are.

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 course — no published weighting yet · 3 lessons · starts with “Network Models and Encapsulation”
2. 2Network InfrastructurePilot course — no published weighting yet · 3 lessons · starts with “Switching and VLANs”
3. 3Network ServicesPilot course — no published weighting yet · 3 lessons · starts with “DNS, DHCP, and Address Translation”
4. 4Network OperationsPilot course — no published weighting yet · 3 lessons · starts with “Monitoring, Baselines, and Documentation”
5. 5Network SecurityPilot course — no published weighting yet · 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

Interactive labs for Networking

Frequently asked questions