An administrator runs `nginx -t` and receives the output: "nginx: [emerg] unknown directive \"server_name\" in /etc/nginx/nginx.conf:12". What does this indicate?

The `server_name` directive is deprecated and should be removed.

The directive `server_name` is not valid in the context where it appears.

The configuration file is missing a closing brace.

The `server_name` directive requires a value.

NGINX fails to start. The error log shows: `[emerg] open() "/etc/nginx/ssl/example.com.key" failed (13: Permission denied)`. The file is owned by `root:ssl-cert` with permissions `640`. The master process runs as root. What is the most likely cause?

The `user` directive in the main configuration is set to a non-root user, preventing the master from reading the file.

SELinux or AppArmor is blocking NGINX from reading the key file despite standard Unix permissions.

The file is on a filesystem mounted with the `noexec` option, preventing NGINX from reading the key.

The file is a symlink pointing to a location that does not exist.

NGINX fails to start on a server that also runs a custom application bound to a Unix domain socket. The error log shows: `[emerg] bind() to unix:/var/run/app.sock failed (98: Address already in use)`. What is the most appropriate action?

Increase the `worker_processes` value to allow more workers to bind to the socket.

Delete the socket file `/var/run/app.sock` and restart NGINX.

Stop the custom application that is using the socket, or configure NGINX to use a different socket path.

Change the `user` directive to run NGINX as the same user as the custom application.

F5Certified Administrator NGINX - Troubleshooting

Domain 2Objective 2

Identify Start up Failures F5N4 Practice Questions (Page 3)

Part of the Troubleshoot basic use cases domain, which makes up ~60% of our current practice bank. F5 does not publish an official question count, but from its 30-minute exam (~10–20 total, ~6–12 in this domain), expect 1–2 from this objective — we provide 26 practice questions to prepare you well beyond it. (estimate)

26questions here

6free pages

7concepts

Questions 11–15

11foundation · easy
An administrator runs `nginx -t` and receives the output: "nginx: [emerg] unknown directive \"server_name\" in /etc/nginx/nginx.conf:12". What does this indicate?
Select an answer first
12application · medium
NGINX fails to start. The error log shows: `[emerg] open() "/etc/nginx/ssl/example.com.key" failed (13: Permission denied)`. The file is owned by `root:ssl-cert` with permissions `640`. The master process runs as root. What is the most likely cause?
Select an answer first
13foundation · easy
Which command can be used to identify which process is listening on a specific port, such as port 80?
Select an answer first
14application · medium
NGINX fails to start on a server that also runs a custom application bound to a Unix domain socket. The error log shows: `[emerg] bind() to unix:/var/run/app.sock failed (98: Address already in use)`. What is the most appropriate action?
Select an answer first
15foundation · easy
An NGINX startup fails because the configuration file has a syntax error. After fixing the error, which command should be run to verify that NGINX can start successfully?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to F5N4

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by F5. “F5N4” is a trademark of its owner, used for identification only.

Identify Start up Failures F5N4 Practice Questions (Page 3)

Questions 11–15

An administrator runs `nginx -t` and receives the output: "nginx: [emerg] unknown directive \"server_name\" in /etc/nginx/nginx.conf:12". What does this indicate?

NGINX fails to start. The error log shows: `[emerg] open() "/etc/nginx/ssl/example.com.key" failed (13: Permission denied)`. The file is owned by `root:ssl-cert` with permissions `640`. The master process runs as root. What is the most likely cause?

Which command can be used to identify which process is listening on a specific port, such as port 80?

NGINX fails to start on a server that also runs a custom application bound to a Unix domain socket. The error log shows: `[emerg] bind() to unix:/var/run/app.sock failed (98: Address already in use)`. What is the most appropriate action?

An NGINX startup fails because the configuration file has a syntax error. After fixing the error, which command should be run to verify that NGINX can start successfully?

Keep studying — Troubleshoot basic use cases