SNOW-CSA Database Administration and CMDB Practice Question
A company has an enterprise ServiceNow instance with a CMDB that contains over 50,000 CIs. The instance is integrated with multiple discovery tools: ServiceNow Discovery, a third-party IPAM tool, and a cloud management platform. Recently, the CMDB health score dropped significantly due to an increase in duplicate CIs. Upon investigation, you find that many CIs from the IPAM tool have the same serial number as CIs discovered by ServiceNow Discovery, but with slight differences in the hardware model field. Also, the cloud management platform creates CIs with the same name but different serial numbers. The business requires that each physical device should have only one CI record, and the serial number is the authoritative identifier. The current reconciliation rules are set to merge based on name and IP address, but they are not effectively resolving duplicates. What should the administrator do to resolve this issue most effectively?
⚠ Common exam trap
Candidates often think adding a unique constraint (Option B) is sufficient, but they overlook that existing duplicates must be resolved first, and a unique constraint alone does not handle the reconciliation of CIs from multiple discovery sources with differing non-key attributes.
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
✓
Modify the reconciliation rule to match on serial number instead of name and IP
The business requirement states that serial number is the authoritative identifier for physical devices. By modifying the reconciliation rule to match on serial number instead of name and IP, the system will correctly identify and merge duplicate CIs that share the same serial number, even if other fields like hardware model differ. This directly addresses the root cause of the duplicate CIs from the IPAM tool and cloud management platform.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create an approval workflow for every new CI creation to manually check for duplicates
Why it's wrong here
Not scalable for 50k CIs; would introduce bottlenecks.
- ✗
Add a unique constraint on the serial number field to prevent future duplicates
Why it's wrong here
Unique constraint prevents new duplicates but existing duplicates will still cause errors and need to be resolved manually.
- ✓
Modify the reconciliation rule to match on serial number instead of name and IP
Why this is correct
Serial number is the authoritative identifier; matching on it will accurately identify duplicates across sources.
- ✗
Disable the IPAM tool and cloud management platform integrations to stop duplicate creation
Why it's wrong here
This loses valuable data and does not solve the existing duplicates.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every SNOW-CSA question from scratch — 504 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
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.