TheCMDBis a foundational capability that enables organizations to operate IT services withconfidence, resilience, and efficiency. Its value lies not in automation for its own sake or financial data management, but in how it supportsservice-aware operations and decision-making.
Strengthening operational resiliency(Option A) is a core value of the CMDB. By maintaining accurate configuration data and relationships, organizations can better understand dependencies, assess risk, and recover more quickly from incidents or outages. A trusted CMDB enables proactive problem management and informed change planning, directly contributing to resiliency.
Streamlining Incident and Change Management(Option B) is another primary value. Accurate CI data allows incidents to be routed automatically to the correct support groups, enables faster root-cause analysis, and supports risk-based change assessments. This reduces manual effort, improves response times, and lowers operational risk.
Option C is incorrect becauseautomating CI relationship maintenanceis a capability enabled by tools like Discovery and Service Mapping-not a value in itself. Option D is also incorrect becausefinancial data managementis the domain of IT Asset Management (ITAM) and Financial Management, not the CMDB's core value proposition.
In summary, the CMDB delivers value byimproving operational resilienceandoptimizing ITSM processes, makingOptions A and Bthe correct answers.

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.