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.
Question 221 A government data center has CMDB duplicates following a migration from legacy inventory to Service Graph Connectors. Old and new feeds create separate CIs for the same physical storage controller. Which choice most directly solves this issue? Normalize identifiers and validate source mapping through IRE before repeating batch imports Compare device serial, class and IRE source identifiers before approving a merge Keep the records separate and correct any misleading display labels Choose a survivor and reconcile retained fields and references through the supported deduplication process Explanation Correct Answer B:Mapping evidence is required to distinguish duplicate identity from two controllers in a redundancy pair. Incorrect Answers A:Future source writes must converge on the same identity to keep deduplication work durable. C:Name collisions across sites should not collapse two genuine routers into one operational record. D:Correct remediation requires preserving the stronger attributes and links rather than keeping the newest row blindly.
Question 222 A government data center has CMDB duplicates following a migration from legacy inventory to Service Graph Connectors. One duplicate record contains the correct owner while the other holds the active change history. How should the team proceed without weakening data integrity? Restrict cleanup to verified duplicate or retired records after relationship and lifecycle review Choose a survivor and reconcile retained fields and references through the supported deduplication process Compare device serial, class and IRE source identifiers before approving a merge Track incoming identifier errors in addition to the deduplication health metric Explanation Correct Answer B:Correct remediation requires preserving the stronger attributes and links rather than keeping the newest row blindly. Incorrect Answers A:While Restrict cleanup to verified duplicate or retired records after relationship and lifecycle review is suitable if the migration team proposes deleting all CIs created by the old integration because broad source-based deletion can remove the only correct CI for a device no longer visible to the new feed, the presented problem is one duplicate record contains the correct owner while the other holds the active change history, making Choose a survivor and reconcile retained fields and references through the supported deduplication process the better choice. C:Mapping evidence is required to distinguish duplicate identity from two controllers in a redundancy pair. D:A declining backlog does not prove the underlying import is consistently identifying CIs.
Question 223 A government data center has CMDB duplicates following a migration from legacy inventory to Service Graph Connectors. The migration team proposes deleting all CIs created by the old integration. Which option matches this operational need? Choose a survivor and reconcile retained fields and references through the supported deduplication process Use a deduplication task or wizard to review the records and decide the authoritative survivor Restrict cleanup to verified duplicate or retired records after relationship and lifecycle review Normalize identifiers and validate source mapping through IRE before repeating batch imports Explanation Correct Answer C:Broad source-based deletion can remove the only correct CI for a device no longer visible to the new feed. Incorrect Answers A:Correct remediation requires preserving the stronger attributes and links rather than keeping the newest row blindly. B:Manual deletion without reviewing attributes and references can orphan incidents and service links. D:Future source writes must converge on the same identity to keep deduplication work durable.
Question 224 A government data center has CMDB duplicates following a migration from legacy inventory to Service Graph Connectors. New connector runs still fail to match CIs created by the legacy source. What should the implementation specialist do next? Compare device serial, class and IRE source identifiers before approving a merge Restrict cleanup to verified duplicate or retired records after relationship and lifecycle review Correct the upstream identification rule or import mapping that recreates the second CI Normalize identifiers and validate source mapping through IRE before repeating batch imports Explanation Correct Answer D:Future source writes must converge on the same identity to keep deduplication work durable. Incorrect Answers A:Mapping evidence is required to distinguish duplicate identity from two controllers in a redundancy pair. B:Broad source-based deletion can remove the only correct CI for a device no longer visible to the new feed. C:Merging existing CIs treats symptoms.
Question 225 A hospital's CMDB contains duplicate imaging servers after a supplier replaced a management agent. The new agent changes its source identifier but the physical machine is unchanged. Which implementation should the CMDB team select? Track incoming identifier errors in addition to the deduplication health metric Review both sets of dependent records during a supported deduplication wizard action Retain hardware-stable identification criteria so the agent change does not generate a new CI Preserve separate CIs after confirming independent serial numbers and failover roles Explanation Correct Answer C:Device identity should not depend solely on a replaceable management-agent registration ID. Incorrect Answers A:A declining backlog does not prove the underlying import is consistently identifying CIs. B:A survivor should retain relevant incident and clinical service relationships for accurate operational history. D:A redundant pair must remain two managed devices even if it shares a service name.
Question 226 A hospital's CMDB contains duplicate imaging servers after a supplier replaced a management agent. Clinical incident records are split across two server CIs. Which action best addresses the specific requirement? Preserve separate CIs after confirming independent serial numbers and failover roles Inspect the active identification rule and subsequent import results for recurring matching defects Normalize identifiers and validate source mapping through IRE before repeating batch imports Review both sets of dependent records during a supported deduplication wizard action Explanation Correct Answer D:A survivor should retain relevant incident and clinical service relationships for accurate operational history. Incorrect Answers A:A redundant pair must remain two managed devices even if it shares a service name. B:Sustained duplicate reduction requires fixing generation, not repeatedly hiding the scorecard entry. C:Future source writes must converge on the same identity to keep deduplication work durable.
Question 227 A hospital's CMDB contains duplicate imaging servers after a supplier replaced a management agent. One alleged duplicate is actually a separate active-standby imaging appliance. What should the administrator verify or change? Choose a survivor and reconcile retained fields and references through the supported deduplication process Retain hardware-stable identification criteria so the agent change does not generate a new CI Inspect the active identification rule and subsequent import results for recurring matching defects Preserve separate CIs after confirming independent serial numbers and failover roles Explanation Correct Answer D:A redundant pair must remain two managed devices even if it shares a service name. Incorrect Answers A:Correct remediation requires preserving the stronger attributes and links rather than keeping the newest row blindly. B:Device identity should not depend solely on a replaceable management-agent registration ID. C:Sustained duplicate reduction requires fixing generation, not repeatedly hiding the scorecard entry.
Question 228 A hospital's CMDB contains duplicate imaging servers after a supplier replaced a management agent. The health dashboard continues to flag duplicate identity after remediation. Which choice most directly solves this issue? Inspect the active identification rule and subsequent import results for recurring matching defects Review both sets of dependent records during a supported deduplication wizard action 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 Explanation Correct Answer A:Sustained duplicate reduction requires fixing generation, not repeatedly hiding the scorecard entry. Incorrect Answers B:A survivor should retain relevant incident and clinical service relationships for accurate operational history. C: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 health dashboard continues to flag duplicate identity after remediation, making Inspect the active identification rule and subsequent import results for recurring matching defects the better choice. D:Device identity should not depend solely on a replaceable management-agent registration ID.
Question 229 An insurance company is establishing a CMDB governance board with teams from infrastructure, procurement and application operations. No one can authorize changes to the CI class model. Which option matches this operational need? Assign accountable ownership for CMDB schema and class design decisions Map affected CI classes to managed-by groups and remediation owners Preserve change requests, approvers and postchange validation for class and rule modifications Set measurable quality and operational KPIs tied to class coverage and incident/change outcomes Explanation Correct Answer A:Governance needs a clear decision owner to prevent competing groups from customizing the shared CI taxonomy independently. Incorrect Answers B:While Map affected CI classes to managed-by groups and remediation owners is suitable if health tasks are assigned to a generic mailbox without an operational owner because quality findings need accountable resolver groups rather than remaining anonymous dashboard counts, the presented problem is no one can authorize changes to the CI class model, making Assign accountable ownership for CMDB schema and class design decisions the better choice. C:Provenance links sensitive configuration changes to accountable authorization and verified results. D:CI count alone cannot establish better service impact, faster triage, or accurate data stewardship.
Question 230 An insurance company is establishing a CMDB governance board with teams from infrastructure, procurement and application operations. Import data repeatedly overwrites fields that business teams regard as authoritative. What should the implementation specialist do next? Require governed change review and representative regression tests for shared matching rules Assign accountable ownership for CMDB schema and class design decisions Define data source ownership and reconciliation escalation responsibilities Set measurable quality and operational KPIs tied to class coverage and incident/change outcomes Explanation Correct Answer C:Each critical attribute needs a trusted data source and a process for resolving conflicting updates. Incorrect Answers A:While Require governed change review and representative regression tests for shared matching rules is suitable if regional CMDB teams frequently change identification rules independently because identification changes have cross-source effects and need stronger controls than local form preference adjustments, the presented problem is import data repeatedly overwrites fields that business teams regard as authoritative, making Define data source ownership and reconciliation escalation responsibilities the better choice. B:Governance needs a clear decision owner to prevent competing groups from customizing the shared CI taxonomy independently. D:CI count alone cannot establish better service impact, faster triage, or accurate data stewardship.