Pass the ServiceNow CIS-Data Foundations (CMDB and CSDM) CIS-DF Questions and answers with CertsForce

In ServiceNow, protecting CMDB data quality during ingestion is a core Data Foundations principle. The Identification and Reconciliation Engine (IRE) is designed to ensure that CI records are uniquely identified, merged correctly, and protected from unauthorized overwrites. Any ingestion method that bypasses IRE introduces a high risk of duplicates and data corruption.

IntegrationHub ETL is the recommended method because it is natively designed to work with the Identification and Reconciliation API. When properly configured, IntegrationHub ETL ensures that incoming data is processed through IRE, applying identification rules, reconciliation rules, and source precedence. This allows multiple data sources to coexist safely while maintaining CMDB integrity.

Option B (Table API) is explicitly discouraged for CMDB ingestion because it writes directly to CMDB tables and bypasses IRE entirely, making it one of the most common causes of duplicate and conflicting CI records. While REST and SOAP APIs are powerful, they are not safe for CMDB ingestion unless they explicitly invoke the IRE API, which most generic table integrations do not.

Option C (Import Sets and Transform Maps) can be configured to call IRE, but this requires additional scripting and strict governance. Because of this complexity and higher risk of misconfiguration, it is not the recommended approach when safer, purpose-built options exist.

Therefore, IntegrationHub ETL is the verified and best-practice answer, making Option A correct.

Agent Client Collector

Automated agent-based solution running patterns

Import Sets

Organization-built solution using transform maps

Service Graph Connector

Pre-built store integration solutions that require minimal customization

ServiceNow Discovery

Automated agentless solution running patterns

Agent Client Collector: This is ServiceNow ' s agent-based approach. It requires a software agent to be installed on the target host to run discovery patterns locally.

Import Sets: This is the traditional, manual way to bring in data. You define the source, and the organization builds the logic (Transform Maps) to move that data into the CMDB.

Service Graph Connector: These are found in the ServiceNow Store. They are " certified " integrations built to work with specific third-party vendors (like SCCM or Jamf) with minimal setup.

ServiceNow Discovery: The classic agentless method. It probes the network and uses patterns to identify and map CIs without needing software installed on every machine.

The CMDB is a foundational capability that enables organizations to operate IT services with confidence, resilience, and efficiency. Its value lies not in automation for its own sake or financial data management, but in how it supports service-aware operations and decision-making.

Strengthening operational resiliency (Option A) is a core value of the CMDB. By maintaining accurate configuration data and relationships, organizations can better understand dependencies, assess risk, and recover more quickly from incidents or outages. A trusted CMDB enables proactive problem management and informed change planning, directly contributing to resiliency.

Streamlining Incident and Change Management (Option B) is another primary value. Accurate CI data allows incidents to be routed automatically to the correct support groups, enables faster root-cause analysis, and supports risk-based change assessments. This reduces manual effort, improves response times, and lowers operational risk.

Option C is incorrect because automating CI relationship maintenance is a capability enabled by tools like Discovery and Service Mapping—not a value in itself. Option D is also incorrect because financial data management is the domain of IT Asset Management (ITAM) and Financial Management, not the CMDB’s core value proposition.

In summary, the CMDB delivers value by improving operational resilience and optimizing ITSM processes, making Options A and B the correct answers.

CMDB Data Manager is the governance capability designed to control the lifecycle of CI records through policy-driven actions. Its policy types include Retire, Archive, Delete, Attestation, and Certification. These policies enable obsolete or no-longer-relevant records to be identified and processed consistently rather than removed through uncontrolled scripts or manual cleanup.

Archive policies remove eligible records from active operational use while retaining them for a defined recovery or compliance period. Delete policies permanently remove records after applicable lifecycle and retention requirements are satisfied. Retire policies transition CIs out of active operational status. The guide identifies automated archival and deletion according to retention policies as a primary purpose of CMDB Data Manager.

The CMDB Health and Data Foundations dashboards identify problems but do not perform lifecycle removal themselves. CI Class Manager governs classes, while de-duplication templates address duplicates specifically. Therefore, B is correct.

=========

The CMDB Data Foundations Dashboard gives Configuration Management teams visibility into the condition, readiness, and quality of CMDB data. It presents curated metrics that expose gaps involving important attributes, configuration practices, relationships, ownership, and data-governance readiness. These results help administrators determine where corrective action is necessary and prioritize remediation according to operational risk.

The dashboard does not eliminate audits. Auditing, certification, attestation, and health calculations remain separate controls required to validate data. It also does not automatically correct every issue. Instead, the dashboard provides actionable findings and links to structured remediation playbooks that guide administrators through analysing, correcting, and governing the affected data.

The study guide specifically describes dashboard benefits as providing actionable insights for improving data quality and completeness and enabling CMDB health to be monitored over time. Therefore, improved visibility into CMDB health and data quality is the only accurate answer.

=========

Creating new CI classes is a high-impact configuration activity and must follow strict Data Foundations and CSDM-aligned best practices to avoid long-term technical debt and upgrade risk.

Option B is a recommended first step. Before creating any new CI class, administrators should install or update the CMDB CI Class Models Store application and verify whether an appropriate class already exists. ServiceNow frequently delivers new CI classes through updates and class model packages, and duplicating an existing or planned class can lead to fragmentation and governance issues.

Option C is also correct. When a new class is truly required, it should be added under an appropriate parent class to inherit attributes, behaviors, and discovery patterns. For an IoT Sensor, this might be under a hardware or device-related parent class, ensuring consistency and minimizing customization.

Option A is incorrect and dangerous—deleting unused classes can break dependencies and historical data. Option D is also discouraged; modifying existing classes to repurpose them violates upgrade-safe design principles and can negatively impact discovery, integrations, and reporting.

By verifying existing models first and extending the class hierarchy correctly, organizations maintain a clean, scalable, and upgrade-safe CMDB.

Therefore, the correct answers are B and C.

CMDB 360/Multisource CMDB retains information about the values contributed by individual data sources. When reconciliation logic is modified, the administrator can perform a recompute operation so the latest rules are applied to the stored source contributions without waiting for every external system to send the data again.

This enables administrators to test and refine source-precedence or dynamic reconciliation rules and then recalculate the resulting CI attribute values using the available historical source data. The capability is particularly useful when correcting an inappropriate source-priority rule or implementing dynamic rules such as Most Reported or Last Updated.

CMDB 360 does not eliminate identification rules, permanently lock records, or automatically archive records based on quarterly reporting behaviour. Identification remains necessary to match incoming data to the correct CI, while reconciliation determines which authorized source controls an attribute.

=========

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.

In CSDM version 5, enterprise-wide capability tracking is firmly positioned within the Design and Planning domain. This domain is specifically intended to support Enterprise Architecture, Portfolio Management, and Strategic Planning use cases, making it the correct choice for an Enterprise Architect working across the organization.

The Design and Planning (Design) domain focuses on answering “what the business needs and how it should be designed” before services are built or delivered. It includes core concepts such as Business Capabilities, Value Streams, Information Objects, Business Applications, and Architectural relationships. Business capabilities represent what an organization does to achieve its objectives, independent of organizational structure, technology, or implementation. This abstraction is essential for enterprise architects, especially in highly regulated industries like financial services, where strategic alignment and impact analysis are critical.

The other domains do not fit this requirement:

Foundation provides shared reference data (companies, locations, users) but does not model enterprise capabilities.

Build and Integration focuses on application development, CI/CD pipelines, and integration layers.

Service Consumption is concerned with customers, offerings, and how services are consumed.

Service Delivery models the operational and technical delivery of services, including infrastructure and runtime environments.

From a Data Foundations and CSDM governance perspective, tracking enterprise capabilities in the Design and Planning domain ensures:

Clear separation between strategy, design, and operations

Alignment with ITIL 4 strategy and planning practices

Strong support for impact analysis, rationalization, and transformation initiatives

Therefore, Design and Planning (D) is the correct and fully aligned CSDM 5 domain for tracking enterprise capabilities.

In Data Foundations, “govern” is not only about defining standards—it also includes implementing repeatable controls that keep CMDB data clean over time. CMDB Data Manager is the ServiceNow capability built specifically for policy-driven CI lifecycle operations such as deletion, archival, and attestation. Rather than relying on one-off scripts or manual cleanup, Data Manager applies consistent lifecycle rules at scale, which is a core expectation of CMDB Data Foundations governance.

The place to administer these lifecycle policies is within CMDB Workspace, under the Management area, where the Data Manager tools expose a dedicated Policies experience. From there, a Data Manager can create new policies, publish them, and manage existing policies used to automate lifecycle processing. This aligns with the intent of “keeping the CMDB healthy and efficient” because it operationalizes governance through automated, standardized actions and controlled approvals where needed.

By contrast, CI Class Manager is primarily for managing CI class definitions and class-level settings (for example, class configuration related to identification, reconciliation, and health rules), not for publishing CI lifecycle automation policies. “CMDB 360” is oriented toward exploring CI/service context, and “Service Operations Workspace” is designed for operational workflows rather than CMDB lifecycle policy administration.