Completeness → Required
Compliance → Audit
Correctness → Orphan
The CMDB Health Dashboard helps administrators measure whether the CMDB is trustworthy, usable, and aligned with governance expectations. The three main CMDB Health KPIs are Completeness , Compliance , and Correctness , and each KPI evaluates a different aspect of CMDB data quality.
Completeness focuses on whether required or expected fields are populated on CI records. A CI may exist in the CMDB, but if important fields such as owner, support group, location, serial number, or environment are missing, the record is not complete enough to support operational processes. Therefore, Required belongs under Completeness .
Compliance focuses on whether CIs follow defined rules, policies, and governance requirements. The Audit sub-metric is associated with Compliance because audits check whether records meet expected standards and whether governance controls are being followed.
Correctness focuses on whether the CI data is accurate and logically valid. Orphan belongs under Correctness because an orphan CI lacks expected relationships or context. For example, a server without expected dependencies or service relationships may reduce the accuracy of impact analysis and operational reporting.
The other visible options, such as Stability , Suggested , and Certify , are not the best fit for the three answer slots shown in this question.
