Pass CIS-DF Exam Guide

In ServiceNow CMDB governance, the CI Class Manager allows administrators to assign ownership and accountability at the class level. This ownership is used by governance tools—especially CMDB Data Manager—to automatically determine who receives tasks and actions related to data lifecycle management.

The group reference field that aligns with class ownership and is consumed by CMDB Data Manager policies is the Managed By Group. This field represents the team responsible for the technical stewardship and lifecycle management of CIs within that class.

When CMDB Data Manager executes policies such as retention, archival, or cleanup, it uses the Managed By Group to assign tasks to the appropriate data owners. This ensures governance actions are routed to the correct accountable team without manual intervention.

Approval Group, Support Group, and Change Group serve different purposes. Approval Group is used for workflow approvals, Support Group is used for operational ticket routing, and Change Group supports Change Management governance. None of these reflect data ownership at the class level.

Therefore, to leverage CI class ownership defined in the CI Class Manager within CMDB Data Manager policies, the correct field is Managed By Group, making Option B the verified answer.

The CMDB Data Foundations Dashboard identifies implementation risks and data-quality deficiencies, while its associated playbooks provide structured remediation guidance. The playbooks lead the administrator through a repeatable sequence for understanding the problem, identifying affected records and data sources, correcting existing data, and introducing governance controls to prevent recurrence.

The dashboard does not automatically install or configure third-party integrations. Those integrations are handled through capabilities such as Service Graph Connectors, IntegrationHub ETL, and Discovery. It also does not replace the CMDB Health Dashboard. CMDB Health calculates and reports metrics such as completeness, correctness, compliance, duplicates, orphaned CIs, and stale CIs. The Data Foundations Dashboard complements those health capabilities by focusing on foundational readiness and guided improvement.

Therefore, the defining benefit of the playbook is its step-by-step approach to improving CMDB data quality and alignment with recommended practices.

=========

In ServiceNow, validating whether Configuration Items (CIs) still exist is a core CMDB governance activity. Over time, environments change rapidly—servers are decommissioned, cloud resources are torn down, and applications are replaced. If existence validation is not enforced, the CMDB quickly fills with obsolete or “ghost” CIs.

Attestation policies are specifically designed to address this need. An attestation policy automatically generates and assigns tasks to responsible users or groups, asking them to confirm that a CI still exists and is still relevant. This process focuses on acknowledgment rather than deep data validation, making it lightweight and scalable across large CMDBs.

Certification policies (Option A) are used when specific attributes must be validated, such as lifecycle status, support group, or environment. While important for data correctness, certification is not intended solely to confirm CI existence. Delete (Option B) and Retire (Option C) policies are lifecycle actions that remove or transition records, but they do not validate existence before taking action.

Attestation integrates cleanly with CMDB Workspace, assigns tasks automatically, and supports auditability—ensuring accountability for CI ownership. This makes it the correct and Data Foundations–aligned policy type for validating CI existence.

Therefore, Option D – Attestation is the correct answer.

Identification rules are configured through CMDB CI Class Manager . These rules define how the Identification and Reconciliation Engine determines whether an incoming CI already exists or whether a new CI record should be created. For server records, identification rules usually rely on attributes such as serial number, name, hostname, hardware identifiers, or other class-specific criteria. If these rules are weak or missing, duplicate server records can be created during Discovery, Service Graph Connector imports, or other integrations. The CMDB Health Dashboard detects health issues such as duplicates, but it is not where identification rules are configured. CMDB Workspace provides operational access to CMDB capabilities, but CI Class Manager is the correct configuration location. CMDB Data Manager governs lifecycle policies, not IRE identification logic. Therefore, the correct answer is B.

=========