hardmultiple choiceObjective-mapped

Exhibit

User test results:
- ping 10.20.30.40 = success
- open http://10.20.30.40 = success
- open http://intranet.corp.local = fail

Based on the exhibit, what is the strongest explanation for why users can reach an internal server by IP address but not by hostname?

Question 1hardmultiple choice
Full question →

Based on the exhibit, what is the strongest explanation for why users can reach an internal server 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 to the server works.

This is correct because the symptom points directly to a DNS-related problem.

B

Distractor review

The server must be in the wrong VLAN because IP works.

This is wrong because successful IP access already shows the host can reach the server.

C

Distractor review

The default gateway is missing on the client.

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

D

Distractor review

A GRE tunnel is required for hostname access.

This is wrong because hostname access does not require GRE tunneling.

Common exam trap

Common exam trap: answer the scenario, not the keyword

A common exam trap is to confuse IP connectivity problems with DNS resolution issues. Candidates often select options related to VLAN misconfigurations or missing default gateways because they assume network path problems cause hostname failures. However, if users can reach the server by IP address, Layer 3 routing and VLAN membership are correct. The trap is ignoring the DNS layer, which is responsible for translating hostnames. Misinterpreting this leads to incorrect troubleshooting steps and wrong exam answers.

Technical deep dive

How to think about this question

DNS (Domain Name System) is the core service that translates human-readable hostnames into IP addresses, enabling users to access resources by name rather than numeric IPs. In Cisco networking and CCNA contexts, DNS resolution is critical for network services and user convenience, especially when internal servers are accessed within an enterprise network. When users can reach a server by IP address but not by hostname, it indicates that the underlying Layer 3 routing and connectivity are intact, but the name resolution process is failing. The decision process to diagnose this scenario begins by confirming IP connectivity, which is successful here. Since IP access works, the problem lies in DNS configuration or availability. This could be due to incorrect DNS server settings on the client, missing DNS records for the server hostname, or DNS server unavailability. Cisco devices rely on proper DNS settings to resolve names, and troubleshooting involves verifying DNS server IPs, ensuring the DNS service is operational, and confirming that the server’s hostname is correctly registered. A common exam trap is to confuse IP connectivity issues with DNS problems. Candidates might incorrectly assume VLAN misconfigurations or missing gateways cause hostname resolution failures. However, since IP communication succeeds, these options are invalid. Practically, DNS failures manifest as inability to resolve names despite reachable IPs. Understanding this distinction helps avoid misdiagnosis and ensures focused troubleshooting on DNS rather than Layer 2 or Layer 3 connectivity issues.

KKey Concepts to Remember

  • DNS translates hostnames into IP addresses, enabling users to access network resources by name rather than numeric IPs.
  • Successful IP connectivity to a server confirms that Layer 3 routing and forwarding are functioning correctly.
  • Failure to reach a server by hostname despite IP access indicates a problem with DNS name resolution or DNS server configuration.
  • Cisco devices require correct DNS server IP addresses configured on clients to resolve hostnames properly.
  • DNS failures can result from missing DNS records, unreachable DNS servers, or incorrect DNS client settings.
  • IP connectivity issues such as VLAN misconfigurations or missing default gateways prevent access by both IP and hostname.
  • Troubleshooting hostname resolution problems should prioritize verifying DNS server availability and client DNS settings.
  • Exam questions testing hostname versus IP access often assess understanding of DNS role versus routing and VLAN configurations.

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 translates hostnames into IP addresses, enabling users to access network resources by name rather than numeric IPs.

What is the correct answer to this question?

The correct answer is: Name resolution is failing even though IP connectivity to the server works. — The strongest explanation is a DNS problem rather than a raw IP connectivity problem. In practical terms, successful access by IP address shows that Layer 3 reachability to the server exists. Failure only when using the hostname strongly suggests name resolution is missing, incorrect, or unavailable. This is a classic symptom-based troubleshooting question. The network path works, but the naming service does not.

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.