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

The CMDB Data Manager is the ServiceNow capability responsible for generating actionable governance tasks and assigning them to CI class owners and data stewards. These tasks appear directly in the “My Work” tab within the CMDB Workspace, enabling proactive and role-based CMDB governance.

CMDB Data Manager focuses on data lifecycle management, including archival, retirement, and cleanup of CIs based on defined policies. When lifecycle rules or retention thresholds are met—or when human validation is required—the Data Manager creates tasks to prompt responsible owners to take action. This ensures that CMDB data remains accurate, compliant, and lean over time.

The CMDB Health Dashboard (Option C) provides visibility into health metrics such as completeness, correctness, and compliance, but it does not generate tasks. Similarly, De-duplication templates (Option A) support duplicate identification and remediation workflows, but they do not create ongoing governance tasks in the CMDB Workspace.

By surfacing tasks in “My Work,” CMDB Data Manager operationalizes governance and embeds accountability into daily workflows, which is a key principle of CMDB Data Foundations.

Therefore, the correct answer is Option B – CMDB Data Manager.

CI Analyst → Manages assigned CI tables, keeps records updated, and resolves tasks related to CMDB records

Service or Product Owner → Accountable for managing all elements that make up a portfolio throughout their entire lifecycle

Configuration Manager / CMDB Admin → Obtains the highest-level role for CMDB privileges

CMDB Process Owner → Has read-only access to CMDB data and to basic user interfaces such as CMDB reports and dashboards

IntegrationHub ETL is a ServiceNow data-ingestion application used to extract data from external sources, transform it through defined mappings, and load it into the CMDB. Its Robust Transform Engine provides a guided, low-code mechanism for mapping source data to appropriate CMDB classes, attributes, and relationships.

A major Data Foundations advantage of IntegrationHub ETL is its integration with the Identification and Reconciliation Engine. Incoming records can be processed through identification and reconciliation rules so that existing CIs are updated correctly, duplicate creation is reduced, and source-authority controls are respected.

Agent Client Collector is used to gather inventory and telemetry from devices through an installed endpoint agent. Service Mapping builds Application Service topology and dependency relationships; it is not the general ETL application for importing data from multiple external sources.

The guide identifies IntegrationHub ETL as the recommended method for importing external data through the Identification and Reconciliation API when a dedicated Service Graph Connector is not the applicable solution.

The CMDB Process Owner is accountable for the overall Configuration Management process and its governance framework. This includes establishing data standards, defining ownership and stewardship expectations, coordinating remediation processes, monitoring CMDB health, and ensuring that identification and reconciliation practices support trustworthy data.

A CI Analyst performs operational work on assigned CI classes, including updating records and resolving specific CMDB-related tasks. However, the analyst does not own organization-wide governance standards. A CMDB Architect designs the CMDB data model and technical architecture, while a Service Owner is accountable for a particular service. The IT Asset Manager focuses primarily on financial, contractual, and asset-lifecycle information.

Because the requirement covers organizational standards, cross-source data quality, and ongoing governance accountability—not merely individual record maintenance—the CMDB Process Owner is the correct role.

=========

For a hardware item that has both a CI record and an associated Asset record, ServiceNow maintains alignment between corresponding lifecycle fields. When the Hardware Status value changes on the CI, the related high-level lifecycle value on the Asset is synchronized through the State field.

The Asset State field represents the asset’s broad lifecycle condition, such as In Stock, In Use, In Maintenance, Missing, or Retired. A Substate provides a more detailed qualification of a State and is not the direct field requested by this Hardware Status update. The Asset tag is an identifying inventory value, while Installed is a date-related field; neither represents the corresponding lifecycle state.

The Data Foundations guide explains that the platform uses Asset-to-CI and CI-to-Asset synchronization logic so that updates made from either operational Configuration Management or financial and lifecycle Asset Management remain aligned. This prevents conflicting status information, inaccurate reports, and incorrect lifecycle decisions. Therefore, the associated Asset’s State field is automatically synchronized.

In ServiceNow, the Duplicate CI Remediator is a governed tool designed to safely resolve duplicate Configuration Items while preserving the most valuable and authoritative record. The first step in the remediation wizard is identifying the Main CI, which will be retained after remediation.

ServiceNow uses two primary attributes to help determine the best candidate for the Main CI:

Oldest Created (Option A)

The oldest CI is often preferred because it typically has a longer operational history, may be referenced by historical incidents, changes, problems, or audits, and is more likely to be embedded in downstream processes and reports. Retaining the oldest CI helps avoid breaking historical references.

Most Related Items (Option B)

A CI with the most relationships (for example, links to applications, services, incidents, or other CIs) is generally the most valuable from a business and operational context perspective. Preserving these relationships is critical for impact analysis, Change Management, and CSDM-aligned service modeling.

Options C (Newest Created) and D (Least Related Items) are not used as selection criteria because newer or weakly-related CIs typically contain less historical and relational value and are better candidates for removal or merging.

By prioritizing Oldest Created and Most Related Items, the Duplicate CI Remediator aligns with CMDB Data Foundations best practices, ensuring minimal data loss, preserved business context, and safer de-duplication outcomes.

Therefore, the correct answers are A and B.

The correct answer is Data Quality Scheduled Job because CMDB data quality checks are not simply visual or manual activities. Scheduled jobs are used to execute recurring evaluations that calculate and refresh quality indicators for CI records. These jobs support CMDB health and data quality by periodically checking records against configured rules, such as stale records, missing required attributes, compliance conditions, or correctness-related metrics. CMDB Workspace is the interface where users can review and act on CMDB information, but it is not itself the mechanism that performs scheduled quality evaluation. Business rules can enforce logic during insert or update actions, but they are not the normal mechanism for recurring CMDB data quality calculation. Therefore, the Data Quality Scheduled Job is the best answer.

=========

The correct answers are C and D. Identification and reconciliation rules are essential because they control how incoming CI data is matched to existing records and how updates from different sources are reconciled. This prevents duplicate CIs and ensures that authoritative sources update the correct attributes. CI Class Manager is also required because it provides governance over CI class structure, attributes, and inheritance. Standardized CI classes prevent each source from classifying the same real-world object differently. Option A is the cause of the problem, not the solution. Option B introduces avoidable technical debt because custom scripts are harder to govern, maintain, and upgrade. A Data Foundations-aligned solution uses standard class governance plus IRE rules to enforce consistency across all sources.

=========

The Design and Planning domain of CSDM focuses on planning-level constructs such as Business Applications, Business Capabilities, Information Objects, and architecture context. The two roles most directly involved are the Application Owner and the Enterprise Architect . Application Owners provide authoritative ownership, lifecycle, criticality, and portfolio information for Business Applications. Enterprise Architects define and govern enterprise capabilities, application rationalization, architecture alignment, and strategic planning relationships. Application Service Owners are more closely aligned with operational service delivery and application service health, especially in the technical/manage domain. Business Relationship Managers are more closely tied to consumption, offerings, and business-facing service value. Because Design and Planning is about application portfolio and enterprise architecture structure, the correct roles are Application Owner and Enterprise Architect.

=========

The CMDB Data Foundations Dashboard in ServiceNow is intended to provide ongoing, trend-based visibility into how well the CMDB ingestion and maintenance processes are functioning—not just point-in-time issue lists. This is why continual monitoring of its metrics is valuable.

Option B is correct because tracking active CIs updated in the last 90 days provides a strong indicator of data freshness and operational relevance. A healthy CMDB should reflect recent updates from Discovery, integrations, and governed manual processes. Monitoring this metric over time helps organizations detect stagnation, discovery failures, or integration issues early.

Option C is also correct because metrics for CIs processed by the Identification and Reconciliation Engine (IRE) directly indicate the effectiveness and adoption of governed ingestion practices. Consistent IRE processing confirms that integrations are not bypassing identification rules, reducing duplicates and improving trust in CMDB data. Trending this metric helps validate Data Foundations maturity.

Option A is incorrect because the dashboard is not designed to provide exhaustive audit failure lists; those are handled through certification and remediation workflows. Option D is also incorrect because orphan CIs are a specific health condition surfaced via health rules and remediation tools, not a core benefit metric for continual dashboard monitoring.

Therefore, the correct answers are B and C.