Separate config files per site in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of nginx -t with separate site configs

You have two separate site config files in /etc/nginx/sites-available/ enabled via symlinks in /etc/nginx/sites-enabled/. What is the output of nginx -t if both configs are syntactically correct?

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] conflicting server name in /etc/nginx/sites-enabled/site2.conf:15

C nginx: [emerg] duplicate server name "example.com" in /etc/nginx/sites-enabled/site1.conf:10

D nginx: [error] failed to open configuration file /etc/nginx/sites-enabled/site1.conf

💡 Hint

If configs are correct and enabled properly, nginx -t reports syntax ok and test successful.

When separate site config files are correctly placed and linked, nginx -t checks all configs and reports syntax ok and test successful if no errors.

❓ Configuration

intermediate

Correct way to enable a site config in nginx

Which command correctly enables a site config file named mysite.conf located in /etc/nginx/sites-available/ by creating a symlink in /etc/nginx/sites-enabled/?

A cp /etc/nginx/sites-available/mysite.conf /etc/nginx/sites-enabled/mysite.conf

B mv /etc/nginx/sites-available/mysite.conf /etc/nginx/sites-enabled/

C ln -s /etc/nginx/sites-available/mysite.conf /etc/nginx/sites-enabled/mysite.conf

D rm /etc/nginx/sites-enabled/mysite.conf

💡 Hint

Enabling a site means linking the config, not copying or moving it.

The standard practice is to create a symbolic link from sites-available to sites-enabled so nginx loads the config without duplicating files.

❓ Troubleshoot

advanced

Troubleshooting nginx site config not loading

You added a new site config file in /etc/nginx/sites-available/ and created a symlink in /etc/nginx/sites-enabled/. After reloading nginx, the site does not respond. What is the most likely cause?

A The config file is in JSON format instead of nginx syntax

B The symlink points to a non-existent file or has incorrect permissions

C The server block in the config is missing a <code>listen</code> directive

D nginx does not support multiple site config files

💡 Hint

Check if the symlink is valid and accessible by nginx.

If the symlink is broken or permissions prevent nginx from reading the config, the site won't load even if the config looks correct.

🔀 Workflow

advanced

Order of steps to add a new site with separate config

What is the correct order of steps to add a new website using separate config files in nginx?

A 1,3,4,2

B 1,2,3,4

C 3,1,2,4

D 1,3,2,4

💡 Hint

Always test config before reloading nginx.

First create the config file, then enable it by linking, then test syntax, and finally reload nginx to apply.

✅ Best Practice

expert

Best practice for managing multiple site configs in nginx

Which practice is best for managing multiple site configurations in nginx to ensure easy maintenance and minimal downtime?

A Use separate config files per site in sites-available, enable with symlinks in sites-enabled, test configs before reload

B Keep all site configs in a single large file and reload nginx after every change

C Edit the main nginx.conf directly for each site and restart nginx service to apply

D Store site configs in random directories and include them manually in nginx.conf

💡 Hint

Modular config files and testing before reload reduce errors and downtime.

Separating configs per site and enabling them with symlinks allows easy management. Testing before reload prevents downtime.