Identify Start up Failures F5N4 Practice Questions (Page 4)

Questions 16–20

1. 16application · medium

   After a recent deployment, NGINX fails to start. The error log contains: `[emerg] open() "/etc/nginx/sites-enabled/example.com" failed (13: Permission denied)`. The file exists and `ls -l` shows `-rw-r----- 1 root www-data 512 Mar 12 10:00 example.com`. The master process runs as root. What is the most likely cause?

   • ASELinux or AppArmor is blocking NGINX from reading the file despite standard Unix permissions.
   • BThe file is owned by root and the group www-data, but the master process cannot read it because the file's group permissions are insufficient.
   • CThe worker process, not the master, is trying to read the file and lacks the necessary group membership.
   • DThe file is a symlink pointing to a non-existent target, causing the open() to fail with a permission error.
   Reveal Solution Discussion Select an answer first
2. 17application · medium

   An admin is troubleshooting a NGINX startup failure. The error log shows: `[emerg] getpwnam("nginx") failed (2: No such file or directory)`. What is the most likely cause?

   • AThe `worker_processes` setting is invalid, causing NGINX to fail to start.
   • BThe `error_log` directive points to a file that does not exist.
   • CThe `pid` file is missing, preventing NGINX from writing its process ID.
   • DThe `user` directive in nginx.conf specifies a username that does not exist on the system.
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   NGINX fails to start on a server with multiple network interfaces. The error log shows: `[emerg] bind() to 192.168.1.10:80 failed (99: Cannot assign requested address)`. The IP address 192.168.1.10 is not assigned to any interface. What is the most likely cause?

   • AThe `user` directive is set to a non-root user, preventing NGINX from binding to privileged ports.
   • BThe `worker_processes` setting is too high, preventing NGINX from binding to the interface.
   • CThe `listen` directive specifies an IP address that does not exist on any local interface.
   • DPort 80 is already in use by another process on that interface.
   Reveal Solution Discussion Select an answer first
5. 19foundation · easy

   An NGINX startup failure occurs. Where should an administrator look first to find the root cause?

   • AThe syslog
   • BThe error log
   • CThe systemd journal
   • DThe access log
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   NGINX fails to start on a server with a very high `worker_connections` setting. The error log shows: `[emerg] socket() failed (24: Too many open files)`. The admin has already verified that the configuration syntax is valid. What is the most direct fix?

   • AMove the `pid` file to a different directory with more space.
   • BDisable the `epoll` event model and use `select` instead.
   • CIncrease the system-wide file descriptor limit (e.g., `ulimit -n` or `LimitNOFILE` in the service unit).
   • DReduce the `worker_processes` directive to 1 to lower resource usage.
   Reveal Solution Discussion Select an answer first