Directives and blocks in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of nginx configuration test with nested blocks

Given the following nginx configuration snippet, what will be the output of nginx -t command?

Nginx

http {
    server {
        listen 80;
        location / {
            root /var/www/html;
        }
    }
    location /images/ {
        root /var/www/images;
    }
}

A

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

B

nginx: [warn] duplicate location "/images/" in /etc/nginx/nginx.conf:8
nginx: configuration file /etc/nginx/nginx.conf test failed

C

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

D

nginx: [emerg] "location" directive is not allowed here in /etc/nginx/nginx.conf:8
nginx: configuration file /etc/nginx/nginx.conf test failed

💡 Hint

Check where location blocks are allowed inside nginx configuration.

The location directive must be inside a server block. Here, the location /images/ block is placed directly inside the http block, which is invalid. This causes an error when testing the configuration.

🧠 Conceptual

intermediate

Understanding directive context in nginx

Which of the following directives can only be used inside a server block and not directly inside the http block?

A include

B listen

C log_format

D worker_processes

💡 Hint

Think about where nginx listens for connections.

The listen directive specifies the IP and port for a server to accept connections and must be inside a server block. The others are valid in the http or main context.

❓ Troubleshoot

advanced

Troubleshooting nginx block nesting error

You added this snippet to your nginx config but get an error on reload. What is the cause?

Nginx

server {
    listen 443 ssl;
    ssl_certificate /etc/ssl/cert.pem;
    ssl_certificate_key /etc/ssl/key.pem;
    server_name example.com;
    http {
        location / {
            proxy_pass http://localhost:3000;
        }
    }
}

A The <code>http</code> block cannot be nested inside a <code>server</code> block.

B The <code>ssl_certificate</code> directive is misplaced and should be inside <code>location</code>.

C The <code>proxy_pass</code> directive must be outside any block.

D The <code>server_name</code> directive is missing a semicolon.

💡 Hint

Check nginx block hierarchy rules.

The http block is a top-level block and cannot be placed inside a server block. Nesting it inside causes a configuration error.

🔀 Workflow

advanced

Order of nginx configuration blocks for a basic web server

What is the correct order of nginx configuration blocks from top-level to nested for a basic HTTP server?

A 2,3,1,4

B 3,2,1,4

C 2,1,3,4

D 1,3,2,4

💡 Hint

Think about the main blocks and their nesting levels.

The http block is the top-level block for HTTP settings. Inside it, you place server blocks. Inside server, you place location blocks.

✅ Best Practice

expert

Best practice for organizing nginx directives and blocks

Which practice is best for organizing nginx configuration files to improve maintainability and clarity?

A Place all directives inside the main <code>nginx.conf</code> file without includes.

B Avoid using <code>include</code> directives to prevent confusion.

C Use multiple <code>server</code> blocks inside <code>http</code> and split configuration into separate files included with <code>include</code> directive.

D Put <code>location</code> blocks directly inside the <code>http</code> block for simplicity.

💡 Hint

Think about modularity and ease of updates.

Using multiple server blocks inside http and splitting configuration into separate files included with include directives helps keep configuration organized and easier to maintain.