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

Question 1

Which THREE types of metrics are tracked by the CMDB Health Dashboard?

Accepted Answer

Compliance. The CMDB Health Dashboard tracks metrics across three categories: Completeness, Correctness, and Compliance.

Answer

Performance

Answer

Scalability

Question 2

Which of the following is the most effective way to monitor the health of your discovery process on a daily basis?

Accepted Answer

Using the CMDB Health Dashboard.. The CMDB Health Dashboard provides automated, configurable health metrics for the CMDB.

Answer

Running a manual script to count CIs.

Answer

Reviewing the System Log every morning.

Answer

Checking the MID Server status every hour.

Question 3

When the Identification and Reconciliation Engine (IRE) processes a payload, which THREE components determine if a CI is updated or created?

Accepted Answer

Data Source. The Identification and Reconciliation Engine (IRE) relies on three core inputs when processing a payload to decide whether a CI is created or updated. The Data Source (C) is correct because it defines the source precedence and the set of identifiers/attributes that IRE uses to evaluate incoming data against existing CIs. Identification Rules (E) are correct because they specify which attributes (identifiers) must match to determine that an incoming record corresponds to an existing CI rather than a new one. Reconciliation Rules (D) are correct because they govern how conflicting attribute values from different data sources are resolved and which values get written to the CI when an update occurs. The MID Server configuration (A) only affects connectivity and data collection/execution, not the create-versus-update decision logic, and the Discovery Schedule (B) merely controls when and what Discovery runs, so neither participates in IRE's identification and reconciliation processing.

Answer

MID Server configuration

Answer

Discovery Schedule

Question 4

During a Discovery run in a large data center, the same Windows server is being discovered by two separate MID Servers that both have network access to the server's subnet. The server appears as a single CI, but its 'Last discovered' timestamp and certain network adapter attributes keep flipping between values from each MID Server on every run. Which configuration should you review first to understand and control this behavior?

Accepted Answer

The MID Server selection configuration and IP range/behavior settings that determine which MID Server is responsible for the server's subnet.. The behavior described is caused by two MID Servers both being permitted to discover the same IP range, so each run overwrites the other's data for the shared CI. ServiceNow Discovery uses MID Server IP range and behavior configuration to determine which MID Server is responsible for a subnet. Ensuring only one MID Server covers the server's subnet stops the oscillation and yields consistent discovery results.

Answer

The Discovery schedule's 'Maximum run time' and 'Concurrent schedules' settings to ensure the two runs do not overlap in time.

Answer

The CI Class Manager's identification and reconciliation rules for the Windows Server class, specifically the priority of the discovery source.

Answer

The CMDB Health Dashboard's duplicate CI metrics to see if the same server is being registered twice under different names.

Question 5

A CMDB administrator notices that a Linux server CI created by Discovery has a serial number attribute populated by a third-party import, while Discovery populates the same attribute with a different value. The administrator wants Discovery's value to take precedence over the import when both sources update the CI. Which mechanism should be configured to control this precedence?

Accepted Answer

A CMDB data source precedence rule under CI Class Manager that ranks the Discovery source above the import source for the serial number attribute.. ServiceNow CMDB reconciliation lets administrators define source precedence for CI attributes in CI Class Manager. When Discovery and an import both update the same attribute, the source with higher precedence wins. Ranking the Discovery source above the import source for the serial number attribute ensures Discovery's value is applied consistently, without custom scripts or import-specific workarounds.

Answer

A business rule on the CMDB CI table that blocks updates to the serial number field when the source is the import.

Answer

A scheduled job that runs after discovery and copies the Discovery serial number into the CI, overwriting the import value.

Answer

A transform map coalesce setting in the import set that matches on serial number and overwrites existing values.

Question 6

During a CMDB health check, an administrator notices that a Windows server CI has a stale record in the CMDB even though the server was decommissioned three months ago. The administrator wants to ensure that decommissioned CIs are automatically marked as retired. Which CMDB feature should be configured to achieve this?

Accepted Answer

CMDB Data Manager. CMDB Data Manager is designed to automate the lifecycle management of CIs, including retirement and deletion based on defined policies. By configuring a policy that targets CIs with a last discovered date older than a threshold, the administrator can ensure decommissioned CIs are retired automatically. This reduces manual effort and maintains CMDB accuracy.

Answer

CI Class Manager

Answer

Discovery Schedules

Answer

CMDB Health Dashboard

Question 7

A ServiceNow administrator is configuring a CI identification rule for a custom CI class 'Network Router'. The class has a unique attribute 'serial_number' and a non-unique attribute 'model'. The administrator wants to ensure that if a router with the same serial number already exists, Discovery updates that CI instead of creating a new one. Which identification rule configuration should be used?

Accepted Answer

Create a rule with 'serial_number' as the only identifier.. For CI identification, it is best practice to use the minimal set of attributes that uniquely identify a CI. Since serial_number is unique for network routers, it should be the only identifier. This ensures accurate matching and prevents duplicates, even if other attributes like model or name change.

Answer

Create a rule with 'serial_number' and 'name' as identifiers.

Answer

Create a rule with 'model' as the only identifier.

Answer

Create a rule with both 'serial_number' and 'model' as identifiers.

Question 8

An administrator needs to review which CIs were recently modified by an integration and confirm the source of each change. Which CMDB capability provides a chronological record of attribute-level changes on a CI, including the data source that made the change?

Accepted Answer

CMDB Audit History on the CI record. CMDB Audit History is the built-in mechanism that records attribute-level changes on CI records, including the actor and timestamp. It is the correct place to verify which integration or user changed a value. The other capabilities shown are administrative, scoring, or scheduling views that do not expose per-attribute change history.

Answer

Discovery Schedule history

Answer

CI Class Manager

Answer

CMDB Health Dashboard

Question 9

A CMDB administrator is troubleshooting why a Linux server CI keeps losing its correct 'CPU count' value after each nightly discovery run. The discovery source correctly reports 8 CPUs, but the stored value reverts to 2. Which configuration should be inspected first to explain the reversion?

Accepted Answer

The reconciliation precedence list for the CPU count attribute on the Linux Server class. When Discovery reports the correct value but the stored CI reverts, the most likely cause is a competing data source with higher precedence for that attribute. Reviewing the reconciliation precedence list for CPU count on the Linux Server class identifies the source that is winning and allows the administrator to correct the ordering.

Answer

The Discovery schedule's MID Server selection criteria

Answer

The MID Server's probe timeout setting for the Linux command probes

Answer

The pattern's CI Identification section for the Linux Server class

Question 10

A CMDB manager must reduce duplicate server CIs that are being created because two discovery sources report slightly different values for the same hostname. Which TWO actions should be taken to improve matching and reduce duplicate creation? (Choose two.)

Accepted Answer

Configure data source precedence so that one source is authoritative for the conflicting attributes, preventing value flapping.. Duplicates from multiple sources are caused by inconsistent identifying attributes and by conflicting values flapping between sources. A robust identification rule using stable attributes ensures both sources match the same CI, and precedence ensures the stored values stop fluctuating, so subsequent reconciliations match instead of inserting new records.

Answer

Delete the existing duplicate CIs and rely on the next discovery run to recreate them correctly.

Answer

Increase the Discovery schedule frequency so both sources run closer together.

Answer

Disable reconciliation on the server class so Discovery always inserts new records.

Question 11

You are a ServiceNow Discovery administrator for a large enterprise. You have configured Discovery to populate the CMDB with data from multiple sources, including ServiceNow Discovery, SCCM, and a third-party asset management system. You need to ensure that the CMDB is not polluted with duplicate CIs and that the most authoritative data source wins when there are conflicts. Which feature should you use to achieve this?

Accepted Answer

CMDB Identification and Reconciliation Engine (IRE). The CMDB Identification and Reconciliation Engine (IRE) is the correct feature because it provides the framework for identifying unique CIs and reconciling data from multiple sources. It allows you to define identification rules that specify which attributes to use for matching, and reconciliation rules that determine which source is authoritative for each attribute. This ensures data integrity and prevents duplicates. Other options do not provide these capabilities.

Answer

Service Mapping

Answer

Discovery Schedules

Answer

CMDB Health Dashboard

Question 12

During a Discovery run, a Windows server is discovered and its hostname matches an existing CI in the CMDB, but the serial number differs. The CI Class Manager shows that the class uses a CI Identification rule with 'Hostname' as the only identifier. What is the most likely outcome for this CI?

Accepted Answer

The existing CI will be updated with the new serial number, and no new CI will be created.. The CI Identification rule defines which attributes are used to match discovered data to existing CIs. When Hostname is the only identifier, a match on hostname is sufficient to identify the CI, regardless of other attribute differences. Discovery then updates the CI's attributes, including serial number, to reflect the discovered state. This prevents duplicate CIs and maintains CMDB accuracy.

Answer

A new CI will be created because the serial number does not match, and the existing CI will be marked as duplicate.

Answer

A new CI will be created because the existing CI's serial number does not match, and the old CI will be retired.

Answer

The Discovery run will fail because the serial number mismatch violates the identification rule.

Question 13

A CMDB administrator notices that a business application CI's relationships to its supporting servers are correct, but the application's 'Environment' attribute is blank even though Discovery populates it on the servers. Which concept explains why the application CI lacks the value and what should be done?

Accepted Answer

The application CI is a manually created class not covered by any discovery pattern, so the attribute must be populated through an integration or manual update.. Discovery populates only the classes and attributes its patterns are designed for. Business application CIs are usually created by Service Mapping or manual entry, and unless a source writes the Environment attribute, it remains blank. The correct action is to populate it through the appropriate integration or update process rather than expecting inheritance or reconciliation to fill it.

Answer

The application CI is failing reconciliation because its identifier is incomplete, so all non-identifier attributes are skipped.

Answer

The Environment attribute is protected by a dictionary attribute-level read-only flag set by the base system, blocking all writes.

Answer

The Environment attribute is a dependent attribute that must be inherited from a related server CI through a rollup.

Question 14

A CMDB administrator notices that a Linux server CI has multiple IP addresses, but only one is being discovered and stored in the 'ip_address' field. The Discovery pattern uses the 'nmap' command to scan the server. What is the most likely reason for this behavior?

Accepted Answer

The 'ip_address' field is a single-value field and can only store one IP address; additional IPs are stored in related network adapter CIs.. The 'ip_address' field on a server CI is designed to hold a single primary IP address. To capture multiple IPs, Discovery creates or updates Network Adapter CIs, each representing a network interface with its own IP address. These adapters are related to the server CI via relationships. This approach maintains a normalized data model and allows for detailed network configuration tracking. The pattern's logic determines which IP is considered primary and stored on the server CI, while others are stored on adapters.

Answer

The CMDB does not support storing multiple IP addresses for a single CI, so only one can be recorded.

Answer

The server's firewall is blocking the discovery of secondary IP addresses, so only the primary IP is reachable.

Answer

The 'nmap' command only returns the first IP address it finds, so Discovery cannot capture additional IPs.

Question 15

You are a ServiceNow Discovery administrator. After a recent discovery run, you notice that a Linux server CI has an incorrect operating system version attribute. You want to manually correct this value in the CMDB. Which module should you use to edit the CI record?

Accepted Answer

Configuration > CIs. To manually edit a CI record in the CMDB, you use the Configuration > CIs module. This module lists all CIs and allows you to open and modify their attributes. The other options are not designed for editing individual CI records; they serve different purposes such as managing classes, scheduling discovery, or monitoring CMDB health.

Answer

Discovery > Discovery Schedules

Answer

Configuration > CI Class Manager

Answer

Configuration > CMDB Health Dashboard