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

When data quality issues such asmissing serial numbersthreaten CMDB integrity and increase the risk of duplicates, ServiceNow providesprescriptive, step-by-step remediation guidancethrough theCMDB Data Foundations Dashboard Playbooks.

These playbooks are specifically designed to help administratorsidentify 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.

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

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

In a healthcare environment, identifyingwho is impactedduring a critical incident is essential to patient safety and continuity of care. Within theCommon Service Data Model (CSDM), the most effective way to determine impacted users is throughService Offerings, particularly when they are definedby department or location.

Service Offeringsrepresent how a service is consumed by specific user groups. In this case, a patient management system may have different offerings for departments such as Emergency, Inpatient Care, or Outpatient Services, or be scoped by hospital location. These offerings explicitly defineconsumer context, allowing incident responders to immediately identify which clinicians, staff, or facilities are affected.

Option D (Affected CI related list) identifies technical impact but does not translate that impact intouser or consumer context. Option A provides historical insight but does not identify current impacted users. Option C (service environment) helps differentiate production vs non-production but does not identifywhois impacted.

By leveragingService Offerings by Department or Location, the provider can quickly notify the right users, prioritize response based on clinical impact, and coordinate mitigation effectively—aligning with CSDM and ITIL best practices.

Therefore, the correct answer isB – Service Offerings by Department or Location.

In theCommon Service Data Model (CSDM), the Incident form is designed to captureoperational impactand enableeffective incident routing, prioritization, and communication. To achieve this, CSDM prescribes using classes that representhow services are delivered and consumed, not how they are planned or governed.

Application Service(Option A) is an appropriate class on the Incident form because it represents thetechnical service that is running in productionand is directly impacted during an incident. Application Services are service-mapped, relate to underlying infrastructure, and support impact analysis, root cause investigation, and automated assignment. This makes them ideal for associating incidents with technical outages or degradations.

Service Offering(Option C) is also appropriate because it representshow a service is consumed by users or business units. Service Offerings allow Incident Management to understandwho is affected, enable targeted communications, and support SLA/OLA alignment. For example, an email service offering for a specific department clearly identifies the impacted consumer group.

Business Application(Option B) isnotrecommended on the Incident form. Business Applications are logical representations used for portfolio, ownership, and governance purposes, not day-to-day operational incident handling. Using them directly on incidents can reduce precision and automation.

Service Portfolio(Option D) is a strategic construct used for service lifecycle management and is never associated with operational incidents.

Therefore, according to CSDM best practices, the correct classes used on the Incident form areApplication ServiceandService Offering, makingOptions A and Cthe correct answers.

InServiceNow, duplicate CI management spansdetection, insight, and remediation:

TheCMDB Health Dashboard – Correctnesssurfaceswhere duplicates existand their impact, providing visibility and prioritization.

Certification Taskssupportgoverned resolution, allowing assignment to individuals or groups to validate and correct data.

De-duplication Templatesenablebulk remediation, ideal when standardized merge rules can be applied across many duplicates.

TheDuplicate CI Remediatoroffers aguided, record-by-record wizard, preserving relationships and history for safer individual resolutions.

De-duplication Tasksare the work items generated by these processes, but they do not themselves represent an outcome—hencenot applicable.

This mapping aligns withCMDB Data Foundations best practices, ensuring duplicates are identified, prioritized, and remediated efficiently and safely.

TheCMDB Data Managercapability inServiceNowis designed to supportCMDB governance, specifically arounddata lifecycle management. Its primary purpose is to ensure that CI records areretained, archived, and deletedin accordance with definedretention policies, regulatory requirements, and organizational data governance standards.

As CMDBs mature, they naturally accumulate obsolete, retired, or decommissioned CIs. If these records are not properly managed, they negatively impact CMDB health, reporting accuracy, discovery reconciliation, and performance. CMDB Data Manager addresses this byautomating the archival and deletion of recordsonce lifecycle conditions and retention thresholds are met.

Option A is incorrect because encryption of archived records is handled by platform-level security and data protection features, not CMDB Data Manager. Option B is also incorrect becauserelationship rule enforcementis managed through CSDM guidance, CMDB relationship rules, and identification/reconciliation logic—not by CMDB Data Manager.

By automating retention-based archival and cleanup, CMDB Data Manager helps organizations maintain alean, compliant, and high-quality CMDB, which directly supports CMDB Health metrics such as correctness and compliance.

Therefore, the correct and verified answer isOption C.

TheIdentification and Reconciliation Engine (IRE)is acore platform capabilityinServiceNowand doesnot require CMDB 360 / Multisource CMDBto function. Even without the ITOM Discovery license, organizations can still define and useIRE reconciliation rulesacross multiple data sources.

IRE rules are source-aware and can evaluate attributes based onsource precedence, regardless of whether CMDB 360 is enabled. CMDB 360 enhances visibility, governance, and monitoring of multiple sources, but it isnot a prerequisitefor reconciliation logic itself.

Option A is incorrect because purchasing ITOM Discovery is not mandatory to use multisource reconciliation. Option C is also incorrect because CMDB 360 / Multisource CMDB is alicensed add-on, not a universally available platform feature.

Therefore, the Data Owner can proceed by configuringIRE reconciliation rules directly, makingOption Bthe correct answer.

InServiceNow, theDuplicate CI Remediatoris designed to resolve duplicate records while preserving themost authoritative datafrom each source. Data Foundations guidance clearly states thatautomated discovery is the system of record for technical attributes, such as IP address, hostname, and operational status, while manually maintained records often containvaluable business context, such as relationships to business applications or services.

In this scenario, the discovered CI contains the most accurate and up-to-datetechnical data, making it the correct CI to retain as the primary record. However, the manually imported CI has acritical relationship to a business application, which is essential for impact analysis, incident prioritization, and CSDM alignment. Deleting this CI without preserving the relationship would result in loss of business context and reduced CMDB value.

The Duplicate CI Remediator supportsselective merging, allowing administrators to retain one CI while merging specific attributes or relationships from the duplicate. Option C reflects this best practice by retaining the discovered CI and merging the relationship from the manually imported CI, ensuring both technical accuracy and business relevance are preserved.

Options A and D would result in the loss of important relationship data, while Option B would discard the discovered CI, violating the principle that discovery should be the authoritative source for technical attributes.

Therefore,Option Cis the correct and Data Foundations–aligned answer.

TheCMDB Data Foundations DashboardinServiceNowis intended to provideongoing, trend-based visibilityinto 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 Bis correct because trackingactive CIs updated in the last 90 daysprovides a strong indicator ofdata 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 Cis also correct because metrics forCIs processed by the Identification and Reconciliation Engine (IRE)directly indicate the effectiveness and adoption ofgoverned 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 becauseorphan CIsare a specific health condition surfaced via health rules and remediation tools, not a core benefit metric for continual dashboard monitoring.

Therefore, the correct answers areB and C.

Automatic relationship creation is fundamental to maintaining aservice-aware and trustworthy CMDB. InServiceNow, this capability is primarily delivered byDiscoveryandService Mapping.

Discovery(Option C) automatically identifies infrastructure components—such as servers, network devices, and storage—and createstechnical relationshipsbetween them (for example, “runs on,” “connected to,” or “depends on”). These relationships form the backbone of infrastructure dependency mapping.

Service Mapping(Option B) builds on Discovery by creatingapplication- and service-level relationships. It maps how application components interact across servers, databases, and middleware, resulting in accurateApplication Servicemodels aligned with CSDM. These relationships are created and maintained automatically as the environment changes.

Option A (IntegrationHub ETL) focuses on data ingestion and transformation; it does not inherently create or maintain relationships unless explicitly scripted. Option D (Workflow Studio) orchestrates processes and automations but does not discover or infer CI relationships.

Therefore, the ServiceNow solutions that create automatic relationships areService MappingandDiscovery, makingOptions B and Ccorrect.

TheUnified Mapis a visualization capability used to understandservice composition, dependencies, and relationshipsacross CIs, Application Services, and infrastructure. InServiceNow, the Unified Map is accessed through theCMDB Workspace.

CMDB Workspace serves as the central experience for CMDB operations, analytics, and visualization. From within the workspace, users can launch the Unified Map to explore how services are constructed, identify dependencies, and analyze impact—leveraging data from Discovery and Service Mapping.

Option A (CI Class Manager) is used forclass hierarchy, ownership, and principal class configuration, not visualization. Option B (CMDB Data Manager) is focused ongovernance and lifecycle policies, such as archival, certification, and attestation, not service mapping views.

Because Unified Map is anoperational and analytical visualization tool, it is correctly accessed viaCMDB Workspace.

Therefore, the correct answer isC – CMDB Workspace.