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

Questions 11–15

1. 11foundation · easy

   A client receives an HTTP response with a status code of 503. Which category of HTTP error codes does this status code belong to?

   • A3xx redirection
   • B1xx informational
   • C4xx client error
   • D5xx server error
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   An NGINX server is returning 403 Forbidden errors for a specific location. The administrator wants to allow access only from a specific IP address range. Which configuration directive would be used to enforce this access control?

   • Alisten directive
   • Ballow and deny directives
   • Cproxy_pass directive
   • Dclient_max_body_size directive
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   An NGINX server is returning 504 Gateway Timeout errors because upstream requests take longer than the default timeout. Which configuration change would resolve this issue?

   • AIncrease the proxy_read_timeout directive in the location or server block.
   • BSet the client_max_body_size directive to a larger value.
   • CEnable the gzip directive.
   • DDecrease the proxy_connect_timeout directive.
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   An NGINX server returns a 429 Too Many Requests error to a client. What is the most appropriate troubleshooting step?

   • AVerify that the requested file exists on the server.
   • BCheck the upstream server's health and connectivity.
   • CReview the server's SSL certificate configuration.
   • DCheck the NGINX rate-limiting configuration and the client's request rate.
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   An NGINX reverse proxy is returning 502 Bad Gateway for all requests to a specific upstream service. The NGINX error log shows: 'connect() failed (111: Connection refused) while connecting to upstream'. The upstream service is running and listening on port 8080. What is the most likely cause?

   • AThe proxy_pass directive points to the wrong port, such as 8081 instead of 8080. Update the proxy_pass URL to the correct port.
   • BThe proxy_read_timeout is set too low, causing NGINX to give up waiting for a response. Increase the proxy_read_timeout value.
   • CThe upstream service is returning a 500 Internal Server Error. Restart the upstream service to clear the error state.
   • DThe client's request is malformed, causing NGINX to reject it. Fix the client application's request format.
   Reveal Solution Discussion Select an answer first