AP Networking • Unit 1 • Evidence-first assessment
AP Networking Unit 1 Practice Test: Managing My Connections
Test whether you can diagnose one-device failures, separate connectivity from performance, identify endpoint security needs, choose narrowly scoped controls, and explain exactly what each observation proves—and does not prove.
Independent AP Networking resource • Updated 2026-10-01 • 18 explained practice questions + 24 free digital flashcards
AP Networking Premium: Add guided practice, answer explanations, artifact work, and structured review to the free study system.
Do not hunt for vocabulary—locate the failure boundary
Unit 1 becomes much easier when every answer begins with the evidence. A link light proves something different from a valid DHCP lease. A successful gateway ping proves something different from a successful DNS query. High throughput proves something different from low latency. A security control being enabled proves something different from that control being correctly scoped.
Individual-device reasoning often depends on interface state, address classification, and service configuration. Use AP Networking Practice Tests by Topic to choose a components, addressing, or DNS/DHCP diagnostic, then return to this unit to combine those dependencies.
Observation
Name the exact artifact, setting, test result, scope, or timing clue.
Bounded inference
State only what that evidence supports. Do not turn one successful test into “the network works.”
Next discriminating evidence
Choose the next test that separates the leading explanations with the least disruption.
For security questions, extend the chain to requirement → control → scope → positive verification → negative verification. For performance questions, compare the relevant metric before and after a controlled change.
Dependency map
Know which layer of evidence each Unit 1 observation belongs to
Evidence
Supports
Does not prove
Useful next evidence
Link/association present
Some local attachment exists
Valid IP configuration or application reachability
Address, prefix, gateway, DHCP state
Expected address/prefix
Client configuration is plausible
Gateway or remote path works
Gateway reachability
Gateway responds
Local path to next hop works
DNS or remote application works
Known remote IP
Remote IP responds
Useful routed IP path exists
Name resolution or target application succeeds
DNS query / service-specific test
High Wi-Fi signal
Received signal may be adequate
Low contention, low retries, or fast upstream path
Retries, channel use, latency, local throughput
Security control enabled
Configured state exists
Correct scope or preserved authorized access
Positive + negative tests
Swipe horizontally to see the full table.
Interactive Unit 1 assessment
18 questions with immediate evidence-based explanations
Choose an answer before opening the explanation. Your score is useful, but the more important review question is: what observation eliminated each distractor?
Answered: 0 / 18 Correct: 0
TroubleshootingQuestion 1 of 18
Unexpected automatic address
A wired laptop shows link. Its IPv4 address is 169.254.44.18/16. Working peers on the intended classroom network receive 10.14.8.x/24 addresses by DHCP. What is the strongest next investigation?
Answer: B. The physical link has some attachment, but the client did not obtain the expected DHCP configuration. A 169.254.x.x IPv4 address is strong evidence to inspect DHCP/client configuration before dependencies such as DNS or a remote application.
TroubleshootingQuestion 2 of 18
Local works, remote fails
A desktop is 192.168.40.25/24, reaches 192.168.40.50, but cannot reach remote subnets. Its gateway is 192.168.50.1. Which observation is most important?
Answer: A. With /24 addressing, 192.168.40.0/24 is local. The configured gateway at 192.168.50.1 is not on that local subnet, so the expected directly reachable next hop is inconsistent. Same-subnet success also weakens a total-link-failure hypothesis.
TroubleshootingQuestion 3 of 18
Names fail after IP succeeds
A laptop has expected addressing, reaches its gateway, and reaches a known remote server by IP. A query to the configured DNS resolver times out. What is the most discriminating next focus?
Answer: A. Remote IP reachability has already crossed several lower dependencies. The failure appears when name resolution is introduced, so resolver configuration, reachability, filtering, or service state is the narrower boundary.
TroubleshootingQuestion 4 of 18
One device changed manually
One laptop loses remote connectivity immediately after its user manually edits network settings. All peers remain healthy. What should happen before shared infrastructure is restarted?
Answer: A. Scope and timing point toward the changed endpoint. Inspect the smallest failure domain first. A shared-infrastructure change is not justified by one endpoint failing immediately after a local configuration change.
PerformanceQuestion 5 of 18
Location-dependent Wi-Fi
A laptop performs well near the access point. Behind several dense walls, signal quality falls, retries rise, and throughput drops. Wired devices remain normal. Which interpretation best fits?
Answer: C. The symptom changes with location and is accompanied by wireless retry/signal evidence while wired paths remain healthy. That combination localizes the problem toward RF coverage, interference, contention, or client/AP behavior.
PerformanceQuestion 6 of 18
Throughput versus connectivity
A laptop connects successfully on a crowded 2.4 GHz WLAN but gets 28 Mbps. At the same location on an approved 5 GHz WLAN it gets 170 Mbps with lower channel utilization. What does this show?
Answer: B. Both paths provide connectivity. The changed band/channel conditions correlate with a large throughput difference, so this is performance analysis rather than binary connectivity diagnosis.
PerformanceQuestion 7 of 18
Loaded latency
A wired laptop has 8 ms latency when idle and 145 ms latency while a large upload saturates the connection. Throughput remains high. What should be investigated?
Answer: A. The symptom appears specifically under offered load and even on a wired path. That pattern supports queue buildup or congestion at a bottleneck more strongly than a wireless or DNS explanation.
PerformanceQuestion 8 of 18
Negotiated Ethernet rate
A gigabit-capable laptop and switch are connected, but the active Ethernet link negotiates at 100 Mbps. Internet speed tests also plateau below 100 Mbps. What is the strongest first boundary?
Answer: A. The negotiated link itself exposes a local ceiling before Internet testing is interpreted. Cable pairs, connectors, adapter settings/capability, dock, and switch-port negotiation are higher-value checks than unrelated application dependencies.
s="qtop">Security NeedQuestion 9 of 18
Public Wi-Fi exposure
A student uses a laptop on an untrusted public WLAN. Which security need becomes more important without assuming the device is already compromised?
Answer: A. An untrusted local environment increases exposure. The bounded conclusion is that sharing, local services, secure protocols, identity, and policy deserve attention—not that compromise has already occurred.
Security NeedQuestion 10 of 18
Lost laptop
A mobile laptop stores sensitive local records and frequently leaves campus. Which requirement follows most directly from that combination?
Answer: A. Mobility increases physical-loss exposure and sensitive local data increases the consequence. The security requirement can be stated before choosing a particular implementation: protect stored-data confidentiality after device loss.
Security NeedQuestion 11 of 18
Privilege evidence
A student account is a local administrator because one approved lab tool occasionally needs elevation. What is the best security-needs conclusion?
Answer: A. Administrator membership increases potential consequence, but it does not prove compromise. The next question is which task actually requires elevation and whether that capability can be narrowed.
Security NeedQuestion 12 of 18
Unsupported software
A required application is no longer supported by its vendor. Which statement stays within the evidence?
Answer: A. Unsupported status raises risk because future fixes may not be available. It does not prove active exploitation. Strong reasoning separates the risk condition from claims the evidence cannot establish.
Security ControlQuestion 13 of 18
MFA mechanism
A privileged account is exposed to password-phishing risk. What does MFA most directly change?
Answer: A. MFA addresses the authentication path. It does not patch software, encrypt stored data, or improve RF performance. The control should be matched to the threat path it changes.
Security ControlQuestion 14 of 18
Narrow firewall rule
SSH management should be available only from an approved administrator subnet. Which control is strongest?
Answer: A. The narrow rule preserves the required management flow while reducing unnecessary exposure. Verification should include an approved-source connection and an unapproved-source denial.
Security ControlQuestion 15 of 18
Encryption boundary
Full-disk encryption is enabled on a laptop. Which claim is accurate?
Answer: A. Disk encryption addresses a particular data-at-rest condition. Once an authorized session has unlocked data, other controls still matter. Encryption also does not establish remote-site trust or recover deleted data.
Security ControlQuestion 16 of 18
Backup versus sync
A synchronization client uploads ransomware-encrypted versions of files to cloud storage and reports success. What lesson follows?
Answer: A. A recovery control must provide a usable trustworthy recovery point. Versioning, protected backups, separation from the working copy, and restore testing matter. A successful sync status can faithfully copy damage.
VerificationQuestion 17 of 18
Positive and negative tests
A new firewall rule blocks an unwanted service from the guest network. What additional test is needed before calling the change fully verified?
Answer: A. A negative test proves restriction, but not availability of legitimate use. Strong verification tests both sides of the intended boundary: what must work and what must remain denied.
VerificationQuestion 18 of 18
Patch evidence
An updater says “security update available.” Which evidence is stronger after remediation?
Answer: A. Availability of a patch and installation of a patch are different states. Version/build or managed update status is closer to the security outcome being verified.
Artifact analysis
A prefix mismatch changes the client's forwarding decision before a router ever sees the packet
Affected endpoint
IPv4: 10.30.12.44
Prefix: /16
Gateway: 10.30.12.1
Working peer on same intended VLAN
IPv4: 10.30.12.51
Prefix: /24
Gateway: 10.30.12.1
Target: 10.30.25.20
The affected endpoint's /16 treats 10.30.25.20 as local, so it attempts local Layer 2 resolution for that destination. The expected /24 treats 10.30.25.20 as remote and sends the packet toward the gateway. The identical gateway values do not cancel the prefix mismatch: the prefix determines whether the gateway is used for that destination.
The strongest repair is not “restart routing.” Confirm the documented prefix, correct the endpoint if /24 is intended, and then verify both a same-subnet destination and a remote destination. This tests the mechanism that actually changed.
Differential diagnosis
Similar user complaints can sit at very different boundaries
“The Internet is down.”
If the endpoint has 169.254.x.x where DHCP should provide 10.x.x.x, the first boundary is expected IP configuration—not the Internet.
“Wi-Fi is slow.”
If local wireless throughput is fast but Internet throughput is slow on wired and wireless paths, the evidence moves the bottleneck upstream.
“The website is broken.”
If the server works by IP but not hostname, test DNS before declaring the application server unavailable.
“The firewall broke it.”
If disabling the firewall restores a service, policy is relevant. The final repair is a justified narrow rule—not permanent firewall removal.
One endpoint, multiple problems
Do not force unrelated symptoms into one cause
A laptop can simultaneously have a DNS configuration problem, poor Wi-Fi performance in one room, and a pending security update. Restoring DNS does not prove the RF problem disappeared. Improving RF performance does not install the patch. Installing the patch does not prove hostname resolution works.
Separate each complaint into a requirement and evidence chain. For DNS, verify resolver behavior after IP reachability. For wireless performance, compare metrics such as retries, latency, throughput, and channel conditions. For the security update, verify the installed version/build. Then retest each original symptom independently.
Information-gain rule: the best next test is often the one that changes your belief about competing causes, not the one that produces the most output.
Working-peer method
A comparison is useful only when the peer is expected to receive the same policy
Suppose an affected laptop and a working laptop are intended for the same wired classroom network. Both show link. The working laptop has 10.18.4.62/24, gateway 10.18.4.1, DNS 10.18.1.53. The affected laptop has 10.18.4.91/24, gateway 10.18.4.254, and the same DNS server. Same-subnet peers work only on the affected laptop.
The gateway difference is relevant to the remote-only symptom, but first confirm the documented gateway. If 10.18.4.1 is intended, correct that endpoint and retest a remote IP before testing DNS. A nearby laptop on another VLAN or SSID might legitimately have different values, so “different from a peer” is evidence only when the comparison group is valid.
Performance evidence
Optimization requires a metric tied to the user's requirement
A file-transfer workload may care about throughput. Interactive remote work may care more about latency and loss. Voice/video can be sensitive to jitter and loss even when headline bandwidth is high. Therefore, “make it faster” is not yet a measurable requirement.
★ Routing Practice • Unit 1 Practice Test: Managing My Connections
A five-minute warm-up for AP Networking Unit 1 Practice Test: Managing My Connections
Tomorrow’s opening question can pick up where this page leaves off: ask students to explain the idea in their own words and apply it to a real network. The 300 Bell Ringers give you short questions and teacher answers you can use without preparing a new starter each morning.
Establish a baseline, isolate the path, change one justified variable, and repeat the same measurement. A local wired-versus-wireless comparison can separate RF/access-path limits from upstream limits. Idle-versus-loaded latency can expose queue buildup. A negotiated Ethernet rate can reveal a local ceiling before an Internet speed test is interpreted.
Security evidence
Connectivity success can coexist with unnecessary exposure
A laptop may reach every required service while file sharing is enabled on an untrusted network, the host firewall is disabled, software is unsupported, and the user has unnecessary administrator privilege. Successful connectivity proves none of those security conditions are acceptable.
Applied Exam Practice • 120 Missions
Let students try AP Networking Unit 1 Practice Test: Managing My Connections for themselves
Reading the explanation is a start. In the browser simulator, students work through a broken network, choose what to test and see whether their fix worked. It gives them another chance to use what they learned about AP Networking Unit 1 Practice Test: Managing My Connections.
Topic 1.3 asks what needs protection and why. Topic 1.4 chooses the smallest effective control. A strong security answer identifies the threat path, applies a narrow mechanism, proves required use still succeeds, and proves the prohibited behavior remains denied.
Free digital flashcards
24 Unit 1 evidence-reasoning flashcards
These cards mix troubleshooting, performance, security needs, control selection, verification, and distractor analysis so the review behaves more like an unfamiliar scenario than a vocabulary list.
Routing Exam Practice • Ap Networking Unit 1 Practice Test
Check whether AP Networking Unit 1 Practice Test: Managing My Connections has really stuck
Once students have worked through this topic, give them questions mixed in with the rest of the course. The Exam Prep Vault includes practice exams, multiple-choice questions and artifact labs so they cannot rely on a chapter heading to tell them what to do.
Now explain which evidence makes this answer stronger than an alternative.
0 seen•24 cards
Second-pass review
Convert every missed multiple-choice question into open response
Hide the choices and write three things: the strongest observation, the next command/inspection/test, and the result that would support or weaken your leading explanation. This removes vocabulary cues and exposes whether you actually understand the dependency.
Premium Exam-Reasoning Feedback
Spend less time marking explanations about AP Networking Unit 1 Practice Test: Managing My Connections
When students explain their answer, it takes more than a right-or-wrong check to see what they understand. The Grading Copilot helps you review how they used the clues, where their explanation falls short and what feedback to give next. You make the final grading decision.
If your answer says “check the network,” make it narrower. Check the active interface, address/prefix, gateway, configured resolver, local versus remote reachability, negotiated link, RF evidence, account state, update version, firewall scope, or restore capability—whichever the scenario makes relevant.
NEW • COMPLETE 180-DAY TEACHER CURRICULUM
Teach AP Networking Unit 1 Practice Test: Managing My Connections as part of a planned school year
This page gives you one topic. The 180-Day Teacher Curriculum puts it into a full course plan, with daily teaching notes, student activities and checks for understanding. Use it when you need to know what comes before this lesson and what to teach next.
A high-quality explanation does not merely name the right technology. It shows why the evidence places the failure or risk at a particular boundary. It then chooses the next test or control that changes the least while revealing the most.
For troubleshooting, verify the original symptom and adjacent dependencies after repair. For performance, repeat the relevant metric under comparable conditions. For security, verify both authorized and prohibited behavior. That final verification step is what turns a plausible answer into a demonstrated result.