An NGINX access log shows a request with a status code of 200 and a request_time of 30 seconds. The upstream_response_time is 0.5 seconds. The client is on a slow mobile network. What is the MOST likely cause of the high request_time?

The NGINX server is overloaded and queuing requests.

The DNS resolution for the upstream hostname is slow.

The response body is large, and the client's slow network is taking a long time to receive it.

The upstream server is slow to process the request.

Users report slow page loads. The NGINX access log shows a request with a status code of 200 and a request_time of 12.5 seconds. The upstream_response_time is 0.2 seconds. What does this indicate?

The DNS resolution for the client's hostname is slow.

The client is taking a long time to send the request body or receive the response.

The upstream server is slow to process the request.

The NGINX server is overloaded and queuing requests.

A customer reports intermittent 'connection reset' errors when accessing a web application through NGINX. The NGINX error log shows 'SSL_do_handshake() failed while SSL handshaking' entries. Which tool should you use FIRST to determine whether the issue is client-side TLS negotiation or an upstream server problem?

Review the NGINX configuration for the 'ssl_protocols' directive.

Run tcpdump on the NGINX server's external interface and inspect the TLS ClientHello and ServerHello packets.

Use curl with the '--tlsv1.2' flag from the NGINX server to the upstream.

Check the upstream server's access log for the client's IP address.

F5Certified Administrator NGINX - Troubleshooting

Domain 2Objective 7

Describe How to Troubleshoot Client and Server Connections 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 20 practice questions to prepare you well beyond it. (estimate)

20questions here

4free pages

5concepts

Questions 11–15

11expert · hard
An NGINX access log shows a request with a status code of 200 and a request_time of 30 seconds. The upstream_response_time is 0.5 seconds. The client is on a slow mobile network. What is the MOST likely cause of the high request_time?
Select an answer first
12application · medium
Users report slow page loads. The NGINX access log shows a request with a status code of 200 and a request_time of 12.5 seconds. The upstream_response_time is 0.2 seconds. What does this indicate?
Select an answer first
13foundation · easy
An NGINX administrator notices that clients receive a 504 Gateway Timeout error. Which server-side issue is most likely causing this?
Select an answer first
14application · medium
A customer reports intermittent 'connection reset' errors when accessing a web application through NGINX. The NGINX error log shows 'SSL_do_handshake() failed while SSL handshaking' entries. Which tool should you use FIRST to determine whether the issue is client-side TLS negotiation or an upstream server problem?
Select an answer first
15foundation · easy
A client reports intermittent connection failures when accessing a website. The client's browser shows a 'This site can't be reached' error, but the server is healthy. Which client-side issue is most likely causing this symptom?
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.

Describe How to Troubleshoot Client and Server Connections F5N4 Practice Questions (Page 3)

Questions 11–15

An NGINX access log shows a request with a status code of 200 and a request_time of 30 seconds. The upstream_response_time is 0.5 seconds. The client is on a slow mobile network. What is the MOST likely cause of the high request_time?

Users report slow page loads. The NGINX access log shows a request with a status code of 200 and a request_time of 12.5 seconds. The upstream_response_time is 0.2 seconds. What does this indicate?

An NGINX administrator notices that clients receive a 504 Gateway Timeout error. Which server-side issue is most likely causing this?

A client reports intermittent connection failures when accessing a website. The client's browser shows a 'This site can't be reached' error, but the server is healthy. Which client-side issue is most likely causing this symptom?

Keep studying — Troubleshoot basic use cases