Configuration testing (nginx -t) - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of nginx -t with a valid configuration?

You run nginx -t after editing the configuration file and it is valid. What output do you expect?

A

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

B

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

C

nginx: [warn] deprecated syntax in /etc/nginx/nginx.conf:5
nginx: configuration file /etc/nginx/nginx.conf test failed

D bash: nginx: command not found

💡 Hint

Think about what nginx -t reports when the config is correct.

The nginx -t command checks the syntax of the configuration file. If the config is valid, it outputs a success message indicating syntax is ok and test is successful.

💻 Command Output

intermediate

What error does nginx -t show for a missing semicolon?

You forgot a semicolon at the end of a directive in /etc/nginx/nginx.conf. What error message will nginx -t display?

A

nginx: [error] invalid directive in /etc/nginx/nginx.conf:15
nginx: configuration file /etc/nginx/nginx.conf test failed

B

nginx: [emerg] unexpected end of file, expecting ";" or "}" in /etc/nginx/nginx.conf:15
nginx: configuration file /etc/nginx/nginx.conf test failed

C

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

D

nginx: [warn] missing semicolon in /etc/nginx/nginx.conf:15
nginx: configuration file /etc/nginx/nginx.conf test is successful

💡 Hint

Look for an error mentioning missing semicolon or unexpected end of file.

When a semicolon is missing, nginx reports an emergency error about unexpected end of file expecting a semicolon or closing brace, and the test fails.

❓ Troubleshoot

advanced

Why does nginx -t fail with 'unknown directive' error?

You added a new directive bad_directive in your nginx config and ran nginx -t. It failed with an 'unknown directive' error. What is the most likely cause?

A The directive name is misspelled or not supported by the installed nginx version.

B The server block is missing a closing brace.

C The configuration file has incorrect file permissions.

D The nginx service is not running, so the test cannot complete.

💡 Hint

Think about what 'unknown directive' means in nginx config context.

An 'unknown directive' error means nginx does not recognize the directive name. This usually happens if the directive is misspelled or belongs to a module not installed or enabled.

✅ Best Practice

advanced

What is the best practice before reloading nginx after config changes?

You edited the nginx configuration file. What should you do before running systemctl reload nginx to avoid downtime?

A Delete the old configuration file to avoid conflicts.

B Restart the server to apply changes safely.

C Run <code>nginx -t</code> to test the configuration syntax for errors.

D Run <code>systemctl stop nginx</code> before reloading.

💡 Hint

Think about how to check config correctness without stopping the service.

Running nginx -t tests the configuration syntax and catches errors before reloading. This prevents nginx from failing to reload and causing downtime.

🔀 Workflow

expert

Order the steps to safely update nginx configuration with zero downtime

Arrange the following steps in the correct order to update nginx configuration safely without downtime.

A 1,2,4,3

B 2,1,3,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Remember to test config before reloading, and verify service after reload.

The safe workflow is: first edit the config, then test it with nginx -t. If the test passes, reload nginx to apply changes. Finally, check nginx status to ensure it is running correctly.