Performance-task practice should make you produce a defensible network decision
These are independent AP Networking-style practice tasks, not official College Board submissions. Each task gives you a requirement, realistic evidence, competing explanations, and a deliverable. Your job is to decide what the network should do, compare that with what the artifacts show, make the narrowest justified correction, and explain how you would verify success.
The rule for every task
Do not begin with the fix. Begin with the requirement, identify the first contradiction, then produce a change that is supported by the evidence and a verification test that matches the original goal.
Use all four course skills as verbs
Use REQUIREMENT → EXPECTED STATE → ARTIFACT → DECISION → IMPLEMENT → VERIFY
A strong response is not just technically plausible—it is evidence-linked
| Dimension | Weak response | Strong response | Self-check question |
|---|---|---|---|
| Requirement | Repeats a keyword | States the exact behavior that must work | What outcome am I trying to restore or create? |
| Evidence | Uses general networking knowledge only | Cites the exact artifact/value that matters | Which line, field, counter, route, or rule supports me? |
| Mechanism | Names a device | Explains why that artifact produces the symptom | How does the configuration change packet behavior? |
| Change | Uses a broad reset or ANY/ANY rule | Changes only the demonstrated dependency | What is the narrowest justified correction? |
| Verification | “Check if it works” | Repeats the original task plus a relevant control | What evidence would prove the requirement now succeeds? |
Swipe horizontally to use the complete scoring lens.
Repair a client that cannot reach remote networks
Scenario
A new workstation should join the Finance VLAN and reach both a local printer and a remote accounting server.
Choose a subnet for a growing lab without wasting the entire /24
Scenario
A lab needs addresses for 42 current devices and 10 planned devices. The available parent block is 10.70.12.0/24.
Find why VLAN 30 clients cannot obtain DHCP leases
Deliverable: explain the packet path for the initial DHCP exchange, identify where VLAN 30 is blocked in the shown design, propose the narrow correction, and verify that a VLAN 30 client receives the intended subnet/gateway/DNS options.
Build a least-privilege rule for a grade portal
Requirement: Student VLAN users may access the grade portal securely. They may not administer the server.
Verification: confirm HTTPS succeeds from an allowed student client; confirm SSH remains denied; preserve server administration from the authorized management network if that is a separate requirement.
Localize intermittent packet loss with timed evidence
Deliverable: identify the strongest failure boundary, explain why the evidence supports queue congestion rather than a client cable fault, name a falsifying control, and define a verification window.
Resolve a DNS-vs-HTTPS dependency problem
Deliverable: state which dependencies have succeeded, identify the first failed stage, and name at least two plausible causes that fit the certificate mismatch.
Choose layered controls for a shared wireless network
Scenario: A school guest network must provide Internet access to visitors while preventing guest-to-internal-server access and reducing risk from unauthorized wireless use.
Use AI as a hypothesis generator—not the authority
Your team sees intermittent packet loss on one Wi-Fi client. An AI assistant recommends “upgrade the Internet plan because the network is overloaded.”
Deliverable: assign team roles, critique the AI recommendation with evidence, choose the next test, and document the verified conclusion.
Choose the actual path using longest-prefix match
Deliverable: identify every matching route, select the route the router should use, explain why, then state what this table does not prove about the return path.
Repair a segmented network without breaking what already works
Requirement: Staff VLAN 20 must access an internal HTTPS app and DNS. Guest VLAN 40 must access public Internet only.
Task: identify the missing requirement-specific rule, explain why the current guest behavior should be preserved, write the narrow rule concept, and describe verification.
One changed artifact should be allowed to change your answer
| Original task evidence | Changed fact | Reasoning change |
|---|---|---|
| Gateway outside client's /24 | Client prefix changes to /16 by design | Gateway may now be local; re-evaluate before changing it |
| VLAN 30 omitted from shown trunk | Packet capture proves VLAN 30 crosses another active trunk | The displayed trunk is not the whole path |
| HTTPS timeout | TCP handshake succeeds and TLS cert fails | Move above transport to TLS/certificate analysis |
| WAN utilization 99% with drops | Utilization now 30% and drops do not rise | Simple queue-saturation diagnosis weakens |
| AI recommends bandwidth upgrade | Wired and wireless controls both show loss beyond gateway | Broaden beyond wireless; shared upstream path becomes stronger |
Swipe horizontally to practice changed-fact reasoning.
Score the reasoning, not whether the student guessed the device name
| Score area | Full-credit behavior | Common weak response |
|---|---|---|
| Requirement | Defines the exact connectivity/security/performance goal | Repeats “fix network” |
| Artifact use | Cites exact values, routes, ports, rules, counters, or states | Uses only memorized definitions |
| Mechanism | Explains how the evidence changes packet behavior | Names a device without mechanism |
| Change scope | Corrects the narrow demonstrated dependency | Reboots or opens everything |
| Verification | Retests original goal and a relevant control | “See if it works” |
| Evidence limits | States what remains unproven | Claims certainty beyond the artifact |
Swipe horizontally to use the scoring rubric.
Eight habits that weaken otherwise good answers
- Fix-first reasoning: proposing a change before identifying the requirement and contradiction.
- Vocabulary-only answers: defining DNS, VLAN, or NAT without using the artifact.
- Broad changes: ANY/ANY firewall rules, blanket resets, or unnecessary renumbering.
- Ignoring controls: failing to use what still works to narrow the boundary.
- Forward-path tunnel vision: proving the request path but never considering the return path.
- One-test certainty: stretching a ping, listener, route, or DNS answer beyond what it proves.
- AI deference: treating generated advice as evidence instead of a hypothesis to test.
- Weak verification: checking a different task than the one that originally failed.
24 performance-task reasoning flashcards
These cards mix configuration, security, troubleshooting, collaboration, artifact interpretation, and verification.