Describe How to Run NGINX as a Specific User Type F5N1 Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   When running NGINX worker processes as a non-root user, which file must be writable by that user to avoid startup failure?

   • AThe configuration file
   • BThe SSL certificate files
   • CThe PID file
   • DThe NGINX binary
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   An administrator sets 'user appuser;' in nginx.conf. After starting NGINX, the administrator finds that the temporary directory /var/lib/nginx/tmp is not writable by the worker processes, causing errors when NGINX tries to buffer requests. The directory is owned by root:root with permissions 755. What should the administrator do to resolve this?

   • AChange the user directive to 'user root;' so workers can write to the directory.
   • BChange ownership of /var/lib/nginx/tmp to appuser:appuser and set permissions to 755.
   • CMove the temporary directory to /tmp and set permissions to 777.
   • DAdd the 'appuser' user to the 'root' group to grant write access.
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   A developer wants to run NGINX on a development workstation to test a configuration that listens on port 8080. The developer does not have root access and wants to run the master process as their own user 'devuser'. What is the correct approach to start NGINX as 'devuser'?

   • ARun 'sudo -u devuser nginx' to start the master as devuser; this is the only way to run NGINX as a non-root user.
   • BRun 'nginx -u devuser' to specify the master process user at the command line.
   • CRun 'nginx' directly as devuser; the master process will run as devuser, and workers will run as the user specified in the user directive.
   • DRun 'sudo nginx' so the master process starts as root, then the workers run as devuser.
   Reveal Solution Discussion Select an answer first
5. 9expert · hard

   An organization runs NGINX with worker processes as 'nginx'. The administrator needs to rotate the access log file. The log file /var/log/nginx/access.log is owned by nginx:nginx with permissions 644. The logrotate script runs as root and renames the file, then sends a USR1 signal to NGINX to reopen logs. After rotation, NGINX fails to create a new access.log file. What is the most likely cause?

   • AThe logrotate script does not send the USR1 signal correctly.
   • BThe directory /var/log/nginx is not writable by the 'nginx' user.
   • CThe 'nginx' user does not have permission to read the rotated log file.
   • DThe master process must be restarted, not signaled, to reopen logs.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   An administrator installs NGINX from a distribution package and does not modify nginx.conf. The administrator wants to know which user the worker processes will run as. What is the most reliable way to determine this?

   • ACheck the compiled-in default by running 'nginx -V' and looking for the --user and --group configure arguments.
   • BAssume the default is 'nginx' because that is the most common user.
   • CRun 'ps aux | grep nginx' and look at the user column.
   • DCheck the /etc/passwd file for the 'nginx' user.
   Reveal Solution Discussion Select an answer first