Identify Start up Failures F5N4 Practice Questions (Page 1)

Questions 1–5

1. 1application · medium

   An admin runs `nginx -t` and receives: `nginx: [emerg] directive "server" is not terminated by ";" in /etc/nginx/nginx.conf:10`. What is the most likely cause?

   • AThe `server` directive is placed inside a `location` block, which is not allowed.
   • BThe `server` directive is missing a required argument, such as a port number.
   • CThe `server` directive is misspelled and should be `server_name`.
   • DThe `server` block is missing its opening or closing brace, causing the parser to expect a semicolon.
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   An admin fixes a port conflict by changing the `listen` directive from 80 to 8080. After running `nginx -t`, the output is `syntax is ok` and `test is successful`. The admin then runs `systemctl start nginx` and it succeeds. What is the most appropriate next step to verify the fix?

   • ARun `curl http://localhost:8080` to confirm NGINX is serving requests on the new port.
   • BRestart the server to ensure the configuration persists across reboots.
   • CCheck the error log for any new warnings about the port change.
   • DRun `nginx -s reload` to apply the configuration change without restarting.
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   Which system limit, when exhausted, can cause NGINX to fail with the error "Cannot allocate memory"?

   • AMemory limit
   • BProcess limit
   • CPort limit
   • DFile descriptor limit
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   NGINX fails to start. The error log shows: `[emerg] open() "/etc/nginx/mime.types" failed (2: No such file or directory)`. The file exists and is readable. What is the most likely cause?

   • AThe `mime.types` file is corrupted and cannot be parsed.
   • BThe `user` directive is set to a non-root user, preventing NGINX from reading the file.
   • CThe `mime.types` file is a symlink pointing to a non-existent target.
   • DThe `include` directive in nginx.conf points to a path that does not match the actual file location.
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   An admin is troubleshooting a NGINX startup failure. The error log shows: `[emerg] mmap(MAP_ANON|MAP_SHARED, 1073741824) failed (12: Cannot allocate memory)`. The server has 2 GB of RAM and 1 GB of swap. What is the most likely cause?

   • AThe `pid` file is located on a filesystem with insufficient space, preventing NGINX from writing its process ID.
   • BThe `worker_connections` setting is too high, causing NGINX to allocate excessive shared memory for connection tracking.
   • CThe system is out of memory, and the kernel cannot allocate the requested shared memory segment.
   • DThe `worker_processes` setting is too high, causing NGINX to request more shared memory than the system can provide.
   Reveal Solution Discussion Select an answer first