AP Networking Practice Tests by Topic

Start with a decision you need to improve

A broad practice exam can tell you that networking questions are costing points, but its total score may hide the cause. A missed question could be a subnet-boundary error, an incorrect assumption about a VLAN, a route lookup mistake, or a conclusion that goes beyond what a successful ping proves. Topic practice makes that missing step visible.

This library now covers twenty-two connected subjects and 1,650 explained questions across Phases 1–6. Every test offers 25 Easy, 25 Medium, and 25 Hard items. The split lets you distinguish direct-rule uncertainty from trouble combining evidence. Students who recognize a gateway definition may still need practice deciding whether a host will ARP locally, which installed route wins, and whether a reply can return.

Use this directory for diagnosis and targeted repetition. The existing practice questions provide broader review, unit guides organize teaching, and full practice exams help test transfer across subjects. These resources serve different stages of study rather than being interchangeable lists of questions.

All questions here are independent instructional items. They are not released College Board questions, and these local difficulty labels or scores do not predict a national exam score.

Taking the May 2027 pilot? Start with the 2027 pilot exam practice test and study guide: 32 original scenarios across all four units, with immediate feedback. Use its result to choose a specific topic test below; the diagnostic is not an official full-length exam.

The Phase 1 topic library

Choose by the evidence you find confusing. If the symptom is a missing link or uncertain power budget, begin with components/media. If the client chooses the wrong local or remote path, begin with addressing. If the intended segment disappears across a trunk, choose switching/VLANs. If the next hop or reply path is uncertain, choose routing. If an address or name-dependent stage is missing, choose DNS/DHCP.

Phase 2: diagnose wireless, policy, command, transport, and IPv6 failures

After the foundation tests, use Phase 2 to investigate the missing boundary in a more specific troubleshooting problem. A wireless client can associate yet lose its VLAN service path; a route can exist yet policy deny one transport; an IPv6 address can form without a usable default router.

Use the existing command-output lesson for a guided reading of artifacts, then take the CLI test to check selection and inference across difficulty levels. Use first-match policy practice for a narrower rule-order exercise before the broader ACL diagnostic. The new tests extend these lessons with structured self-assessment rather than replace them.

Phase 3: trace evidence, evaluate access, and verify resilient service

Phase 3 moves from a single connectivity symptom to evidence collection and operational decisions. Trace rewritten tuples through NAT, evaluate what a capture can see, calculate valid monitoring rates, distinguish identity from action permission, and test whether a redundant design recovers the required task.

Use the NAT lesson for the translation foundation and the guided packet-capture practice for an initial artifact reading. The new tests add scored diagnostic sets and wider evidence combinations. Choose monitoring practice for measurement uncertainty; choose design and redundancy practice when the question is whether an alternate path meets the required workload and failure case.

Phase 4: resolve protocol state and document a verified repair

Phase 4 examines protocol state and the reasoning behind a repair. Use DNS when the exact query, authority path or cached result is uncertain. Use DHCP when assignment, timers, relay delivery or allocation capacity is the missing step. ARP practice separates route-selected neighbors from switch forwarding and competing ownership. Encapsulation follows fields and size budgets across processing boundaries. Troubleshooting practice tests the experiment, acceptance condition and handoff that make a result defensible.

The earlier broad protocol test checks initial protocol selection. These focused sets go further into state, conflicting observations and controlled verification. Use troubleshooting methods and documentation across the technical topics: record the exact attempt, separate evidence from interpretation, and test both recovery and the restrictions that must remain.

Phase 5: troubleshoot HTTPS, TLS, and certificate failures

A responding server is not enough: students must distinguish a reachable listener, an authenticated service name, an accepted trust path, and a successful application task. This focused set adds 75 questions and a practical guide to testing those boundaries.

Phase 6: troubleshoot MTU, MSS, and path-size failures

Small requests can pass while a large transfer stalls. This focused set connects packet budgets, feedback delivery, tunnel overhead, and evidence from both directions.

Progress from a rule to an evidence-based decision

Easy: Identify a device function, apply a stated prefix, read one direct observation, or recognize a protocol stage. Explain the rule before advancing. A correct guess based on a familiar word is a signal to review, not a reason to skip the explanation.

Medium: Combine two pieces of evidence. A powered AP without a link separates power from data. A host address and mask must be read together before deciding whether its gateway is local. A DHCP exchange that ends after Offer calls for a different next observation from one that reaches ACK with wrong options.

Hard: Choose among plausible decisions while respecting the limits of the observations. You may need to consider a return path, an overlapping subnet, a VLAN-specific failure on an otherwise healthy trunk, or a resolver cache that differs from authoritative data. Difficulty comes from the reasoning burden, not merely a longer prompt.

You can start at any level, but a useful diagnostic order is Easy, then Medium, then Hard on one topic. Each selected level contains exactly 25 questions. Switching levels resets the attempt, so download the attempt log before changing if you want a record. Every answer receives immediate feedback; the first selection is scored. There is no time limit in these diagnostic activities.

Read a result as a dependency map

Compare the pattern of misses, not only the percentage. Strong Easy performance with weaker Medium results often calls for combining artifacts: address plus mask, VLAN assignment plus trunk allowance, or DNS response plus transport test. Strong Medium performance with weaker Hard results may expose overclaiming or difficulty handling an alternative explanation.

For example, a gateway ping proves a local ICMP exchange with that gateway at that time. It does not prove that a remote website's DNS answer is correct, that TCP 443 is permitted, or that the server returns traffic to the client's source subnet. When reviewing an answer, name the tested boundary and the next dependency instead of writing “the network works.”

A route table proves which installed prefix a lookup can select under its current state. It does not prove that the next-hop neighbor answers, the policy permits traffic, or downstream routers have a reply path. A DHCPACK proves an allocation response was observed; its address, mask, gateway, and resolver values still need validation against the intended network.

If you are unsure which inference was excessive, use the site's Wrong Answer Detective to practice comparing observations with conclusions. Then return to the topic that produced the misunderstanding and explain the repair in a narrower sentence.

Build an error log that changes the next study session

After each attempt, use the download control for a CSV containing question ID, difficulty, selected answer, correct answer, result, and explanation. Add your own reasoning note in a spreadsheet or notebook. Keep one line per reasoning failure; copying the entire explanation without naming your original mistake makes the log less useful.

Swipe to see the full error-log example.

Label the mistake as a rule error, calculation error, observation error, path error, or overclaim. Include one tempting distractor and the evidence that rules it out. That entry gives the next session a task: recalculate a boundary, trace a VLAN, compare two source addresses, or identify the missing protocol message.

Revisit a question without rehearsing its answer letter

On the first review, hide the choices. Write the strongest observation, your bounded conclusion, and the next test. Then open the explained item and compare the method. If you can remember the correct letter but cannot explain why an alternative fails, the reasoning still needs attention.

On a later session, change the representation. Draw the packet path for a routing answer, list subnet boundaries for an addressing answer, sketch the access/trunk chain for a VLAN answer, or mark the last observed message in a DHCP exchange. This is a more useful transfer check than immediately restarting the same 25 items until the score rises.

Use subnetting practice questions when a calculation step is weak, and routing-table analysis when a route decision needs an artifact-based second pass. These existing resources deepen one operation. Return here when you are ready to place that operation inside a larger scenario.

Keep score history separate from evidence of transfer. A higher score on a familiar bank is encouraging, but an unfamiliar artifact, a written explanation, or a mixed-topic task provides stronger information about whether the skill generalizes.

Move from topic practice to unit and full-exam work

Once errors have a clear cause and you can explain a corrected decision, move to the appropriate Unit 1 practice, Unit 2 practice, Unit 3 practice, or Unit 4 practice. Unit work requires choosing the relevant tool among related course concepts.

Then use full practice exams for mixed-topic selection and endurance. If the missed question concerns an explanation rather than only a selection, pair it with free-response practice or artifact analysis. State what the artifact proves, what remains uncertain, and which observation would distinguish your leading explanations.

A practical sequence is topic diagnosis, a focused guide, explained topic practice, an unfamiliar unit task, then a mixed exam or written artifact response. Move backward when a result reveals a missing prerequisite. There is no benefit in continuing full exams while repeating the same unchecked subnet assumption.

How the library connects to the course

The current pilot framework organizes AP Networking around four units: Managing My Connections, Managing Shared Connections, Managing Many Connections, and Managing Global Connections. Components and addressing support decisions about individual and shared connections; switching and segmentation become especially important when managing many connections; routing and service protocols help explain broader paths.

Those are teaching connections, not claims that each topic belongs exclusively to one unit or carries a fixed exam weight. A single troubleshooting scenario may combine a client's interface, address, VLAN, route, resolver, and security policy. The topic names help isolate a weak operation before students recombine those dependencies.

College Board currently describes the national exam for May 2028 as fully digital in Bluebook, with scenario-based multiple choice and artifact/evidence-based free response. These browser activities support the underlying reasoning; they are not a Bluebook simulator or a reproduction of official exam timing and scoring. Consult the site's exam guide for the broader preparation context and the official exam overview for current national assessment guidance.

Phases 1–4 are complete; Phase 5 adds a focused secure-service diagnostic to this provisional ten-phase project. Later topics should be checked against the live inventory and current framework before publication. No unbuilt tests are listed as available here.

Use the tests in a classroom

Assign one level rather than all 75 items at once when the purpose is diagnosis. Collect a brief explanation for two choices: one correct answer with a tempting distractor and one missed answer after review. That combination shows whether the student understood the decision or merely recognized an answer pattern.

Group students by the missing step. One group may need prefix boundaries; another may need to separate VLAN forwarding from routing; another may need to distinguish resolver success from application availability. Use projected configurations and annotated paths when a live lab is unavailable. The static explained library remains readable even when JavaScript is disabled.

For paired work, ask one student to defend the bounded conclusion and another to propose a plausible alternative. They should identify the next observation that separates the two. A useful exit ticket is a three-sentence account: evidence, conclusion with limits, and next test. The site’s teacher resources can support the follow-up lesson after the diagnostic reveals which operation needs practice.

Require students to record the topic, level, question ID, and attempt date if you need a review trail. These pages do not submit results to a teacher dashboard. The student can download the current attempt log and attach it through the classroom system you already use.