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

Questions 11–15

1. 11foundation · easy

   Which command can be used to start the NGINX master process as a specific non-root user, assuming the user has the necessary permissions?

   • Asu nginx nginx
   • Brunuser nginx nginx
   • Csudo -u nginx nginx
   • Dnginx --user nginx
   Reveal Solution Discussion Select an answer first
2. 12application · medium

   A developer wants to run NGINX on a development machine to test a configuration that listens on port 8080. The developer has sudo access but wants the master process to run as their user 'devuser' to avoid permission issues with log files. What is the correct command to start NGINX as 'devuser'?

   • Asudo nginx
   • Bnginx -u devuser
   • Csudo -u devuser nginx
   • Dsu devuser -c nginx
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   A security team is reviewing an NGINX configuration where the user directive is set to 'user root;'. The team lead asks why this is a bad practice. What is the primary reason?

   • ARunning as root makes the configuration file unreadable.
   • BRunning as root causes NGINX to use more memory.
   • CRunning worker processes as root increases the impact of a vulnerability in NGINX or a worker process.
   • DRunning as root prevents NGINX from binding to privileged ports.
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   Why is it common to start the NGINX master process as root?

   • ATo allow worker processes to run as root
   • BTo bind to privileged ports (e.g., port 80) and read configuration files
   • CTo increase the performance of worker processes
   • DTo allow the master process to change its own user after startup
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   An administrator is setting up NGINX on a server where the application team requires worker processes to run as the 'webapp' user and the 'webgrp' group. The administrator edits nginx.conf and adds the directive 'user webapp webgrp;' in the main context. After reloading NGINX, the administrator notices that the error log file /var/log/nginx/error.log is owned by root:root. What is the most likely reason the worker processes cannot write to the log, and what should the administrator do?

   • AThe log file permissions do not allow the 'webapp' user to write; change ownership of the log file to webapp:webgrp or adjust permissions.
   • BThe user directive must be placed in the http context to affect log file ownership; move the directive.
   • CThe master process must also run as webapp:webgrp for the log to be writable; change the master process user.
   • DThe user directive syntax is wrong; it should be 'user webapp:webgrp;' with a colon separator.
   Reveal Solution Discussion Select an answer first