How can the Health Indicator status severity order be changed?

Question

Options

• AUsing the @Primary annotation
• BUsing the @Ordered annotation
• CIt cannot be changed.
• DUsing the property management.health.status.order

• A
  5% (2)
• B
  2% (1)
• C
  2% (1)
• D
  90% (37)

Explanation

Option D is correct because Spring Boot exposes the management.health.status.order property specifically to let you define the severity precedence of health statuses (e.g., DOWN,OUT_OF_SERVICE,UNKNOWN,UP). The HealthAggregator reads this ordered list to determine the overall system health when multiple indicators report different statuses.

• A (@Primary) is wrong because @Primary resolves bean ambiguity in the Spring context - it has no concept of health status ordering.
• B (@Ordered) is wrong because @Ordered controls the execution order of beans in a chain, not the severity ranking of health statuses.
• C (cannot be changed) is wrong because Spring Boot intentionally makes this configurable to support custom status types beyond the built-in defaults.

Memory tip: Think of it as a management concern - you manage the health status priority through management.health.status.order, just like other actuator behavior lives under the management.* namespace.

No community discussion yet for this question.