Spring Boot Actuator

Question Variations

"How do you expose health checks safely?"
"What is the difference between readiness and liveness?"
"Why should management endpoints be restricted?"

Why This Is Asked

Actuator questions assess whether a developer designs a service that can be monitored and operated in production.

Key Concepts

Actuator exposes health, metrics, and management endpoints.
Endpoint exposure and access must be configured deliberately.
Liveness and readiness groups support orchestrated deployments.
Health details can reveal sensitive topology if exposed broadly.

Question Variations

“How do you expose health checks safely?”
“What is the difference between readiness and liveness?”
“Why should management endpoints be restricted?”

Answers by Technology

+ Add Variant

Spring BootImprove this answer ✏️

Expected Answer (Spring Boot 4.1.0 / Java 17+)

Spring Boot Actuator provides production endpoints for health, metrics, and application information. Expose only the endpoints operators need and restrict access because environment, health details, and configuration can reveal sensitive information. Use liveness to answer whether the process should be restarted and readiness to answer whether it should receive traffic; make readiness fail while a service is initializing or draining.

Why It Matters

Actuator makes services observable and deployable, but careless endpoint exposure increases attack surface.

Code Example

management:
  endpoints:
    web:
      exposure:
        include: health,info,prometheus
  endpoint:
    health:
      probes:
        enabled: true

Common Mistakes

Exposing every management endpoint publicly: Operational details can leak.
Using readiness as a deep unbounded dependency scan: It can amplify outages.

Follow-up Questions

What does readiness control? (Answer: Whether an instance should receive traffic.)
Why restrict Actuator? (Answer: Management data can be security-sensitive.)