CIS-DF Practice Questions

Duplicate identifies data quality issues where the same asset is modeled more than once, violating CMDB trust principles.

Required ensures minimum viable CI creation and update—critical for ingestion and lifecycle integrity.

Orphan highlights broken relationships, which directly impact impact analysis, Service Mapping, and Change Management.

Stale flags CIs that are no longer being refreshed by Discovery or other sources but still exist in the CMD

B.  

Recommended improves completeness and usability, supporting operational and reporting use cases without being mandatory.

Audit validates data correctness by comparing CI field values against predefined templates or policies.

This exact mapping is what ServiceNow expects in CMDB Health Dashboard–related exam questions and real-world implementations.

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.

The CMDB Data Foundations Dashboard is paired with Get Well Playbooks that guide administrators through structured remediation. The “Services Have Owners Identified” playbook focuses on closing ownership gaps for services, which is a governance and data correction activity.

Fix Data (Option A) is used to correct missing or incorrect values, such as populating owner fields, assigning responsible groups, or updating relationships. In this playbook, Fix Data actions are required to actually remediate the issue by assigning owners to services.

Govern Data (Option D) is also required because ownership is not a one-time correction—it must be enforced and sustained. Govern Data establishes policies, ownership accountability, and controls (such as certifications or attestations) to ensure services continue to have owners over time and do not regress.

Analyze Data (Option B) is used to understand patterns and root causes, but it does not remediate the issue. Report Data (Option C) provides visibility and communication, not corrective action.

Therefore, the remediation plays that apply to the Services Have Owners Identified playbook are Fix Data and Govern Data, making Options A and D correct.

Discovery and Service Mapping are the correct answers because both capabilities can automatically create CMDB relationships that support Application Services. ServiceNow Discovery identifies infrastructure, applications, running processes, and dependencies in the environment. During discovery, it can create technical relationships between discovered CIs, such as servers, applications, databases, and other supporting components. Service Mapping extends this further by building application service topology, identifying how application components interact, and creating the relationship model that connects CIs into an Application Service. These relationships are essential for impact analysis, change risk assessment, incident correlation, and service-aware operations. Event Management does not create application-service CI relationships; it correlates operational events and alerts. Data Manager governs lifecycle, attestation, certification, archival, retirement, and deletion policies, but it does not discover application topology. IntegrationHub ETL can ingest and transform external CMDB data, but it does not automatically discover service relationships in the same way Discovery and Service Mapping do. Therefore, Discovery and Service Mapping are the ServiceNow solutions that automatically create these relationships.