Download ServiceNow.CIS-Discovery.VCEplus.2024-12-02.60q.tqb

CMDB Health measures the quality of the data in the CMDB by testing it against predefined rules and metrics.One of the categories of these rules isCorrectness, which tests the data against data integrity rules such as identification rules, orphan CI rules, and stale CI rules1.These rules help identify and flag the existing CMDB relationships that are not compliant with the suggested relationships2.Duplicaterelationships are those that have more than one relationship of the same type between the same two CIs3. For example, if a server CI has two relationships of type ''Depends on'' with the same network CI, it is a duplicate relationship.Stalerelationships are those that have not been updated for a specified period of time3. For example, if a server CI has a relationship of type ''Runs on'' with a virtual machine CI that has not been discovered for more than 60 days, it is a stale relationship. Orphanrelationships are those that are missing a defined relationship within the CMDB3. For example, if a server CI has no relationship of type ''Depends on'' with any network CI, it is an orphan relationship.

The Discovery Dashboard provides a summary of the Discovery status, including the number of active discovery errors, the number of devices discovered, and the number of credentials used. Each error has a help link that provides more information about the cause and possible solutions.Discovery DashboardDiscovery troubleshooting | Error messages

A classifier is a set of rules that identifies a device type based on the results of a probe. A classifier can have one or more related lists that define the classification criteria, the pattern probes, and the triggers probes. The pattern probes related list specifies which horizontal discovery pattern to run for the device type. The triggers probes related list specifies which probes to run after the device is classified, and before the horizontal discovery pattern is executed.The triggers probes can be used to gather additional information or credentials that are needed for the horizontal discovery pattern12.1: ServiceNow Discovery Overview, page 92: ServiceNow Discovery Documentation, Classifiers section

The ECC Queue is the normal connection point between an instance and other systems that integrate with ServiceNow, such as MID Servers1.The ECC Queue displays input and output messages from and to MID Servers2.The actual XML payload that is sent to or from an instance is stored in the ECC Queue3.The ECC Queue also provides a connected flow of probe and sensor activity, as probes are sent from the instance to the MID Server, and sensors are sent from the MID Server to the instance2. 1:ServiceNow Discovery Overview2:ECC Queue Processing and Debugging, with ''Discovery - Sensors'' used as an example3:Manage ECC Queue content for a MID Server

CI identifiers can be viewed under the CI record1.A CI identifier is a set of attributes that uniquely identify a CI of a specific class2.CI identifiers are used by the identification and reconciliation engine (IRE) to match incoming data with existing CIs in the CMDB3.CI identifiers can be viewed and edited in the CI record by clicking the Identification Information related link1.1:View and edit CI identifiers2:Create or edit a CI identification rule3:Identification rules

Tracked configuration files are files that contain settings and parameters of certain applications or devices that Discovery can find and add to the CMDB. Some of the benefits of tracked configuration files are:Content version comparison: You can compare the content of different versions of the same configuration file and see the changes that occurred over time. This can help you troubleshoot issues, audit changes, and restore previous configurations if needed.Files tracked as CIs: You can view the configuration files as configuration items (CIs) in the CMDB and see their relationships with other CIs, such as the applications or devices they belong to. This can help you understand the dependencies and impact of the configuration files on your IT environment.

A Functionality Definition is a configuration record that defines what protocols to detect from within a Behavior. A Behavior is a set of Functionality Definitions that Discovery uses to identify and explore a device or application.A Functionality Definition specifies the order, type, and parameters of the probes that Discovery launches to gather information about a device or application12.Functionality DefinitionBehavior

The Shazzam probe is placed in the ECC queue as a first step in horizontal discovery.The ECC queue is a table that stores requests and responses for communication between the MID Server and the ServiceNow instance1.The Shazzam probe is a script that performs port scanning on a target host to determine what protocols are available and what classifiers to trigger2.The Shazzam probe is sent from the ServiceNow instance to the MID Server, which executes it on the target host and returns the results to the ECC queue3.1: ECC queue - Product Documentation: San Diego - ServiceNow2: Shazzam probe, port probes, and protocols - Product Documentation: San Diego - ServiceNow3: Discovery Phase Shazzam - Support and Troubleshooting - ServiceNower: D

A is true because the target table $cmdb_ci_web_server is a ServiceNow CMDB table that stores information about web servers1.B is true because the merge table operation is typically used for application patterns, which are horizontal patterns that discover applications and their dependencies. The condition on the process.executablePath variable suggests that the operation is looking for a specific application (mongoose) running on the web servers.D is true because the merge table operation requires at least one matching field value between the two source tables1. In this case, the process.executablePath variable is the matching field, and it must contain ''mongoose'' for the operation to run.1: Merge tables - Product Documentation: San Diego - Now Support Portal3: Product Documentation | ServiceNow[4]: Discovery Patterns - Product Documentation: San Diego - Now Support Portal

In ServiceNow Discovery, the reconciliation process is governed by precedence rules. These rules determine which data source's information will be retained if there are conflicts when multiple sources discover the same CI.In this case, Altiris has a higher order of precedence (300) compared to ServiceNow (100), as seen in the ''Data Source Precedents'' section of the image. Therefore, if Altiris discovers 'Windows2' for the name attribute on the same CI after ServiceNow sets it to 'Windows1', the name will change to 'Windows2' due to Altiris's higher precedence.ReconciliationData source precedents