Contexts (main, events, http, server, location) in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Identify the correct context for worker_connections

In which Nginx configuration context should the directive worker_connections be placed to properly set the maximum number of simultaneous connections per worker process?

A location

B http

C server

D events

💡 Hint

Think about where Nginx manages connection handling globally.

The worker_connections directive belongs in the events context because it controls the maximum number of connections each worker process can handle. It is not part of http, server, or location contexts.

💻 Command Output

intermediate

Output of nginx -T with misplaced location block

What error message will Nginx produce if a location block is placed directly inside the main context (outside http) and you run nginx -T to test the configuration?

Nginx

location /test {
    proxy_pass http://localhost:8080;
}

A nginx: configuration file /etc/nginx/nginx.conf test is successful

B nginx: [emerg] "location" directive is not allowed here in /etc/nginx/nginx.conf:2

C nginx: [warn] unknown directive "location" in /etc/nginx/nginx.conf:2

D nginx: [error] invalid parameter in location block in /etc/nginx/nginx.conf:2

💡 Hint

Consider which contexts allow location blocks.

The location directive is only valid inside the server context, which itself must be inside http. Placing it in the main context causes an emergency error on config test.

🔀 Workflow

advanced

Order of contexts for serving a request

Arrange the Nginx configuration contexts in the order they are processed when serving an HTTP request.

A 2,1,3,4,5

B 1,3,2,4,5

C 1,2,3,4,5

D 1,3,4,5,2

💡 Hint

Think about the global setup, connection handling, HTTP processing, and request routing.

The main context is the global config. events handles connection limits. http processes HTTP settings. server matches the domain/port. location matches the request URI.

❓ Troubleshoot

advanced

Why is proxy_pass ignored in main context?

You added the directive proxy_pass http://backend; directly inside the http context, but it has no effect on requests. Why?

A <code>proxy_pass</code> must be inside a <code>location</code> block, not directly in <code>http</code>

B <code>proxy_pass</code> is deprecated and ignored in all contexts

C <code>proxy_pass</code> only works inside <code>server</code> blocks, not <code>http</code>

D <code>proxy_pass</code> requires the <code>events</code> context to be enabled

💡 Hint

Where do you usually put routing rules?

The proxy_pass directive must be inside a location block to apply to specific request URIs. Placing it directly in http does nothing.

✅ Best Practice

expert

Best context for gzip compression directives

Where should you place gzip compression directives like gzip on; and gzip_types for best practice and efficient configuration?

A Inside the <code>http</code> context to apply globally to all servers

B Inside each <code>server</code> block to customize per domain

C Inside the <code>location</code> blocks to control compression per URI

D Inside the <code>events</code> context because it handles connections

💡 Hint

Compression usually applies to all HTTP responses unless you want exceptions.

Placing gzip directives in the http context enables compression globally for all servers and locations, which is efficient and easier to manage.