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

Questions 11–15

1. 11application · medium

   An e-commerce site uses NGINX caching for product images. After a marketing campaign, the images are updated on the origin server, but users still see the old images. What is the most likely cause?

   • AThe cached responses are still considered fresh because their expiration time has not yet passed.
   • BThe client browser is caching the images and NGINX is not involved in serving them.
   • CThe origin server is not sending the new images because the cache key is incorrect.
   • DNGINX is configured to ignore the `Cache-Control` header from the origin.
   Reveal Solution Discussion Select an answer first
2. 12application · medium

   A financial services company wants to cache public marketing pages but must ensure that authenticated user dashboards are never cached. What is the most appropriate approach?

   • AConfigure caching for the marketing pages and use `proxy_no_cache` with a condition that matches authenticated requests.
   • BUse a separate NGINX server for authenticated traffic and cache only on the public server.
   • CCache all responses but set a very short expiration time for authenticated requests.
   • DDisable caching entirely to avoid any risk of serving sensitive data.
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   An NGINX cache is configured with `proxy_cache_valid 200 10m;`. A cached response with status 200 is now 12 minutes old. A client requests the same resource. What will NGINX do?

   • AServe the cached response as stale and simultaneously revalidate it with the origin in the background.
   • BServe the stale cached response to the client without contacting the origin.
   • CForward the request to the origin server, wait for a fresh response, and then serve it to the client.
   • DDelete the cached response and return a 504 Gateway Timeout to the client.
   Reveal Solution Discussion Select an answer first
5. 14expert · hard

   A company caches static assets with NGINX. The marketing team frequently updates images and wants changes to appear immediately. The operations team wants to maintain caching for performance. Which solution best satisfies both requirements?

   • ASet `proxy_cache_valid` to 0 for all image responses.
   • BUse a cache purge mechanism to remove specific cached responses when assets are updated.
   • CUse a very long `proxy_cache_valid` and rely on the origin to send `Cache-Control: no-cache` for updated images.
   • DConfigure `proxy_cache_use_stale updating;` to serve stale images while updating in the background.
   Reveal Solution Discussion Select an answer first
6. 15expert · medium

   An e-commerce platform caches product pages. After a price change, the origin updates the page, but NGINX continues to serve the old price for up to 1 hour. The business requires price updates to be visible within 5 minutes. Which approach balances freshness with caching benefits?

   • ASet `proxy_cache_use_stale error;` to serve stale content only on origin errors.
   • BReduce `proxy_cache_valid` to 5 minutes for product pages.
   • CUse `proxy_cache_bypass` with a cookie that indicates an admin session.
   • DDisable caching for product pages entirely.
   Reveal Solution Discussion Select an answer first