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

Questions 1–5

1. 1expert · hard

   A cloud-native company runs its microservices on Kubernetes. The platform team wants to expose some services to external partners through a single API gateway that supports JWT validation and rate limiting. They already use NGINX Ingress Controller for internal routing. Which approach is most appropriate?

   • AExpose each microservice directly with its own public LoadBalancer service.
   • BDeploy NGINX as a dedicated API gateway in front of the Kubernetes cluster, configuring JWT validation and rate limiting.
   • CUse a service mesh exclusively for all external traffic.
   • DUse the existing NGINX Ingress Controller for both internal and external traffic without additional configuration.
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   A logistics company has multiple internal teams that each maintain their own APIs. The company wants to provide a single, consistent entry point for external partners, hide the internal API structure, and apply common policies like authentication and logging. Which role does NGINX play in this architecture?

   • AContent delivery network that caches API responses at edge locations.
   • BDatabase proxy that translates API calls into SQL queries.
   • CAPI gateway that abstracts the internal APIs behind a unified endpoint and applies cross-cutting policies.
   • DWeb server that serves static documentation for each internal API.
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   A SaaS provider wants to offer a public API to external developers. The API must support JSON payloads, require an API key, and log all requests for auditing. The provider already runs NGINX in front of its application servers. Which set of NGINX features should be enabled to fulfill these API gateway requirements?

   • AStatic file serving, gzip compression, and error_page for custom error responses.
   • BLoad balancing with round-robin and sticky sessions for session persistence.
   • CTLS termination and HTTP/2 support for secure, efficient transport.
   • DProxy pass to application servers, auth_request for API key validation, and access_log for auditing.
   Reveal Solution Discussion Select an answer first
5. 4expert · hard

   A financial services company has a public API that must handle high throughput with low latency. The API is read-heavy, and many responses are identical for long periods. The company wants to reduce backend load and improve response times. They also need to invalidate cached responses when data changes. Which NGINX configuration best meets these needs?

   • AEnable proxy_cache with cache key based on the request URI and use proxy_cache_purge to invalidate on updates.
   • BEnable gzip compression to reduce response size and improve transfer speed.
   • CConfigure limit_req to reduce the number of requests reaching the backend.
   • DUse upstream keepalive to maintain persistent connections to the backend.
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A retail company exposes a public product-search API. The backend expects a header named X-Client-ID, but external partners send the client identifier in a query parameter named client_id. The API team wants NGINX to translate the query parameter into the required header before forwarding the request. Which NGINX capability should be used?

   • AResponse transformation using the sub_filter module to rewrite the backend response.
   • BConnection pooling using keepalive to reuse upstream connections.
   • CStatic file serving with alias to map the query parameter to a file path.
   • DRequest transformation using the set directive and proxy_set_header to map the query parameter to a header.
   Reveal Solution Discussion Select an answer first