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

Questions 16–20

1. 16foundation · easy

   Which NGINX directive enables debug-level logging to trace connection issues?

   • Aerror_log /var/log/nginx/error.log debug;
   • Bworker_processes 4;
   • Caccess_log /var/log/nginx/access.log main;
   • Dkeepalive_timeout 65;
   Reveal Solution Discussion Select an answer first
2. 17foundation · easy

   An NGINX access log entry shows a status code of 502 for a request. What does this status code indicate?

   • AGateway Timeout
   • BBad Gateway
   • CService Unavailable
   • DNot Found
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   An NGINX error log contains the entry: 'no live upstreams while connecting to upstream'. What is the MOST likely cause of this error?

   • AThe client's connection is being reset by the firewall.
   • BThe proxy_pass directive is pointing to an invalid URL.
   • CAll servers in the upstream group are marked as down or have failed health checks.
   • DThe DNS resolution for the upstream hostname is failing.
   Reveal Solution Discussion Select an answer first
5. 19application · medium

   An NGINX error log contains the entry: 'upstream timed out (110: Connection timed out) while reading response header from upstream'. What is the MOST appropriate configuration change to address this issue?

   • AIncrease the proxy_read_timeout directive for the affected location.
   • BIncrease the client_body_timeout directive.
   • CIncrease the worker_connections directive.
   • DIncrease the keepalive_timeout directive.
   Reveal Solution Discussion Select an answer first
6. 20expert · hard

   An NGINX error log shows the following entry: 'upstream prematurely closed connection while reading response header from upstream'. The upstream server is a PHP-FPM service. What is the MOST likely cause of this error?

   • AThe PHP-FPM process crashed or timed out while processing the request.
   • BThe proxy_read_timeout is set too low.
   • CThe NGINX server's worker_processes is set too low.
   • DThe client closed the connection before NGINX could send the response.
   Reveal Solution Discussion Select an answer first