SERVICENOW-CIS-DISCOVERY CMDB Integration And Maintenance Practice Test 2 — 15 Questions

Question 1

During Discovery, a switch is identified, but its related interfaces are not appearing in the CMDB. What is the first thing you should check?

Accepted Answer

Identification Rule for the interface class. When a switch is discovered but its interfaces do not appear in the CMDB, the most likely cause is that the interface CI class has no Identification Rule (or a misconfigured one), so Discovery cannot create or reconcile the interface CIs. Identification Rules define the unique key (e.g., name + switch sys_id) used to match discovered interface data to existing CI records, and without one, interfaces are dropped or duplicated.

Answer

MID Server capacity

Answer

Discovery Schedule timing

Answer

Discovery Error Log

Question 2

You are tasked with ensuring that Discovery only populates the 'Short Description' field on a CI if it is currently empty. Which IRE feature allows for this conditional update?

Accepted Answer

IRE Data Source Rules with 'Skip if not empty' logic. The 'Apply to' and conditional logic in the IRE or Data Source rules allows for fine-grained control over attribute updates.

Answer

Business Rule on the CI table

Answer

Discovery Pattern Step: 'Update only if empty'

Answer

Reconciliation Rule Priority

Question 3

A complex environment requires that two different Discovery sources (e.g., ServiceWatch and a third-party tool) populate the same CI attributes. How can you ensure the third-party tool's data is preferred over Discovery for specific attributes?

Accepted Answer

Set the third-party data source priority to 100 and discovery to 200.. Reconciliation Rules assign a priority value to data sources; the highest priority source wins the attribute update.

Answer

Disable 'Discovery' in the CI Class identification rule.

Answer

Use a Business Rule to intercept the discovery payload.

Answer

Set the discovery source priority to 100 and the third-party source to 200.

Question 4

Which TWO actions should you perform to maintain the integrity of the CMDB when a CI is decommissioned?

Accepted Answer

Update the 'Operational status' field to 'Retired'.. To properly retire a CI, you must update its status and ensure it no longer appears in active discovery processes.

Answer

Delete the CI record from the database.

Answer

Clear the 'Last discovered' field.

Answer

Change the CI class to 'Archive'.

Question 5

Which TWO issues might be discovered in the 'Correctness' category of the CMDB Health Dashboard?

Accepted Answer

Duplicate CIs. Correctness metrics specifically identify duplicates and orphaned CIs that threaten CMDB data integrity.

Answer

Stale CIs

Answer

Expired credentials

Answer

Missing critical attributes

Question 6

Which THREE of the following are valid sources for the Identification and Reconciliation Engine (IRE)?

Accepted Answer

Service Graph Connectors. The IRE is agnostic to the source, and data can come from Discovery, Service Graph Connectors, or manual imports.

Answer

System Logs

Answer

Manual CI creation via UI

Question 7

During a CMDB health review, you find a Windows server CI whose 'Serial number' attribute was populated by SCCM integration but is actually the system's asset tag, not the hardware serial. The correct hardware serial is available from the Discovery source. Which feature should you configure to ensure the hardware serial from Discovery wins over the SCCM value on subsequent updates?

Accepted Answer

Configure an attribute-level data source precedence for Serial number on the Windows Server class, placing Discovery above the SCCM source.. The conflict is a source-precedence problem for a single attribute, and ServiceNow resolves this with attribute-level data source precedence on the CI class. Listing Discovery ahead of the SCCM source makes Discovery's hardware serial authoritative on reconciliation while still allowing SCCM to populate other attributes it owns.

Answer

Add a transform map on the SCCM staging table that maps the asset tag field to a custom attribute instead of Serial number.

Answer

Set the CI's 'Operational status' to 'Repair in progress' so the SCCM integration skips updates to the Serial number field.

Answer

Create a new Identification Rule that includes the Serial number attribute so the CI is re-identified using the Discovery value.

Question 8

You are a ServiceNow Discovery administrator. A new Windows server was discovered and a CI was created in the CMDB. Later, the server's hostname was changed from WEB01 to WEB02. After the next discovery run, you notice that the original CI for WEB01 still exists and a new CI for WEB02 has been created. What is the most likely cause of this duplicate CI?

Accepted Answer

The CI Identification rule for Windows servers is configured to use the serial number as the primary identifier, but the serial number was not collected during discovery, so the hostname was used as the primary identifier.. The duplicate CI occurred because the identification rule for Windows servers uses serial number as the primary identifier, but when serial number is not available, the system may use hostname as a fallback. Since the hostname changed, the new hostname did not match the existing CI, resulting in a new CI. The old CI remains because it was identified by the old hostname. This highlights the importance of ensuring reliable identifiers are collected and that identification rules are robust.

Answer

The CI Identification rule for Windows servers is configured to use a combination of serial number and hostname, and the serial number was not collected, so the hostname was used as a fallback.

Answer

The CI Identification rule for Windows servers is configured to use the serial number as the primary identifier, but the serial number was not collected during discovery.

Answer

The CI Identification rule for Windows servers is configured to use the hostname as the primary identifier.

Question 9

A discovery administrator is troubleshooting why a CI's 'operational_status' is not being updated during Discovery, even though the CI is discovered and other attributes are refreshed. The CI Class Manager shows that the class has an identification rule that uses 'Name' and 'Serial Number'. What is the most likely cause?

Accepted Answer

The CI's 'operational_status' is manually set and Discovery does not overwrite manually set values by default.. Discovery updates CI attributes based on the pattern's payload, but it respects manual changes to fields to avoid overwriting intentional modifications. The 'operational_status' field is often manually set to reflect operational states like 'Repair in Progress' or 'Retired'. By default, Discovery does not overwrite manually set values unless the 'Overwrite' option is enabled for that field in the pattern or via a system property. This protection ensures that manual data is not lost during automated updates.

Answer

The CI class does not have the 'operational_status' field enabled for Discovery updates.

Answer

The identification rule is missing 'operational_status' as an identifier, so the field is not updated.

Answer

The 'operational_status' field is not included in the Discovery pattern's payload, so it is not updated.

Question 10

You are troubleshooting a scenario where Discovery is creating duplicate CIs for the same server. Which table should you inspect to verify the Identification Rule settings for the specific CI class?

Accepted Answer

cmdb_identifier_entry. Identification Rules for CI classes are stored in the cmdb_identifier_entry table, which holds the individual identifier entries (e.g., serial number, name, MAC address) that the IRE uses to match incoming records to existing CIs. Inspecting this table lets you verify which identifiers are configured for a specific CI class and whether they are correctly set up to prevent duplicates.

Answer

discovery_device_history

Answer

sys_reconciliation_rule

Answer

cmdb_ci_relation

Question 11

During a Discovery run, a Linux server is identified, but the CMDB record is not updated with the latest memory information. Which log should be inspected to troubleshoot the Identification and Reconciliation engine (IRE) process?

Accepted Answer

System Logs > Identification and Reconciliation Engine Logs. The Identification and Reconciliation Engine (IRE) processes discovery data to identify CIs and reconcile them into the CMDB. When IRE fails to update CI attributes such as memory information, the IRE log is the correct place to inspect for identification errors, reconciliation rule mismatches, or payload issues. This log is accessed via System Logs > Identification and Reconciliation Engine Logs.

Answer

System Logs > Node Logs

Answer

Discovery > Pattern Logs

Answer

System Logs > Discovery Logs

Question 12

A Discovery scan successfully identifies a Linux server, but the 'Operating System' field is not being updated in the CMDB. You have verified that the pattern correctly extracts the OS version. What is the most likely configuration issue?

Accepted Answer

A Reconciliation Rule exists that prevents the 'ServiceNow' data source from updating the 'Operating System' attribute.. Data source reconciliation rules determine which data sources have update authority for specific fields.

Answer

The CI class is marked as 'Read Only' in the CMDB dashboard.

Answer

The Discovery schedule is using the wrong MID server.

Answer

The Linux pattern is not published to the production environment.

Question 13

You notice that Discovery is creating duplicate CIs for Windows servers. Which CMDB feature should you investigate first to ensure Discovery correctly identifies existing CIs?

Accepted Answer

Identification Rules. Identification Rules define the attributes (such as serial number, MAC address, or name) that the Identification and Reconciliation Engine uses to match discovered data to existing CIs. If duplicates are being created, the identification rules are likely too narrow or missing key attributes, causing IRE to fail to match and instead create new CIs. Investigating Identification Rules is the correct first step.

Answer

Discovery Schedules

Answer

Transform Maps

Answer

Data Preserver

Question 14

When reviewing the CMDB Health Dashboard, you notice a high 'Staleness' score for several Windows servers. What is the primary cause of high staleness?

Accepted Answer

The CIs have not been updated by Discovery within the configured staleness threshold.. The Staleness score in the CMDB Health Dashboard measures how long it has been since a CI was last updated by Discovery or another authoritative source. A high staleness score means the CI's 'last discovered' or 'updated' timestamp exceeds the configured staleness threshold, indicating the CI data is outdated. This is the direct definition of staleness in ServiceNow CMDB Health.

Answer

The CIs are not being reconciled correctly.

Answer

The Discovery credentials failed during the last scan.

Answer

The CIs have invalid relationship types.

Question 15

Which tool provides a visual representation of how different data sources are contributing to the current state of a CI record?

Accepted Answer

CI Timeline. The CI Timeline or the 'CMDB Data Manager' visual tools allow viewing update history and sources.

Answer

Discovery Log

Answer

CMDB Health Dashboard

Answer

Service Map