Free F5CANR sample questions

Correct answer: Deploy NGINX as a Layer 7 reverse proxy, configuring 'ssl_certificate' in the server block, a 'location /images/' block with a 'root' directive, and 'proxy_cache_bypass $http_cache_control' in the API location blocks.

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.

Correct answer: Inside the 'http' block

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.

Correct answer: False

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.

Correct answer: The 'main' (global) context

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.

Correct answers: Clients receive '403 Forbidden' errors when requesting static HTML files.; NGINX cannot write to its configured error log file in /var/log/nginx/.

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.

Correct answer: chown -R nginx:nginx /var/www/html/images

The 'chown' (change owner) command is used to change the user and group ownership of files. Using 'chown -R nginx:nginx' recursively changes the ownership to the nginx user and group, allowing the worker processes to read the files. Using chmod 777 is a severe security risk, and adding the nginx user to the root group violates least privilege.