Top 4 Actuator Interview Questions
Browse 4 real-world technical and behavioral interview questions about Actuator. Review scenarios, edge cases, and architectural best practices.
Your Spring Boot service needs 50 seconds to start and Kubernetes keeps killing it before it is ready. What do you change, and in which order?
First stop the kills: add a Kubernetes startup probe with a budget longer than the worst observed start, and point liveness and readiness at Actuator's separate health groups. Then measure where the 50 seconds goes before tuning, because lazy initialisation only moves the cost onto the first requests.
A property has one value in application.yml, another in production, and nobody can say where the production value comes from. How do you find out?
Ask the running application, not the files. Actuator's env endpoint queried for that property lists the property sources in precedence order with the value each holds, the first holder winning. Then trace it: an environment variable matched by relaxed binding, a profile file, a command-line argument or a JVM system property.
Security review asks which Actuator endpoints are exposed in production. What do you expose, to whom, and which one quietly leaks secrets?
Expose health to the platform, metrics to the scraper, and nothing else over HTTP without authentication, ideally on a separate management port. The quiet leak is heapdump: masking protects the env and configprops responses, but a heap dump holds every secret, token and customer record in memory unmasked.
How does Spring Boot auto-configuration decide what to create, and how do you override it?
Spring Boot auto-configuration loads candidate classes from AutoConfiguration.imports, applies conditional annotations, and backs off when your own beans or properties already define the needed behavior.