Health check pattern in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of a health check in microservices?

In a microservices architecture, why do we implement health checks?

A To automatically update the service's code

B To increase the service's processing speed

C To store user data securely

D To monitor if a service is running and responsive

💡 Hint

Think about what helps keep the system reliable by knowing if parts are working.

Health checks help detect if a service is alive and able to respond, which is crucial for system reliability.

❓ Architecture

intermediate

Which component typically performs health checks in a microservices system?

In a microservices setup, who usually initiates health checks to verify service status?

A The service itself periodically checks its own health

B An external monitoring system or load balancer

C The database server connected to the service

D The client application making requests

💡 Hint

Consider who needs to know if a service is healthy to route traffic properly.

External systems like load balancers or monitoring tools perform health checks to decide if a service should receive traffic.

❓ scaling

advanced

How does health check frequency affect system scalability?

What is the impact of setting very frequent health checks on a microservices system?

A It can increase network and CPU load, potentially reducing scalability

B It reduces the number of service instances needed

C It has no impact on system resources or scalability

D It always improves scalability by detecting failures faster

💡 Hint

Think about how often checking status uses resources.

Very frequent health checks increase resource usage, which can reduce the system's ability to scale efficiently.

❓ tradeoff

advanced

What is a tradeoff when choosing between simple and deep health checks?

Choosing between a simple ping check and a deep check (database, dependencies) involves what tradeoff?

A Deep checks never fail; simple checks cause false alarms

B Simple checks always detect all failures; deep checks are unnecessary

C Simple checks are faster but may miss hidden failures; deep checks are slower but more accurate

D There is no difference; both provide the same information

💡 Hint

Consider speed versus thoroughness.

Simple checks quickly confirm if a service responds but may miss internal issues. Deep checks take longer but verify full functionality.

❓ estimation

expert

Estimate the network overhead of health checks in a system with 1000 services checking every 30 seconds

Each health check request and response is 1 KB. How much network data is used per minute by all services combined?

A 2000 KB per minute

B 200 KB per minute

C 120 KB per minute

D 100 KB per minute

💡 Hint

Calculate requests per minute and multiply by data size.

Each service sends 2 checks per minute (60/30). 1000 services × 2 checks × 1 KB (request + response) = 2000 KB per minute.