F5 Certified Administrator, NGINX Recertification Exam Free Sample Questions

NGINX operating as a Reverse Proxy and Load Balancer perfectly fits this scenario. It can terminate TLS, serve static files using the 'root' directive before forwarding requests, and use upstream blocks with 'least_conn' to distribute dynamic traffic. While it acts as a web server for the static files, the overarching role managing the API distribution and TLS termination for backends is a reverse proxy/load balancer. A standalone web server would not distribute traffic, and a CDN Edge is a broader infrastructure concept rather than the specific NGINX role described.

This approach correctly addresses all requirements. NGINX operates at Layer 7 to inspect URIs (routing /api/v1 vs /api/v2), terminates TLS using 'ssl_certificate', serves static files directly via the 'root' directive in a specific location, and utilizes 'proxy_cache_bypass $http_cache_control' to respect client cache-busting requests. Layer 4 load balancing (stream module) cannot inspect URIs or serve static files. Terminating TLS at the pods violates the edge-termination requirement.

Virtual host definitions (server blocks) that handle HTTP/HTTPS traffic must reside within the 'http' context. Therefore, the 'include /etc/nginx/conf.d/*.conf;' directive intended to load these server blocks must be placed inside the 'http' block in the main nginx.conf file. Placing it in the main context would result in syntax errors because 'server' blocks are not valid in the global context.

False. The 'sites-available' and 'sites-enabled' structure is a convention popularized by Debian/Ubuntu package maintainers to easily toggle virtual hosts via symlinks. It is not a requirement of the core NGINX binary. NGINX natively uses the 'include' directive, and standard upstream packages typically use 'conf.d/*.conf' instead.

The 'user' directive defines the privileges used by worker processes and MUST be placed in the 'main' (or global) context of the nginx.conf file, outside of any other blocks like 'http' or 'events'. Placing it elsewhere will result in a configuration syntax error.

If the worker process runs as 'www-data', it must have read permissions on the static files and execute permissions on the directory path. If files are owned by root and lack world-read permissions, NGINX will return a 403 Forbidden error.

Worker processes need write access to log files (if opened by the worker) or temporary directories (like proxy_temp_path). If /var/log/nginx/ or specific temporary paths are strictly owned by root, the worker process cannot write to them, causing failures or missing logs.