Spring Boot Monitoring with Actuator 4

Question 1

What is the default behavior of the /actuator/health endpoint when detail is not explicitly configured?

Accepted Answer

Returns only the overall status without component details to unauthenticated callers

Answer

By default, health details are only shown to authorized users; anonymous requests see only the top-level status.

Question 2

Which Actuator endpoint exposes the current values of all @ConfigurationProperties beans?

Accepted Answer

/actuator/configprops

Answer

The /actuator/configprops endpoint lists all @ConfigurationProperties beans and their current effective values.

Question 3

How does Spring Boot Actuator integrate with Micrometer for JVM memory metrics?

Accepted Answer

JvmMemoryMetrics is auto-configured and registers gauges for heap and non-heap memory

Answer

Spring Boot auto-configures JvmMemoryMetrics which registers jvm.memory.used, jvm.memory.committed, and jvm.memory.max gauges automatically.

Question 4

What is the effect of setting management.endpoint.health.probes.enabled=true?

Accepted Answer

Enables the /actuator/health/liveness and /actuator/health/readiness sub-endpoints

Answer

Setting this property to true activates the liveness and readiness sub-endpoints for Kubernetes probe integration.

Question 5

Which interface should a component implement to participate in the readiness state of a Spring Boot application?

Accepted Answer

ApplicationListener<AvailabilityChangeEvent>

Answer

Components listen for AvailabilityChangeEvent<ReadinessState> to react to or influence the application's readiness state.

Spring Boot Practice Test