Understand How to Enable and Optimize Keep-Alives for the NGINX Server and Its Upstreams F5N3 Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   What is the primary purpose of HTTP keep-alive connections in NGINX?

   • ATo increase the maximum number of concurrent connections NGINX can handle
   • BTo encrypt HTTP traffic between the client and NGINX
   • CTo compress HTTP responses before sending them to the client
   • DTo reduce latency by reusing an existing TCP connection for multiple HTTP requests
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   A company runs an NGINX server that serves a public website. They have noticed that some clients are keeping connections open for a very long time, which is consuming worker connections and preventing new users from connecting. The website is a standard content site where users typically load a page and then move on. The team wants to free up connections more aggressively without impacting the normal user experience. Which configuration change best achieves this?

   • ASet worker_connections to a higher value
   • BReduce keepalive_timeout to 10s
   • CIncrease keepalive_timeout to 120s
   • DSet keepalive_requests to 1
   Reveal Solution Discussion Select an answer first
4. 8expert · hard

   A company runs an NGINX server that acts as both a static file server and a reverse proxy for a backend API. The static files are served directly by NGINX, while the API requests are proxied to a backend. The team has noticed that the backend API is slow to respond under load. They suspect that the upstream keep-alive pool is not large enough. The current configuration has keepalive 16; in the upstream block. What is the most important factor to consider when increasing this value?

   • AThe proxy_http_version setting, as it must be set to 1.1 for the keepalive directive to have any effect.
   • BThe number of backend servers in the upstream block, as the keepalive value must be evenly divisible by the number of servers.
   • CThe number of worker_connections available, as each keep-alive connection to the upstream consumes a worker connection.
   • DThe keepalive_timeout value for client connections, as it determines how long the upstream connections will be kept open.
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   What is a potential downside of setting a very large keepalive_timeout for client connections?

   • AIncreased memory usage because idle connections remain open longer
   • BHigher bandwidth consumption because connections stay open
   • CIncreased CPU usage due to more frequent TLS handshakes
   • DReduced throughput because NGINX processes requests more slowly
   Reveal Solution Discussion Select an answer first
6. 10foundation · easy

   An administrator wants to limit the number of requests a single client can make over one keep-alive connection. Which directive should be used?

   • Akeepalive_timeout
   • Bkeepalive_disable
   • Cclient_max_body_size
   • Dkeepalive_requests
   Reveal Solution Discussion Select an answer first