ServiceNow CMDB Reconciliation Rules Practice
Unlimited ServiceNow CMDB practice on reconciliation rules: may this discovery source update this CI attribute? Each problem gives four static rules on cmdb_ci_computer and its child class cmdb_ci_linux_server, plus the last update. Decide if a new value is accepted, then tap the rules in force. A wrong answer names the slip, such as letting priority beat a rule that lists the attribute.
Static reconciliation rules
Every rule here is an active static rule, set before the last update, and there are no dynamic rules. Effective Duration comes from the data refresh rule for the last update's source on the CI's class.
CMDB exam prep
Practice question packs for the ServiceNow CIS Data Foundations and CIS Discovery exams. Start with the free real exam questions, then get the full pack.
Reconciliation FAQ
What does a reconciliation rule do?
Reconciliation rules decide which discovery sources can update CI attributes. Without them, discovery sources can overwrite each other's updates. A static rule names a discovery source, a class, the attributes it may update and a priority.
Does a higher priority rule beat a rule for a specific attribute?
No. A rule configured for a specific attribute has precedence over a rule set to apply to all attributes, regardless of the priority value. So an all attributes rule at priority 100 loses that attribute to a rule that lists it at priority 150.
What does an empty Attributes list mean?
It means all attributes in the class. In ServiceNow's example, leaving the Attributes field empty authorizes ServiceWatch to update all attributes in cmdb_ci_linux_server. It is not a rule for no attributes.
Do child class rules override parent class rules?
Yes. Child classes derive the rules of their parent class, and a rule defined directly for the child class overrides the derived rule for the attributes they share. In ServiceNow's example, Discovery may update name on cmdb_ci_computer, but a ServiceWatch rule for name on cmdb_ci_linux_server means only ServiceWatch may update name on Linux servers. A rule for a specific attribute still comes first: a parent rule that lists name beats a child rule for all attributes.
Is a smaller priority number a higher priority?
Yes. Smaller numbers designate higher priority. After an authorized source updates an attribute, later updates are accepted only from the same source or from a source with a higher priority.
When can a lower priority source update the CI?
When the CI is stale for the source that last updated it. A data refresh rule gives that source an Effective Duration: if it has not updated the CI within that time, a lower priority authorized source may update it. With the default Effective Duration of 0, the CI is stale right after each update, so a lower priority source is always authorized.
Does a stale CI let an all attributes rule win?
No. A rule that applies to all attributes does not have precedence over a lower priority rule that applies to a specific attribute, even if the CI is stale. Data refresh rules do not change the precedence order of the reconciliation rules.
Can two sources be authorized for the same attribute?
Yes. Static rules that authorize different discovery sources for the same attributes of the same class can coexist. Both sources may update the attribute, and their priorities stop them from overwriting each other's updates.
What about dynamic reconciliation rules?
They need CMDB 360. When a static and a dynamic rule exist for the same CI attribute, the dynamic rule takes precedence, and data refresh rules have no impact while dynamic rules are in effect. This drill uses static rules only.
What does this drill leave out?
Equal priorities, sources that have no rule at all, the first update of a new CI, data refresh rules on a parent class, a time exactly equal to the Effective Duration, dynamic rules and more than one level of classes.
Sources
- ServiceNow docs (Brazil), Reconciliation rules: the cmdb_ci_computer and cmdb_ci_linux_server example rules; rules are derived by child classes; an empty Attributes list covers all attributes; a rule for specific attributes overrides one with an empty list; child class rules override parent class rules; overlapping rules coexist; dynamic rules take precedence.
- ServiceNow docs (Brazil), Create a CI reconciliation rule: the precedence order of static rules (specific attribute first regardless of priority, then the rule directly for the class, then priority); smaller numbers designate higher priority; later updates only from the same source or a higher priority one, unless the CI is stale; all attributes rules lose to specific ones even if the CI is stale.
- ServiceNow docs (Brazil), Create a data refresh rule: Effective Duration and staleness for a discovery source, the default of 0, and no impact under dynamic rules.
- ServiceNow docs (Brazil), General guidelines for using CMDB Identification: the cmdb_ci_linux_server payload examples with the name, ram and short_description attributes used here.
- Checked 21 November 2026. The tool's own approach: problems are invented; every rule is an active static rule set before the last update; every source in a problem has a rule; the cases under "What does this drill leave out?" never appear. An independent re-solver (written separately in Python, reading only the text on screen) agreed with the drill on 20,000 generated problems.
Checked 21 November 2026 against ServiceNow's CMDB reconciliation rule and data refresh rule documentation (Brazil release).
- DrillServiceNow ACL practiceDecide if a read or write is granted and tap the ACL that decides it.
- DrillSalesforce record access practiceTap the access a user gets from OWD, roles, sharing rules, teams and View All.
- DrillSnowflake access control practiceDecide if a role can query a table from the role hierarchy, USAGE and future grants, and tap the missing grant.