Why static file serving is the primary use case in Nginx - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to serve static files from the /var/www/html directory.

Nginx

location / {
    root [1];
}

Drag options to blanks, or click blank then click option'

A/usr/share/nginx/html

B/etc/nginx/html

C/home/user/html

D/var/www/html

Attempts:

3 left

💡 Hint

Common Mistakes

Using a directory that does not exist or is not accessible by nginx.

Confusing root with alias.

The root directive sets the directory from which static files are served. /var/www/html is the standard directory for static content.

2fill in blank

medium

Complete the code to enable index file serving for static content.

Nginx

location / {
    root /var/www/html;
    [1] index.html index.htm;
}

Drag options to blanks, or click blank then click option'

Aindex

Bautoindex on;

Cindex on;

Dautoindex off;

Attempts:

3 left

💡 Hint

Common Mistakes

Using autoindex instead of index to serve default files.

Adding a semicolon after index keyword incorrectly.

The index directive specifies the default files nginx looks for when a directory is requested.

3fill in blank

hard

Fix the error in the code to correctly serve static files with caching headers.

Nginx

location /static/ {
    root /var/www/html;
    add_header Cache-Control [1];
}

Drag options to blanks, or click blank then click option'

A"no-cache"

Bno-cache

C"max-age=3600"

Dmax-age=3600

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting the header value causing nginx to fail to start.

Using incorrect header values that do not control caching.

The add_header directive requires the header value to be in quotes if it contains special characters like '='.

4fill in blank

hard

Fill both blanks to configure nginx to serve static files and disable directory listing.

Nginx

location /files/ {
    root [1];
    autoindex [2];
}

Drag options to blanks, or click blank then click option'

A/srv/static

Bon

Coff

D/var/www/files

Attempts:

3 left

💡 Hint

Common Mistakes

Setting autoindex to on, which allows directory listing.

Using incorrect directory paths that do not exist.

The root directive sets the directory for static files. autoindex off; disables directory listing for security.

5fill in blank

hard

Fill all three blanks to create a location block that serves static files with gzip compression and caching.

Nginx

location /assets/ {
    root [1];
    gzip [2];
    add_header Cache-Control [3];
}

Drag options to blanks, or click blank then click option'

A/usr/share/nginx/assets

Bon

C"max-age=86400"

Doff

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to enable gzip compression.

Not quoting the Cache-Control header value.

Using wrong directory paths.

Serving static files from /usr/share/nginx/assets with gzip compression enabled (gzip on;) improves speed. Adding caching headers with "max-age=86400" caches files for one day.

Practice

1. Why is static file serving considered the primary use case for nginx?

easy

A. Because it is mainly used for sending emails

B. Because it handles static files very fast and reduces load on app servers

C. Because it can run complex database queries efficiently

D. Because it replaces the need for any backend server

Solution

1. Step 1: Understand nginx's design focus

   nginx is built to serve static files like images, CSS, and HTML quickly and efficiently.

2. Step 2: Recognize the benefit of static file serving

   Serving static files directly reduces the load on backend application servers, improving website speed.

3. Final Answer:

   Because it handles static files very fast and reduces load on app servers -> Option B

4. Quick Check:

   Static file serving = primary nginx use [OK]

Hint: Remember nginx shines at fast static file delivery [OK]

Common Mistakes:

• Thinking nginx runs database queries
• Confusing nginx with email servers
• Assuming nginx replaces backend logic

2. Which of the following nginx configuration snippets correctly sets the root directory for static files?

easy

A. root /var/www/html;

B. root: /var/www/html

C. root = /var/www/html

D. root => /var/www/html

Solution

1. Step 1: Recall correct syntax for root directive

   The root directive uses the format: root /path/to/directory; with a semicolon.

2. Step 2: Identify correct option

   root /var/www/html; uses correct syntax with no extra symbols and ends with a semicolon.

3. Final Answer:

   root /var/www/html; -> Option A

4. Quick Check:

   Correct root syntax ends with semicolon [OK]

Hint: Look for semicolon and no extra symbols in root directive [OK]

Common Mistakes:

• Using colon instead of space
• Using equals sign or arrow instead of space
• Omitting the semicolon

3. Given this nginx config snippet:

location / {
    root /usr/share/nginx/html;
    index index.html index.htm;
}

What file will nginx serve when a user visits http://example.com/?

medium

A. /usr/share/nginx/html/index.html

B. /usr/share/nginx/html/home.html

C. /usr/share/nginx/html/default.html

D. /usr/share/nginx/html/index.htm

Solution

1. Step 1: Understand index directive order

   The index directive lists files nginx tries in order: first index.html, then index.htm.

2. Step 2: Determine served file

   Since index.html is first, nginx will serve /usr/share/nginx/html/index.html if it exists.

3. Final Answer:

   /usr/share/nginx/html/index.html -> Option A

4. Quick Check:

   Index files served in order listed [OK]

Hint: Check index files order to find served file [OK]

Common Mistakes:

• Choosing second index file without checking first
• Assuming default.html or home.html served
• Ignoring root path in location block

4. You configured nginx to serve static files with:

location /static/ {
    root /var/www/html;
}

But requests to /static/style.css return 404 errors. What is the likely cause?

medium

A. nginx cannot serve CSS files by default

B. The index directive is missing

C. The root path is incorrect; it should be /var/www/html/static

D. The location block should use alias instead of root

Solution

1. Step 1: Understand root vs alias behavior

   Using root with a location adds the URI path after root, causing path mismatch for /static/style.css.

2. Step 2: Identify correct directive for this case

   alias replaces the location prefix, so alias /var/www/html/static/; correctly maps requests.

3. Final Answer:

   The location block should use alias instead of root -> Option D

4. Quick Check:

   Use alias for subdirectory location paths [OK]

Hint: Use alias, not root, for subdirectory location paths [OK]

Common Mistakes:

• Confusing root and alias directives
• Adding index directive unnecessarily
• Thinking nginx blocks CSS files

5. You want nginx to serve static files from /data/site when users visit /files/. Which configuration correctly achieves this without exposing the /data directory structure in URLs?

hard

A. location /files/ {
root /data/site;
}

B. location /files/ {
root /data;
}

C. location /files/ {
alias /data/site/;
}

D. location /files/ {
alias /data/;
}

Solution

1. Step 1: Understand URL to file path mapping

   Using alias with trailing slash maps /files/ URLs directly to /data/site/ files without adding extra path segments.

2. Step 2: Compare root vs alias for this case

   root /data/site; would append /files/ to path, causing incorrect file paths. alias /data/site/; correctly maps URLs.

3. Final Answer:

   location /files/ { alias /data/site/; } -> Option C

4. Quick Check:

   Use alias with trailing slash for clean URL mapping [OK]

Hint: Use alias with trailing slash for subdirectory static serving [OK]

Common Mistakes:

• Using root which appends location path incorrectly
• Omitting trailing slash in alias causing path errors
• Exposing parent directory structure in URLs