ServiceNow CIS-Discovery Dumps - Pass Certified Implementation Specialist - Discovery Exam in First Attempt 2026

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.

Reconciliation

Data source precedents

The main Key Performance Indicators (KPIs) for the CMDB Health scorecard in ServiceNow include Correctness, Completeness, and Staleness. These KPIs are critical for assessing the overall health and quality of the CMDB. Correctness refers to the accuracy of the data in the CMDB, Completeness measures whether all required CI data is present, and Staleness indicates the freshness or timeliness of the CI data. Compliance and Duplicates, while important, are not considered main KPIs in the context of the CMDB Health scorecard. Reference = ServiceNow CMDB documentation and CMDB Health Dashboard user guide, focusing on the key performance indicators for CMDB health.

An extension section of a discovery pattern is a section that allows you to modify or extend the functionality of an existing pattern without customizing it. An extension section can contain shared libraries, which are reusable code snippets that can be invoked from any pattern or extension section. Shared libraries can be used to define common functions, variables, or constants that are used across multiple patterns or extension sections.Shared libraries can also be used to override the default behavior of some built-in functions, such as identification or classification12.Reference=1: ITOM: Extending Discovery/Service Mapping Patterns - GlideFast ServiceNow2: How to Create Discovery Pattern Extensions and Why to Use Them

The Set Parameter Value operation is used to assign a value to a variable in a Discovery pattern1.The syntax for this operation is as follows2:

Set Parameter Value: <Variable Name> = <Value>

The<Value>can be either a constant or an expression. To declare a constant, unchanging value, one must use quotes around the value.For example2:

Set Parameter Value: $name = 'John'

This assigns the string ''John'' to the variable $name. The quotes indicate that the value is a constant and will not change. The other options, hash tag, brackets, and dollar sign, are not used to declare a constant value. They have different meanings in the syntax of the Set Parameter Value operation.A hash tag (#) is used to indicate a comment2.Brackets ([]) are used to access an element of an array or a map2. A dollar sign

The image shows a part of a horizontal pattern in Pattern Designer that uses the WMI Query operation to retrieve information about the processes running on a Windows server. The operation takes a WQL query as an input parameter and returns a tabular variable that contains the results of the query. The tabular variable is named 'WMI Query' by default, but it can be renamed by the user. The WQL query in the image selects four attributes from the Win32_Process class: Name, MaximumWorkingSetSize, PageFaults, and PeakVirtualSize. These attributes are stored as scalar variables in the tabular variable, and they can be accessed by using the dot notation, such as WMI Query.Name or WMI Query.MaximumWorkingSetSize. Therefore, the most probable results of the image are a tabular variable named 'WMI Query' and two scalar variables named 'MaximumWorkingSetSize' and 'PeakVirtualSize'.

Pattern Designer | WMI Query

Win32_Process class

WQL (SQL for WMI)