Identify Start up Failures F5N4 Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   Which of the following is a common symptom of an NGINX startup failure?

   • AThe NGINX process starts and runs, but the configuration file is not being read.
   • BThe NGINX process starts and runs, but the access log shows many 404 errors.
   • CThe NGINX process starts and runs, but the error log shows repeated 'upstream timed out' messages.
   • DThe NGINX process exits immediately, and the error log contains a message about a missing file.
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   An admin runs `nginx -t` and receives: `nginx: [emerg] unexpected end of file, expecting ';' or '}' in /etc/nginx/nginx.conf:45`. The admin opens the file and sees that line 45 is the last line of the file and contains `}`. What is the most likely cause?

   • AThe file is missing a newline at the end, causing the parser to fail.
   • BThe file has a trailing whitespace character that confuses the parser.
   • CThe `}` on line 45 is not recognized because it is preceded by a semicolon.
   • DA missing closing brace in a block that started earlier, causing the parser to reach the end of the file unexpectedly.
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   Which command is used to test the NGINX configuration for syntax errors before restarting the service?

   • Anginx -s reload
   • Bnginx -c /etc/nginx/nginx.conf
   • Cnginx -t
   • Dnginx -v
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   NGINX fails to start. The error log shows: `[emerg] open() "/var/www/html/index.html" failed (2: No such file or directory)`. The file is referenced in the `root` directive of a server block. What is the most likely cause?

   • AThe `user` directive in the main configuration does not have permission to read the file.
   • BThe `server_name` directive does not match the requested host header.
   • CThe `root` directive points to a directory that does not exist, or the file was not deployed to the expected path.
   • DThe `index` directive is missing, so NGINX cannot find a default file to serve.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   An admin tries to start NGINX on a server where Apache is already listening on port 80. The error log shows: `[emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)`. What is the most appropriate corrective action?

   • ADelete the default server block that listens on port 80 and restart NGINX.
   • BIncrease the `worker_connections` value to allow more simultaneous connections on port 80.
   • CRun `nginx -s reload` to force NGINX to retry binding to port 80.
   • DChange the `listen` directive in the NGINX configuration to a different port, such as 8080.
   Reveal Solution Discussion Select an answer first