
F5Certified Administrator NGINX
Domain 4Objective 2
Describe Why Directives Use a Shared Memory Zone F5N1 Practice Questions (Page 3)
Part of the Manage shared memory zones domain, which makes up ~13% of our current practice bank. F5 does not publish an official question count, but from its 30-minute exam (~10–20 total, ~1–3 in this domain), expect 1–2 from this objective — we provide 18 practice questions to prepare you well beyond it. (estimate)
18questions here
4free pages
3concepts
Questions 11–15
- 11
A company runs NGINX with multiple worker processes. They are using the sticky directive to maintain session affinity. The administrator notices that sometimes a client's request is routed to a different upstream server than expected. What is the most likely cause of this issue?
Select an answer first - 12
Why do NGINX directives such as limit_req and limit_conn use a shared memory zone?
Select an answer first - 13
A company uses NGINX to serve a large number of static files. They want to implement a simple rate limit to prevent any single IP from making more than 100 requests per minute. They are considering whether to use the limit_req_zone directive. What is the primary reason this directive requires a shared memory zone?
Select an answer first - 14
Which NGINX directive requires a shared memory zone to function correctly?
Select an answer first - 15
A company runs a critical API on NGINX with 16 worker processes. They use both limit_req_zone and limit_conn_zone directives. The administrator wants to ensure that rate limiting and connection limiting are accurate even under high load. What is the most important consideration when configuring the shared memory zones for these directives?
Select an answer first
Finished these 5 questions?
Review the revealed explanations, or continue through the curriculum.
Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by F5. “F5N1” is a trademark of its owner, used for identification only.