A CMDB Administrator identifies duplicate CIs. One was created by a manual import, and the other was created by automated discovery. The discovered CI has the latest IP address, while the manually imported CI has an accurate relationship to a critical business application. How does the Administrator use the Duplicate CI Remediator to resolve this issue?

The Duplicate CI Remediator is designed to resolve de-duplication tasks by allowing an administrator to merge valuable information from multiple duplicate CIs into a single, authoritative "master" CI. In this scenario, the best practice is to select the most up-to-date CI (the discovered one) as the master and then selectively merge critical data, such as the business application relationship, from the duplicate CI before it is deleted. This ensures no critical data is lost during the remediation process.

A. This approach would lose the critical relationship data from the manually imported CI, which is an undesirable outcome.
B. This approach would result in losing the most current IP address, making the retained CI's data stale.
D. This approach is incorrect because it discards the critical relationship information without merging it into the retained CI.

1. ServiceNow Product Documentation. (2024). Remediate a de-duplication task. ServiceNow. Retrieved from the ServiceNow Product Documentation site. The documentation details the process: "In the Remediate dialog box, you can compare the duplicate CIs, select a CI to be the master CI, and then merge any relationships... from the other CIs to the master CI."