Health checks in Nginx - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a basic HTTP health check location in nginx.

Nginx

location /healthz {
    return [1];
}

Drag options to blanks, or click blank then click option'

A404

B301

C200

D500

Attempts:

3 left

💡 Hint

Common Mistakes

Using 404 or 500 which indicate errors.

Using 301 which is a redirect, not a health check response.

The return 200; directive sends a simple HTTP 200 OK response, which is commonly used for health checks.

2fill in blank

medium

Complete the code to enable active health checks for an upstream server in nginx.

Nginx

upstream backend {
    server backend1.example.com;
    [1];
}

Drag options to blanks, or click blank then click option'

Aenable_health

Bcheck_health

Cactive_check

Dhealth_check

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect directive names like check_health or active_check.

Forgetting to add the directive inside the upstream block.

The health_check; directive enables active health checks on the upstream servers.

3fill in blank

hard

Fix the error in the health check configuration by completing the directive correctly.

Nginx

server {
    location /health {
        proxy_pass http://backend;
        proxy_next_upstream [1];
    }
}

Drag options to blanks, or click blank then click option'

Aon

Boff

Cerror

Dfail

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'on' which enables retries and can hide failures.

Using invalid values like 'error' or 'fail'.

The proxy_next_upstream off; directive disables retrying the next upstream server on failure, which is often desired for health check endpoints to get accurate status.

4fill in blank

hard

Fill both blanks to configure a passive health check that marks a server down after 3 failures.

Nginx

upstream backend {
    server backend1.example.com max_fails=[1] fail_timeout=[2];
}

Drag options to blanks, or click blank then click option'

A3

B5s

C10s

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Using too low max_fails like 1 which may mark server down too quickly.

Using fail_timeout without 's' suffix or with wrong units.

max_fails=3 means the server is marked down after 3 failed attempts. fail_timeout=10s sets the time period to consider those failures.

5fill in blank

hard

Fill all three blanks to configure an HTTP health check with interval, timeout, and HTTP status match.

Nginx

health_check interval=[1] timeout=[2] rise=2 fall=5 http_statuses=[3];

Drag options to blanks, or click blank then click option'

A5s

B2s

C200-299

D10s

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up interval and timeout values.

Using invalid HTTP status ranges.

The interval=5s sets how often to check. timeout=2s sets how long to wait for a response. http_statuses=200-299 defines which HTTP codes mean healthy.

Practice

1. What is the main purpose of a health check in an nginx setup?

easy

A. To increase the server's CPU speed

B. To verify if a server is ready to handle requests

C. To change the server's IP address automatically

D. To backup server files regularly

Solution

1. Step 1: Understand health check concept

   Health checks are used to confirm if a server is ready and able to serve requests.

2. Step 2: Identify the purpose in nginx context

   In nginx, health checks help route traffic only to servers that respond correctly, ensuring reliability.

3. Final Answer:

   To verify if a server is ready to handle requests -> Option B

4. Quick Check:

   Health check purpose = Verify readiness [OK]

Hint: Health checks confirm server readiness to serve requests [OK]

Common Mistakes:

• Thinking health checks speed up the server
• Confusing health checks with backups
• Assuming health checks change server IP

2. Which of the following is the correct way to define a simple health check endpoint in nginx configuration?

easy

A. location /healthcheck { return 200 "OK"; }

B. location /healthcheck { proxy_pass http://backend; }

C. location /healthcheck { error_page 404 /404.html; }

D. location /healthcheck { deny all; }

Solution

1. Step 1: Review nginx location syntax for health check

   A simple health check returns a 200 status with a message like 'OK'.

2. Step 2: Identify correct return directive

   location /healthcheck { return 200 "OK"; } uses return 200 "OK"; which correctly sends a success response for health checks.

3. Final Answer:

   location /healthcheck { return 200 "OK"; } -> Option A

4. Quick Check:

   Simple health check = return 200 [OK]

Hint: Health check returns 200 with OK message [OK]

Common Mistakes:

• Using proxy_pass instead of return for simple checks
• Setting error_page instead of success response
• Denying access blocks health check

3. Given this nginx config snippet, what will be the HTTP status code when accessing /health?

location /health {
  return 204;
}

medium

A. 204

B. 404

C. 500

D. 200

Solution

1. Step 1: Understand the return directive in nginx

   The return 204; sends an HTTP status code 204 (No Content) response.

2. Step 2: Match the status code with the request

   Accessing /health triggers this location and returns 204 as configured.

3. Final Answer:

   204 -> Option A

4. Quick Check:

   return 204 sends status 204 [OK]

Hint: return 204 sends HTTP 204 No Content status [OK]

Common Mistakes:

• Assuming default 200 status without checking return
• Confusing 204 with 404 or 500 errors
• Ignoring the explicit return directive

4. You configured this health check in nginx:

location /healthcheck {
  return 200 "OK"
}

But the health check fails with a syntax error. What is the problem?

medium

A. The return directive cannot include a message string

B. The return code 200 is invalid

C. The location block is missing a semicolon after return

D. The location path must be /health, not /healthcheck

Solution

1. Step 1: Check nginx configuration syntax

   All nginx directives must end with a semicolon (;).

2. Step 2: Locate the error in the snippet

   The return 200 "OK" line is missing the trailing semicolon, causing a syntax error.

3. Final Answer:

   The location block is missing a semicolon after return -> Option C

4. Quick Check:

   nginx directives require semicolon [OK]

Hint: Every nginx directive must end with a semicolon [OK]

Common Mistakes:

• Adding message string directly after return
• Missing semicolon causing syntax error
• Using wrong location path for health check

5. You want to configure nginx to perform active health checks on backend servers and mark them unhealthy if they fail. Which directive and module combination should you use?

hard

A. Use proxy_pass with proxy_next_upstream and enable ngx_http_healthcheck_module

B. Use deny all in location to block unhealthy servers

C. Use return 200 in location block for backend health

D. Use check directive inside upstream block with ngx_http_upstream_check_module

Solution

1. Step 1: Identify active health check method in nginx

   Active health checks require special modules like ngx_http_upstream_check_module and directives like check inside upstream blocks.

2. Step 2: Match correct directive and module

   Use check directive inside upstream block with ngx_http_upstream_check_module correctly pairs check directive with ngx_http_upstream_check_module for active health checks.

3. Final Answer:

   Use check directive inside upstream block with ngx_http_upstream_check_module -> Option D

4. Quick Check:

   Active health checks = check + upstream_check_module [OK]

Hint: Active health checks need check directive and module [OK]

Common Mistakes:

• Confusing passive proxy_next_upstream with active health checks
• Using return 200 for backend health checks
• Blocking servers instead of checking health