Identify Start up Failures F5N4 Practice Questions (Page 5)

Questions 21–25

1. 21foundation · easy

   Which of the following is a valid method to verify that NGINX has the correct permissions to access a file referenced in its configuration?

   • ARun `ls -l` on the file and check the permissions.
   • BRun `ps aux | grep nginx` to check permissions.
   • CRun `cat /etc/nginx/nginx.conf` to check permissions.
   • DRun `nginx -t` to check permissions.
   Reveal Solution Discussion Select an answer first
2. 22foundation · easy

   An NGINX startup fails with the error: "[emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)". What is the most likely cause?

   • AAnother process is already listening on port 80.
   • BThe system is out of memory.
   • CThe NGINX configuration has a syntax error.
   • DThe NGINX user does not have permission to bind to port 80.
   Reveal Solution Discussion Select an answer first
4. 23application · medium

   A junior admin runs `systemctl start nginx` on a fresh Ubuntu server and the service fails. The error log shows: `[emerg] unexpected end of file, expecting ';' or '}' in /etc/nginx/nginx.conf:12`. The admin runs `nginx -t` and sees the same message. What is the most likely cause and immediate next step?

   • APort 80 is already in use by another process; stop the conflicting service and restart NGINX.
   • BA missing semicolon or closing brace in the main configuration file; edit line 12 of nginx.conf to fix the syntax.
   • CThe configuration includes a file that does not exist; create the missing include file referenced near line 12.
   • DThe worker process lacks permission to read nginx.conf; change the file ownership to the nginx user.
   Reveal Solution Discussion Select an answer first
5. 24foundation · easy

   An NGINX startup fails with the error: "[emerg] socket() failed (24: Too many open files)". What is the most likely cause?

   • AThe NGINX configuration has a syntax error.
   • BThe NGINX user does not have permission to create sockets.
   • CThe system is out of memory.
   • DThe system has reached its file descriptor limit.
   Reveal Solution Discussion Select an answer first
6. 25foundation · easy

   An NGINX startup fails because another process is using port 80. Which corrective action would resolve the conflict?

   • AIncrease the file descriptor limit.
   • BReboot the system.
   • CStop the conflicting process or change NGINX's listen port.
   • DRun `nginx -t` to fix the configuration.
   Reveal Solution Discussion Select an answer first