220-1101 Hardware and Network Troubleshooting Practice Question
A technician configures a server with a static IP address of 192.168.1.100, subnet mask 255.255.0.0, and default gateway 192.168.1.1. The server can access the internet and devices on the 192.168.1.0/24 network. However, it cannot reach a network printer at 192.168.2.50. The printer is on the same physical LAN but in a different subnet (192.168.2.0/24). The router's interface for the 192.168.2.0 network is 192.168.1.2, and routing is properly configured. Other devices on the 192.168.1.0/24 network (with correct subnet mask 255.255.255.0) can reach the printer successfully. Which of the following is the MOST likely cause of the server's inability to reach the printer?
⚠ Common exam trap
Test-takers frequently assume the server's static IP and gateway are correct because the server can reach the internet and local devices, overlooking how an overly broad subnet mask causes the server to bypass the gateway for destinations it incorrectly considers local.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
B. The server's subnet mask is too broad, causing it to try to reach the printer directly rather than through the gateway
The server's subnet mask of 255.255.0.0 creates a /16 network (192.168.0.0/16), which includes both 192.168.1.0/24 and 192.168.2.0/24. Because the server believes the printer is on the same local subnet, it sends ARP requests for 192.168.2.50 directly instead of forwarding traffic to the default gateway. Since the printer is on a different physical subnet (despite being on the same LAN), the ARP request never reaches it, and the connection fails.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A. The server's default gateway should be set to 192.168.1.2 instead of 192.168.1.1
Why it's wrong here
The default gateway is already 192.168.1.1, which is the router's IP on the same subnet (192.168.1.0/24). The router's other interface 192.168.1.2 is for a different subnet. Changing the gateway to 192.168.1.2 would not fix the issue because the core problem is the subnet mask causing the server to not use the gateway at all.
When this WOULD be correct
In a scenario where the router's interface for the 192.168.2.0/24 network is 192.168.1.2 and the server's default gateway is incorrectly set to 192.168.1.1, but the server's subnet mask is correct (e.g., /24), then the server would send traffic to the gateway, but the gateway might not route it properly if the gateway IP is wrong. However, this would only be correct if the router's interface for the server's subnet is actually 192.168.1.2, which is not the case here.
- ✓
B. The server's subnet mask is too broad, causing it to try to reach the printer directly rather than through the gateway
Why this is correct
With a subnet mask of 255.255.0.0, the server believes the entire 192.168.0.0/16 range is local. It will attempt to ARP for 192.168.2.50 instead of forwarding to the gateway. Changing the mask to 255.255.255.0 resolves the issue.
- ✗
C. The router is blocking traffic from the server's IP address to the 192.168.2.0 network
Why it's wrong here
The router is not blocking traffic; other devices reach the printer successfully. The issue is that the server never sends traffic to the router because it incorrectly considers the destination local.
When this WOULD be correct
This option would be correct in a scenario where a router's ACL or firewall rule explicitly denies traffic from the server's IP address to the 192.168.2.0 network, while other devices are allowed. For example, if a security policy blocks the server's IP but permits others, and routing is otherwise functional.
- ✗
D. The printer's default gateway is misconfigured
Why it's wrong here
The printer's default gateway is irrelevant for this scenario because the problem is at the server side. The server cannot even initiate the communication due to its own incorrect subnet mask.
When this WOULD be correct
A server can reach local devices but not the internet, and other devices on the same subnet can reach the internet. The server's default gateway is correct, but the printer's default gateway is set to an incorrect IP, preventing return traffic from reaching the server.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 220-1101 exam frequently reuses these exact scenarios with slightly different constraints.
✓B. The server's subnet mask is too broad, causing it to try to reach the printer directly rather than through the gatewayCorrect answer▾
Why this is correct
With a subnet mask of 255.255.0.0, the server believes the entire 192.168.0.0/16 range is local. It will attempt to ARP for 192.168.2.50 instead of forwarding to the gateway. Changing the mask to 255.255.255.0 resolves the issue.
✗A. The server's default gateway should be set to 192.168.1.2 instead of 192.168.1.1Wrong answer — click to see why▾
Why this is wrong here
The server's default gateway 192.168.1.1 is the router's interface for the 192.168.1.0/24 network, which is correct for reaching other subnets. The issue is not the gateway IP but the subnet mask causing the server to think the printer is local.
★ When this WOULD be the correct answer
In a scenario where the router's interface for the 192.168.2.0/24 network is 192.168.1.2 and the server's default gateway is incorrectly set to 192.168.1.1, but the server's subnet mask is correct (e.g., /24), then the server would send traffic to the gateway, but the gateway might not route it properly if the gateway IP is wrong. However, this would only be correct if the router's interface for the server's subnet is actually 192.168.1.2, which is not the case here.
Why candidates choose this
Candidates may think that because the printer is on a different subnet, the default gateway must be the router interface for that subnet, overlooking that the server's subnet mask is the root cause.
✗C. The router is blocking traffic from the server's IP address to the 192.168.2.0 networkWrong answer — click to see why▾
Why this is wrong here
The router is properly configured and routing is working for other devices, so it is not blocking traffic from the server's IP specifically. The issue is that the server's broad subnet mask causes it to attempt direct communication with the printer instead of using the gateway.
★ When this WOULD be the correct answer
This option would be correct in a scenario where a router's ACL or firewall rule explicitly denies traffic from the server's IP address to the 192.168.2.0 network, while other devices are allowed. For example, if a security policy blocks the server's IP but permits others, and routing is otherwise functional.
Why candidates choose this
Candidates may assume that if a device cannot reach another subnet, the router must be blocking it, especially when other devices can reach it. They overlook the subnet mask issue and focus on the router as the common point of failure.
✗D. The printer's default gateway is misconfiguredWrong answer — click to see why▾
Why this is wrong here
The printer's default gateway is irrelevant because the server initiates the connection; the printer only needs to reply, and since other devices on the same subnet as the server can reach the printer, the printer's gateway is correctly configured.
★ When this WOULD be the correct answer
A server can reach local devices but not the internet, and other devices on the same subnet can reach the internet. The server's default gateway is correct, but the printer's default gateway is set to an incorrect IP, preventing return traffic from reaching the server.
Why candidates choose this
Candidates may think that both endpoints need correct gateways for communication, but in this scenario the printer's gateway is not the issue because the server's subnet mask causes it to send traffic directly.
Analysis generated from the official 220-1101blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Visual reference
Quick reference
IPv4 Address Class Summary
| Class | First Octet Range | Default Mask | Networks | Hosts per Network |
|---|---|---|---|---|
| A | 1–126 | /8 (255.0.0.0) | 126 | 16,777,214 |
| B | 128–191 | /16 (255.255.0.0) | 16,384 | 65,534 |
| C | 192–223 | /24 (255.255.255.0) | 2,097,152 | 254 |
| D | 224–239 | N/A | Multicast groups | — |
| E | 240–255 | N/A | Reserved / experimental | — |
127.x.x.x is reserved for loopback. Modern networks use CIDR (classless) rather than classful addressing.
Go deeper
Related to this question
About these practice questions
One of 896 original 220-1101 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 220-1101 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 220-1101 exam.