Free ServiceNow CIS-DF Practice Exam with Questions & Answers | Set: 5

Managing CMDB data volume is a key Data Foundations governance objective. Over time, CMDBs naturally accumulate retired, obsolete, or decommissioned CIs. If these records are not properly managed, they degrade CMDB performance, reduce reporting accuracy, and negatively impact discovery reconciliation and health scores.

Archive Policies are the mechanism designed to address this challenge. They define when CI records should be archived or deleted based on lifecycle state, age, or retention requirements. By automating archival and cleanup, archive policies ensure that only relevant, active CIs remain in the operational CMDB, keeping data volume manageable and performant.

Business Rules (Option A) are used to enforce logic during record creation or updates, not for long-term data volume control. Scheduled Jobs (Option B) may execute tasks, but without archive policies they have no governance logic to determine what should be removed or retained.

Archive policies work in conjunction with CMDB Data Manager to enforce lifecycle-based retention and cleanup, making them the correct and verified answer.

Therefore, Option C – Archive Policies is correct.

Design Domain → Enterprise Architect(s), Data Steward(s), Process Owner(s), Platform Owner

Foundation Domain → Enterprise Architect(s), Platform Owner

Portfolio Domain → Service Owner(s), Platform Owner

Technical Domain → Technology Service Owner(s), Application Service Owner(s), Platform Owner

CSDM governance requires the correct domain owners because each domain represents a different type of data accountability. The Design Domain is architecture-heavy and requires Enterprise Architects, Data Stewards, Process Owners, and the Platform Owner to ensure planning data is accurate and aligned. The Foundation Domain depends on shared platform reference data, so Enterprise Architects and the Platform Owner are key stakeholders. The Portfolio Domain is concerned with service ownership and service portfolio accountability, so Service Owners and the Platform Owner are the primary governance roles. The Technical Domain governs operational service and application service data, so Technology Service Owners, Application Service Owners, and the Platform Owner are needed. This division prevents one team from owning all CSDM data incorrectly and creates clear accountability.

=========

The Identification and Reconciliation Engine (IRE) is a core platform capability in ServiceNow and does not require CMDB 360 / Multisource CMDB to function. Even without the ITOM Discovery license, organizations can still define and use IRE reconciliation rules across multiple data sources.

IRE rules are source-aware and can evaluate attributes based on source precedence, regardless of whether CMDB 360 is enabled. CMDB 360 enhances visibility, governance, and monitoring of multiple sources, but it is not a prerequisite for reconciliation logic itself.

Option A is incorrect because purchasing ITOM Discovery is not mandatory to use multisource reconciliation. Option C is also incorrect because CMDB 360 / Multisource CMDB is a licensed add-on, not a universally available platform feature.

Therefore, the Data Owner can proceed by configuring IRE reconciliation rules directly, making Option B the correct answer.

The correct answer is Use the CMDBTransformUtil API in the transform script . Import Sets and Transform Maps can create duplicate CIs if they write directly into CMDB tables without routing the data through the Identification and Reconciliation Engine. The CMDBTransformUtil API is used in transform scripting to process incoming CI data through the CMDB identification and reconciliation logic. This allows ServiceNow to evaluate existing CIs using configured identification rules and then update the correct CI rather than creating a duplicate record. Coalesce rules are not sufficient for CMDB ingestion because they rely on simple field matching and do not apply the full IRE logic. “Comparison rules” is not the correct mechanism. A system property alone is also not the recommended implementation pattern for vendor shipment import data. Therefore, CMDBTransformUtil is the correct method to prevent duplicate CI creation through import sets.

In a mature Configuration Management implementation within ServiceNow, CI operational attributes are leveraged to automate Change Management workflows and reduce manual effort.

When a CI is selected on a Change record, ServiceNow evaluates the CI’s Change Group attribute. If this field is populated on the CI, the platform automatically copies its value into the Change Group field on the Change form. This ensures that change ownership and governance are immediately aligned with the responsible technical team.

The Change Group is distinct from the Assignment Group, which is used primarily in Incident and Task routing. Managed by Group represents lifecycle ownership and is used by CMDB governance tools, while Approval Group controls approval workflows but is not auto-populated from CI selection.

This behavior demonstrates the value of accurate CI attributes: once populated consistently, they enable automatic field population, reduced manual errors, and faster processing across ITSM workflows.

Therefore, the correct answer is A – Change Group.

The CMDB Data Foundations Dashboard identifies foundational CMDB data-quality deficiencies, including hardware CIs that lack important identification attributes such as serial numbers. A missing serial number is particularly serious because serial number is commonly included in Hardware identification rules. Without it, Discovery and external integrations may fail to match an incoming device to its existing record, resulting in duplicate CIs.

The dashboard exposes the affected population and provides remediation playbooks that help administrators analyse the responsible data sources, correct existing records, and establish controls to ensure that serial numbers continue to be populated.

CI Class Manager is used to configure class structures and identification rules, but it is not the dashboard used to locate the full population of affected CIs. CMDB Data Manager governs lifecycle policies, while the CSDM dashboard focuses on service-model alignment.

=========

CMDB Data Foundations Dashboard playbooks explain why a deficient metric matters and provide recommended actions for improving it. This includes insight into downstream consequences such as duplicate creation, inaccurate assignment, unreliable impact analysis, weak service context, incorrect reporting, or ineffective Incident, Change, and Security Operations processes.

The playbooks also provide remediation options. These guide administrators through analysing affected records, identifying responsible data sources, correcting existing data, and introducing governance controls to prevent the condition from returning. The guide describes remediation playbooks as structured guidance for analysing issues and implementing targeted corrective actions.

They are not automatically executed scripts. Human analysis, source correction, ownership decisions, and governance changes are generally required. They are also more than generic remediation templates because their value includes contextual impact information and metric-specific recommendations.

Therefore, the two stated benefits are downstream-impact insight and remediation options, making B and D correct.

=========

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 CMDB.

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.

The correct answer is CMDB Workspace. Service Graph Connector Central is designed to improve visibility into Service Graph Connector activity and source contribution within the CMDB operating experience. Since the objective is to understand data sources contributing to the CMDB, the functionality is surfaced in CMDB Workspace rather than a separate Service Graph Connector Workspace or Discovery Admin Workspace. CMDB Workspace is the central workspace for managing CMDB data quality, source visibility, health, governance, and operational CMDB activities. Discovery Admin Workspace is focused on Discovery configuration and operations, not central CMDB source insight. Therefore, once the Service Graph Connector Central plugin is installed, the related tab is available in CMDB Workspace.

=========

The Management tab provides the direct administrative path to CMDB Data Manager. Under Management tools, the administrator can open Data Manager to create, edit, review, publish, and track lifecycle policies. ServiceNow’s documented procedure for creating a policy begins by selecting CMDB Workspace > Management > Data Manager > Policies .

The Home tab also provides access through its Quick Links section. The Data Manager quick link opens the same policy-management capability and allows authorized administrators to create, review, publish, and monitor policies.

The My Work tab is used primarily to review and process tasks generated after policies run; it is not the policy-configuration entry point. CMDB 360 is used for multisource data visibility, while Insights focuses on analytical and adoption information. Therefore, the two tabs providing access are Management and Home.

=========