Identify User Context (i.e. Using the Configuration File) F5N1 Practice Questions (Page 3)

Questions 11–15

1. 11expert · hard

   An administrator needs to run NGINX worker processes as 'appuser' with the group 'appgroup'. The administrator adds 'user appuser appgroup;' to the main context. After starting NGINX, the administrator runs 'ps -o user,group -C nginx' and sees 'appuser appgroup' for worker processes. However, a scheduled task that runs as 'appuser' cannot write to a directory that NGINX also writes to. What is the most likely reason?

   • AThe 'user' directive only affects NGINX worker processes, not other processes running as 'appuser'.
   • BNGINX worker processes run with a different umask than the scheduled task.
   • CThe directory has permissions that allow the group but not the user.
   • DThe directory is owned by root and has permissions 755.
   Reveal Solution Discussion Select an answer first
2. 12application · easy

   A security team is hardening an NGINX server and wants to ensure that worker processes run with the least privilege possible. The current configuration has no 'user' directive. The team wants to explicitly set the user to 'nobody' to match the NGINX default. Where should this directive be placed?

   • AIn the main context, outside any block.
   • BIn each server block that needs it.
   • CIn the http block, at the top level.
   • DIn the events block.
   Reveal Solution Discussion Select an answer first
4. 13expert · hard

   An administrator is troubleshooting a permission issue where NGINX cannot read a file in a directory. The directory is owned by 'www-data:www-data' with permissions 750. The NGINX configuration has no 'user' directive, and the binary was compiled with --user=www-data --group=www-data. What is the most likely reason NGINX cannot read the file?

   • AThe file itself has permissions that deny read access to the 'www-data' user.
   • BThe 'user' directive is missing, so NGINX runs as 'nobody'.
   • CThe master process runs as root and cannot read the file.
   • DThe directory permissions are too restrictive for NGINX.
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   An administrator is debugging a permission issue where NGINX worker processes cannot write to a cache directory. The administrator runs 'ps aux | grep nginx' and sees the master process owned by root and worker processes owned by 'www-data'. The nginx.conf file contains the line 'user www-data;'. What additional information does the administrator need to fully understand the user context?

   • AThe number of worker processes configured.
   • BThe compile-time default user of the NGINX binary.
   • CThe group that the worker processes run as.
   • DThe operating system's umask setting.
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   An administrator is migrating an NGINX configuration from a source-compiled installation to a distribution package (e.g., from source to the nginx.org repository). The old configuration had no 'user' directive, and the administrator wants to ensure the new installation behaves identically. What is the safest way to guarantee the same user context?

   • AAdd 'user nobody;' to the main context of the new configuration.
   • BRely on the default user of the distribution package.
   • CSet the user in the http block to 'nobody'.
   • DUse the 'worker_user' directive in the events block.
   Reveal Solution Discussion Select an answer first