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

Questions 16–20

1. 16application · medium

   A company wants to expose a set of internal APIs to external partners. The APIs are currently only accessible on the internal network. The team needs a secure, controlled way to publish these APIs without exposing the internal network directly. Which NGINX deployment is most appropriate?

   • ADeploy NGINX in a DMZ as an API gateway, proxying requests to internal APIs while enforcing authentication and rate limits.
   • BUse NGINX as a mail proxy to forward API requests.
   • CDeploy NGINX as a static file server for API documentation only.
   • DOpen firewall ports to allow external partners to access the internal APIs directly.
   Reveal Solution Discussion Select an answer first
2. 17expert · hard

   A healthcare organization exposes patient-data APIs to a small number of trusted partners. The organization must comply with strict audit requirements, logging every request with the partner identity. The partners use different authentication mechanisms: some use OAuth2, others use client certificates. The organization wants to minimize the number of moving parts and already uses NGINX. Which approach best satisfies the audit and heterogeneous authentication requirements?

   • AUse NGINX as a load balancer and rely on each backend to handle its own authentication and logging.
   • BUse NGINX as an API gateway with auth_request for OAuth2 validation and ssl_client_certificate for mTLS, logging partner identity in access_log.
   • CConfigure NGINX to accept only OAuth2 and require all partners to migrate from client certificates.
   • DDeploy a separate reverse proxy for each partner to handle their specific authentication method.
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   A fintech startup has three microservices (accounts, payments, and notifications) that each expose their own REST APIs. The security team requires all external clients to authenticate with OAuth2 tokens before reaching any backend, and the operations team wants a single place to enforce a 100 requests-per-minute limit per client. The backend services must not be modified. What should the team configure on NGINX to meet these requirements?

   • AConfigure NGINX as a reverse proxy with auth_request to a token introspection endpoint and limit_req zones per client IP.
   • BDeploy NGINX as a load balancer in front of the three services and enable gzip compression for all responses.
   • CUse NGINX as a caching layer only, storing responses from the three services to reduce backend load.
   • DInstall NGINX as a web server and serve static API documentation for the three services.
   Reveal Solution Discussion Select an answer first
5. 19application · medium

   A university runs several independent APIs for course registration, grades, and library services. The IT department wants to provide a single URL (api.university.edu) that routes to the correct service based on the path (e.g., /courses, /grades, /library). They also want to apply a shared authentication check. What should they deploy?

   • AA database replication setup to synchronize data across services.
   • BA DNS load balancer that randomly distributes requests to the APIs.
   • CA separate web server for each API, each with its own URL.
   • DNGINX as an API gateway with location-based routing and a common auth_request directive.
   Reveal Solution Discussion Select an answer first
6. 20foundation · easy

   Which API gateway function verifies the identity of a client before allowing access to backend services?

   • ALoad balancing
   • BRequest routing
   • CAuthentication
   • DRate limiting
   Reveal Solution Discussion Select an answer first