Advanced NGINX Features F5N2 Practice Questions (Page 1)

Questions 1–5

1. 1application · medium

   A load balancer uses `sticky` sessions with a shared memory zone. The administrator notices that after a configuration reload, some sessions are lost. What is the likely reason?

   • AThe `proxy_pass` directive is not configured correctly.
   • BThe `sticky` directive is not supported in the `upstream` block.
   • CThe shared memory zone is not persistent across reloads; sessions are lost when the zone is reinitialized.
   • DThe `keepalive` directive is causing connections to be closed.
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   A development team wants to test a new version of their API by sending a copy of live production traffic to a staging server, without affecting the production responses. They are using NGINX as a reverse proxy. What configuration should they use?

   • AUse the `mirror` directive in the `location` block to copy requests to a separate `upstream` block that points to the staging server.
   • BUse the `proxy_pass` directive to send all traffic to the staging server and then use `return` to send the response back to the client.
   • CUse the `proxy_cache` directive to cache responses from the staging server and serve them to clients.
   • DUse the `split_clients` module to route a percentage of traffic to the staging server.
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   In NGINX, which directive defines the size of a shared memory zone used for rate limiting?

   • Aupstream
   • Blimit_req_zone
   • Cproxy_cache_path
   • Dlimit_conn_zone
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   An administrator is tuning NGINX for high traffic. They are using a shared memory zone for rate limiting and notice that the zone is filling up, causing some requests to be rejected. What is the best way to address this?

   • AIncrease the `worker_processes` value to distribute the load.
   • BDecrease the `limit_req` rate to allow fewer requests per second.
   • CRemove the `limit_req` directive entirely to stop rejecting requests.
   • DIncrease the `zone` size in the `limit_req_zone` directive.
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A team is comparing NGINX with traditional load balancers. They need to justify NGINX's event-driven architecture for handling high concurrency. Which statement best describes this advantage?

   • ANGINX spawns a new process for each connection, similar to traditional load balancers.
   • BNGINX relies on the operating system's kernel to manage connections, which limits scalability.
   • CNGINX uses a single-threaded event loop that can handle thousands of concurrent connections with low memory usage.
   • DNGINX uses a thread pool to handle each request, which increases memory usage under load.
   Reveal Solution Discussion Select an answer first