Describe NGINX as an API Gateway F5N1 Practice Questions (Page 5)

Questions 21–22

1. 21application · medium

   An e-commerce platform has a public checkout API that experiences occasional traffic spikes during flash sales. The backend can handle normal load but becomes unstable under sudden bursts. The team wants to protect the backend by allowing a steady rate of requests while permitting short bursts. Which NGINX configuration approach should be used?

   • AUse upstream keepalive to maintain persistent connections to the backend.
   • BEnable proxy_cache to serve cached responses for all checkout requests.
   • CConfigure limit_req with a burst parameter and nodelay to allow short bursts while enforcing the average rate.
   • DSet limit_conn to restrict the number of concurrent connections per client IP.
   Reveal Solution Discussion Select an answer first
2. 22application · medium

   A company has multiple backend services that use different authentication schemes. The API team wants to standardize authentication for all external clients by validating tokens at a single point before requests reach the backends. Which NGINX capability directly supports this?

   • Aauth_request module to validate tokens against an external authentication service.
   • Blimit_req to rate-limit authentication attempts.
   • Caccess_log to record authentication failures.
   • Dproxy_set_header to forward the original Authorization header to backends.
   Reveal Solution Discussion Select an answer first