Configuration reload vs restart in Nginx - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Difference between reload and restart in Nginx

What is the main difference between nginx -s reload and systemctl restart nginx commands?

A Reload deletes all logs, restart preserves logs.

B Reload stops the server completely, restart only reloads the configuration without downtime.

C Both reload and restart stop the server but reload is faster.

D Reload applies configuration changes without stopping the server, while restart stops and starts the server causing downtime.

💡 Hint

Think about whether the server process is stopped or kept running during each command.

Reload sends a signal to Nginx to re-read its configuration without stopping the worker processes, so no downtime occurs. Restart fully stops and then starts the Nginx service, causing a brief downtime.

💻 Command Output

intermediate

Output of reload command with syntax error

What output will you see if you run nginx -s reload when the configuration file has a syntax error?

Nginx

nginx -s reload

A nginx: [emerg] unknown directive "bad_directive" in /etc/nginx/nginx.conf:10

B nginx: command not found

C Reload successful, no errors found.

D Service restarted successfully.

💡 Hint

Consider what happens if Nginx tries to reload a bad config.

If the config has syntax errors, Nginx will report an emergency error and refuse to reload.

🔀 Workflow

advanced

Correct sequence to safely apply config changes

What is the correct order of commands to safely apply new Nginx configuration changes without downtime?

A 3,2,1,4

B 1,3,2,4

C 3,1,2,4

D 2,3,1,4

💡 Hint

Think about editing config first, then testing, then reloading.

First edit the config file, then test it with nginx -t to check syntax, then reload Nginx to apply changes, finally verify the website is working.

❓ Troubleshoot

advanced

Troubleshooting Nginx restart failure

After running systemctl restart nginx, the service fails to start. Which of the following is the most likely cause?

A Nginx configuration file has syntax errors.

B The reload command was used instead of restart.

C The Nginx logs are full.

D The server has no internet connection.

💡 Hint

Consider what prevents Nginx from starting after restart.

If the config file has syntax errors, Nginx will fail to start on restart because it validates config on startup.

✅ Best Practice

expert

Best practice for applying critical config changes

For critical Nginx configuration changes that affect SSL certificates, which approach minimizes risk of downtime?

A Directly restart Nginx with <code>systemctl restart nginx</code> without testing.

B Test config with <code>nginx -t</code>, then reload with <code>nginx -s reload</code>.

C Edit config and wait for automatic reload by Nginx.

D Stop Nginx, edit config, then start Nginx.

💡 Hint

Think about testing before applying changes and avoiding downtime.

Testing config first ensures no syntax errors. Reload applies changes without stopping Nginx, minimizing downtime risk.