Govern
About 35% of the CIS-DF exam — see all 5 domains.
Governance is the largest domain, so lead with it.
CMDB Health aggregates three KPIs — Correctness, Completeness, and Compliance (the "3 C's") — built from six sub-metrics, plus a separate Relationships group:
| KPI | Sub-metrics | What they measure |
|---|---|---|
| Correctness | Orphan, Staleness, Duplicate | Orphan CIs (fail an orphan rule — e.g., missing required attributes and/or missing relationships); stale CIs (not updated within the staleness rule's effective duration, base default 60 days on cmdb_ci); duplicate CIs (detected via identification rules) |
| Completeness | Required, Recommended | CIs missing mandatory (dictionary-mandatory) fields; CIs missing fields flagged as recommended |
| Compliance | Audit | CIs that fail their CMDB audits |
A separate Relationship Health dimension scores orphan/stale/duplicate relationships and relations not compliant with suggested/containment/hosting rules. Per the docs, the overall CMDB Health score aggregates only the three KPIs (Correctness, Completeness, Compliance) by their scorecard weights — Relationship Health is reported separately and does NOT roll into the overall score. All of this surfaces on the CMDB Health Dashboard and the CMDB / CSDM Data Foundations Dashboards, supporting KPIs and Critical Success Factors (CSFs).
Precision note: they are three KPIs composed of six sub-metrics — not "six metrics across three dashboards." Dashboards (Health, service, group, CI, Data Foundations) are a separate UI layer.
CMDB Data Manager is a policy-driven framework for bulk CI life-cycle operations — specifically deletion, archival, and attestation — at scale, rather than ad hoc record-by-record cleanup. Key ideas:
- Policies define a lifecycle action and the conditions under which it runs (e.g., archive CIs not updated in N days). On a scenario question, match the goal (e.g., "remove CIs not seen in 90 days") to the correct Data Manager policy.
- Principal classes — a real CMDB concept (there is a Principal Class filter) for the meaningful top-level classes an organization actively manages. Policies and reporting are scoped to principal classes so governance focuses on what matters instead of every class.
Deduplication: duplicates arise when the same real-world item is created by multiple sources or with insufficient identification data, so the IRE cannot match them. The IRE/Health create a De-duplication task for each set of duplicates; De-duplication templates group those tasks for bulk remediation. To remediate a single de-duplication task, ServiceNow provides the out-of-the-box Duplicate CI Remediator wizard (pick the surviving CI, merge/remove the rest, re-point relationships); the De-duplication templates and the CMDB Workspace De-duplication Dashboard handle bulk/consistent remediation. (The OOB wizard exists — its name is "Duplicate CI Remediator," not "Deduplication Wizard.")
Key governance roles (know who does what):
- CMDB / Configuration Manager — owns the overall process and health.
- CI Class Owner / Data Steward / CMDB Librarian — owns data quality for specific classes.
- Platform Owner / Architect — design and standards.
Operationalizing the CMDB means moving from a one-time build to ongoing, repeatable governance: dashboards monitored, KPIs tracked, remediation tasks worked, audits run regularly.
CMDB Workspace is the modern, role-based interface for working with CMDB data — viewing CI details, relationships, health, and remediation in one place, rather than navigating raw lists.
Sample questions from this domain
Three of the 103 in this domain, with the reasoning. The full set is in the question bank.
The overall CMDB Health score aggregates three high-level KPIs (often called the '3 C's'). Which set correctly names them?
- A. Correctness, Completeness, and Compliance ✓
- B. Discovery, Mapping, and Reconciliation
- C. Create, Read, and Update
- D. Foundation, Design, and Sell
Why: CMDB Health aggregates three KPIs — Correctness, Completeness, and Compliance (the '3 C's') — which are built from six sub-metrics (Orphan, Staleness, Duplicate / Required, Recommended / Audit). Foundation/Design/Sell are CSDM domain names, not health KPIs.
A CI that has no relationships to any other CI is flagged in CMDB Health. What is this type of data-quality problem called?
- A. A stale CI
- B. A principal CI
- C. An orphan CI ✓
- D. A duplicate CI
Why: A CI flagged for having no relationships is an orphan CI. (Officially, 'orphan' is whatever fails the orphan rule — commonly missing relationships and/or missing required attributes — so 'no relationships' is one trigger, not the whole definition.) A stale CI is one not updated within a threshold; a duplicate is the same item represented more than once. Orphan, Staleness, and Duplicate are the three Correctness sub-metrics.
An organization wants to automatically retire and eventually archive Configuration Items that have not been discovered or updated in 90 days. Which tool is designed to manage this CI lifecycle through policy?
- A. Data Manager ✓
- B. Virtual Agent
- C. Form Designer
- D. CI Class Manager
Why: Data Manager governs the CI lifecycle and enforces policies — for example, retiring or archiving stale CIs based on rules. CI Class Manager configures class structure but does not run lifecycle policies.