Networking questions on CompTIA A+ are not trying to turn you into a network engineer. They are testing whether you can look at a broken connection, narrow the scope, and choose the best next step without immediately blaming “the network” like a haunted fog machine.
Use these A+ networking troubleshooting practice questions as a focused drill for common help desk scenarios: no internet, DNS problems, bad Wi-Fi, APIPA addresses, VPN issues, printer connectivity, shared folders, and basic command-line checks. Read the scenario, pick the best answer, then spend more time on the explanation than the letter.
If you are early in your A+ prep, pair this with a CompTIA A+ study plan. If you are already doing full exams, use this after a broader A+ practice test to patch the networking holes.
Quick framework for A+ networking questions
Before you choose an answer, ask three boring questions. Boring is good. Boring fixes tickets.
- What is the scope? One user, one device, one office, one app, or everyone?
- What changed? New dock, new Wi-Fi password, laptop update, switch move, VPN client update, printer replacement, or DHCP change?
- Where does it fail? Local link, IP address, DNS, gateway, firewall/VPN, application, or permissions?
A+ questions often hide the answer in scope. If one laptop cannot connect but every other laptop works, replacing the router is probably not your first move. If everyone on one switch lost network access, stop reinstalling browser extensions and look at the physical/network layer.
A+ networking troubleshooting practice questions
1. Laptop shows a 169.254 address
A user says their laptop is connected by Ethernet but cannot access the internet or internal sites. ipconfig shows an IPv4 address starting with 169.254. Other users are online. What should you check first?
A. Whether the laptop received a valid DHCP lease
B. Whether the user’s monitor supports HDMI 2.1
C. Whether the browser cache is full
D. Whether the public website is down
Answer: A. Whether the laptop received a valid DHCP lease.
A 169.254.x.x address is an APIPA address. It usually means the device did not receive an address from DHCP. Check the cable, switch port, adapter status, VLAN/port configuration, DHCP availability, and whether another device works on the same jack. Do not start with browser settings when the IP address is already telling you the network setup failed early.
2. Websites fail by name but work by IP
A desktop can ping 8.8.8.8, but browsing to normal websites by name fails. What is the most likely area to investigate?
A. DNS configuration
B. Monitor refresh rate
C. Printer toner level
D. CMOS battery
Answer: A. DNS configuration.
If IP connectivity works but names do not resolve, DNS moves to the top of the list. Check DNS server settings, whether the DNS server is reachable, VPN DNS behavior, and whether only one site or all names are failing. This is a classic exam pattern and a real support pattern.
3. One conference room has weak Wi-Fi
Users report that Wi-Fi is fine in most of the office, but calls drop in one conference room. What is the best first troubleshooting step?
A. Reinstall Windows on every laptop
B. Check signal strength, access point placement, interference, and client density in that room
C. Replace the company’s firewall immediately
D. Tell users to stop using video calls
Answer: B. Check signal strength, access point placement, interference, and client density in that room.
The scope is physical: one room. That points to RF coverage, interference, roaming, or overloaded access points before it points to a company-wide network problem. Look for distance from the AP, walls, metal, neighboring networks, Bluetooth-heavy rooms, and whether too many clients are pinned to one access point.
4. VPN connects, but internal file shares do not work
A remote user says the VPN client shows “connected,” but mapped drives and internal file shares fail. Email and public websites work. What should you check next?
A. VPN routes, DNS suffix/search behavior, and access permissions
B. The user’s laptop wallpaper
C. The office coffee machine
D. Whether the mouse is paired by Bluetooth
Answer: A. VPN routes, DNS suffix/search behavior, and access permissions.
“VPN connected” only tells you the tunnel came up. It does not prove the user can resolve internal names, route to the file server, or access the share. Check whether internal resources work by IP, whether split tunneling is expected, whether DNS changes after connection, and whether the user account has permission. For a longer workflow, use the VPN troubleshooting checklist.
5. Everyone on one switch loses network access
Several users sitting near each other report no network access at the same time. Users in the rest of the office are fine. What is the most likely first area to check?
A. The access switch, uplink, power, or cabling for that area
B. Every user’s browser history
C. The public DNS record for the company website
D. The CEO’s email signature
Answer: A. The access switch, uplink, power, or cabling for that area.
Again, scope gives it away. Multiple nearby users failing together points to shared infrastructure: switch, patch panel, uplink, PoE/power, or a local cabling issue. Do not troubleshoot each laptop as a separate mystery novel until you rule out the common point of failure.
6. Printer is online, but one subnet cannot print
A network printer works for users on the first floor, but users on the second floor cannot print. The printer web page opens from the first-floor subnet but not the second-floor subnet. What should you investigate?
A. Routing, firewall rules, printer IP/subnet settings, or ACLs between subnets
B. Whether the printer has enough paper
C. Whether every second-floor user has bad RAM
D. Whether the printer display brightness is too low
Answer: A. Routing, firewall rules, printer IP/subnet settings, or ACLs between subnets.
When one network segment can reach a device and another cannot, think routing and filtering. Check the printer’s IP, subnet mask, gateway, VLAN, firewall rules, and whether the second-floor subnet is allowed to reach printer services. If the issue were paper, everyone would have the same bad day.
7. User can reach websites but not a shared folder
A user can browse the internet and access email, but cannot open a mapped drive. Coworkers can open the same share. What should you check first?
A. The user’s permissions, mapped drive path, credentials, and name resolution to the file server
B. The ISP’s backbone routing
C. Replace all office switches
D. Disable DNS for the entire company
Answer: A. The user’s permissions, mapped drive path, credentials, and name resolution to the file server.
The network is not fully down. The problem is specific to one user and one resource. Check whether the user can reach the server, whether the path is correct, whether credentials are stale, whether the account is locked or removed from a group, and whether the drive mapping points to an old server. The network share troubleshooting checklist covers the full version.
8. New desk phone has no power
A newly installed VoIP phone does not power on. The same network jack works with a laptop. What should you verify early?
A. Whether the switch port provides PoE or whether the phone needs a power adapter
B. Whether the phone has the right ringtone
C. Whether the user’s Outlook signature is synced
D. Whether the browser default search engine changed
Answer: A. Whether the switch port provides PoE or whether the phone needs a power adapter.
Many VoIP phones use Power over Ethernet. A laptop working on the jack proves network connectivity, not PoE availability. Check switch port PoE settings, power budget, cabling, phone power requirements, and whether a power brick is needed.
9. Wi-Fi connects but says “No internet”
A laptop connects to the office Wi-Fi SSID, receives a normal private IP address, but cannot reach websites. Other users on the same Wi-Fi are online. What should you check next?
A. Gateway/DNS settings, captive portal, proxy/VPN client, and local firewall on that laptop
B. Replace every access point
C. Assume the entire internet is down
D. Change the user’s keyboard
Answer: A. Gateway/DNS settings, captive portal, proxy/VPN client, and local firewall on that laptop.
The laptop associated with Wi-Fi and received an IP address, so do not stop at “Wi-Fi bad.” Check whether it can ping the gateway, resolve names, reach IP addresses, pass a captive portal, or is being trapped by a stale VPN/proxy/security client. One device failing while others work usually means local configuration or policy.
10. After moving desks, Ethernet is dead
A user moved to a new desk. Wi-Fi works, but wired Ethernet shows disconnected. The same laptop and cable worked at the old desk. What should you check first?
A. Patch panel/switch port mapping and whether the wall jack is active
B. Reinstall the operating system
C. Replace the user’s keyboard
D. Reset the user’s email password
Answer: A. Patch panel/switch port mapping and whether the wall jack is active.
The recent change is the desk move. Check the physical path: wall jack, patch panel, switch port, cable, port status, and whether that jack is actually patched. This is exactly the kind of ticket where a ten-second cable path check beats an hour of software fiddling.
Review table: symptom to likely layer
| Symptom | Likely layer | First useful check |
|---|---|---|
169.254.x.x address | DHCP / local link | Cable, adapter, switch port, DHCP lease |
| IP works but names fail | DNS | DNS server, suffix, VPN DNS behavior |
| One room has weak Wi-Fi | Wireless/RF | Signal, interference, AP placement |
| Nearby users fail together | Shared infrastructure | Switch, uplink, power, patching |
| One user cannot reach one share | Permissions/app resource | Path, credentials, group access, name resolution |
| VPN connects but resources fail | Routes/DNS/permissions | Internal DNS, split tunnel, ACLs, share rights |
How to review missed networking questions
Do not write “networking is hard” in your notes and move on. Write down the exact pattern you missed.
Use this format:
- Symptom: What failed?
- Scope: Who or what was affected?
- Layer: Physical, IP, DNS, routing, firewall/VPN, application, or permissions?
- Clue ignored: What sentence in the question mattered?
- Better next step: What would you check before doing anything dramatic?
That last part matters. A+ questions love answers that are technically possible but operationally silly. Could a bad firewall break web browsing? Sure. Should you replace the firewall because one laptop has a proxy error? Please do not be that ticket update.
FAQ
Are networking questions a big part of CompTIA A+?
They matter because A+ is built around entry-level support work, and entry-level support sees network-ish problems constantly. You do not need CCNA depth, but you should be comfortable with IP addresses, DHCP, DNS, Wi-Fi basics, VPN symptoms, and basic commands.
What commands should I know for A+ networking troubleshooting?
Know what ipconfig, ping, tracert, nslookup, and basic Wi-Fi status checks are for. The exam is less about memorizing every switch and more about knowing which tool fits the symptom.
Should I take Network+ before A+?
Usually no. A+ is the better first step for many help desk candidates because it covers hardware, operating systems, troubleshooting, and support basics. Network+ makes more sense after you know you want deeper networking.
Next step
Networking gets easier when you stop memorizing random acronyms and start tracing the failure path. Review the A+ cost breakdown, pick one solid resource from the best A+ study guides, and drill a few real troubleshooting scenarios each week.
For hands-on command-line confidence, Shell Samurai is useful practice for getting comfortable in terminals and thinking in steps instead of vibes. For the exam, keep the goal simple: identify the symptom, narrow the scope, test the likely layer, and verify the fix.