1. Subnet boundary and gateway
Correct answer: B. A /27 creates 32-address blocks. Both .70 and .65 are in 10.14.8.64/27.
Why this matters: This question tests whether you calculate the prefix boundary instead of guessing from familiar /24 patterns.
How to practice
A mixed question bank should force you to identify the topic from the evidence
These scenarios connect addressing, protocols, switching, routing, security, wireless, performance, and troubleshooting. Choose an answer from the observations in each prompt, then use the explanation to check your reasoning.
If mixed questions make it hard to tell which prerequisite is weak, start with AP Networking Practice Tests by Topic. Its explained sets let you review a specific boundary or protocol stage, then return here to practice recognizing the method without a topic label.
For each question, do four things before reading the explanation. First, define the required behavior. Second, mark the strongest positive and negative evidence. Third, identify which answer choices contradict those facts. Fourth, choose the action or conclusion that changes the fewest unsupported variables.
The goal is not to guess the topic from a heading. In real troubleshooting—and in a well-written networking assessment—the symptom can cross several domains. A “website problem” can actually be DNS, routing, firewall policy, TLS, or the server process. A “Wi-Fi problem” can actually be DHCP or congestion. Mixed practice is valuable because it removes the label and makes the evidence do the classification.
Practice questions are most useful when you understand what you are working toward. If you are considering the course or wondering whether taking the AP Exam is worthwhile, see why students take AP Networking and what they can gain from it, including potential college credit or placement, career-connected skills, the AP Networking Credential, and experience solving real networking problems.
Evidence discipline
Use successful checkpoints to eliminate entire branches
| Observation | What it supports | What it weakens | What remains open |
|---|---|---|---|
| Gateway ping succeeds | Local IP reachability to the gateway | Total local-link/gateway failure | Remote routing, DNS, transport, application |
| Remote numeric IP succeeds | That tested routed IP path | Complete remote IP outage | DNS, service-specific filtering, application |
| DNS returns expected address | Name resolution for that query | Basic DNS-record failure for that query | Route to service, port, firewall, TLS, listener |
| One VLAN fails; peers work | Shared infrastructure is at least partly functioning | Total site-wide outage | VLAN-specific switching, gateway, DHCP, policy |
| Firewall log shows matching DENY | Policy blocked the observed flow | Pure DNS explanation for that same denied flow | Rule scope/order and intended authorization |
Swipe horizontally to see the full table.
Notice the wording: a successful test does not prove everything above it. It simply removes or weakens some explanations. That precision is what makes later decisions defensible.
Original mixed practice bank
12 interactive AP Networking scenario questions
Choose one answer for each question. You will then see whether your choice is correct and read the explanation. Your first choice counts toward your score; use Reset Test to start a new attempt. Work from the evidence before checking your notes.
0 of 12 answered · 0 correct
2. Numeric IP works, hostname fails
Correct answer: C. The numeric control shows the tested IP path works without DNS; the DNS timeout makes resolver configuration/path/service the stronger next branch.
Why this matters: Do not claim the entire network is healthy—only that the numeric-IP test succeeded.
3. VLAN-specific outage
Correct answer: B. The shared uplink working for other VLANs weakens a total physical-uplink failure. Investigate what is unique to VLAN 30.
Why this matters: Scope is evidence.
4. Route-table choice
Correct answer: C. The /24 is the longest matching prefix.
Why this matters: After selecting C, you still have not proved that next hop C or the downstream/return path is healthy.
5. Firewall rule order
Correct answer: A. The broader deny matches first. A narrow rule-order correction restores the required flow without opening unrelated traffic.
Why this matters: Verification should include HTTPS success and a negative test for traffic that must remain denied.
6. Wireless contention
Correct answer: B. Strong signal with retries/utilization points toward airtime contention or interference rather than simple weak coverage.
Why this matters: Compare channel conditions and a wired control before blaming the ISP.
7. WAN congestion
Correct answer: B. The time-correlated utilization, drops, and remote latency support congestion on the shared upstream path.
Why this matters: Correlation is stronger because the local gateway control stays stable.
8. No web listener
Correct answer: B. A firewall cannot create an application listener. The evidence has moved the failure boundary to the service endpoint.
Why this matters: This is a classic example of stopping network changes when network evidence is already sufficient.
9. Duplicate IP
Correct answer: A. Conflicting IP-to-MAC ownership strongly supports a duplicate-address problem.
Why this matters: Confirm which endpoints are configured for the address before changing DNS or routing.
10. CRC errors
Correct answer: A. CRC growth points toward cabling, transceiver, interface, or negotiation evidence rather than pure capacity congestion.
Why this matters: Compare the error counter before/after a physical-layer correction.
11. APIPA on one host
Correct answer: B. The one-host scope plus APIPA-style address suggests failed normal address assignment; compare endpoint and DHCP-path evidence.
Why this matters: A manual static address might hide rather than fix the underlying problem.
12. Successful gateway ping
Correct answer: B. The gateway reply is positive evidence for the local path. The failing numeric remote test does not require DNS.
Why this matters: This question rewards bounded claims rather than 'the network works' or 'the network is down.'
Free digital flashcards
24 AP Networking evidence-and-decision flashcards
Use these after the worked questions. The deck is intentionally mixed across the same domains so you practice recognition without a chapter label.
All topics
Click or press Enter/Space to reveal.
Before moving on, identify one distractor this evidence eliminates.
0 seen•24 cards
Distractor analysis
Wrong answers are most useful when you can explain exactly why they are weaker
Right concept, wrong scope
DNS can cause name failures, but it is a weak answer when the failing test uses only a numeric IP. A firewall can block traffic, but not every failure is a firewall problem.
Possible cause, contradicted evidence
A dead uplink is possible in general, but much weaker when other VLANs are working over that same uplink.
Repair too broad
“Allow all” may restore one application while violating the security requirement. The better answer restores only the required communication.
Correct tool, wrong question
Ping can test ICMP reachability, but it cannot prove TCP/443 is open. nslookup can test DNS, but it does not prove HTTPS works.
Artifact overclaim
A route table can prove a local forwarding choice, not the complete end-to-end and return path.
Workaround instead of repair
A static IP can hide a DHCP problem. A permanent broad allow can hide a policy-design problem. Prefer the cause-level correction.
Question construction
Build your own practice questions from controlled changes in evidence
A powerful study method is to take one scenario and change exactly one observation. Start with: “The client cannot open portal.example.” Then add “the client cannot reach its gateway.” That pushes the diagnosis toward local configuration or link/VLAN evidence. Replace that with “the gateway works and the server IP works, but the name fails.” Now DNS becomes the stronger branch. Replace that with “DNS returns the expected IP, but TCP/443 is denied by a firewall rule.” The same user symptom now has a completely different best answer.
When you miss a practice question, look beyond the answer key: which observation did you overlook, and what did your chosen answer assume? Our 20-case Wrong Answer Detective makes you compare the evidence and explains why tempting alternatives fail.
This controlled-change method teaches causality because you can see which new fact moved the diagnostic boundary. It also prepares you for plausible distractors, because several options remain technically possible until the evidence rules them down.
Practice rule: when you miss a question, do not only memorize the correct choice. Write the observation that made it correct, the mechanism behind it, and one fact that would have made another choice stronger.
From concept drills to mixed sets
Use three practice phases instead of jumping straight to a full mixed exam
Phase one is mechanism repair. If you cannot reliably calculate a /27 boundary, do not hide that weakness inside a 40-question mixed set. Fix subnetting directly. If longest-prefix matching is unstable, practice route tables until the forwarding rule is automatic.
Phase two is mixed recognition. Combine addressing, DNS, switching, routing, security, wireless, and performance so the prompt must reveal the domain. Phase three adds time pressure and cumulative review. Speed belongs at the end because fast guessing does not build a network model.
Use AP Networking Study Guide for mechanism repair, Artifact Analysis for evidence reading, and Final Review when you are ready to combine everything.
Error log method
Turn every missed question into a reusable troubleshooting rule
Do not record only the letter of the correct answer. For each miss, write four short notes: the mechanism you misunderstood, the exact evidence you overlooked, the distractor that fooled you, and the verification you would use in a real network. This creates a far more useful review log than a simple score.
For example, if you miss a question because you chose DNS after a numeric-IP test already failed, the lesson is not “remember question 7.” The reusable rule is that DNS is not required for a numeric-IP test, so a failed numeric control keeps lower-layer or routed-path causes alive. If you choose a default route when a more-specific route exists, the rule is to identify all matching prefixes before considering the default. If you choose an allow-all firewall fix, the rule is to translate the requirement into the narrowest permitted flow and verify that unrelated traffic remains blocked.
After several practice sessions, sort your misses by mechanism rather than by page. A cluster of errors around subnet boundaries, rule order, route specificity, or evidence overclaiming is a clear signal for targeted review. That is how a mixed question bank becomes a diagnostic tool for your own learning.
Verification thinking
Every practice answer should end with “How would I prove the fix worked?”
For a DHCP repair, verify the client receives the intended address, prefix, gateway, and DNS settings from the expected source. For a DNS repair, repeat the original hostname query and application operation. For a routing repair, verify the intended destination selects the expected path and test a nearby control destination. For a firewall repair, verify the required flow succeeds and unauthorized traffic remains blocked. For a wireless-capacity change, compare retries, channel utilization, throughput, and user behavior before and after the adjustment.
Verification converts a proposed answer into an operational one. It is also a strong way to catch bad distractors: if you cannot describe what successful verification would look like, you may not yet understand the mechanism the answer claims to fix.
Continue practicing