In Data Foundations, "Insight" is about using health metrics to understand whether the CMDB is trustworthy and operationally usable. The CMDB Health Dashboard organizes health into scorecards that group related checks. When leadership asks for Duplicate CIs, Orphan CIs, and Stale CIs, they are asking about the CMDB' s ongoing hygiene and adherence to governance expectations-not simply whether fields are filled in.
These three metrics align best with Compliance because they represent whether CI records comply with rules that keep the CMDB clean and current over time:
* Duplicate CIs indicate the identification and governance controls are not consistently preventing multiple records for the same real-world item.
* Orphan CIs indicate relationship governance gaps-records exist without expected relationships or context, reducing their operational value and often signaling incomplete ingestion or lifecycle control issues.
* Stale CIs indicate lifecycle management gaps-records are not being updated, attested, retired, or archived appropriately, which increases risk and noise in operational processes.
By contrast, Completeness focuses on whether required attributes are populated (owners, support group, environment, etc.). Correctness focuses on whether values and relationships are accurate and logically valid.
While duplicates/orphans/stale can affect correctness indirectly, the dashboard's grouping for these hygiene and lifecycle-oriented measures is best represented by Compliance, which is why B is the correct answer.