The correct answer is that reconciliation rules define which source has priority for updating CI attributes. This is because the Identification and Reconciliation Engine (IRE) in ServiceNow CMDB processes incoming CI data from Discovery, Service Mapping, or integrations by first running identification rules to match the CI to an existing record, then applying reconciliation rules to resolve attribute conflicts based on source priority, ensuring data integrity. On the ServiceNow Certified System Administrator CSA exam, this concept tests your understanding of how the IRE prevents data overwrites from lower-priority sources, often appearing in questions that contrast identification rules (which find the CI) with reconciliation rules (which decide which source’s data wins). A common trap is confusing these two functions, so remember: identification finds the needle, reconciliation decides whose thread sews it. A useful memory tip is “IRE: Identify first, Reconcile second—priority wins.”
SNOW-CSA Database Administration and CMDB Practice Question
This SNOW-CSA practice question tests your understanding of database administration and cmdb. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which TWO statements about ServiceNow CMDB identification and reconciliation are correct?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The Identification and Reconciliation (IRE) engine processes incoming CI data.
Option B is correct because the Identification and Reconciliation (IRE) engine is the ServiceNow component responsible for processing incoming CI data from sources like Discovery, Service Mapping, or integrations. It applies identification rules to determine if a CI already exists and reconciliation rules to resolve attribute conflicts, ensuring data integrity in the CMDB.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The 'Source' field on a CI can be set per attribute.
Why it's wrong here
Source is set at the CI level, not per attribute.
✓
The Identification and Reconciliation (IRE) engine processes incoming CI data.
Why this is correct
The IRE handles identification and reconciliation of CI data.
Related concept
Read the scenario before looking for a memorised answer.
✗
Reconciliation rules are used to identify duplicate CIs.
Why it's wrong here
Identification rules, not reconciliation, handle duplicates.
✓
Reconciliation rules define which source has priority for updating CI attributes.
Why this is correct
Reconciliation rules determine source priority.
Related concept
Read the scenario before looking for a memorised answer.
✗
The CMDB automatically deletes duplicate CIs when detected.
Why it's wrong here
Duplicates are flagged but not automatically deleted.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse the roles of identification rules (which find duplicates) with reconciliation rules (which resolve attribute conflicts), leading them to incorrectly select option C as correct.
Detailed technical explanation
How to think about this question
Under the hood, the IRE engine uses a three-phase process: identification (matching via identifier fields), reconciliation (applying priority rules to resolve attribute conflicts), and then updating or creating the CI. A subtle behavior is that if no identification rule matches, the IRE creates a new CI, but if multiple matches are found, it can create a duplicate unless a 'deny duplicate' rule is configured. In a real-world scenario, a network switch discovered by both SNMP Discovery and a cloud API might have conflicting 'location' attributes, and reconciliation rules with source priority (e.g., 'Discovery' over 'API') ensure the correct value is retained.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the SNOW-CSA exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Database Administration and CMDB — This question tests Database Administration and CMDB — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The Identification and Reconciliation (IRE) engine processes incoming CI data. — Option B is correct because the Identification and Reconciliation (IRE) engine is the ServiceNow component responsible for processing incoming CI data from sources like Discovery, Service Mapping, or integrations. It applies identification rules to determine if a CI already exists and reconciliation rules to resolve attribute conflicts, ensuring data integrity in the CMDB.
What should I do if I get this SNOW-CSA question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
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. A CMDB administrator notices that duplicate CIs are being created for the same server from different discovery sources. What is the most likely cause?
easy
✓ A.The identification rules for the CI class are not correctly defined.
B.The 'Prevent duplicates' flag is not enabled.
C.The reconciliation rules are misconfigured.
D.The CMDB is set to read-only mode.
Why A: Duplicate CIs occur when multiple discovery sources (e.g., Service Mapping, Discovery, or cloud APIs) identify the same server but the identification rules fail to reconcile them into a single CI. Identification rules define which attributes (such as serial number, MAC address, or FQDN) uniquely identify a CI class. If these rules are missing, incomplete, or incorrectly prioritized, the system treats each discovery event as a new CI, leading to duplicates.
Variation 2. During a CMDB health review, an administrator finds that many CI records have the same serial number but different names and IP addresses. What is the most likely root cause?
hard
A.The CMDB has a scheduled job that deletes old CIs.
B.The CI class has a unique constraint on the name field.
✓ C.The identification rule for the CI class does not include the serial number.
D.The reconciliation rule is set to 'Create' instead of 'Update'.
Why C: The correct answer is C because the identification rule determines which fields are used to uniquely identify a CI. If the serial number is not included in the identification rule, the CMDB cannot detect duplicates based on serial number, allowing multiple CIs with the same serial number but different names and IP addresses to be created. This is a common misconfiguration that leads to CI proliferation and data inconsistency.
Variation 3. An administrator inspects the IRE log and sees the exhibit. The IRE created a new CI despite finding a match on serial_number. What is the most likely reason?
hard
A.The identification rule for cmdb_ci_server includes serial_number.
B.The IRE is configured to always create new records regardless of matches.
✓ C.The identification rule for cmdb_ci_server does NOT include serial_number.
D.The existing CI has a different name, so IRE considers it a different CI.
Why C: Option C is correct because the IRE uses identification rules to determine which attributes are used for matching CIs. If the identification rule for cmdb_ci_server does NOT include serial_number, then even though a match on serial_number exists, the IRE will not consider it a match and will create a new CI. The IRE only reconciles based on the attributes defined in the identification rule.
Variation 4. An administrator discovers that a scheduled discovery job is creating duplicate CI records for the same physical server. The server has two IP addresses (one for management, one for production). What is the most likely cause?
hard
A.The discovery schedule is set to run too frequently.
B.The discovery job is configured to scan only the management IP.
✓ C.The identification rule for the CI class does not include a unique hardware identifier like serial number.
D.The server has too many IP addresses for discovery to handle.
Why C: Option C is correct because ServiceNow's CMDB uses identification rules to determine whether a discovered CI is new or matches an existing record. For a physical server with multiple IP addresses, the identification rule must include a unique hardware identifier such as a serial number (e.g., from SMBIOS) to prevent duplicate CIs. Without that, the system may treat each IP address as a separate CI, even though they belong to the same server.
Variation 5. Based on the exhibit, why did the identification rule fail?
hard
✓ A.The serial_number field is empty, but the rule requires it to be non-empty.
B.The name field is missing from the payload.
C.The rule has a dependency that is not satisfied.
D.The ip_address field is not included in the identification rule.
Why A: The identification rule fails because the serial_number field, which is defined as a required identifier field in the rule configuration, is empty in the incoming payload. ServiceNow CMDB identification rules use a set of fields to uniquely identify CI records; if any required field is missing or null, the rule cannot match or create a record, resulting in a failure. In this case, the payload contains the serial_number field but with no value, which the rule treats as a violation of its non-empty constraint.
Last reviewed: Jun 11, 2026
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.