Health checks in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Nginx active health check status output

You have configured an active health check in Nginx for your backend servers. Which command output snippet correctly shows that the backend server is healthy?

Nginx

curl -s http://localhost/nginx_status | grep 'upstream server'

A upstream server backend1 is UP

B upstream server backend1 is DOWN

C upstream server backend1 is UNKNOWN

D upstream server backend1 is TIMEOUT

💡 Hint

Look for the status that indicates the server is responding correctly.

The active health check reports the backend server status. 'UP' means the server is healthy and responding.

❓ Configuration

intermediate

Correct Nginx passive health check directive

Which Nginx configuration snippet correctly enables passive health checks for an upstream named app_servers?

A

upstream app_servers {
    server 192.168.1.10;
    server 192.168.1.11;
    health_check;
}

B

upstream app_servers {
    server 192.168.1.10 max_fails=3 fail_timeout=30s;
    server 192.168.1.11 max_fails=3 fail_timeout=30s;
}

C

upstream app_servers {
    server 192.168.1.10;
    server 192.168.1.11;
    passive_check;
}

D

upstream app_servers {
    server 192.168.1.10;
    server 192.168.1.11;
    passive_health_check on;
}

💡 Hint

Passive health checks use max_fails and fail_timeout parameters.

Passive health checks in Nginx are controlled by max_fails and fail_timeout on server directives. The health_check directive enables active checks, not passive.

❓ Troubleshoot

advanced

Diagnosing failed active health checks in Nginx

You configured active health checks in Nginx but all backend servers show as DOWN. Which of the following is the most likely cause?

A The health check URI path is incorrect or returns a non-200 status

B The upstream servers are overloaded but still respond with 200 OK

C The passive health check parameters max_fails and fail_timeout are missing

D The Nginx worker_processes is set to 1

💡 Hint

Active health checks depend on a correct URI and response status.

Active health checks send requests to a specific URI. If the URI is wrong or the server returns an error status, Nginx marks the server as DOWN.

🔀 Workflow

advanced

Order of steps to enable active health checks in Nginx

Arrange the steps in the correct order to enable active health checks for an upstream in Nginx.

A 2,1,4,3

B 4,1,2,3

C 1,2,4,3

D 1,4,2,3

💡 Hint

You must define servers before adding health checks and reload last.

First define servers, then configure health check details, add the directive, and finally reload Nginx.

✅ Best Practice

expert

Best practice for health check intervals in production

What is the best practice for setting the interval of active health checks in a high-traffic production Nginx environment?

A Set a very long interval (5 minutes) to reduce load on backend servers

B Disable active health checks and rely only on passive checks

C Set a moderate interval (10-30 seconds) balancing detection speed and load

D Set a very short interval (1 second) to detect failures immediately

💡 Hint

Consider backend load and failure detection speed.

Too frequent checks increase load; too infrequent delay failure detection. A moderate interval balances both.