Keepalive connections in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the purpose of keepalive connections in nginx?

Choose the best explanation for why nginx uses keepalive connections.

A To close connections immediately after each request to save memory.

B To encrypt all connections automatically without extra configuration.

C To reuse TCP connections for multiple requests, reducing latency and CPU usage.

D To limit the number of simultaneous connections to a fixed number.

💡 Hint

Think about how reusing connections affects speed and resource use.

Keepalive connections allow nginx to reuse the same TCP connection for multiple HTTP requests, which reduces the overhead of opening new connections and improves performance.

❓ Configuration

intermediate

Identify the correct nginx directive to enable keepalive connections to an upstream server

Which configuration snippet correctly enables keepalive connections for upstream servers in nginx?

Nginx

upstream backend {
    server backend1.example.com;
    server backend2.example.com;
    # Which line enables keepalive?
}

A keepalive 32;

B keepalive_timeout 32;

C keepalive_disable off;

D keepalive_requests 32;

💡 Hint

Look for the directive that sets the number of idle keepalive connections.

The keepalive directive inside an upstream block sets how many idle keepalive connections nginx keeps open to upstream servers.

💻 Command Output

advanced

What is the output of this nginx status command regarding keepalive connections?

Given the following snippet from nginx_status output, what does the Keep-Alive field represent?

Nginx

Active connections: 291 
server accepts handled requests
 166309 166309 310704 
Reading: 12 Writing: 14 Waiting: 265
Keep-Alive: 150

A The total number of keepalive connections closed since server start.

B The number of currently open keepalive connections waiting for requests.

C The maximum allowed keepalive connections configured in nginx.

D The number of keepalive connections rejected due to timeout.

💡 Hint

Focus on what 'Waiting' and 'Keep-Alive' mean in nginx status.

The 'Keep-Alive' field shows how many connections are currently kept open and idle, ready to accept new requests without reopening TCP connections.

❓ Troubleshoot

advanced

Why might nginx close keepalive connections prematurely?

After enabling keepalive connections, nginx closes them too soon. Which configuration is most likely causing this?

A keepalive_timeout 5s;

B keepalive 100;

C client_max_body_size 1m;

D proxy_buffering off;

💡 Hint

Consider which setting controls how long idle connections stay open.

The keepalive_timeout directive sets how long nginx keeps idle connections open. A low value like 5 seconds causes early closing.

🔀 Workflow

expert

Order the steps to enable and verify keepalive connections in nginx

Put these steps in the correct order to enable and confirm keepalive connections work in nginx.

A 1,2,4,3

B 4,1,2,3

C 2,1,4,3

D 1,4,2,3

💡 Hint

Think about configuration first, then client setup, then reload, then verification.

First configure nginx upstream with keepalive, then ensure clients send keepalive headers, reload nginx to apply changes, and finally verify with status.

Practice

1. What is the main benefit of using keepalive connections in nginx?

easy

A. They disable caching on the server.

B. They close connections immediately after each request.

C. They increase the number of open connections indefinitely.

D. They reuse the same connection for multiple requests, improving speed.

Solution

1. Step 1: Understand what keepalive connections do

   Keepalive connections allow the same connection to be reused for multiple requests instead of opening a new one each time.

2. Step 2: Identify the benefit of reusing connections

   Reusing connections reduces the time and resources needed to establish new connections, thus improving speed and reducing server load.

3. Final Answer:

   They reuse the same connection for multiple requests, improving speed. -> Option D

4. Quick Check:

   Keepalive = reuse connection for speed [OK]

Hint: Keepalive means reuse connection to speed up requests [OK]

Common Mistakes:

• Thinking keepalive closes connections immediately
• Believing keepalive increases open connections endlessly
• Confusing keepalive with caching

2. Which of the following is the correct syntax to set the keepalive timeout to 30 seconds in nginx?

easy

A. keepalive_timeout 30s

B. keepalive_timeout 30;

C. keepalive_timeout: 30s;

D. keepalive_timeout = 30;

Solution

1. Step 1: Recall nginx directive syntax

   Nginx directives use the format: directive_name value; without equal signs or colons.

2. Step 2: Check the correct value format for time

   Timeout values in nginx can be specified as numbers (seconds) without units or with units like 's'. Both are accepted, but the common practice is just a number for seconds.

3. Final Answer:

   keepalive_timeout 30; -> Option B

4. Quick Check:

   Directive syntax = name value; no '=' or ':' [OK]

Hint: Nginx directives use 'name value;' syntax without '=' [OK]

Common Mistakes:

• Using '=' sign in directive
• Adding colon ':' after directive name
• Adding units like 's' unnecessarily

3. Given this nginx configuration snippet:

keepalive_timeout 10;
keepalive_requests 100;

What happens after 100 requests on the same keepalive connection?

medium

A. The connection is closed and a new one is opened for the next request.

B. The connection stays open indefinitely.

C. The server resets the timeout to 10 seconds again.

D. The connection is closed immediately after the first request.

Solution

1. Step 1: Understand keepalive_requests directive

   This directive limits how many requests can be sent over one keepalive connection before it closes.

2. Step 2: Apply the limit of 100 requests

   After 100 requests, nginx closes the connection and opens a new one for the next request to avoid stale connections.

3. Final Answer:

   The connection is closed and a new one is opened for the next request. -> Option A

4. Quick Check:

   keepalive_requests = max requests per connection [OK]

Hint: keepalive_requests limits requests per connection [OK]

Common Mistakes:

• Thinking connection stays open forever
• Confusing timeout with request count
• Assuming connection closes after first request

4. You set keepalive_timeout 20; but clients report connections close too quickly. Which is the likely mistake?

medium

A. The keepalive_requests is set to 1, closing after one request.

B. The timeout value is too low for client needs.

C. You forgot to reload nginx after changing config.

D. The server is running an old nginx version without keepalive support.

Solution

1. Step 1: Check common reasons for config changes not applying

   If nginx is not reloaded or restarted after config changes, old settings remain active.

2. Step 2: Confirm reload necessity

   After changing keepalive_timeout, nginx must be reloaded with nginx -s reload or restarted to apply changes.

3. Final Answer:

   You forgot to reload nginx after changing config. -> Option C

4. Quick Check:

   Config changes need reload to apply [OK]

Hint: Reload nginx after config changes to apply them [OK]

Common Mistakes:

• Assuming timeout value alone fixes issue
• Ignoring need to reload nginx
• Blaming nginx version without checking

5. You want to optimize nginx for many short requests by keeping connections alive but closing them after 15 seconds or 50 requests, whichever comes first. Which configuration is correct?

hard

A. keepalive_timeout 15;\nkeepalive_requests 50;

B. keepalive_timeout 50;\nkeepalive_requests 15;

C. keepalive_timeout 15s;\nkeepalive_requests 50s;

D. keepalive_timeout 15s;\nkeepalive_requests 50; keepalive_disable none;

Solution

1. Step 1: Set keepalive_timeout to 15 seconds

   This controls how long a connection stays open waiting for new requests.

2. Step 2: Set keepalive_requests to 50

   This limits the number of requests per connection before closing it.

3. Step 3: Verify correct syntax and values

   keepalive_timeout 15;\nkeepalive_requests 50; uses correct syntax and values matching the requirement: 15 seconds timeout and 50 requests limit.

4. Final Answer:

   keepalive_timeout 15;\nkeepalive_requests 50; -> Option A

5. Quick Check:

   Timeout 15 + Requests 50 = correct config [OK]

Hint: Timeout sets seconds, requests sets max requests per connection [OK]

Common Mistakes:

• Swapping timeout and requests values
• Adding units to keepalive_requests
• Using invalid directives like keepalive_disable