ServiceNow CIS-Discovery Practice Test - Questions Answers

In a discovery pattern, CI Attributes are the fields that store the information about the configuration items (CIs) that are discovered by the pattern. The Pattern Designer is a graphical interface that allows users to create and edit patterns using drag-and-drop operations. In the Pattern Designer, there are two types of CI Attributes that are available: Main pattern CI type and Related CI types. The Main pattern CI type is the CI type that the pattern is designed to discover, such as Windows Server, Linux Server, or Database. The Related CI types are the CI types that are related to the main CI type, such as IP Address, Network Adapter, or Software Installation.Users can select the CI Attributes from these types to populate the CMDB tables with the data collected by the pattern123.

Patterns and horizontal discovery - Product Documentation: Tokyo - Now Support Portal

Pattern Designer - Product Documentation: Vancouver - ServiceNow

Discovery pattern designer - ServiceNow IT Operations Management [Book]

CI reclassification is the process of changing the class of a CI in the CMDB based on the discovery data. It can be done manually or automatically, depending on the configuration settings. CI reclassification can result in data loss if the new class has fewer or different attributes than the original class, and the existing attribute values are not preserved or mapped to the new class. This can happen when a CI is switched to a different class hierarchy, such as from a Linux Server to a Windows Server, or when a CI is downgraded to a less specific class, such as from a Database to a Software Instance. Therefore, switching and downgrading have a higher chance of leading to lost data during CI reclassification.

CI reclassification

Reclassify CIs

Configure automatic CI reclassification

Variables are used in discovery patterns to store and manipulate data that is collected or calculated during the discovery process.There are three kinds of variables used in discovery patterns12:

CI attributes: These are variables that correspond to the attributes of the configuration item (CI) type that the pattern is discovering. For example, name, serial_number, manufacturer, etc. CI attributes are used to populate the CI record in the CMDB with the information gathered by the pattern.

Temporary: These are variables that are created and used within the pattern, but are not stored in the CMDB. For example, $result, $output, $user_var, etc. Temporary variables are used to store and manipulate data such as the output of a command, the value of a parameter, or the result of a calculation.

Global: These are variables that are defined in the global scope and can be accessed by any pattern. For example, $mid, $target, $ip_address, etc. Global variables are used to store and access data that is common to all patterns, such as the MID Server, the target device, or the IP address.

1: ServiceNow Discovery Documentation, Pattern Variables section

2: ServiceNow Discovery Overview, page 11

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 identifiers

2:Create or edit a CI identification rule

3: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 Definition

Behavior

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 - ServiceNow

2: Shazzam probe, port probes, and protocols - Product Documentation: San Diego - ServiceNow

3: Discovery Phase Shazzam - Support and Troubleshooting - ServiceNow

er: 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 Portal

3: 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.

Reconciliation

Data source precedents