Describe Why Directives Use a Shared Memory Zone F5N1 Practice Questions (Page 4)

Questions 16–18

1. 16application · medium

   An NGINX administrator is explaining to a colleague why the limit_conn_zone directive needs a shared memory zone. The colleague suggests that the counters could be stored in a regular file on disk. What is the most important reason why a file-based approach would be unsuitable?

   • AFiles on disk are not accessible to multiple processes simultaneously
   • BDisk I/O is too slow for the high-frequency updates required by connection counting
   • CFiles are not persistent across system reboots
   • DFiles cannot store integer counters
   Reveal Solution Discussion Select an answer first
2. 17foundation · easy

   Why does the limit_conn directive need a shared memory zone?

   • ATo store SSL session data for connection reuse.
   • BTo store the configuration of connection limits for each server block.
   • CTo track the number of active connections per key across all worker processes.
   • DTo cache connection objects for faster reuse.
   Reveal Solution Discussion Select an answer first
3. 18expert · hard

   An NGINX administrator is designing a rate-limiting solution for a high-traffic service. They need to ensure that the rate limit is accurate even when a client's requests are distributed across multiple worker processes. They are considering two approaches: using a shared memory zone or using a centralized database. What is the most important advantage of the shared memory zone approach?

   • AIt eliminates the need for locking mechanisms to ensure consistency
   • BIt allows the master process to centrally manage the counters
   • CIt provides lower latency for counter updates compared to a database
   • DIt provides persistent storage of counters across NGINX restarts
   Reveal Solution Discussion Select an answer first