Main configuration file (nginx.conf) - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this nginx configuration test command?

You have an nginx configuration file with a syntax error. You run the command nginx -t to test the configuration. What output will you see?

Nginx

nginx: [emerg] unknown directive "serve_static" in /etc/nginx/nginx.conf:12
nginx: configuration file /etc/nginx/nginx.conf test failed

A nginx: configuration file /etc/nginx/nginx.conf syntax is ok\nnginx: configuration file /etc/nginx/nginx.conf test is successful

B nginx: [emerg] unknown directive "serve_static" in /etc/nginx/nginx.conf:12\nnginx: configuration file /etc/nginx/nginx.conf test failed

C nginx: [warn] deprecated directive used in /etc/nginx/nginx.conf:12\nnginx: configuration file /etc/nginx/nginx.conf test failed

D nginx: error: could not open configuration file /etc/nginx/nginx.conf

💡 Hint

Look for the exact error message when nginx finds an unknown directive.

When nginx encounters an unknown directive in the configuration file, it reports an emergency level error with the line number and states that the configuration test failed.

🧠 Conceptual

intermediate

Which directive in nginx.conf sets the maximum number of worker processes?

In the main nginx configuration file, which directive controls how many worker processes nginx will start to handle requests?

A worker_processes

B worker_connections

C max_clients

D process_limit

💡 Hint

Think about the directive that defines how many separate workers run.

The worker_processes directive sets the number of worker processes nginx will spawn. Each worker handles connections.

❓ Configuration

advanced

Identify the error in this nginx.conf snippet

Look at this snippet from an nginx.conf file. What is the error that will cause nginx to fail to start?

Nginx

http {
    server {
        listen 80;
        server_name example.com;
        location / {
            root /var/www/html;
            index index.html index.htm;
        }
    }
    worker_processes 4;
}

A The directive 'worker_processes' is inside the 'http' block, which is invalid.

B The 'root' directive must be inside the 'server' block, not 'location'.

C The 'listen' directive must be outside the 'server' block.

D The 'index' directive cannot have multiple files listed.

💡 Hint

Check where 'worker_processes' is allowed in nginx.conf.

The 'worker_processes' directive must be in the main context, not inside 'http' or 'server' blocks. Placing it inside 'http' causes a configuration error.

❓ Troubleshoot

advanced

Why does nginx fail to reload with this configuration?

You updated nginx.conf and ran nginx -s reload. The reload failed with this error: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use). What is the most likely cause?

A The firewall is blocking port 80.

B The nginx user does not have permission to bind to port 80.

C The configuration file has a syntax error on the listen directive.

D Another process is already using port 80, so nginx cannot bind to it.

💡 Hint

The error says 'Address already in use'. What does that mean?

The error means some other process is already listening on port 80, so nginx cannot bind to it again. This is often caused by another web server or an existing nginx instance.

🔀 Workflow

expert

Order the steps to safely update nginx.conf and reload nginx without downtime

Put these steps in the correct order to update nginx configuration safely and reload nginx without downtime.

A 4,2,1,3

B 1,4,2,3

C 4,1,2,3

D 2,4,1,3

💡 Hint

Think about protecting the current config before editing and verifying before reloading.

First backup the current config to restore if needed. Then edit the file. Next test syntax to catch errors. Finally reload nginx to apply changes without downtime.