CMDB Health Verification: Identify Missing or Invalid CI Relationships
An administrator wants to ensure that CI relationship data is accurate. Which tool should be used to identify CIs that have missing or invalid relationships?
Quick Answer
CMDB Health Verification is correct because it is the purpose-built tool for auditing the quality of configuration item data, and relationships are one of its core health dimensions alongside completeness, correctness, and duplication. When an administrator needs to know whether CIs are missing relationships they should have, such as an application not being linked to the server it runs on, Health Verification runs systematic checks against the CMDB and surfaces the gaps through dashboards and reports rather than requiring someone to manually inspect each CI. This makes it the right choice over general reporting tools or ad hoc queries, which can show you what relationships exist but will not proactively flag what is missing or invalid the way a dedicated health check does. The distinction to hold onto is that Health Verification is about ongoing data quality monitoring for CIs already in the database, checking that the information already stored is complete and trustworthy, rather than about discovering new CIs or building relationships in the first place, which is the job of tools like Discovery or Service Mapping. Whenever a scenario describes verifying, auditing, or scoring the accuracy and completeness of existing CMDB data, especially around relationships, attributes, or duplicates, Health Verification is the feature being described, and recognizing that split between quality checking and data collection will help you answer similar questions quickly.
⚠ Common exam trap
Watch out — candidates often confuse Discovery (which creates relationships) with CMDB Health Verification (which validates existing relationships), leading them to choose Discovery as the tool for identifying missing relationships.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
CMDB Health Verification
CMDB Health Verification is the correct tool because it specifically evaluates the completeness and accuracy of CI relationships by running health checks that flag CIs with missing or invalid relationships. It provides a dashboard and reports that highlight relationship gaps, enabling administrators to remediate data quality issues directly.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
CMDB Data Manager
Why it's wrong here
CMDB Data Manager handles updates and imports, not validation.
- ✓
CMDB Health Verification
Why this is correct
CMDB Health Verification runs checks on CI data including relationships.
- ✗
Discovery
Why it's wrong here
Discovers CIs and relationships, but does not specifically identify missing or invalid relationships.
- ✗
CI Change Request
Why it's wrong here
CI Change Request associates CIs with changes, but does not validate relationships.
Go deeper
Related to this question
About these practice questions
One of 504 original SNOW-CSA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on SNOW-CSA
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An administrator wants to ensure that the CMDB remains accurate after a change management process. Which TWO actions should the administrator take? (Select two.)
medium- ✓ A.Use CI Change Request to link CIs to change requests.
- B.Create a business rule to update CI status when a change request is approved.
- C.Set up CMDB Data Manager to automatically update CIs based on change requests.
- D.Enable CMDB CI Class Manager to enforce class hierarchy.
- ✓ E.Configure CMDB Health Verification to run daily on all CIs.
Why A: Running CMDB Health Verification helps identify stale or incorrect CIs, ensuring accuracy. Using CI Change Request links CIs to change requests, automatically updating status. Option B (creating a business rule) is a custom approach, not a standard best practice. Option C (Data Manager) is for bulk updates, not accuracy. Option D (CI Class Manager) enforces class hierarchy but does not directly ensure accuracy after change management.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SNOW-CSA practice question is part of Courseiva's free ServiceNow certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SNOW-CSA exam.