An NGINX reverse proxy occasionally returns 504 Gateway Timeout for long-running API requests. The upstream application is healthy and responds within 60 seconds. The NGINX configuration has proxy_read_timeout set to 30 seconds. What should you do?

Increase proxy_read_timeout to 90 seconds to allow the upstream more time to respond.

Increase proxy_send_timeout to 90 seconds to allow more time for sending the request to the upstream.

Set proxy_connect_timeout to 90 seconds to allow more time for the initial connection.

Disable proxy_buffering to allow responses to stream directly to the client.

A user reports receiving a 403 Forbidden error when accessing a static file served by NGINX. The file exists and the URI is correct. What is the most likely cause?

The server is experiencing high load and cannot process the request.

The requested file has been moved to a different location.

The client's IP address is not allowed by the server's firewall.

The file permissions do not allow NGINX to read the file.

An NGINX server is returning 500 Internal Server Error for requests to a PHP application. The NGINX error log shows: 'connect() failed (111: Connection refused) while connecting to upstream' for the PHP-FPM socket. What is the most likely cause?

The fastcgi_read_timeout is set too low. Increase the fastcgi_read_timeout value.

The client's request is too large, exceeding the client_max_body_size. Increase the client_max_body_size directive.

The PHP application has a syntax error in its code. Fix the PHP code syntax.

The PHP-FPM service is not running or is not listening on the configured socket. Start the PHP-FPM service or correct the fastcgi_pass directive.

An NGINX server is returning 500 Internal Server Error for a specific URL. The error log shows: 'upstream sent too big header while reading response header from upstream'. The upstream application is healthy. What is the most likely cause?

The proxy_read_timeout is set too low, causing NGINX to close the connection. Increase the proxy_read_timeout value.

The upstream is sending response headers that exceed NGINX's proxy_buffer_size. Increase the proxy_buffer_size directive.

The client's request is too large, exceeding the client_max_body_size. Increase the client_max_body_size directive.

The upstream server is returning a malformed response. Fix the upstream application's code.

F5Certified Administrator NGINX - Troubleshooting

Domain 2Objective 3

Describe How to Deal with HTTP Error Codes F5N4 Practice Questions (Page 4)

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 22 practice questions to prepare you well beyond it. (estimate)

22questions here

5free pages

5concepts

Questions 16–20

16application · medium
An NGINX reverse proxy occasionally returns 504 Gateway Timeout for long-running API requests. The upstream application is healthy and responds within 60 seconds. The NGINX configuration has proxy_read_timeout set to 30 seconds. What should you do?
Select an answer first
17foundation · easy
A user reports receiving a 403 Forbidden error when accessing a static file served by NGINX. The file exists and the URI is correct. What is the most likely cause?
Select an answer first
18foundation · easy
Which of the following HTTP status codes is a 4xx client error?
Select an answer first
19application · medium
An NGINX server is returning 500 Internal Server Error for requests to a PHP application. The NGINX error log shows: 'connect() failed (111: Connection refused) while connecting to upstream' for the PHP-FPM socket. What is the most likely cause?
Select an answer first
20application · medium
An NGINX server is returning 500 Internal Server Error for a specific URL. The error log shows: 'upstream sent too big header while reading response header from upstream'. The upstream application is healthy. What is the most likely cause?
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.