The answer is to change the nsswitch.conf line to 'hosts: dns files'. This is correct because the original order 'hosts: files dns' forces the resolver to scan every entry in a large /etc/hosts file before attempting a DNS query, creating a bottleneck that causes slow name resolution. By reversing the order to 'hosts: dns files', the system queries DNS first—which is typically much faster for most lookups—and only falls back to the local file if the DNS query fails, directly addressing the performance issue without removing data or adding services. On the LPIC-2 exam, this scenario tests your understanding of the Name Service Switch (NSS) configuration and its impact on resolution speed; a common trap is assuming that adding more entries to /etc/hosts always speeds things up, when in fact it can slow the process if checked first. A useful memory tip: think "DNS first for speed, files last for fallback"—or simply remember that the order in nsswitch.conf is the order the resolver follows, so put the fastest source first.
LPIC-2 Network Client Management Practice Question
This LPIC-2 practice question tests your understanding of network client management. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A Linux client is experiencing slow name resolution. The /etc/nsswitch.conf file has the line 'hosts: files dns'. The /etc/hosts file contains many entries. What is the most effective way to improve resolution speed?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Change the nsswitch.conf line to 'hosts: dns files'
Option B is correct because the current order 'hosts: files dns' causes the resolver to check the entire /etc/hosts file first for every query, which is slow when the file contains many entries. Reversing the order to 'hosts: dns files' makes the resolver query DNS first, which is typically faster for most lookups, and only falls back to the local file if DNS fails. This directly addresses the bottleneck without requiring additional services or data removal.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Increase the DNS timeout in /etc/resolv.conf
Why it's wrong here
Increasing timeout would make resolution slower, not faster.
✓
Change the nsswitch.conf line to 'hosts: dns files'
Why this is correct
Checking DNS first avoids reading the large hosts file for most queries, improving resolution speed for external names.
Related concept
Read the scenario before looking for a memorised answer.
✗
Install and configure nscd (Name Service Cache Daemon)
Why it's wrong here
nscd caches results but initial resolution may still be slow due to the hosts file check order.
✗
Remove all entries from /etc/hosts except localhost
Why it's wrong here
This may break internal resolution for hosts that rely on the hosts file.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume removing entries from /etc/hosts or adding a caching daemon will fix the speed issue, when the real problem is the lookup order in nsswitch.conf, which directly controls whether the resolver checks a potentially large local file before querying DNS.
Detailed technical explanation
How to think about this question
The Name Service Switch (NSS) configuration in /etc/nsswitch.conf controls the order of lookup sources via the glibc resolver. When 'files' is first, the resolver reads the entire /etc/hosts file sequentially, which can be slow with many entries due to linear scanning. By placing 'dns' first, the resolver sends a DNS query (typically using UDP to port 53) and only reads /etc/hosts if the query fails or returns NXDOMAIN, leveraging the efficiency of DNS caching and shorter response times for common lookups.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
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.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the LPIC-2 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Network Client Management — This question tests Network Client Management — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Change the nsswitch.conf line to 'hosts: dns files' — Option B is correct because the current order 'hosts: files dns' causes the resolver to check the entire /etc/hosts file first for every query, which is slow when the file contains many entries. Reversing the order to 'hosts: dns files' makes the resolver query DNS first, which is typically faster for most lookups, and only falls back to the local file if DNS fails. This directly addresses the bottleneck without requiring additional services or data removal.
What should I do if I get this LPIC-2 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This LPIC-2 practice question is part of Courseiva's free LPI 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 LPIC-2 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.