Question 560
A ServiceNow administrator finds: A CMDB dashboard reports ten thousand CIs but has no warning that most lack support owners. 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: A CMDB dashboard reports ten thousand CIs but has no warning that most lack support owners. The appropriate control is: Monitor CMDB completeness, correctness, duplication and aging indicators with accountable remediation rather than treating a populated table as trustworthy. It addresses the risk that a large CI count can hide stale, orphaned and noncompliant items that distort incident triage and service ownership. Check effectiveness with: A measured health baseline shows fewer duplicates, stale entries and missing required attributes after targeted fixes.
Incorrect Answers
Cmdb identification and reconciliation engine: Two discovery sources can create duplicate CIs or overwrite trusted fields when identifiers and source precedence are unclear. That mechanism alone cannot establish Cmdb health completeness correctness and compliance for this question.
Common service data model and business services: Mixing service portfolio concepts with infrastructure CIs produces inconsistent ownership and unreliable impact reporting. That may be useful independently, but the missing requirement here is Cmdb health completeness correctness and compliance.
Cmdb relationship modeling and service impact: Incorrect relationships can make impact analysis miss critical dependent applications or falsely identify unrelated services as affected. Here the decisive check is Cmdb health completeness correctness and compliance, not that separate capability.