Question 540
A ServiceNow administrator finds: Two integrations create separate CIs for one physical host because one uses name and the other serial identity. The intended correction must preserve access controls, business process consistency and the supported platform configuration. Which administrative change most directly addresses this specific failure?
Explanation
Correct Answer
The decisive detail is: Two integrations create separate CIs for one physical host because one uses name and the other serial identity. The appropriate control is: Use supported CI identification and reconciliation rules to avoid duplicate CI identities and protect authoritative attribute ownership. It addresses the risk that two discovery sources can create duplicate CIs or overwrite trusted fields when identifiers and source precedence are unclear. Check effectiveness with: A replay from independent sources resolves to the same intended CI and honors approved attribute ownership.
Incorrect Answers
Common service data model and business services: Mixing service portfolio concepts with infrastructure CIs produces inconsistent ownership and unreliable impact reporting. That mechanism alone cannot establish Cmdb identification and reconciliation engine for this question.
Cmdb relationship modeling and service impact: Incorrect relationships can make impact analysis miss critical dependent applications or falsely identify unrelated services as affected. That may be useful independently, but the missing requirement here is Cmdb identification and reconciliation engine.
Cmdb health completeness correctness and compliance: A large CI count can hide stale, orphaned and noncompliant items that distort incident triage and service ownership. Here the decisive check is Cmdb identification and reconciliation engine, not that separate capability.