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

The CMDB Data Foundations Dashboard is designed to provide visibility, insight, and guidance into the overall health of CMDB data. Its purpose is not to automate ITSM workflows, but to enable informed decision-making and continuous improvement of configuration data.

One of its primary benefits is providing actionable insights to improve data quality and completeness (Option B). The dashboard highlights gaps in CI attributes, missing relationships, and compliance issues, enabling CMDB administrators and data owners to take targeted corrective actions using Get Well Playbooks.

Another core benefit is enabling organizations to monitor and track CMDB health over time (Option D). The dashboard presents trends across health dimensions—completeness, correctness, and compliance—allowing teams to measure progress, justify investments, and demonstrate maturity improvements aligned to CSDM adoption stages.

Option A is incorrect because Change Management approvals are handled by workflow and policy engines, not the Data Foundations Dashboard. Option C is also incorrect because duplicate detection and remediation are handled through de-duplication tools and the Duplicate CI Remediator, not directly by the dashboard itself.

Therefore, the correct answers are B and D, which accurately reflect the strategic and operational value of the CMDB Data Foundations Dashboard.

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.

=========

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.

The correct answer is Relationship Map. In CMDB Workspace, the Relationship Map is used to visualize how Configuration Items are connected through CMDB relationships. This is useful when a Configuration Manager needs to understand dependency paths, parent-child relationships, hosted-on relationships, application-to-infrastructure relationships, or other CI-to-CI connections. Unified Map is more service-oriented and is typically used to understand the composition of a service and related operational context. Business Service Map is focused on service-level visualization rather than general CI relationship inspection. Since the question asks specifically how CIs are connected to each other, the most precise tool is the Relationship Map.

In ServiceNow, validating whether Configuration Items (CIs) still exist is a core CMDB governance activity. Over time, environments change rapidly—servers are decommissioned, cloud resources are torn down, and applications are replaced. If existence validation is not enforced, the CMDB quickly fills with obsolete or “ghost” CIs.

Attestation policies are specifically designed to address this need. An attestation policy automatically generates and assigns tasks to responsible users or groups, asking them to confirm that a CI still exists and is still relevant. This process focuses on acknowledgment rather than deep data validation, making it lightweight and scalable across large CMDBs.

Certification policies (Option A) are used when specific attributes must be validated, such as lifecycle status, support group, or environment. While important for data correctness, certification is not intended solely to confirm CI existence. Delete (Option B) and Retire (Option C) policies are lifecycle actions that remove or transition records, but they do not validate existence before taking action.

Attestation integrates cleanly with CMDB Workspace, assigns tasks automatically, and supports auditability—ensuring accountability for CI ownership. This makes it the correct and Data Foundations–aligned policy type for validating CI existence.

Therefore, Option D – Attestation is the correct answer.

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.

=========

CMDB Data Manager provides policy-driven lifecycle governance for configuration items. The organization should configure Life Cycle Stage automation in Data Manager so that a qualifying lifecycle change on a parent CI is propagated consistently to the relevant child CIs.

This approach creates a controlled and auditable lifecycle process. It avoids relying on custom scripts or disconnected import logic and ensures that lifecycle transitions are applied according to defined conditions and CI relationships.

A Transform Map is intended to transform and import source data. It is not the appropriate mechanism for continuously cascading lifecycle changes between related CIs. Creating a new CI class would also be incorrect because lifecycle management is a behaviour applied to existing CI classes rather than a separate CI type.

CMDB Data Manager is specifically designed to automate CI lifecycle activities such as retirement, archival, deletion, certification, and attestation. Therefore, Data Manager lifecycle automation is the governed solution.

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.

In ServiceNow, ingesting custom CIs must be done with a strong focus on upgrade safety, governance, and long-term maintainability. Data Foundations guidance explicitly discourages repurposing or overloading base classes, as this creates technical debt and upgrade risk.

Option B is a best practice because the CMDB CI Class Models Store delivers ServiceNow-supported CI classes that align with platform evolution. Before creating or extending classes, administrators should verify whether a suitable class already exists or has been introduced in newer releases. This avoids duplication and ensures future compatibility.

Option D is also correct. When no suitable class exists, extending an existing CI class (under the appropriate parent) to add required attributes preserves inheritance, discovery behavior, reporting, and upgrade compatibility. This approach is preferred over creating entirely new, disconnected schemas.

Option A is incorrect because repurposing base classes and renaming attributes breaks standard semantics, causes confusion, and complicates upgrades. Option C is incorrect because extending Asset tables to represent CIs conflates ITAM and CMDB concerns; assets and CIs serve different purposes and lifecycles.

Therefore, the solutions that minimize technical debt and ensure upgrade compliance are B and D.