First Nginx configuration - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of the command to test Nginx configuration?

You have created a new Nginx configuration file. Which command will correctly test the syntax of this configuration and what will be the output if the syntax is correct?

Nginx

sudo nginx -t

A

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

B Syntax error in /etc/nginx/nginx.conf at line 10

C nginx: command not found

D Failed to start nginx.service: Unit nginx.service not found.

💡 Hint

Use the command that checks Nginx configuration syntax without starting the server.

The command 'sudo nginx -t' tests the syntax of the Nginx configuration files. If the syntax is correct, it outputs confirmation messages indicating success.

❓ Configuration

intermediate

Identify the correct server block to serve a static website on port 8080

You want Nginx to serve a static website from /var/www/html on port 8080. Which server block configuration is correct?

A server { listen 8080; root /var/www; index index.html; }

B server { listen 8080; root /var/www/html; index index.html; }

C server { listen 80; root /var/www/html; index index.html; }

D server { listen 8080; root /var/www/html; }

💡 Hint

The server block must listen on port 8080 and point root to the exact folder with index.html.

Option B correctly sets the listen port to 8080, root directory to /var/www/html, and specifies index.html as the index file.

❓ Troubleshoot

advanced

Why does Nginx fail to start after adding a new server block?

You added this server block to your Nginx config but Nginx fails to start: server { listen 80; server_name example.com; root /var/www/example; index index.html; location / { try_files $uri $uri/ =404 } } What is the cause of the failure?

Nginx

server {
  listen 80;
  server_name example.com;
  root /var/www/example;
  index index.html;
  location / {
    try_files $uri $uri/ =404
  }
}

A server_name directive is invalid

B Root directory /var/www/example does not exist

C Missing semicolon after 'try_files $uri $uri/ =404' causes syntax error

D listen directive must specify IP address

💡 Hint

Check the syntax carefully for missing punctuation.

Nginx requires semicolons at the end of directives. The 'try_files' line is missing a semicolon, causing a syntax error and preventing Nginx from starting.

🔀 Workflow

advanced

Order the steps to safely reload Nginx after configuration changes

Put these steps in the correct order to safely apply new Nginx configuration changes without downtime.

A 3,1,2,4

B 1,3,2,4

C 3,2,1,4

D 2,3,1,4

💡 Hint

You must edit first, then test, then reload, then check status.

First edit the config, then test syntax, then reload Nginx to apply changes, finally check status to ensure it runs.

✅ Best Practice

expert

Which practice improves Nginx configuration maintainability?

You want to keep your Nginx configuration easy to manage as it grows. Which practice is best?

A Disable syntax testing to speed up reloads

B Put all server blocks in one large nginx.conf file

C Avoid comments to keep files clean

D Use include directives to split configuration into smaller files

💡 Hint

Think about how to organize files for clarity and ease of updates.

Using 'include' directives to split configuration into smaller files helps organize settings logically and makes maintenance easier.