Include directive for modular config in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the effect of this nginx config snippet?

Given this nginx configuration snippet, what will be the result when nginx starts?

http {
    include /etc/nginx/conf.d/*.conf;
}

Nginx

http {
    include /etc/nginx/conf.d/*.conf;
}

A nginx loads only the first .conf file found in /etc/nginx/conf.d/

B nginx ignores the include directive because wildcards are not supported

C nginx throws a syntax error due to invalid include path

D nginx loads all configuration files ending with .conf from /etc/nginx/conf.d/ directory

💡 Hint

The include directive supports wildcards to modularize configs.

The include directive in nginx supports wildcards like *.conf to load multiple configuration files from a directory, allowing modular configuration.

❓ Configuration

intermediate

Choose the correct syntax to include a single config file

Which option correctly includes the file /etc/nginx/sites-enabled/example.conf inside the server block?

Nginx

server {
    # include directive here
}

A include /etc/nginx/sites-enabled/example.conf;

B include "/etc/nginx/sites-enabled/example.conf"

C include /etc/nginx/sites-enabled/example.conf

D include '/etc/nginx/sites-enabled/example.conf';

💡 Hint

Include directive requires a semicolon at the end.

The include directive syntax requires the path followed by a semicolon. Quotes are optional but not required.

❓ Troubleshoot

advanced

Why does nginx fail to start with this include?

You added this line to your nginx.conf:

include /etc/nginx/conf.d/*.conf;

But nginx fails to start with an error:
nginx: [emerg] open() "/etc/nginx/conf.d/invalid.conf" failed (2: No such file or directory)
What is the most likely cause?

Nginx

include /etc/nginx/conf.d/*.conf;

A The include directive does not support wildcards in nginx

B One of the files matched by the wildcard does not exist or has been deleted

C The directory /etc/nginx/conf.d/ does not have read permissions

D nginx.conf syntax error unrelated to include

💡 Hint

Check if all files matched by the wildcard exist.

If any file matched by the wildcard does not exist or is a broken symlink, nginx will fail to start with an open() error.

🔀 Workflow

advanced

Order the steps to modularize nginx config using include

Put these steps in the correct order to modularize nginx configuration using the include directive:

A 1,3,2,4

B 2,1,3,4

C 3,1,2,4

D 1,2,3,4

💡 Hint

Think about creating directory before placing files and including them.

First create the directory, then place config files inside, then add include directive, finally test and reload nginx.

✅ Best Practice

expert

Which practice is best for modular nginx config using include?

Which option is the best practice for organizing nginx configuration files using the include directive?

A Use include directive only for SSL certificates paths

B Put all configuration in a single large nginx.conf file without includes

C Use include with wildcards to load multiple small config files grouped by function or site

D Avoid using include directive to prevent complexity

💡 Hint

Modular config helps maintainability and clarity.

Using include with wildcards to load multiple small config files grouped logically is best practice for maintainability and clarity.