CIS-ITSM CMDB — Timed 15 Questions

Question 1

An organization requires that network gear attributes can only be updated by the Network Discovery data source, while server attributes can be updated by both Discovery and a manual import set. Where must this restriction be configured?

15 minute time limit — choose an answer to begin.

Accepted Answer

Reconciliation Definitions. Reconciliation Definitions are used to specify which data source can update which attributes on a CI. By configuring reconciliation definitions, you can set rules that allow only the Network Discovery data source to update network gear attributes, while allowing both Discovery and manual import sets to update server attributes. This provides granular control over attribute-level data source precedence.

Answer

Access Control Lists (ACLs)

Answer

CI Class Manager Identification Rules

Answer

Data Source Precedence Rules

Question 2

An administrator needs to ensure that network gear discovered by Discovery is classified under a specific custom child table of cmdb_ci_netgear. Where should the administrator define the classification criteria to map network devices to this custom table?

Accepted Answer

CI Class Manager. The CI Class Manager is the central console in ServiceNow for managing the CMDB class hierarchy, including creating custom child classes and defining the identification and reconciliation rules that determine which class a discovered CI is placed into. When Discovery finds a network device, the classification criteria (such as SNMP sysObjectID, sysDescr patterns, or other attributes) defined in CI Class Manager determine whether the CI lands in cmdb_ci_netgear or a custom child table. This makes CI Class Manager the correct place to map discovered network gear to a custom child table.

Answer

Discovery Definition > Network Classifications

Answer

CMDB Properties

Answer

CI Identifier Rules module

Question 3

During an import of server CIs, duplicate records are being created because different data sources send serial numbers in different cases (uppercase vs lowercase). Which configuration in Identification and Reconciliation Engine (IRE) will prevent this issue?

Accepted Answer

Enable case-insensitive matching on the identifier entry for the Serial Number attribute.. The Identification and Reconciliation Engine (IRE) allows each identifier entry (such as Serial Number) to be configured with a 'case insensitive' flag. When enabled, IRE normalizes the incoming value before matching, so 'ABC123' and 'abc123' resolve to the same CI instead of creating two records. This is the correct, targeted fix because the duplication is caused purely by case variance in the identifier value.

Answer

Create a custom CMDB Data Manager policy to merge duplicates automatically.

Answer

Set the Reconciliation Rule to discard updates from the secondary data source.

Answer

Modify the Identification Rule weight to a higher number.

Question 4

An organization defines a multi-attribute identification rule for the Linux Server class using 'serial_number' and 'ip_address'. During a payload execution, the IRE finds an existing CI matching the serial number, but the IP address has changed. How does the IRE process this payload?

Accepted Answer

It updates the existing CI's IP address and any other payload attributes, treating it as the same physical asset based on the matching rule entry.. The IRE uses multi-attribute identification rules to determine if a payload matches an existing CI. When multiple attributes are defined, the rule is satisfied if any one of the attributes matches (OR logic). Here, the serial number matches an existing CI, so the IRE treats the payload as the same CI and updates the CI's attributes—including the changed IP address—with the new values from the payload. This ensures the CMDB reflects the current state of the asset without creating duplicates.

Answer

It flags the payload in the IRE Error Dashboard as an identification conflict requiring manual resolution.

Answer

It creates a new CI record because the IP address attribute does not match the historical value.

Answer

It deletes the existing CI and inserts a new one with the updated attributes.

Question 5

An engineer needs to add a custom attribute called 'Rack Number' to all Linux Server CIs. Where should this modification be performed to ensure it applies correctly to the table hierarchy?

Accepted Answer

CI Class Manager. CI Class Manager is the correct place to add a custom attribute to all Linux Server CIs because it manages the CI class hierarchy and allows attributes to be added at the appropriate class level, ensuring inheritance to child classes. Adding the attribute via CI Class Manager on the Linux Server class ensures it applies correctly across the hierarchy. This is the ServiceNow-recommended approach for extending CI classes.

Answer

Table Builder on cmdb_ci_linux_server

Answer

System Definition > Custom Fields

Answer

Dictionary Editor on cmdb_ci

Question 6

A team is importing asset and CI data from an external asset management tool. They want to ensure that when a CI is deleted in the external tool, it is also deleted in the ServiceNow CMDB. Which IRE payload setting accomplishes this?

Accepted Answer

Including 'operation': 'delete' in the IRE payload structure for the target CI.. The IRE (Identification and Reconciliation Engine) payload supports an 'operation' field that explicitly tells the engine what action to take on the target CI. Setting 'operation': 'delete' instructs IRE to delete the specified CI from the CMDB, which is the correct way to propagate a deletion from an external source. This is a direct, payload-level instruction rather than a rule or transform map behavior.

Answer

Setting the Reconciliation Rule action to 'Cascade Delete'.

Answer

Enabling 'Auto-Delete' on the Data Source transform map properties.

Answer

Configuring the CI Class Manager to purge orphans automatically.

Question 7

An administrator creates a custom identification rule for a new class. The rule has two entries: Entry 1 uses 'serial_number' (weight 100), and Entry 2 uses 'mac_address' (weight 50). When a payload arrives containing both attributes, how does the IRE evaluate the rule entries?

Accepted Answer

The IRE evaluates Entry 1 first. If a match is found, it uses that CI; if no match is found, it proceeds to evaluate Entry 2.. IRE evaluates identification rule entries in order of their priority or weight, or matches using the first matching entry based on configuration criteria.

Answer

The IRE averages the weights and creates a new CI if the combined score is below 75.

Answer

The IRE rejects the payload because conflicting matching criteria are defined within the same rule.

Question 8

A business service map displays a critical application server as disconnected from its underlying database. Upon investigation, the database CI was updated with a new IP address, breaking the relationship. Which ServiceNow feature helps automatically maintain relationships when attributes change?

Accepted Answer

Identification and Reconciliation Engine relationship processing via Discovery patterns. Service Mapping and Discovery rely on IRE and pattern synchronization, but relationship maintenance is often preserved through automated discovery or reference qualifier linkage. When considering CMDB core mechanisms, IRE handles updates, and relationship rules or dynamic CI groups maintain groupings.

Answer

Dependency View Auto-Heal Business Rule

Answer

Dynamic CI Group query rules

Answer

CMDB Data Manager relationship synchronizer

Question 9

Which TWO of the following are core components evaluated by the CMDB Health Dashboard? (Choose two.)

Accepted Answer

Completeness. CMDB Health consists of three pillars: Completeness, Correctness, and Compliance.

Answer

Security

Answer

Availability

Answer

Performance

Question 10

Which TWO of the following tables are standard base or parent tables in the CMDB hierarchy? (Choose two.)

Accepted Answer

cmdb_rel_ci. cmdb and cmdb_ci are foundational parent tables for all configuration items and related metadata in ServiceNow.

Answer

sys_user

Answer

incident

Answer

ast_contract

Question 11

Which THREE of the following metrics are tracked under the Correctness pillar of the CMDB Health Dashboard? (Choose three.)

Accepted Answer

Relationships (Invalid relationships). In the CMDB Health Dashboard, the Correctness pillar measures whether CI records are accurate and complete in their data and relationships, and it tracks three specific metrics: Relationships (Invalid relationships) (B), Duplicate CIs (C), and Orphan CIs (E). Invalid relationships (B) are flagged when a CI has relationship records that violate the defined relationship rules or CI class rules, indicating incorrect data. Duplicate CIs (C) are detected when multiple CI records appear to represent the same actual configuration item, which is a correctness defect. Orphan CIs (E) are CIs that have no relationships at all, which the Correctness pillar treats as a data-accuracy problem because the CI is not properly connected in the CMDB. Staleness (A) belongs to the Health/Completeness-related metrics (it measures how recently a CI was updated or discovered), and Required fields populated (D) is tracked under the Completeness pillar, not Correctness, so neither belongs here.

Answer

Staleness

Answer

Required fields populated

Question 12

A configuration manager notices that several CIs have a 'Duplicate of' relationship pointing to other CIs. These duplicates were created by a discovery source that bypassed the Identification and Reconciliation Engine (IRE). The manager wants to remediate these duplicates by merging them into the correct CIs. Which action should the manager take?

Accepted Answer

Use the Identification and Reconciliation Engine (IRE) to merge the duplicate CIs into the correct ones.. The Identification and Reconciliation Engine (IRE) includes a merge feature that can combine duplicate CIs into a single record, transferring relationships and attributes. When duplicates are created outside of IRE, the administrator can still use IRE to perform a merge by specifying the source and target CIs. This ensures data integrity and leverages the same reconciliation logic used during normal discovery.

Answer

Run the 'Merge Duplicate CIs' scheduled job from the CMDB module.

Answer

Use the CMDB Duplicate CI Remediator to merge the duplicate CIs into the correct ones.

Answer

Manually delete the duplicate CIs and update the relationships on the correct CIs.

Question 13

A service desk manager wants to ensure that when an incident is created for a business service, the affected CIs are automatically populated based on the service's CI relationships. Which CMDB feature should be configured to achieve this?

Accepted Answer

Affected CI auto-population rules. Affected CI auto-population rules are designed to automatically add CIs to task records based on the service selected. These rules can be configured to traverse relationships from the business service to its underlying CIs and populate the Affected CIs list. This reduces manual effort and ensures accuracy in impact analysis.

Answer

Service Mapping

Answer

CMDB Health Dashboard

Answer

CI Relationship Editor

Question 14

A service mapping administrator is creating a service map for a critical business application. The application runs on a cluster of web servers behind a load balancer, and the web servers connect to a database cluster. The administrator wants to ensure that the service map accurately reflects the dependencies and can be used for impact analysis. Which CMDB relationship type should be used to represent the connection between the load balancer and the web servers?

Accepted Answer

Connects to::Connected by. The Connects to::Connected by relationship is the standard CMDB relationship for representing network connections between CIs. In a service map, it is used to show how components are linked, such as a load balancer connecting to web servers. This relationship enables accurate impact analysis because it indicates a direct connection; if one CI is down, the connected CI may be impacted. Using the correct relationship type ensures the service map reflects the actual architecture.

Answer

Depends on::Used by

Answer

Runs on::Runs

Answer

Contains::Contained by

Question 15

An administrator needs to evaluate the overall health of the CMDB, specifically measuring the percentage of CIs that have not been updated or verified within the last 90 days. Which CMDB Health metric addresses this?

Accepted Answer

Staleness (Compliance metric). Staleness is the correct CMDB Health metric because it measures the percentage of CIs that have not been updated or verified within a defined threshold (e.g., 90 days). It falls under the Compliance metric category in CMDB Health, which tracks whether CIs meet governance requirements like timely verification. Staleness specifically uses the 'last updated' or 'last verified' timestamp to flag aging CIs.

Answer

Orphans (Correctness metric)

Answer

Audit (Completeness metric)

Answer

Duplicate CIs (Correctness metric)