hardmultiple choiceObjective-mapped

Exhibit

Client tests:
- ping 172.16.20.50 = success
- open http://172.16.20.50 = success
- open http://portal.corp.example = fail

Based on the exhibit, what is the strongest explanation for why clients can browse by IP address but not by hostname?

Question 1hardmultiple choice
Full question →

Based on the exhibit, what is the strongest explanation for why clients can browse by IP address but not by hostname?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Name resolution is failing even though IP connectivity works.

This is correct because the difference between IP success and hostname failure points to DNS.

B

Distractor review

The client has the wrong default gateway.

This is wrong because the client can already reach the server by IP.

C

Distractor review

The switch trunk native VLAN is wrong.

This is wrong because the symptom is specifically name-based failure, not a total path failure.

D

Distractor review

The server must run PPP before hostnames can work.

This is wrong because PPP is unrelated to DNS-based service access here.

Common exam trap

Common exam trap: answer the scenario, not the keyword

A frequent exam trap is assuming that if hostname resolution fails, the problem must be with routing or VLAN configurations such as the default gateway or switch trunk native VLAN. However, since clients can browse by IP address, these path elements are functioning correctly. Misattributing the failure to routing or VLAN issues wastes time and leads to incorrect answers. The key mistake is not recognizing that DNS operates at a higher layer and that name resolution failures are distinct from IP connectivity problems.

Technical deep dive

How to think about this question

DNS is a critical IP service that maps human-friendly hostnames to IP addresses, allowing users to access resources without memorizing numeric addresses. When a client attempts to browse a server by hostname, it sends a DNS query to a configured DNS server. If the DNS server responds correctly, the client receives the IP address and initiates communication. This process is fundamental in Cisco networking environments and is covered in the CCNA 200-301 exam under IP Services. When clients can browse by IP address but not by hostname, the network path is confirmed operational, indicating that routing, switching, and default gateway configurations are correct. The failure lies in the DNS resolution step. This means either the DNS server is unreachable, misconfigured, or the client has incorrect DNS settings. Cisco devices often use DHCP to provide DNS server information, so misconfigurations in DHCP or static DNS entries can cause this issue. A common exam trap is to confuse connectivity issues with DNS problems. For example, assuming the default gateway or VLAN trunking is at fault when IP connectivity works leads to incorrect conclusions. Practically, network engineers verify IP connectivity first, then isolate DNS issues by checking DNS server reachability and client DNS configurations. Understanding this separation is vital for troubleshooting and passing the CCNA exam.

KKey Concepts to Remember

  • DNS (Domain Name System) resolves hostnames to IP addresses, enabling clients to access network resources using human-readable names.
  • Successful IP connectivity with failed hostname access indicates a problem specifically in the DNS name resolution process, not in routing or switching.
  • Clients rely on configured DNS servers to translate hostnames; if DNS is misconfigured or unreachable, hostname-based access fails.
  • A correct default gateway allows IP packets to route properly, but it does not affect DNS resolution directly.
  • Switch trunk native VLAN mismatches cause VLAN tagging issues affecting connectivity, but they do not selectively block hostname resolution.
  • PPP (Point-to-Point Protocol) is unrelated to DNS or hostname resolution in typical LAN browsing scenarios.
  • Troubleshooting hostname resolution issues requires verifying DNS server settings, DNS service availability, and client DNS configuration.
  • Network path verification by IP address helps isolate whether connectivity or name resolution is the root cause of access problems.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Related practice questions

Related 200-301 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this 200-301 question test?

DNS (Domain Name System) resolves hostnames to IP addresses, enabling clients to access network resources using human-readable names.

What is the correct answer to this question?

The correct answer is: Name resolution is failing even though IP connectivity works. — The strongest explanation is a DNS failure or DNS configuration problem. In practical terms, successful browsing by IP address shows that the client can already reach the destination over the network path. When the same service fails only by hostname, the issue is much more likely in name resolution than in routing, switching, or raw connectivity. This is one of the most useful support patterns because it quickly separates path problems from naming problems.

What should I do if I get this 200-301 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.