Which two statements are correct regarding the Health Indicator status? (Choose two.)

Question

Options

• AThe last status in a sorted list of HealthIndicators is used to derive the final system health.
• BThe status with the least severity is used as the top-level status.
• CCustom status values can be created.
• DThe built-in status values are DOWN, OUT_OF_SERVICE, UNKNOWN, and UP in decreasing
• EThe severity order cannot be changed due to security reasons.

• A
  7% (3)
• B
  2% (1)
• C
  88% (37)
• E
  2% (1)

Explanation

C is correct because Spring Boot explicitly supports creating custom Status values - you can define any string-labeled status (e.g., new Status("DEGRADED")) and register it with a custom HealthAggregator, making the system extensible for application-specific health semantics.

D is correct because Spring Boot ships with exactly four built-in statuses - DOWN, OUT_OF_SERVICE, UNKNOWN, and UP - ordered by decreasing severity, meaning DOWN is the most severe and UP is the least.

A is wrong because the first (highest-severity) status in the sorted list drives the final system health, not the last - the aggregator surfaces the worst condition, not the best.

B is wrong for the same reason in reverse: the highest-severity status "wins" and becomes the top-level status, since the goal is to expose the most critical problem.

E is wrong because the severity order can be customized via the management.endpoint.health.status.order configuration property - security is not a factor here.

Memory tip: Think of health aggregation like a fire alarm - the loudest alarm (highest severity) is what gets reported, and you can always add custom alarm types (custom statuses) to the system.

No community discussion yet for this question.