Why caching improves response times in Nginx - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable basic caching in nginx.

Nginx

proxy_cache_path /var/cache/nginx levels=1:2 keys_zone=my_cache:10m [1] inactive=60m;

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

Amax_size=10g

Bmax_size=1g

Cmax_size=100m

Dmax_size=500m

Attempts:

3 left

💡 Hint

Common Mistakes

Using too small cache size limits caching benefits.

Omitting the max_size directive.

The max_size directive sets the maximum size of the cache. Setting it to 1 gigabyte allows nginx to store cached files up to that size, improving response times by serving cached content.

2fill in blank

medium

Complete the code to enable caching for a proxy location in nginx.

Nginx

location /api/ {
    proxy_cache my_cache;
    proxy_pass http://backend_server;
    proxy_cache_valid 200 [1];
}

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

A1h

B10m

C30s

D5h

Attempts:

3 left

💡 Hint

Common Mistakes

Setting cache time too short, reducing caching benefits.

Using invalid time format.

The proxy_cache_valid directive sets how long a successful response (status 200) is cached. Setting it to 1 hour means nginx will serve cached content for one hour, improving response times.

3fill in blank

hard

Fix the error in the caching configuration to properly enable caching.

Nginx

proxy_cache_path /var/cache/nginx levels=1:2 keys_zone=my_cache:10m max_size=1g inactive=60m;

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

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

Acache_zone

Bmycache

Ccache_my

Dmy_cache

Attempts:

3 left

💡 Hint

Common Mistakes

Misspelling the cache zone name.

Using a different name than defined.

The proxy_cache directive must match the name of the cache zone defined in keys_zone. Here, it is my_cache. Using a different name causes caching not to work.

4fill in blank

hard

Fill both blanks to configure nginx to cache only GET requests and bypass caching for POST requests.

Nginx

proxy_cache_methods [1];
proxy_cache_bypass [2];

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

AGET

BPOST

CPUT

DDELETE

Attempts:

3 left

💡 Hint

Common Mistakes

Caching POST requests causing stale data.

Not specifying methods correctly.

proxy_cache_methods GET; tells nginx to cache only GET requests. proxy_cache_bypass POST; tells nginx to bypass cache for POST requests, ensuring dynamic data is not cached.

5fill in blank

hard

Fill both blanks to create a cache key that includes the host, URI, and query string.

Nginx

proxy_cache_key [1]$host:$request_uri[2]$query_string;

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

A"

B_

C:

D-

Attempts:

3 left

💡 Hint

Common Mistakes

Missing quotes causing syntax errors.

Using wrong separators causing cache misses.

The cache key is a string combining host, URI, and query string. Quotes " wrap the key. Colons : and underscores _ separate parts for clarity and uniqueness.

Practice

1. Why does caching improve response times in nginx?

easy

A. Because it increases the number of server processes

B. Because it disables logging to speed up requests

C. Because it stores copies of responses to serve future requests faster

D. Because it compresses all responses before sending

Solution

1. Step 1: Understand caching purpose

   Caching saves a copy of a response so the server doesn't have to generate it again.

2. Step 2: Connect caching to response time

   Serving a cached copy is faster than processing the request fully each time.

3. Final Answer:

   Because it stores copies of responses to serve future requests faster -> Option C

4. Quick Check:

   Caching = Faster response by reuse [OK]

Hint: Caching saves work by reusing data, speeding responses [OK]

Common Mistakes:

• Thinking caching increases server processes
• Confusing caching with compression
• Believing caching disables logging

2. Which nginx directive is used to define the cache storage location?

easy

A. proxy_cache_path

B. proxy_cache_key

C. proxy_cache_valid

D. proxy_cache_methods

Solution

1. Step 1: Identify directive for cache storage

   The proxy_cache_path directive sets where cached files are stored on disk.

2. Step 2: Differentiate from other directives

   proxy_cache_key sets cache keys, proxy_cache_valid sets cache time, proxy_cache_methods sets which HTTP methods are cached.

3. Final Answer:

   proxy_cache_path -> Option A

4. Quick Check:

   Cache storage location = proxy_cache_path [OK]

Hint: Cache storage location always uses proxy_cache_path [OK]

Common Mistakes:

• Confusing proxy_cache_key with storage path
• Using proxy_cache_valid for storage
• Mixing proxy_cache_methods with storage location

3. Given this nginx config snippet:

proxy_cache_path /tmp/cache levels=1:2 keys_zone=mycache:10m max_size=1g;
server {
  location / {
    proxy_cache mycache;
    proxy_pass http://backend;
  }
}

What happens when a client requests the same URL twice?

medium

A. The cache is cleared after the first request

B. The second request is served from cache, speeding response

C. Both requests always go to the backend server

D. The second request causes an error due to missing cache

Solution

1. Step 1: Analyze proxy_cache usage

   The config defines a cache zone with proxy_cache_path and enables proxy_cache mycache.

2. Step 2: Check for caching validity directive

   By default, nginx caches responses with status 200, 301, 302 if no proxy_cache_valid is set, so the second request is served from cache.

3. Final Answer:

   The second request is served from cache, speeding response -> Option B

4. Quick Check:

   Default caching behavior serves second request from cache [OK]

Hint: Without proxy_cache_valid, default caching applies for some response codes [OK]

Common Mistakes:

• Assuming cache clears after first request
• Thinking second request served from cache only with proxy_cache_valid
• Believing missing cache causes errors

4. You configured proxy_cache but notice responses are never cached. Which is a likely cause?

medium

A. Missing proxy_cache_path directive to define cache zone

B. Using proxy_cache_valid with too long duration

C. Setting proxy_cache_methods to include GET

D. Enabling gzip compression on responses

Solution

1. Step 1: Check cache zone definition

   Without proxy_cache_path, the cache zone is undefined, so caching won't work.

2. Step 2: Evaluate other options

   proxy_cache_valid duration doesn't prevent caching; proxy_cache_methods including GET enables caching; gzip doesn't stop caching.

3. Final Answer:

   Missing proxy_cache_path directive to define cache zone -> Option A

4. Quick Check:

   Cache zone missing = no caching [OK]

Hint: Always define proxy_cache_path to enable caching [OK]

Common Mistakes:

• Ignoring missing proxy_cache_path
• Thinking gzip disables caching
• Confusing proxy_cache_valid with cache enabling

5. You want to improve response times for a high-traffic site using nginx caching. Which combined approach best achieves this?

hard

A. Enable caching but set proxy_cache_methods to only POST requests

B. Disable caching and increase backend server CPU cores

C. Use only proxy_cache_key to cache all requests without size limits

D. Configure proxy_cache_path with enough size, use proxy_cache in locations, and set proxy_cache_valid for freshness

Solution

1. Step 1: Identify caching configuration needs

   Setting proxy_cache_path defines storage size and location; proxy_cache enables caching per location.

2. Step 2: Ensure cache freshness and efficiency

   proxy_cache_valid controls how long cached data is fresh, balancing speed and accuracy.

3. Step 3: Evaluate other options

   Disabling caching or caching only POST requests reduces benefits; caching without size limits risks disk overflow.

4. Final Answer:

   Configure proxy_cache_path with enough size, use proxy_cache in locations, and set proxy_cache_valid for freshness -> Option D

5. Quick Check:

   Proper cache config + freshness = best response times [OK]

Hint: Combine cache path, enable cache, and set validity for best speed [OK]

Common Mistakes:

• Disabling caching instead of configuring it
• Caching only POST requests (rarely cached)
• Ignoring cache size limits causing errors