CIS-DF ServiceNow Certified Implementation Specialist - Data Foundations (CMDB and CSDM) Free Practice Exam Questions (2026 Updated)

When data quality issues such as missing serial numbers threaten CMDB integrity and increase the risk of duplicates, ServiceNow provides prescriptive, step-by-step remediation guidance through the CMDB Data Foundations Dashboard Playbooks.

These playbooks are specifically designed to help administrators identify root causes, assess ingestion and governance gaps, and apply corrective actions using structured remediation plays (Analyze Data, Fix Data, Govern Data). For missing serial numbers, the playbooks guide teams to review Discovery patterns, identification rules, reconciliation sources, and governance controls to ensure authoritative data capture and prevention of future issues.

The CMDB Health Dashboard Playbooks focus on health scoring and metrics, not guided remediation. CSDM Data Foundations Dashboard Playbooks is not a distinct product naming; the correct construct is CMDB Data Foundations. Now Create Playbooks provide implementation project guidance, not operational troubleshooting for live data issues.

Therefore, the correct answer is A – CMDB Data Foundations Dashboard Playbooks, which are purpose-built to quickly troubleshoot and remediate CMDB data quality problems while aligning with best practices in ServiceNow.

A CI class is set as a Principal Class from the Basic Info tab in CI Class Manager by selecting the Principal Class check box. Principal Classes are important because they control which CI classes are treated as primary, operationally meaningful classes in CMDB processes and reference fields. For example, Principal Classes influence which CIs appear in key task fields such as Configuration Item fields on Incident, Change, and other ITSM records. This keeps users from selecting low-level or irrelevant child records when the business process expects a meaningful CI. There is no separate requirement to click a dedicated Principal Class UI Action, and it is not configured through a Yes/No choice list in this scenario. The Basic Info tab exposes the class-level property directly, so checking the Principal Class checkbox is the correct configuration action.

Delete and archive policies are designed for end-of-life CMDB lifecycle governance. They should apply to records that are no longer active operational CIs and have reached an appropriate retired state. End of Life - Retired is the correct lifecycle state because it indicates that the CI has completed its useful operational lifecycle and can be governed through archival or deletion according to retention rules. Applying delete or archive policies to Inventory - Available records would be dangerous because those CIs may still be valid and usable. “In any lifecycle state” is wrong because unrestricted archival or deletion can remove active, dependent, or operationally important records. “Missing - Stolen” is more aligned with asset disposition and exception handling, not the standard CMDB Data Manager delete/archive target state. Therefore, these policies should affect servers in End of Life - Retired.

=========

The CMDB Health Dashboard is a central component of CMDB Data Foundations insight and governance. It measures and tracks data quality using well-defined health indicators that focus on the accuracy, relevance, and usability of CI data.

Two key data quality areas included in the dashboard are Stale CIs and Duplicate CIs.

Stale CIs (Option D) refer to configuration items that have not been updated within a defined time window. These records are risky because they may no longer reflect the current state of the environment, leading to inaccurate impact analysis, poor change decisions, and misrouted incidents. Monitoring staleness helps organizations identify where discovery, integrations, or ownership processes are failing.

Duplicate CIs (Option E) occur when the same real-world asset or service is represented by multiple records. Duplicates undermine trust in the CMDB, distort reporting, and break service mappings. The CMDB Health Dashboard highlights duplicate trends and integrates with de-duplication and remediation workflows to address them.

Options A (Downgraded CIs), B (Upgraded CIs), and C (Missing CIs) are not standard CMDB Health Dashboard quality dimensions. While “missing” data may be inferred through completeness checks, Missing CIs as a category is not directly tracked.

Therefore, the correct answers are D – Stale CIs and E – Duplicate CIs, which are core CMDB Health indicators used to maintain high-quality configuration data.

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.

=========

In ServiceNow, Dynamic CI Groups are a core Data Foundations capability used to automatically manage CI membership based on rules rather than manual maintenance. When Technology Management Service Offerings (Technical Service Offerings) are related to Dynamic CI Groups, ServiceNow uses those relationships to synchronize operational support attributes to the member CIs.

The two CI attributes that are intentionally designed to sync in this model are the Managed by Group and the Support Group. These groups directly influence operational ownership and support routing, which is why they are automatically aligned when Dynamic CI Groups are used. This ensures that incidents, changes, problems, and operational tasks are routed consistently as CI membership changes over time.

The Support Group defines who provides day-to-day operational support and is critical for Incident and Request Management workflows. The Managed by Group represents the team responsible for the technical lifecycle and operational health of the CI. Synchronizing these attributes eliminates manual updates and reduces misrouted tickets, which is a key goal of Configuration Management maturity.

The Approval Group (Option A) is not synced because approvals are process-driven and often context-specific rather than CI-driven. Similarly, the Owned by Group (Option C) represents accountability or financial ownership, which is intentionally decoupled from dynamic operational grouping to avoid unintended governance changes.

Therefore, the correct answers are B (Managed by Group) and D (Support Group).

The Desired State audit type is included in the CMDB Health Compliance calculation. A desired-state audit compares the actual values stored on a CI against the values or conditions that the organization expects the CI to meet.

In this scenario, the organization’s desired state is that every server must have the current approved patch level. A Certification Template can define the server population and attributes to be evaluated. The resulting audit identifies servers that do not satisfy the expected patch condition, and those results contribute to the Compliance KPI.

“Compliance” is the name of the overall CMDB Health scorecard, not the audit type selected for this check. “Architecture Compliance” is not the applicable audit type for validating server patch-level attributes.

The Compliance scorecard uses audit results to determine whether CIs conform to defined organizational standards. Therefore, the correct audit type is Desired State .

=========

IRE applies identification logic to determine whether incoming data represents an existing record or requires the creation of a new record. This makes Option A correct: properly configured identifiers reduce duplicate creation by matching incoming data to existing records before insertion.

IRE also applies reconciliation controls after identification. Reconciliation rules establish which data sources are authorized to update particular classes or attributes and define source precedence when multiple sources provide competing values. Therefore, Option D is correct because an unauthorized or lower-priority source can be prevented from overwriting controlled data.

IRE does not generally prevent an authorized ingestion source from inserting a genuinely new record when no match exists, so Option B is too broad. Option C is incorrect because identification is based on identifier attributes and identification rules, not simply on whether relationships exist.

The guide describes IRE as the mechanism that uniquely identifies records, reduces duplicate creation, applies source precedence, and protects records from unauthorized overwrites.

=========

The Unified Map in ServiceNow provides a consolidated view of services and their underlying components, integrating Discovery and Service Mapping data. To make this view actionable, Service Owners can apply filters to focus on relevant elements and reduce visual noise.

Filtering by CI type (Option A) is a core capability. It allows the Service Owner to show or hide categories such as servers, databases, load balancers, or applications—making it easier to analyze specific layers of the service.

Filtering by Business Criticality (Option D) is also available and highly valuable. This enables Service Owners to prioritize views around high-impact components, ensuring attention is focused on CIs that pose the greatest risk to service delivery.

Option B (Discovery source) is not typically exposed as a Unified Map filter because the map focuses on operational and service context, not ingestion provenance. Option C (Managed by group) is a governance attribute and is not a standard visual filter within the Unified Map.

Thus, the correct filter options are A – CI type and D – Business criticality.

Within Data Foundations, “Configuration” includes designing the CMDB data model in a way that supports operational usability—especially for ITSM processes like Incident and Change. One common usability challenge is that CI reference fields (such as the Incident “Configuration item” field) can become cluttered and confusing if they allow selection from every CI class, including highly technical or rarely used classes. To address this, ServiceNow uses the concept of Principal Classes: a curated subset of CI classes that are considered primary for operational selection and reporting.

Principal Classes are designated in the CI Class Manager, because this is where administrators configure and manage CI class behaviors and class-level settings. Defining Principal Classes at the class-management layer ensures that the platform can consistently apply this constraint across CI reference fields and related experiences. This aligns with Data Foundations goals: improving data quality and process outcomes by making it easier for users to select the correct CI, which in turn increases accuracy for assignment, routing, impact analysis, and analytics.

The other options do not fit the responsibility. CMDB Workspace is primarily used for exploring and analyzing CMDB data, not configuring class-level constraints. CMDB Data Manager focuses on governance automation (like lifecycle policies and bulk remediation operations), not CI class designation rules. System Properties may influence global behaviors, but Principal Class designation is a modeling configuration handled through CI class configuration, which is why CI Class Manager is the correct location.

CSDM is designed to connect technology delivery to business consumption so organizations can answer questions like “who is impacted?” quickly and consistently. In a critical incident, the healthcare provider needs to identify impacted users in business terms—clinicians, admin teams, specific sites, or departments—rather than only listing technical components.

Option D (“Service Offerings by Department or Location”) is the most CSDM-aligned data because it reflects who consumes the service and how that consumption is segmented. In CSDM, a Business Service / Service Offering represents what customers consume, and the offering can be associated with organizational constructs such as department, business unit, or location. For healthcare, this is especially valuable because impact is often location-based (hospital site, clinic) and role-based (patient intake, scheduling, ward operations). Using service offerings and their consumer mapping helps quickly identify likely impacted user groups and prioritize communications and workarounds.

Option A (environment attribute) helps differentiate production vs non-production and can support prioritization, but it does not identify impacted users. Option B is historical context, not a reliable mechanism to determine current impacted users. Option C is useful operationally for listing impacted configuration items, but it is ITSM task data, not specifically CSDM consumer modeling. CSDM’s value here is linking the technical disruption to the business consumer view via service offerings and consumption segmentation.

A healthy and trusted CMDB that aligns with Data Foundations principles—covering accurate data ingestion, strong governance, and service-aware relationships—directly strengthens the insight available to Change Management. When discovered infrastructure data is integrated with well-maintained non-discoverable attributes (such as assignment groups, support groups, and ownership), the CMDB becomes a reliable source of truth for evaluating change risk and impact.

Option B is correct because Service Mapping establishes relationships between configuration items (CIs) and business services. This enables change practitioners to perform impact analysis, identifying which services, applications, and downstream components may be affected by a proposed change. Rather than relying on assumptions or tribal knowledge, change records can reference real dependency data, improving risk assessment, scheduling decisions, and stakeholder communication. This aligns directly with CSDM and CMDB best practices, where service context is essential for informed decision-making.

Option D is also correct because accurate, governed non-discoverable data—such as support and assignment groups—allows Change Management processes to dynamically route work. When a change is associated with a CI or service, the system can automatically populate the appropriate assignment group based on CMDB relationships. This improves efficiency, reduces manual errors, and ensures accountability across federated support models.

Options A and C are incorrect because a CMDB, regardless of maturity, cannot guarantee zero downtime, nor does it eliminate the need for human governance, approvals, and risk-based decision-making. Data Foundations enhance insight and control—not unchecked automation or absolute outcomes.

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

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.

CMDB 360, also known as Multisource CMDB , provides attribute-level visibility into the data contributed by different discovery and integration sources. It enables an administrator to examine which source supplied a particular attribute, compare competing values, identify missing source contributions, and understand how reconciliation selected the final value stored on the CI.

The guide explains that CMDB 360 reveals gaps in attribute data and differing attribute values across sources. These insights help administrators diagnose reconciliation conflicts, inappropriate source precedence, incomplete integrations, and inconsistent discovery results.

CMDB 360 is not itself the mechanism used to ingest records. Service Graph Connectors, IntegrationHub ETL, Import Sets, and Discovery perform ingestion. CMDB 360 instead preserves and exposes the source- level contributions after ingestion so that data owners can investigate and improve multisource data quality.

=========

Principal Classes are a key CMDB configuration concept used to control which CI classes are selectable in reference fields across ITSM processes. This helps reduce noise, prevent incorrect CI selection, and improve data quality.

In ServiceNow, Principal Classes are designated within the CI Class Manager. This tool allows CMDB administrators to manage the CI class hierarchy, define ownership, and explicitly mark classes as principal. Once a class is marked as principal, its CIs become available in CI reference fields such as those on Incident, Change, and Problem forms.

Option A (CMDB Workspace) provides operational and analytical views but does not control schema-level class behavior. Option C (System Properties) does not manage class designation. Option D (CMDB Data Manager) governs lifecycle and data quality policies, not reference field behavior.

By configuring Principal Classes in the CI Class Manager, organizations ensure that only relevant, high-value CI classes are exposed to end users, aligning with Data Foundations best practices.

Therefore, the correct answer is B – CI Class Manager.

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 CSDM, Technology Services (and their Service Offerings) represent how technical capabilities are delivered and consumed by internal teams. When a server team requests a catalog item for infrastructure services (e.g., VM provisioning, storage, OS builds), the role responsible for initiating the request and defining requirements is the Technology Service Owner.

Technology Service Owners understand the operational capabilities, constraints, SLAs, and fulfillment workflows required to deliver infrastructure services. They define catalog requirements such as options, approvals, fulfillment tasks, and guardrails—ensuring the request aligns with standardization, security, and operational readiness.

Application Service Owners focus on how applications are delivered and supported, not on defining infrastructure catalog items. Enterprise Architects provide standards and guidance but do not initiate or define catalog request requirements.

Thus, the correct role is B – Technology Service Owners.

The correct answer is Establishing clear governance and continuously monitoring CMDB health . A functional CMDB is not achieved simply by loading large quantities of data or deploying discovery tools. Operationalizing the CMDB requires ownership, standards, data policies, lifecycle controls, class governance, relationship governance, health monitoring, and remediation processes. Discovery is valuable, but without governance it can still create stale, incomplete, duplicated, or poorly related CI data. Allowing teams to freely modify CMDB records creates inconsistency and weakens trust. Populating the CMDB with as much data as possible is also a common failure pattern because excessive, unmanaged data reduces usability and increases maintenance effort. Data Foundations emphasizes trusted, governed, and actionable data. Therefore, the most critical success factor is clear governance combined with continuous CMDB Health monitoring.

=========