A DevOps engineer needs to apply a new SSL certificate path in the NGINX config. The site is a critical API with strict uptime requirements. What is the most appropriate action?

Run `nginx -s quit`, replace the certificate, then start NGINX.

Edit the config and run `nginx -t` to apply the changes.

Replace the certificate file, then run `nginx -s reload`.

Run `nginx -s stop`, replace the certificate file, then start NGINX.

What is the primary difference between reloading NGINX and performing a stop/start?

Reload and stop/start are functionally identical; both interrupt service briefly.

Reload is used only for changing SSL certificates; stop/start is used for all other configuration changes.

Reload requires a full system reboot; stop/start only restarts the worker processes.

Reload applies configuration changes without interrupting service; stop/start terminates and restarts the process, causing downtime.

An administrator needs to apply a change to the NGINX configuration with minimal impact on active connections. Which action should they choose?

Stop NGINX and then start it again

Restart the server's operating system

An admin changes the `worker_connections` directive from 1024 to 2048 and runs `nginx -s reload`. A few minutes later, they notice that some old worker processes are still running. What is the most likely reason?

The `worker_connections` change requires a full restart to take effect.

The new workers failed to start, so the old ones were kept as a fallback.

The old workers are still handling long-lived connections that have not yet closed.

The reload failed, and the old workers were never signaled to shut down.

Which situation calls for a reload rather than a stop/start?

The system administrator wants to clear all active connections immediately

A new module has been compiled into the NGINX binary

NGINX is completely unresponsive and must be forcibly terminated

Changing the worker_processes directive from 4 to 8

F5Certified Administrator NGINX - Troubleshooting

Domain 1Objective 2

Describe the Difference Between a Reload and a Stop/start F5N4 Practice Questions (Page 2)

Part of the Demonstrate how to stop, start, and reload NGINX binary domain, which makes up ~22% of our current practice bank. F5 does not publish an official question count, but from its 30-minute exam (~10–20 total, ~2–4 in this domain), expect 1–1 from this objective — we provide 20 practice questions to prepare you well beyond it. (estimate)

20questions here

4free pages

4concepts

Questions 6–10

6application · medium
A DevOps engineer needs to apply a new SSL certificate path in the NGINX config. The site is a critical API with strict uptime requirements. What is the most appropriate action?
Select an answer first
7foundation · easy
What is the primary difference between reloading NGINX and performing a stop/start?
Select an answer first
8foundation · easy
An administrator needs to apply a change to the NGINX configuration with minimal impact on active connections. Which action should they choose?
Select an answer first
9expert · hard
An admin changes the `worker_connections` directive from 1024 to 2048 and runs `nginx -s reload`. A few minutes later, they notice that some old worker processes are still running. What is the most likely reason?
Select an answer first
10foundation · easy
Which situation calls for a reload rather than a stop/start?
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.