Question 1hardmultiple choice
Full question →hardmultiple choiceObjective-mapped
Exhibit
User tests: - ping 192.168.200.50 = success - HTTP to 192.168.200.50 = success - HTTP to app.internal.lab = fail
Based on the exhibit, what is the strongest next troubleshooting focus?
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
DNS or name-resolution configuration for the host or service
This is correct because the difference between IP success and hostname failure points directly to DNS-related troubleshooting.
B
Distractor review
STP root bridge priority on the access switch
This is wrong because the network path to the IP address already works.
C
Distractor review
PPP encapsulation on the WAN edge
This is wrong because the symptom is specific to hostname access, not WAN data-link negotiation.
D
Distractor review
EtherChannel member consistency on the distribution switches
This is wrong because the client already reaches the service by IP.
Common exam trap
Common exam trap: answer the scenario, not the keyword
A frequent exam trap is to select options related to Layer 2 or WAN link issues, such as STP root bridge priority or PPP encapsulation, because candidates associate connectivity problems with these technologies. However, the question states that IP connectivity works, which means switching and routing are operational. Choosing these options wastes time and misses the core issue, which is DNS or name-resolution failure. Candidates must carefully distinguish between IP connectivity and hostname resolution failures to avoid this common pitfall.
Technical deep dive
How to think about this question
DNS (Domain Name System) is a critical IP service that translates human-readable hostnames into IP addresses, enabling users and applications to access network resources by name rather than numeric IPs. In Cisco networking and CCNA contexts, DNS resolution is fundamental for connectivity beyond basic IP routing, especially when hosts or services are referenced by hostname. When a device can ping an IP address but not a hostname, it indicates that Layer 3 routing and switching are functioning, but the name resolution process is failing. Troubleshooting DNS involves verifying the DNS server configuration on the host or router, ensuring the DNS server is reachable, and confirming that the DNS records exist and are correct. The decision process in this question hinges on the fact that IP connectivity is successful, so the next logical step is to isolate the failure to DNS or name-resolution configuration. This approach aligns with CCNA best practices for layered troubleshooting, focusing on the service layer after confirming network layer functionality. A common exam trap is to misattribute hostname resolution failures to lower-layer issues such as spanning-tree protocol (STP) or WAN encapsulation problems. However, since the IP address is reachable, these options are irrelevant here. Practically, this means that network engineers should avoid wasting time on Layer 2 or WAN link troubleshooting when the symptom is strictly related to hostname resolution, focusing instead on DNS configurations and server availability.
KKey Concepts to Remember
- DNS translates hostnames into IP addresses, enabling devices to access network resources by name rather than numeric IPs.
- Successful IP connectivity with hostname resolution failure indicates a DNS or name-resolution configuration issue rather than routing or switching problems.
- Cisco devices use configured DNS servers to resolve hostnames, and misconfigured or unreachable DNS servers cause hostname access failures.
- Spanning Tree Protocol (STP) affects Layer 2 path selection but does not impact IP connectivity if pinging an IP address succeeds.
- PPP encapsulation issues affect WAN link establishment but do not cause hostname resolution failures when IP connectivity is confirmed.
- EtherChannel member inconsistencies disrupt link aggregation but do not prevent IP-level connectivity if pinging the IP address works.
- Troubleshooting layered network issues requires isolating the failure domain by verifying connectivity at each OSI layer sequentially.
- Name resolution problems are best diagnosed by checking DNS server settings, DNS client configuration, and DNS record correctness.
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.
CCNA subnetting practice questions
Practise IPv4 subnetting, CIDR, masks, host ranges and subnet selection.
CCNA OSPF practice questions
Practise OSPF neighbours, router IDs, metrics, areas and routing-table interpretation.
CCNA VLAN practice questions
Practise VLANs, access ports, trunks, allowed VLANs and switching scenarios.
CCNA STP practice questions
Practise spanning tree, root bridge election, port roles and STP troubleshooting.
CCNA EtherChannel practice questions
Practise LACP, PAgP, port-channel behaviour and bundle requirements.
CCNA ACL practice questions
Practise standard and extended ACLs, permit/deny logic and traffic filtering.
CCNA NAT practice questions
Practise static NAT, dynamic NAT, PAT and inside/outside address translation.
CCNA DHCP practice questions
Practise DHCP scopes, relay, leases and troubleshooting.
CCNA show ip route practice questions
Practise routing-table output, longest-prefix match, AD and route selection.
CCNA show interfaces trunk practice questions
Practise trunk verification and VLAN forwarding across switches.
CCNA wireless security practice questions
Practise WLAN security, authentication and wireless architecture concepts.
CCNA IPv6 practice questions
Practise IPv6 addressing, routes, neighbour discovery and common IPv6 exam traps.
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.
Question 1
A router learns the same prefix from both OSPF and EIGRP. Which route is installed by default?
Question 2
A router shows this output: R1#show ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 10.1.1.2 1 FULL/DR 00:00:34 192.168.12.2 GigabitEthernet0/0 10.1.1.3 1 2WAY/DROTHER 00:00:39 192.168.12.3 GigabitEthernet0/0 Which statement is correct?
Question 3
What is the OSPF metric called?
Question 4
A non-root switch has two uplinks toward the root bridge. One path has a lower total STP cost than the other. What role will the lower-cost uplink have?
Question 5
A router interface applies this ACL inbound: 10 deny tcp any any eq 80 20 permit ip any any A user reports that web browsing to a server by IP address fails, but ping works. Which statement best explains the behavior?
Question 6
A router learns route 198.51.100.0/24 from OSPF with AD 110 and also has a static route to the same prefix configured with AD 150. Which route is installed?
FAQ
Questions learners often ask
What does this 200-301 question test?
DNS translates hostnames into IP addresses, enabling devices to access network resources by name rather than numeric IPs.
What is the correct answer to this question?
The correct answer is: DNS or name-resolution configuration for the host or service — The strongest next troubleshooting focus is DNS. In practical terms, the host can already reach the destination by IP address, which means switching, routing, and general Layer 3 connectivity are working for that path. The failure occurs only when the hostname is used, so the most likely remaining fault domain is name resolution rather than the data path itself. This is a classic 'what do you check next' support question and very close to real-world helpdesk and network triage logic.
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.