Health checks configuration in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the protocol used in the health check.

GCP

{
  "name": "basic-health-check",
  "type": "HTTP",
  "httpHealthCheck": {
    "port": 80,
    "requestPath": "/health",
    "protocol": "[1]"
  }
}

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

ASSL

BTCP

CHTTPS

DHTTP

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing TCP or SSL when the health check is HTTP-based.

Using HTTPS when the port is 80.

The protocol for this health check is HTTP, so the correct value is "HTTP".

2fill in blank

medium

Complete the code to set the check interval in seconds.

GCP

{
  "name": "custom-health-check",
  "checkIntervalSec": [1],
  "timeoutSec": 5
}

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

A10

B2

C30

D60

Attempts:

3 left

💡 Hint

Common Mistakes

Setting the interval too low like 2 seconds, causing unnecessary load.

Setting the interval too high like 60 seconds, causing slow detection.

The check interval is commonly set to 10 seconds for a balance between responsiveness and load.

3fill in blank

hard

Fix the error in the health check configuration by selecting the correct port number.

GCP

{
  "name": "tcp-health-check",
  "tcpHealthCheck": {
    "port": [1]
  }
}

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

A443

B80

C8080

D22

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 80 or 443 which are for HTTP/HTTPS, not TCP health checks.

Using port 22 which is for SSH, unrelated to health checks.

The TCP health check should target port 8080 where the service listens, not standard HTTP or SSH ports.

4fill in blank

hard

Fill both blanks to configure a health check with a 5-second timeout and 3 healthy threshold.

GCP

{
  "name": "advanced-health-check",
  "timeoutSec": [1],
  "healthyThreshold": [2]
}

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

A5

B3

C10

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing timeout with interval values.

Setting healthy threshold too low or too high.

The timeout is set to 5 seconds and the healthy threshold to 3 successful checks before marking healthy.

5fill in blank

hard

Fill all three blanks to create a health check that uses HTTPS, checks path '/status', and has an unhealthy threshold of 5.

GCP

{
  "name": "secure-health-check",
  "httpsHealthCheck": {
    "port": 443,
    "requestPath": "[1]",
    "protocol": "[2]"
  },
  "unhealthyThreshold": [3]
}

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

A/status

BHTTPS

C5

D/health

Attempts:

3 left

💡 Hint

Common Mistakes

Using HTTP protocol with port 443.

Using wrong request path like '/health' instead of '/status'.

Setting unhealthy threshold too low.

The health check uses HTTPS protocol, checks the '/status' path, and marks unhealthy after 5 failed checks.

Practice

1.

What is the main purpose of a health check in Google Cloud Platform?

easy

A. To increase server storage capacity

B. To monitor if servers are working properly

C. To speed up network traffic

D. To backup data automatically

Solution

1. Step 1: Understand health check function

   Health checks regularly test if servers respond correctly to requests.

2. Step 2: Identify main purpose

   This helps detect unhealthy servers so they can be fixed or replaced.

3. Final Answer:

   To monitor if servers are working properly -> Option B

4. Quick Check:

   Health check = Monitor server health [OK]

Hint: Health checks watch server health, not storage or speed [OK]

Common Mistakes:

• Confusing health checks with backups
• Thinking health checks increase speed
• Assuming health checks add storage

2.

Which of the following is the correct way to specify a TCP health check in a Google Cloud load balancer configuration?

{
  "type": "TCP",
  "port": 80,
  "checkIntervalSec": 5
}

easy

A. { "type": "TCP", "port": 80, "checkIntervalSec": 5 }

B. { "type": "HTTP", "port": 80, "checkIntervalSec": 5 }

C. { "type": "UDP", "port": 80, "checkIntervalSec": 5 }

D. { "type": "ICMP", "port": 80, "checkIntervalSec": 5 }

Solution

1. Step 1: Identify correct health check type

   TCP health checks use "type": "TCP" to test TCP connections on the port.

2. Step 2: Match correct JSON syntax

   The example matches the correct syntax with type TCP, port 80, and interval 5 seconds.

3. Final Answer:

   { "type": "TCP", "port": 80, "checkIntervalSec": 5 } -> Option A

4. Quick Check:

   TCP type with port 80 = { "type": "TCP", "port": 80, "checkIntervalSec": 5 } [OK]

Hint: TCP health check uses type "TCP" exactly [OK]

Common Mistakes:

• Using HTTP instead of TCP for TCP check
• Using unsupported types like UDP or ICMP
• Wrong JSON syntax or missing fields

3.

Given this health check configuration snippet, what will happen if the server does not respond within 10 seconds?

{
  "type": "HTTP",
  "port": 8080,
  "timeoutSec": 10,
  "unhealthyThreshold": 3
}

medium

A. The server is marked unhealthy after 3 failed checks

B. The server is immediately removed after 1 failed check

C. The server is marked healthy regardless of response time

D. The server is restarted after 10 seconds

Solution

1. Step 1: Understand timeout and threshold

   The timeoutSec of 10 means the check waits 10 seconds for a response before failing.

2. Step 2: Apply unhealthyThreshold logic

   The server must fail 3 consecutive checks to be marked unhealthy.

3. Final Answer:

   The server is marked unhealthy after 3 failed checks -> Option A

4. Quick Check:

   Timeout + 3 failures = unhealthy after 3 tries [OK]

Hint: Unhealthy threshold counts failures before marking unhealthy [OK]

Common Mistakes:

• Thinking server is removed immediately after 1 failure
• Ignoring unhealthyThreshold setting
• Assuming server restarts automatically

4.

Identify the error in this health check configuration snippet:

{
  "type": "HTTP",
  "port": "eighty",
  "requestPath": "/health",
  "checkIntervalSec": 5
}

medium

A. checkIntervalSec must be at least 10 seconds

B. requestPath cannot be used with HTTP type

C. Port must be a number, not a string

D. type "HTTP" is invalid

Solution

1. Step 1: Check port field type

   The port value is "eighty" as a string, but it must be a numeric value like 80.

2. Step 2: Validate other fields

   requestPath is valid for HTTP, checkIntervalSec can be 5, and type "HTTP" is correct.

3. Final Answer:

   Port must be a number, not a string -> Option C

4. Quick Check:

   Port number must be numeric [OK]

Hint: Port must be a number, not words [OK]

Common Mistakes:

• Using string instead of number for port
• Thinking requestPath is invalid for HTTP
• Assuming checkIntervalSec minimum is 10

5.

You want to configure a health check that verifies your web app responds with HTTP 200 on path /status every 15 seconds, and marks the server unhealthy after 2 failures. Which configuration is correct?

hard

A. { "type": "HTTP", "port": 8080, "requestPath": "/status", "checkIntervalSec": 15, "unhealthyThreshold": 2 }

B. { "type": "TCP", "port": 80, "requestPath": "/status", "checkIntervalSec": 15, "unhealthyThreshold": 2 }

C. { "type": "HTTP", "port": 80, "requestPath": "/health", "checkIntervalSec": 10, "unhealthyThreshold": 3 }

D. { "type": "HTTP", "port": 80, "requestPath": "/status", "checkIntervalSec": 15, "unhealthyThreshold": 2 }

Solution

1. Step 1: Match health check type and path

   The app uses HTTP checks on path "/status" so type must be "HTTP" and requestPath "/status".

2. Step 2: Verify timing and thresholds

   Check interval is 15 seconds and unhealthyThreshold is 2, matching requirements.

3. Step 3: Confirm port number

   Port 80 is standard for HTTP, so it fits the web app default.

4. Final Answer:

   { "type": "HTTP", "port": 80, "requestPath": "/status", "checkIntervalSec": 15, "unhealthyThreshold": 2 } -> Option D

5. Quick Check:

   HTTP + /status + 15s + 2 failures = { "type": "HTTP", "port": 80, "requestPath": "/status", "checkIntervalSec": 15, "unhealthyThreshold": 2 } [OK]

Hint: Match type, path, interval, and threshold exactly [OK]

Common Mistakes:

• Using TCP type for HTTP path
• Wrong requestPath or port
• Incorrect checkIntervalSec or unhealthyThreshold