Why Nginx handles API routing - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the server listening on port 80.

Nginx

server {
    listen [1];
}

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

A80

B443

C8080

D22

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 443 without SSL configuration

Using port 22 which is for SSH

The listen directive tells Nginx which port to listen on. Port 80 is the default for HTTP.

2fill in blank

medium

Complete the code to route API requests to the backend server.

Nginx

location /api/ {
    proxy_pass [1];
}

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

Ahttp://localhost:3000

Bhttps://example.com

Cftp://localhost

Dfile:///var/www

Attempts:

3 left

💡 Hint

Common Mistakes

Using HTTPS without backend support

Using file or FTP protocols incorrectly

The proxy_pass directive forwards requests to the backend server. Here, the backend runs on localhost port 3000.

3fill in blank

hard

Fix the error in the proxy header to pass the original host.

Nginx

location /api/ {
    proxy_set_header Host [1];
}

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

A$remote_addr

Blocalhost

C127.0.0.1

D$host

Attempts:

3 left

💡 Hint

Common Mistakes

Setting Host to localhost breaks backend routing

Using remote address instead of host

Using $host passes the original host header to the backend, which is important for routing and logging.

4fill in blank

hard

Complete the code to rewrite the API URL path correctly.

Nginx

location /api/ {
    proxy_pass http://backend[1]api;
}

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

A/

C/v1/

D/api/

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the trailing slash causes path concatenation errors

Adding extra /api/ duplicates the path

Adding a trailing slash / after the backend URL and no extra path after api ensures the path is rewritten correctly.

5fill in blank

hard

Fill all three blanks to add caching headers for API responses.

Nginx

location /api/ {
    proxy_pass http://backend/;
    add_header Cache-Control [1];
    add_header Pragma [2];
    add_header Expires [3];
}

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

A"no-cache"

B"no-store"

C"0"

D"max-age=3600"

Attempts:

3 left

💡 Hint

Common Mistakes

Using max-age enables caching which may cause stale data

Omitting headers leads to default caching behavior

Setting Cache-Control to "no-cache", Pragma to "no-store", and Expires to "0" disables caching for API responses.