Question 210 A bank's overnight infrastructure feeds have produced duplicate server CIs with different open incident histories. The analyst wants to merge a verified pair without discarding meaningful relationships. Which option matches this operational need? Open the deduplication task and inspect both CI histories before selecting a survivor Review candidate identity and preserve support references during the supported merge workflow Use the supported deduplication wizard and review records, fields and relationships before committing Correct the upstream identification rule or import mapping that recreates the second CI Explanation Correct Answer C:Guided deduplication helps preserve operational references while collapsing confirmed duplicate identity. Incorrect Answers A:A duplicate warning is a starting point. B:Data remediation must maintain ticket and dependency links as the duplicates become one operational CI. D:Merging existing CIs treats symptoms.
Question 211 A bank's overnight infrastructure feeds have produced duplicate server CIs with different open incident histories. The duplicate is still recreated every morning after manual cleanup. What should the implementation specialist do next? Use the supported deduplication wizard and review records, fields and relationships before committing Reject the false duplicate candidate after comparing authoritative identifiers Correct the upstream identification rule or import mapping that recreates the second CI Track incoming identifier errors in addition to the deduplication health metric Explanation Correct Answer C:Merging existing CIs treats symptoms; faulty source identity will regenerate duplicates on the next ingestion. Incorrect Answers A:Guided deduplication helps preserve operational references while collapsing confirmed duplicate identity. B:Similar names alone do not prove duplicate physical identity and must not trigger an unsafe merge. D:While Track incoming identifier errors in addition to the deduplication health metric is suitable if a clean-up dashboard shows duplicate counts decreasing while source match failures continue because a declining backlog does not prove the underlying import is consistently identifying CIs, the presented problem is the duplicate is still recreated every morning after manual cleanup, making Correct the upstream identification rule or import mapping that recreates the second CI the better choice.
Question 212 A bank's overnight infrastructure feeds have produced duplicate server CIs with different open incident histories. Two servers share a name but represent different hardware. What is the most defensible ServiceNow approach? Keep the records separate and correct any misleading display labels Correct the upstream identification rule or import mapping that recreates the second CI Open the deduplication task and inspect both CI histories before selecting a survivor Reject the false duplicate candidate after comparing authoritative identifiers Explanation Correct Answer D:Similar names alone do not prove duplicate physical identity and must not trigger an unsafe merge. Incorrect Answers A:Name collisions across sites should not collapse two genuine routers into one operational record. B:Merging existing CIs treats symptoms. C:While Open the deduplication task and inspect both CI histories before selecting a survivor is suitable if the duplicate engine identifies two CIs with identical stable hardware identifiers because a duplicate warning is a starting point; merging blindly can lose the incident and relationship context attached to either record, the presented problem is two servers share a name but represent different hardware, making Reject the false duplicate candidate after comparing authoritative identifiers the better choice.
Question 213 A large retailer sees duplicates for cashier workstations imported from endpoint management and procurement systems. Two records represent the same workstation and the support ticket references only one. Which action best addresses the specific requirement? Choose a survivor and reconcile retained fields and references through the supported deduplication process Revise IRE identification mapping to use stable authorized device identifiers Validate them as distinct assets and avoid merging based on display name similarity Review candidate identity and preserve support references during the supported merge workflow Explanation Correct Answer D:Data remediation must maintain ticket and dependency links as the duplicates become one operational CI. Incorrect Answers A:Correct remediation requires preserving the stronger attributes and links rather than keeping the newest row blindly. B:While Revise IRE identification mapping to use stable authorized device identifiers is suitable if the import uses temporary workstation names as the only identifier because a changeable hostname can create another CI when a device is renamed or reimaged, the presented problem is two records represent the same workstation and the support ticket references only one, making Review candidate identity and preserve support references during the supported merge workflow the better choice. C:Two real devices with a reused label are not the same CI and require separate lifecycles.
Question 214 A large retailer sees duplicates for cashier workstations imported from endpoint management and procurement systems. The import uses temporary workstation names as the only identifier. What should the administrator verify or change? Validate them as distinct assets and avoid merging based on display name similarity Track incoming identifier errors in addition to the deduplication health metric Retain hardware-stable identification criteria so the agent change does not generate a new CI Revise IRE identification mapping to use stable authorized device identifiers Explanation Correct Answer D:A changeable hostname can create another CI when a device is renamed or reimaged. Incorrect Answers A:While Validate them as distinct assets and avoid merging based on display name similarity is suitable if a deduplication task appears for two workstations that have separate valid serial numbers because two real devices with a reused label are not the same CI and require separate lifecycles, the presented problem is the import uses temporary workstation names as the only identifier, making Revise IRE identification mapping to use stable authorized device identifiers the better choice. B:A declining backlog does not prove the underlying import is consistently identifying CIs. C:Device identity should not depend solely on a replaceable management-agent registration ID.
Question 215 A large retailer sees duplicates for cashier workstations imported from endpoint management and procurement systems. A deduplication task appears for two workstations that have separate valid serial numbers. Which choice most directly solves this issue? Track incoming identifier errors in addition to the deduplication health metric Validate them as distinct assets and avoid merging based on display name similarity Preserve separate CIs after confirming independent serial numbers and failover roles Review candidate identity and preserve support references during the supported merge workflow Explanation Correct Answer B:Two real devices with a reused label are not the same CI and require separate lifecycles. Incorrect Answers A:A declining backlog does not prove the underlying import is consistently identifying CIs. C:A redundant pair must remain two managed devices even if it shares a service name. D:Data remediation must maintain ticket and dependency links as the duplicates become one operational CI.
Question 216 A large retailer sees duplicates for cashier workstations imported from endpoint management and procurement systems. A clean-up dashboard shows duplicate counts decreasing while source match failures continue. How should the team proceed without weakening data integrity? Inspect the active identification rule and subsequent import results for recurring matching defects Track incoming identifier errors in addition to the deduplication health metric Revise IRE identification mapping to use stable authorized device identifiers Review candidate identity and preserve support references during the supported merge workflow Explanation Correct Answer B:A declining backlog does not prove the underlying import is consistently identifying CIs. Incorrect Answers A:Sustained duplicate reduction requires fixing generation, not repeatedly hiding the scorecard entry. C:A changeable hostname can create another CI when a device is renamed or reimaged. D:Data remediation must maintain ticket and dependency links as the duplicates become one operational CI.
Question 217 A telecommunications provider is implementing an ongoing duplicate management procedure for its router CMDB. A router appears twice because two scanners provide different source-native IDs. What should the implementation specialist do next? Verify that all contributing sources now use the corrected IRE identifier mapping Keep the records separate and correct any misleading display labels Correlate stable serial and device identifiers and adjust the class identification strategy Reject the false duplicate candidate after comparing authoritative identifiers Explanation Correct Answer C:A common identity rule reduces duplicate creation without trusting a single source's display identifier. Incorrect Answers A:Persistent duplicates indicate an unresolved identity pipeline, not a wizard malfunction. B:Name collisions across sites should not collapse two genuine routers into one operational record. D:Similar names alone do not prove duplicate physical identity and must not trigger an unsafe merge.
Question 218 A telecommunications provider is implementing an ongoing duplicate management procedure for its router CMDB. The team needs to inspect the details of a suspected duplicate before deleting either record. What is the most defensible ServiceNow approach? Use a deduplication task or wizard to review the records and decide the authoritative survivor Verify that all contributing sources now use the corrected IRE identifier mapping Restrict cleanup to verified duplicate or retired records after relationship and lifecycle review Correlate stable serial and device identifiers and adjust the class identification strategy Explanation Correct Answer A:Manual deletion without reviewing attributes and references can orphan incidents and service links. Incorrect Answers B:Persistent duplicates indicate an unresolved identity pipeline, not a wizard malfunction. C:Broad source-based deletion can remove the only correct CI for a device no longer visible to the new feed. D:Two scanners provide different source-native IDs, for which a common identity rule reduces duplicate creation without trusting a single source's display identifier.
Question 219 A telecommunications provider is implementing an ongoing duplicate management procedure for its router CMDB. A device name matches another router at a different branch with distinct serials. Which implementation should the CMDB team select? Correlate stable serial and device identifiers and adjust the class identification strategy Keep the records separate and correct any misleading display labels Use a deduplication task or wizard to review the records and decide the authoritative survivor Reject the false duplicate candidate after comparing authoritative identifiers Explanation Correct Answer B:Name collisions across sites should not collapse two genuine routers into one operational record. Incorrect Answers A:Two scanners provide different source-native IDs, where a common identity rule reduces duplicate creation without trusting a single source's display identifier. C:Manual deletion without reviewing attributes and references can orphan incidents and service links. D:While Reject the false duplicate candidate after comparing authoritative identifiers is suitable if two servers share a name but represent different hardware because similar names alone do not prove duplicate physical identity and must not trigger an unsafe merge, the presented problem is a device name matches another router at a different branch with distinct serials, making Keep the records separate and correct any misleading display labels the better choice.
Question 220 A telecommunications provider is implementing an ongoing duplicate management procedure for its router CMDB. The merged router becomes duplicated again after a scheduled discovery run. Which action best addresses the specific requirement? Use a deduplication task or wizard to review the records and decide the authoritative survivor Validate them as distinct assets and avoid merging based on display name similarity Verify that all contributing sources now use the corrected IRE identifier mapping Keep the records separate and correct any misleading display labels Explanation Correct Answer C:Persistent duplicates indicate an unresolved identity pipeline, not a wizard malfunction. Incorrect Answers A:Manual deletion without reviewing attributes and references can orphan incidents and service links. B:Two real devices with a reused label are not the same CI and require separate lifecycles. D:Name collisions across sites should not collapse two genuine routers into one operational record.