Describe the Why and How of Caching in NGINX F5N2 Practice Questions (Page 2)

Questions 6–10

1. 6expert · hard

   An NGINX cache is configured with `proxy_cache_revalidate on;`. A cached response is stale, and the origin returns a `304 Not Modified` response. What will NGINX do?

   • AReplace the cached response with the 304 response and serve it to the client.
   • BUpdate the expiration time of the cached response and serve it to the client.
   • CDelete the cached response and fetch a fresh copy from the origin.
   • DServe the stale response without contacting the origin.
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   An NGINX cache is configured with `proxy_cache_key "$scheme$host$request_uri";`. A client requests `https://example.com/products?id=1` and then `https://example.com/products?id=2`. How will NGINX treat these two requests?

   • AAs two separate cache entries because the `$request_uri` includes the query string, making the cache keys different.
   • BAs the same cache entry because the path `/products` is identical and the query string is ignored by default.
   • CAs two separate entries only if the `id` parameter is listed in a separate `proxy_cache_key` directive.
   • DAs the same cache entry because `$scheme` and `$host` are identical, and only those variables are used in the key.
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   What does NGINX consider a cached response to be 'fresh'?

   • AThe response has not yet exceeded its expiration time
   • BThe response's ETag matches the origin server's current ETag
   • CThe response has been stored for less than 24 hours
   • DThe response was served to a client at least once
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   A website serves different content to mobile and desktop users at the same URL. The `User-Agent` header determines which version is served. How should the NGINX cache key be configured to handle this correctly?

   • AInclude `$http_user_agent` in the `proxy_cache_key` directive.
   • BDisable caching for requests with a mobile `User-Agent`.
   • CSet `proxy_cache_key` to `$scheme$host$uri` and rely on the origin to send `Vary: User-Agent`.
   • DUse the default cache key because NGINX automatically detects device type.
   Reveal Solution Discussion Select an answer first
6. 10foundation · easy

   What is the primary purpose of configuring NGINX as a content cache server?

   • ATo reduce the load on origin servers and improve response times for clients
   • BTo encrypt responses before they are sent to clients
   • CTo authenticate users before they access cached content
   • DTo rewrite URLs to more user-friendly formats
   Reveal Solution Discussion Select an answer first