The correct answer is to enable TCP keepalive and adjust kernel parameters for faster reuse, as this directly addresses the bottleneck caused by excessive TIME_WAIT connections on an Apache server. When Apache handles many short-lived connections, sockets linger in the TIME_WAIT state to ensure delayed packets are not misinterpreted, which can exhaust available ports and slow response times. By tuning kernel parameters like `net.ipv4.tcp_tw_reuse` (or the deprecated `tcp_tw_recycle` on older kernels), the system safely reuses these sockets for new connections, while TCP keepalive helps detect dead peers and free resources sooner. On the LPIC-1 exam, this scenario tests your understanding of TCP state management and kernel tuning under the Networking and System Administration objectives—a common trap is confusing TIME_WAIT with CLOSE_WAIT, which requires application-level fixes. Remember the mnemonic: "TIME_WAIT ties up ports; reuse and keepalive shorten the wait."
LPIC-1 Essential System Services and Networking Practice Question
This LPIC-1 practice question tests your understanding of essential system services and networking. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 web server running Apache on Linux is experiencing slow response times. The administrator runs 'netstat -tuln' and sees many connections in TIME_WAIT state. Which of the following is the best course of action to improve performance?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable TCP keepalive and adjust kernel parameters for faster reuse.
Option C is correct because TIME_WAIT connections indicate that the server is waiting for lingering packets before fully closing TCP sockets. Enabling TCP keepalive and adjusting kernel parameters like net.ipv4.tcp_tw_reuse (or net.ipv4.tcp_tw_recycle in older kernels) allows the kernel to reuse sockets in TIME_WAIT state for new connections, reducing resource exhaustion and improving performance under high connection rates.
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 KeepAliveTimeout directive.
Why it's wrong here
Longer timeout means connections stay open longer, but does not reduce TIME_WAIT.
✗
Disable the KeepAlive directive.
Why it's wrong here
Disabling keepalive creates more connections, increasing TIME_WAIT.
✓
Enable TCP keepalive and adjust kernel parameters for faster reuse.
Why this is correct
Adjusting tcp_tw_reuse and tcp_tw_recycle can reduce TIME_WAIT.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Increase the MaxKeepAliveRequests directive.
Why it's wrong here
This might increase TIME_WAIT if requests are completed quickly.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse Apache's KeepAlive directives (HTTP-level persistent connections) with TCP-level keepalive and TIME_WAIT management, leading them to incorrectly choose options that adjust HTTP keep-alive settings instead of addressing the TCP socket state.
Detailed technical explanation
How to think about this question
TIME_WAIT is a TCP state that lasts 2*MSL (typically 60 seconds) to ensure delayed packets are not misinterpreted. On busy web servers, this can exhaust the ephemeral port range. Kernel parameters like net.ipv4.tcp_tw_reuse (safe for client-side) or net.ipv4.tcp_tw_recycle (deprecated due to NAT issues) allow the kernel to bypass the TIME_WAIT delay. In modern Linux (4.12+), tcp_tw_recycle is removed, and tcp_tw_reuse is only effective for outbound connections; for inbound servers, increasing the port range or using SO_REUSEADDR on the socket is more appropriate.
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-1 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.
Essential System Services and Networking — This question tests Essential System Services and Networking — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Enable TCP keepalive and adjust kernel parameters for faster reuse. — Option C is correct because TIME_WAIT connections indicate that the server is waiting for lingering packets before fully closing TCP sockets. Enabling TCP keepalive and adjusting kernel parameters like net.ipv4.tcp_tw_reuse (or net.ipv4.tcp_tw_recycle in older kernels) allows the kernel to reuse sockets in TIME_WAIT state for new connections, reducing resource exhaustion and improving performance under high connection rates.
What should I do if I get this LPIC-1 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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-1 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-1 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.