The Identification and Reconciliation Engine (IRE) is a core platform capability in ServiceNow and does not require CMDB 360 / Multisource CMDB to function. Even without the ITOM Discovery license, organizations can still define and use IRE reconciliation rules across multiple data sources.
IRE rules are source-aware and can evaluate attributes based on source precedence, regardless of whether CMDB 360 is enabled. CMDB 360 enhances visibility, governance, and monitoring of multiple sources, but it is not a prerequisite for 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 a licensed add-on, not a universally available platform feature.
Therefore, the Data Owner can proceed by configuring IRE reconciliation rules directly, making Option B the correct answer.

This scenario hinges on how the Identification and Reconciliation Engine (IRE) in ServiceNow evaluates identification rules.
The identification rule for the Apache Web Server class includes Version as part of the identifier criteria, along with Class and Configuration file. Identification rules must match all criterion attributes exactly for an incoming record to be identified as an existing CI and reconciled.
Yesterday's discovery created an Apache Web Server CI with a specific version value. When Apache is upgraded and discovery is rerun, the Version attribute changes. Because Version is part of the identifier, the incoming record no longer matches the existing CI's identifier entry. As a result, the IRE cannot identify the existing CI as the same configuration item.
When identification fails and no matching identifier entry is found, the IRE proceeds to insert a new CI record rather than updating the existing one. This behavior is intentional and protects the CMDB from incorrectly reconciling records that no longer meet identification criteria.
Option A is incorrect because reconciliation only occurs after successful identification.
Option C is incorrect because reclassification is unrelated to identification criteria.
Option D is incorrect because this is not an error condition; it is expected IRE behavior.
This example highlights a best practice caution: volatile attributes (such as Version) should generally not be used as identifier attributes, as they can cause unintended CI duplication during upgrades.

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.

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.

The CMDB Data Foundations Dashboard helps administrators assess whether important CMDB data is valid, properly configured, and aligned with expected data quality practices. It is designed to surface actionable gaps and risks, then guide remediation through playbooks. Therefore, B and C are correct. The dashboard does not automatically remediate all risks by itself; it guides administrators and data owners toward corrective actions through structured playbooks. It also is not primarily a custom metric development framework. Its purpose is to provide curated, ServiceNow-aligned metrics and remediation guidance for CMDB and CSDM maturity.
This makes it useful for improving data health, identifying configuration issues, and supporting governance without requiring custom reporting or manual analysis from scratch.
=========