Pass the ServiceNow Certified Implementation Specialist CIS-Discovery Questions and answers with CertsForce

In the context of ServiceNow Discovery patterns, the types of temporary variables include Scalar/List and Tabular/Table. Scalar/List variables are used to store single values or lists of values, while Tabular/Table variables are used to store structured data in a table format. Command and SQL statement are not types of temporary variables; rather, they are types of operations or steps that can be used within a pattern to execute commands or SQL queries. References = ServiceNow Discovery documentation, especially sections related to Discovery Patterns and the use of temporary variables within patterns.

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.

References:

1: ServiceNow Discovery Overview

2: ECC Queue Processing and Debugging, with “Discovery - Sensors” used as an example

3: Manage ECC Queue content for a MID Server

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.

References: The explanation is inferred from understanding how reconciliation and data source precedents work in ServiceNow Discovery, though not directly quoted from specific documents. You can find more information on these topics in the following links:

Reconciliation

Data source precedents

The Pattern Designer in ServiceNow Discovery uses different types of horizontal patterns to model various IT components and services. The temporary variable 'computer_system' seen in the pattern indicates that this is a 'Computer System' pattern type. This type of pattern is used to model and discover details about computer systems, which typically include hardware, operating system, and other related components.

During the Port Scan phase in ServiceNow Discovery, the warning level error "No results returned from probe" typically indicates a connectivity issue. This error often arises when a logical or physical firewall is blocking the connectivity between the MID Server and the target device. This prevents the probe from successfully scanning the ports and returning results. The other options, such as incorrect process classifier configuration, wrong credentials, or incorrect datasource precedence, would generally lead to different types of errors or issues in the discovery process. References = ServiceNow Discovery documentation, particularly the sections that deal with troubleshooting Port Scan issues and understanding common errors during Discovery phases.

The CMDB contains records of configuration items (CIs) and their relationships. A CI is any component that needs to be managed in order to deliver an IT service, such as a server, an application, or a user. A relation type defines the nature of the connection between two CIs, such as depends on, uses, or contains. A model is a template for a CI that defines its attributes and default values. An asset is a tangible or intangible resource that is tracked and managed by the organization, such as a laptop, a license, or a contract.

References:

Configuration Item (CI) types: Attributes and relationships

What is a configuration management database (CMDB)?

CSA Challenge Questions Flashcards

 The MID Server’s user account must have the mid_server role to interact with a ServiceNow instance. This role allows the MID Server to access protected tables and perform discovery and orchestration tasks on behalf of the instance. The other roles are not related to the MID Server functionality. The discovery_admin role is for configuring and managing discovery, the sm_mid role is for using the Service Mapping MID Server, and the mid_discovery role is for running discovery probes and sensors.

References:

Setting up MID Server user and role

Configure Windows MID Server service credentials

Correcting MID Server Windows service account user and permissions

The Extension section in a horizontal pattern is executed after the Identification sections have completed and the CI has been identified. The Extension section allows adding additional attributes or relationships to the CI, or launching other patterns for further discovery12.

References:

1: ITOM: Extending Discovery/Service Mapping Patterns - GlideFast ServiceNow

2: Horizontal Pattern probe - Product Documentation: San Diego - ServiceNow

The vCenter Event Collector is a MID Server extension that listens for vCenter-related events and updates the CMDB accordingly. The event collector allows the CMDB to be updated with changes to virtual machines (VMs), in addition to the updates detected by Discovery1.

References:

3: Product Documentation | ServiceNow