Pacing principle
Pace by demonstrated skill rather than racing through definitions. Leave room for configuration, troubleshooting, collaboration, and artifact analysis because those activities reveal whether students can use the concepts.
Pair this block with one retrieval check and one applied artifact so content coverage and skill development move together. Carry forward earlier dependencies into later network-scale problems. Apply this within the instructional purpose of ap networking pacing guide.
Weeks 1–3
Unit 1.1–1.2: device troubleshooting, connection, addressing basics, gateway behavior, DHCP, DNS dependencies, basic command evidence, and performance observations.
Pair this block with one retrieval check and one applied artifact so content coverage and skill development move together. Carry forward earlier dependencies into later network-scale problems. Apply this within the instructional purpose of ap networking pacing guide.
Weeks 4–5
Unit 1.3–1.4: device security needs and controls. Include authentication, updates, secure services, least privilege, and verification.
Pair this block with one retrieval check and one applied artifact so content coverage and skill development move together. Carry forward earlier dependencies into later network-scale problems. Apply this within the instructional purpose of ap networking pacing guide.
Weeks 6–8
Unit 2.1–2.2: SOHO troubleshooting and documentation. Students should diagram shared dependencies, inventory addressing, and diagnose one-client versus everyone-down failures.
Pair this block with one retrieval check and one applied artifact so content coverage and skill development move together. Carry forward earlier dependencies into later network-scale problems. In ap networking pacing guide, use this process to support the page's specific classroom objective and document the student evidence produced.
Weeks 9–11
Unit 2.3–2.4: upgrades and advanced features. Compare requirements, wireless capacity, device roles, addressing capacity, and operational tradeoffs.
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Weeks 12–14
Unit 2.5–2.6: security needs and securing the shared network. Build guest isolation, management restrictions, and rule verification.
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Weeks 15–18
Unit 3.1–3.2: devices/connections and switching topologies. Deepen Ethernet switching, MAC tables, VLANs, trunks, topology, and failure scope.
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Weeks 19–22
Unit 3.3–3.4: configuration/verification and segmentation/security. Use subnet plans, VLAN mapping, gateways, inter-VLAN routing, and trust matrices.
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Weeks 23–25
Unit 3.5–3.6: firewall/filtering and segmented-LAN troubleshooting. Emphasize rule order, logs, positive/negative tests, and cross-layer diagnosis.
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Weeks 26–28
Unit 4.1–4.3: failures, models/protocols, and CLI. Students should select commands from the evidence question rather than from habit.
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Weeks 29–31
Unit 4.4–4.6: routing, monitoring/defense, reliability/growth. Include longest-prefix match, next hops, counters, baselines, redundancy, and capacity.
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Weeks 32–34
Cumulative review and mixed incidents. Revisit weak skills from student error logs; combine artifacts rather than reteaching every page.
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Calendar flexibility
Shortened semesters, block schedules, testing days, and local calendars require adjustment. Preserve topic coverage and applied practice; compress repeated lecture before cutting labs that integrate several skills.
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Exam-year note
Pilot schools in 2026-27 should align final practice with the confirmed digital MCQ-only pilot. National 2027-28 classes should also prepare for the artifact/evidence-based free-response component.
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
The opening weeks of an AP Networking pacing plan should establish a common foundation rather than assume every student enters with the same computer background. For a detailed look at what beginners may already know, what they do not need to know, and how teachers can handle a mixed-experience classroom, see our AP Networking prerequisite and readiness guide. It also includes a first-two-weeks leveling approach teachers can use before moving into more demanding networking work.
Teacher implementation checks
Implementation check 1: Pacing principle
Ask students to state the requirement, identify the evidence source, and explain what a successful result would prove. Then introduce one contradictory result and require them to revise the hypothesis. Close by having them document the final verification in language another technician could reproduce. Apply this within the instructional purpose of ap networking pacing guide.
Implementation check 2: Weeks 1–3
Ask students to state the requirement, identify the evidence source, and explain what a successful result would prove. Then introduce one contradictory result and require them to revise the hypothesis. Close by having them document the final verification in language another technician could reproduce. Apply this within the instructional purpose of ap networking pacing guide.
Implementation check 3: Weeks 4–5
Ask students to state the requirement, identify the evidence source, and explain what a successful result would prove. Then introduce one contradictory result and require them to revise the hypothesis. Close by having them document the final verification in language another technician could reproduce. Apply this within the instructional purpose of ap networking pacing guide.
Implementation check 4: Weeks 6–8
Ask students to state the requirement, identify the evidence source, and explain what a successful result would prove. Then introduce one contradictory result and require them to revise the hypothesis. Close by having them document the final verification in language another technician could reproduce. In ap networking pacing guide, use this process to support the page's specific classroom objective and document the student evidence produced.
Implementation check 5: Weeks 9–11
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Implementation check 6: Weeks 12–14
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Implementation check 7: Weeks 15–18
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Implementation check 8: Weeks 19–22
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Implementation check 9: Weeks 23–25
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Implementation check 10: Weeks 26–28
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Implementation check 11: Weeks 29–31
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name t he intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Implementation check 12: Weeks 32–34
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Implementation check 13: Calendar flexibility
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
Implementation check 14: Exam-year note
For AP Networking Pacing Guide, convert this checkpoint into evidence students can produce during class. Have students name the intended network state, select the artifact that can reveal the actual state, interpret the result before making a change, and record why the chosen action is narrower than at least one alternative. Afterward, require them to repeat the original test and explain whether the evidence now satisfies the instructional objective. This makes the activity useful for both teaching and formative assessment.
AP Networking Pacing Guide planning workshop
Planning task 1 — Pacing principle: Use this instructional target: Pace by demonstrated skill rather than racing through definitions. Leave room for configuration, troubleshooting, collaboration, and artifact analysis because those activities reveal whether students can use the concepts. Write a student-facing objective that requires an observable networking decision, not just recall. Choose an artifact students will inspect, define the expected evidence, add one misconception that the artifact can expose, and specify how students will verify the result. Then decide what prior skill must be retrieved before this task and what later unit can reuse the same mechanism at a larger network scale.
Planning task 2 — Weeks 1–3: Use this instructional target: Unit 1.1–1.2: device troubleshooting, connection, addressing basics, gateway behavior, DHCP, DNS dependencies, basic command evidence, and performance observations. Write a student-facing objective that requires an observable networking decision, not just recall. Choose an artifact students will inspect, define the expected evidence, add one misconception that the artifact can expose, and specify how students will verify the result. Then decide what prior skill must be retrieved before this task and what later unit can reuse the same mechanism at a larger network scale.
Planning task 3 — Weeks 4–5: Use this instructional target: Unit 1.3–1.4: device security needs and controls. Include authentication, updates, secure services, least privilege, and verification. Write a student-facing objective that requires an observable networking decision, not just recall. Choose an artifact students will inspect, define the expected evidence, add one misconception that the artifact can expose, and specify how students will verify the result. Then decide what prior skill must be retrieved before this task and what later unit can reuse the same mechanism at a larger network scale.
Planning task 4 — Weeks 6–8: Use this instructional target: Unit 2.1–2.2: SOHO troubleshooting and documentation. Students should diagram shared dependencies, inventory addressing, and diagnose one-client versus everyone-down failures. Write a student-facing objective that requires an observable networking decision, not just recall. Choose an artifact students will inspect, define the expected evidence, add one misconception that the artifact can expose, and specify how students will verify the result. Then decide what prior skill must be retrieved before this task and what later unit can reuse the same mechanism at a larger network scale.
Planning task 5 — Weeks 9–11: Use this instructional target: Unit 2.3–2.4: upgrades and advanced features. Compare requirements, wireless capacity, device roles, addressing capacity, and operational tradeoffs. Write a student-facing objective that requires an observable networking decision, not just recall. Choose an artifact students will inspect, define the expected evidence, add one misconception that the artifact can expose, and specify how students will verify the result. Then decide what prior skill must be retrieved before this task and what later unit can reuse the same mechanism at a larger network scale.
Planning task 6 — Weeks 12–14: Use this instructional target: Unit 2.5–2.6: security needs and securing the shared network. Build guest isolation, management restrictions, and rule verification. Write a student-facing objective that requires an observable networking decision, not just recall. Choose an artifact students will inspect, define the expected evidence, add one misconception that the artifact can expose, and specify how students will verify the result. Then decide what prior skill must be retrieved before this task and what later unit can reuse the same mechanism at a larger network scale.
Planning task 7 — Weeks 15–18: Use this instructional target: Unit 3.1–3.2: devices/connections and switching topologies. Deepen Ethernet switching, MAC tables, VLANs, trunks, topology, and failure scope. Write a student-facing objective that requires an observable networking decision, not just recall. Choose an artifact students will inspect, define the expected evidence, add one misconception that the artifact can expose, and specify how students will verify the result. Then decide what prior skill must be retrieved before this task and what later unit can reuse the same mechanism at a larger network scale.
Planning task 8 — Weeks 19–22: Use this instructional target: Unit 3.3–3.4: configuration/verification and segmentation/security. Use subnet plans, VLAN mapping, gateways, inter-VLAN routing, and trust matrices. Write a student-facing objective that requires an observable networking decision, not just recall. Choose an artifact students will inspect, define the expected evidence, add one misconception that the artifact can expose, and specify how students will verify the result. Then decide what prior skill must be retrieved before this task and what later unit can reuse the same mechanism at a larger network scale.
Related teacher resources
Teacher Hub · Curriculum Map · Classroom Labs · Practice Questions · Site Directory