220-1101 Networking Practice Question
A user reports that they can browse the internet and access all network resources by IP address, but they cannot print to the network printer by its hostname. Other users can print using the hostname without issue. The technician pings the printer's IP address from the affected computer and gets a successful reply. Which of the following should the technician check next?
⚠ Common exam trap
Test-takers frequently assume a network connectivity issue (like a bad cable or firewall) when the symptom of working IP access but failing hostname access clearly isolates the problem to name resolution, not connectivity.
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
✓
The DNS server settings on the user's computer
The user can browse the internet and access resources by IP address but not by hostname, which points to a name resolution failure. Since other users can print to the network printer by hostname, the printer and DNS server are functioning correctly. The issue is isolated to the affected computer's DNS configuration, making checking the DNS server settings on the user's computer the next logical step.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The printer's firewall settings
Why it's wrong here
The printer's firewall settings control access to the printer's own services, such as firewall rules that might block ping or print jobs from certain hosts. However, the user's problem is that hostname resolution fails for all network resources, not just the printer. Even if the printer's firewall were blocking something, it wouldn't affect the client's DNS lookups or ability to browse other websites. Moreover, the user can ping the printer by IP, proving the printer is reachable at the network level, so the firewall isn't blocking ICMP either.
When this WOULD be correct
A technician should check the printer's firewall settings when a user cannot access the printer by IP address or hostname, and other users also cannot access it, indicating a network-level block rather than a name resolution problem.
- ✓
The DNS server settings on the user's computer
Why this is correct
The DNS server settings on the user's computer are the root cause because DNS translates human-friendly hostnames like 'www.example.com' into IP addresses. If the configured DNS server is unreachable, misconfigured, or set to an invalid IP, the client cannot resolve names, so browsing fails and the printer's name won't resolve. Yet IP-based operations like ping to the printer's IP address or direct IP browsing succeed, exactly matching the symptom. Correcting the DNS settings—such as pointing to a valid DNS server or fixing a manually entered wrong address—restores name resolution and full network access.
- ✗
The user's network cable
Why it's wrong here
A faulty network cable would break the physical layer link, preventing the computer from obtaining an IP address, pinging anything, or reaching the internet at all. Since the user can access the internet and ping the printer by IP address, the cable and network interface are demonstrably functional. The issue is not connectivity but the inability to translate names, which operates at the application layer and is unrelated to the physical cable. Thus the cable cannot be the cause.
When this WOULD be correct
A user cannot access any network resources (no internet, no network shares) and the link lights on the NIC are off. In that scenario, checking the network cable would be appropriate.
- ✗
The router's NAT configuration
Why it's wrong here
NAT (Network Address Translation) on the router translates private internal IP addresses to a public IP for outbound internet traffic. It has no role in resolving internal hostnames to IP addresses—that is strictly a DNS function. If NAT were misconfigured, the user would likely lose internet access entirely or fail to route outbound packets, but here internet access works and only name resolution fails. Also, NAT does not affect how a client resolves names on the local network, so it cannot explain the symptom of being unable to reach the printer by name while IP connectivity is intact.
When this WOULD be correct
A technician would check the router's NAT configuration when users on the internal network cannot access external resources (e.g., internet) by IP or hostname, but internal resources work fine. For example, if a user can't browse the web but can ping external IPs, NAT misconfiguration might be the cause.
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.
✓The DNS server settings on the user's computerCorrect answer▾
Why this is correct
The DNS server settings on the user's computer are the root cause because DNS translates human-friendly hostnames like 'www.example.com' into IP addresses. If the configured DNS server is unreachable, misconfigured, or set to an invalid IP, the client cannot resolve names, so browsing fails and the printer's name won't resolve. Yet IP-based operations like ping to the printer's IP address or direct IP browsing succeed, exactly matching the symptom. Correcting the DNS settings—such as pointing to a valid DNS server or fixing a manually entered wrong address—restores name resolution and full network access.
✗The printer's firewall settingsWrong answer — click to see why▾
Why this is wrong here
The printer's firewall settings would not cause a name resolution issue while IP-based access works. Since the user can ping the printer's IP successfully, the printer is reachable and its firewall is not blocking traffic.
★ When this WOULD be the correct answer
A technician should check the printer's firewall settings when a user cannot access the printer by IP address or hostname, and other users also cannot access it, indicating a network-level block rather than a name resolution problem.
Why candidates choose this
Candidates may think that a firewall could block printing traffic, but the symptom (works by IP, fails by hostname) points to DNS, not firewall. They might confuse hostname resolution with network access control.
✗The user's network cableWrong answer — click to see why▾
Why this is wrong here
The user can browse the internet and access network resources by IP, indicating the network cable is functional. The issue is name resolution, not physical connectivity.
★ When this WOULD be the correct answer
A user cannot access any network resources (no internet, no network shares) and the link lights on the NIC are off. In that scenario, checking the network cable would be appropriate.
Why candidates choose this
Candidates may assume any network issue is due to physical connectivity, overlooking that the problem is specific to hostname resolution, not general connectivity.
✗The router's NAT configurationWrong answer — click to see why▾
Why this is wrong here
The router's NAT configuration affects external address translation, not internal hostname resolution. Since the user can access network resources by IP but not by hostname, the issue is with DNS resolution, not NAT.
★ When this WOULD be the correct answer
A technician would check the router's NAT configuration when users on the internal network cannot access external resources (e.g., internet) by IP or hostname, but internal resources work fine. For example, if a user can't browse the web but can ping external IPs, NAT misconfiguration might be the cause.
Why candidates choose this
Candidates may confuse network address translation with DNS resolution, thinking that NAT could affect hostname-to-IP mapping, or they might assume that any network printing issue involves routing or translation problems.
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?”
Go deeper
Related to this question
About these practice questions
Courseiva writes every 220-1101 question from scratch — 896 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.