200-901 Network Fundamentals Practice Question
A network automation engineer must ensure that a Python script running on a management workstation can resolve internal service names such as `inventory.corp.local` and `billing.corp.local`. The workstation currently resolves public names correctly but fails on the internal ones. The engineer inspects `/etc/resolv.conf` and sees a single `nameserver 8.8.8.8` entry. Which change most directly resolves the problem?
⚠ Common exam trap
The trap here is assuming any working nameserver can resolve any name, when a public resolver has no records for a private internal zone and will simply return an empty or negative answer.
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
✓
Add a `search corp.local` line and point the nameserver at the internal DNS server.
The workstation is pointing at a public recursive resolver that has no authority over the private corp.local zone, so internal names return no answer. Pointing the client at the corporate DNS server that hosts the zone, plus adding the search domain for short-name expansion, restores resolution for all internal services rather than a hand-picked few.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Add a `search corp.local` line and point the nameserver at the internal DNS server.
Why this is correct
Internal names like inventory.corp.local are only authoritative on the corporate DNS infrastructure, which a public resolver such as 8.8.8.8 cannot see. Replacing the nameserver with the internal resolver lets the workstation query the zone that actually holds those records, and the search domain allows short names to be expanded automatically.
- ✗
Increase the DNS timeout value so the public resolver has more time to answer.
Why it's wrong here
The public resolver is not slow; it simply has no knowledge of the internal zone and will return NXDOMAIN or a referral, not a delayed answer. Extending the timeout only makes failures take longer. The root cause is querying a resolver that is not authoritative for the corporate domain.
- ✗
Enable DNSSEC validation on the workstation's resolver library.
Why it's wrong here
DNSSEC validates the authenticity of signed responses but does not grant a public resolver visibility into a private internal zone. Enabling validation would not cause internal names to resolve and could even cause failures if the internal zone is unsigned. It addresses a security concern unrelated to the resolution failure.
- ✗
Add static entries for both service names to the local hosts file.
Why it's wrong here
Hard-coding entries would make those two specific names resolve, but it does not fix name resolution generally and will break as soon as IP addresses change or new services are added. It also bypasses the internal DNS zone entirely, leaving the automation script unable to resolve any other corporate name it may need.
Visual reference
Go deeper
Related to this question
About these practice questions
This 200-901 question is part of Courseiva's 975-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Cisco exam blueprint
This 200-901 practice question is part of Courseiva's free Cisco 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 200-901 exam.