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

Questions 1–5

1. 1foundation · easy

   An NGINX access log entry shows a request_time of 30.5 seconds for a request that returned a 200 status code. What does this indicate?

   • AThe request took 30.5 seconds to complete
   • BThe client's connection was closed after 30.5 seconds
   • CThe upstream server returned an error after 30.5 seconds
   • DThe DNS resolution took 30.5 seconds
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   An NGINX error log shows 'SSL_do_handshake() failed (SSL: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure) while SSL handshaking'. What does this entry indicate?

   • AThe upstream server is overloaded
   • BThe access log is misconfigured
   • CThe client's DNS resolution failed
   • DThe TLS handshake with the client failed
   Reveal Solution Discussion Select an answer first
4. 3expert · hard

   An NGINX server proxies to a backend application. The access log shows a mix of 200 and 502 status codes for the same endpoint. The error log shows 'connect() failed (111: Connection refused) while connecting to upstream' intermittently. The backend service is running and listening on port 8080. What is the MOST likely cause of the intermittent 502 errors?

   • AThe client is sending malformed requests that cause the backend to crash.
   • BThe proxy_read_timeout is set too low.
   • CThe NGINX server's worker_processes is set too low.
   • DThe backend server is restarting periodically, causing brief periods where the port is not accepting connections.
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   Which command-line tool is commonly used to test HTTP connectivity and view response headers from a client's perspective?

   • Atcpdump
   • Bnginx -t
   • Csystemctl status nginx
   • Dcurl
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A client reports that they receive a '400 Bad Request' error when accessing a website. The NGINX error log shows 'client sent invalid request line'. What is the MOST likely cause?

   • AThe client's DNS is resolving to the wrong server.
   • BThe server's SSL certificate is misconfigured.
   • CThe server's firewall is blocking the client's IP address.
   • DThe client is using an outdated HTTP/1.0 client that sends malformed request headers.
   Reveal Solution Discussion Select an answer first