SERVICENOW-CIS-DISCOVERY Timed Practice Test 2 — 10 Questions

Question 1

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. The Identification and Reconciliation Engine (IRE) uses identification rules to prevent duplicates by matching incoming data against existing CIs based on defined criteria.

Answer

Discovery Schedules

Answer

Transform Maps

Answer

Data Preserver

Question 2

What is the role of the 'ECC Queue' in Discovery?

Accepted Answer

To act as a message queue for commands and results between instance and MID Server.. The ECC Queue is the communication buffer between the ServiceNow instance and the MID Server.

Answer

To schedule Discovery scans.

Answer

To store the final CMDB data.

Answer

To provide credentials for discovery.

Question 3

You have a custom CI class that is not appearing in the CMDB Health Dashboard reports. What is the first step to ensure it is included?

Accepted Answer

Add the class to the CMDB Health Dashboard 'Dashboard Configuration' settings.. CMDB Health settings must be configured to include specific classes for health metrics calculation.

Answer

Create an ACL for the CMDB Health table.

Answer

Restart the Discovery services.

Answer

Run a full Discovery of the entire environment.

Question 4

During a Discovery run, a Linux server CI is updated with a null value for its serial number, overwriting a manually entered value. Which configuration prevents this?

Accepted Answer

Reconciliation Rules. Discovery Source and reconciliation rules define which data sources are allowed to update specific attributes, preventing lower-priority sources from overwriting authoritative ones.

Answer

CMDB Health Dashboard

Answer

Discovery Pattern Pre/Post scripts

Answer

MID Server Capabilities

Question 5

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.. Staleness is calculated based on the 'sys_updated_on' field compared to the threshold defined in the CMDB Health properties.

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 6

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 IRE logs all interactions between Discovery and the CMDB, including validation failures and attribute update denials.

Answer

System Logs > Node Logs

Answer

Discovery > Pattern Logs

Answer

System Logs > Discovery Logs

Question 7

Which of these is a valid way to organize discovery when dealing with a very large network?

Accepted Answer

Use multiple schedules and MID servers to segment the workload.. Using multiple discovery schedules and assigning them to different MID servers is the standard architectural approach.

Answer

Disable the identification phase.

Answer

Use a single schedule for everything.

Answer

Run everything at once.

Question 8

A Discovery Schedule is configured but not running. Where is the first place you should look for errors?

Accepted Answer

Discovery Log. The Discovery Log and the ECC Queue are the primary sources for troubleshooting discovery issues.

Answer

System Logs

Answer

MID Server Logs

Answer

CMDB Health Dashboard

Question 9

During the Classification phase, Discovery identifies a device as a Linux server but fails to populate the serial number. Which troubleshooting step is most effective?

Accepted Answer

Check the ECC Queue for 'Input' records related to the SNMP probes and review the pattern logs.. If classification succeeds but specific data is missing, the issue is typically in the Exploration phase probes or identifiers.

Answer

Change the MID Server user to an admin account.

Answer

Delete the Discovery Schedule and recreate it.

Answer

Re-run the Shazzam probe for that specific IP.

Question 10

You are implementing a new discovery tool and want to ensure it integrates seamlessly with existing CMDB identification rules. What is the first step?

Accepted Answer

Review existing Identification Rules to ensure they support the new tool's incoming CI data.. You must check existing Identification Rules to see if the new tool's data can be mapped using existing identifiers.

Answer

Delete all existing CIs.

Answer

Disable all existing identification rules.

Answer

Use a new CI class for all data from the new tool.