ServiceNow CIS-DF - Certified Implementation Specialist - Data Foundations (CMDB and CSDM)

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.

Within the CMDB class dictionary in ServiceNow, attributes can be inherited from parent classes or defined directly on a specific class. To identify attributes created specifically for the Windows Server class, administrators must use the Added tab.

The Added tab displays attributes that are unique to the selected class and not inherited from parent classes (such as Server or Computer). This is essential for understanding class-specific extensions—like Windows-only configuration details—that were introduced to support platform requirements, discovery enhancements, or organizational needs.

The All tab shows every attribute available to the class, including inherited and added attributes, which makes it difficult to isolate class-specific additions. The Child tab focuses on attributes inherited by subclasses, not attributes introduced at the current class level. The Derived tab shows attributes calculated or derived from other data, not necessarily those created specifically for the class.

Using the Added tab supports best practices for configuration transparency, impact analysis during upgrades, and governance—especially important in Data Foundations to minimize unnecessary customization and maintain upgrade-safe designs.

Therefore, the correct answer is B – Added.

CMDB 360, also known as Multisource CMDB, is designed to provide visibility into how multiple discovery or integration sources contribute data to the same CI. Its value is not simply identifying duplicate or orphan CIs; those are handled through CMDB Health and de-duplication capabilities. CMDB 360 helps administrators compare source contributions and understand conflicts or gaps across those sources. A key insight is gaps in attribute data, where one source supplies certain CI attributes while another source does not. Another key insight is different attribute values from different data sources, which helps identify reconciliation problems, source precedence issues, and inconsistent discovery results. This is central to improving data trust because the CMDB often receives data from Discovery, SCCM, cloud connectors, manual imports, and third-party systems. Therefore, the correct insights are gaps in attribute data and different attribute values across sources.

Generated CMDB Data Manager policy tasks are reviewed and managed in CMDB Workspace > My Work tab . CMDB Data Manager creates policy-driven tasks for activities such as attestation, certification, archive, retire, and delete workflows. These tasks must be presented to the assigned users or groups in a place where they can take action. The My Work tab in CMDB Workspace is designed for this operational task management experience. The CMDB Health Dashboard provides scorecards and health visibility, but it is not the primary place to work Data Manager policy tasks. The Duplicate CIs tab is specific to duplicate remediation, and the Audit tab is not the correct workspace location for managing assigned Data Manager tasks. Therefore, C is correct.

=========

In Data Foundations, “Insight” includes measuring CMDB health in ways that are actionable—so teams can identify where data is degrading and prioritize remediation. Stale CIs (records that are no longer current, not updated, or no longer exist in the environment) are a common source of CMDB risk: they distort reporting, mislead impact analysis, and create noise for operational processes. Reducing staleness supports higher trust in the CMDB and better decision-making.

On the CMDB Health Dashboard, stale CI concerns align most closely with Compliance because staleness is fundamentally about whether CIs continue to meet defined governance expectations over time—such as update frequency, lifecycle status controls, and adherence to rules that indicate whether records are still valid. Compliance scorecards typically highlight rule-based adherence to standards (for example, policies or health rules indicating that certain CI types must be recently updated or must not exceed staleness thresholds). This makes Compliance the right place to monitor and improve staleness.

By contrast, Completeness focuses on whether required attributes are populated (for example, owner, environment, support group). Correctness focuses on whether values are accurate and relationships make sense. While stale records can indirectly affect correctness, the dashboard tracking of “stale” is primarily treated as a governance adherence issue—whether the CMDB is being maintained according to lifecycle and freshness expectations—therefore it is surfaced through the Compliance scorecard.

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.

The correct answer is Create CMDB Groups with type Health by region . CMDB Health scores can be scoped to meaningful CI populations by using CMDB Groups. When a Configuration Manager needs region-specific health visibility, the correct design is to define CMDB Groups that represent the regional CI population and set the group type appropriately for health evaluation. This allows the dashboard to calculate and display scores for the relevant subset of CIs instead of only showing global or class-level scores. There is no standard “Group scores by region” switch that automatically creates regional scorecards. Customizing scheduled jobs is also a poor approach because it introduces unnecessary technical debt and can interfere with platform-supported health calculations. CMDB Groups provide the governed and supported way to scope health reporting to regional CI populations.

=========

In ServiceNow, Service Graph Connectors deliver data ingestion patterns using protected, upgrade-safe artifacts, including script transforms. When a customer customizes a script transform provided by a Service Graph Connector, ServiceNow follows standard update set and upgrade behavior to protect customer customizations.

During a subsequent upgrade, if the out-of-box (default) script transform definition changes, ServiceNow does not overwrite the customized version. Instead, the platform records a skipped change, indicating that an update was available but intentionally not applied due to a local customization. This ensures customer-specific logic is preserved while still maintaining transparency about what changed in the newer release.

Option A is incorrect because upgrades do not halt due to customized transforms. Option C is also incorrect because Service Graph Connector upgrades proceed normally; they do not refuse to start because of customizations.

This behavior aligns with Data Foundations best practices: avoid modifying OOTB content when possible, but when customization is necessary, ensure it is protected during upgrades. Administrators should review skipped changes after upgrades to decide whether to manually adopt new OOTB logic.

Therefore, the correct answer is B – A skipped change is created and no change is made to the script transform definition.

The CMDB and CSDM Data Foundations Dashboards are obtained from the ServiceNow Store as a free application. This is different from the standard CMDB Health Dashboard, which is part of the platform CMDB capability. The Data Foundations Dashboards provide guided visibility into CMDB and CSDM readiness, maturity, and remediation opportunities through metrics and playbooks. They are intended to help organizations improve CMDB quality and CSDM alignment without building custom dashboards from scratch. Option A is incorrect because this specific dashboard application is not simply active by default. Option B is incorrect because it is not a paid Store application. Option C is incorrect because the correct source is the ServiceNow Store, not Innovation Lab. Therefore, the correct answer is D.

=========

The Unified Map is designed to provide enhanced visual insight and analysis across the CMDB by consolidating configuration item (CI) relationships from multiple sources—such as Discovery, Service Mapping, and manual relationships—into a single, interactive view. While traditional Service Mapping maps are optimized for modeling and understanding application-to-infrastructure dependencies, the Unified Map extends this capability with more flexible visualization and exploration features.

Option B is correct because the Unified Map allows users to zoom in and out, enabling both high-level overviews and detailed inspections of complex CI relationships. This capability is particularly valuable in large enterprise environments where services may span hundreds or thousands of infrastructure components. Zoom functionality supports impact analysis, troubleshooting, and architectural reviews without overwhelming the user with unnecessary detail.

Option C is also correct because the Unified Map supports filtering of map nodes based on user preferences. Administrators and analysts can filter by CI class, relationship type, lifecycle state, or other attributes, allowing them to focus on what is most relevant to their task—such as identifying only production CIs, security-relevant components, or a specific technology stack. This aligns strongly with Data Foundations principles by improving usability and decision-making without altering underlying data.

Option A is incorrect because modifying the number of levels displayed is a characteristic more closely associated with Service Mapping configuration rather than an added Unified Map capability. Option D is incorrect because visibility into an application and its host is a core Service Mapping function, not an enhancement unique to the Unified Map.

In summary, the Unified Map adds value by improving interactivity, flexibility, and user-driven insight across the CMDB.