ServiceNow CIS-Discovery Certified Implementation Specialist - Discovery Exam Practice Test

Answer : A

In ServiceNow Discovery, relationships between Configuration Items (CIs) in a horizontal pattern are created using the 'Create Relation/Reference' operation. This operation allows the pattern to define and establish relationships or references between discovered CIs, based on the information gathered during the discovery process. Options B and C are incorrect as relationships are not automatically created nor is it true that they cannot be created via patterns. Option D, 'Create Connections,' is not a standard operation in this context. Reference = ServiceNow Discovery documentation, specifically the sections on creating and managing horizontal discovery patterns.

Answer : C

When increasing the maximum number of threads for a MID Server in ServiceNow Discovery, it's often necessary to also increase the memory allocated to the MID Server application. This is because more threads can result in higher memory usage as each thread may consume resources while performing discovery tasks. Increasing disk space, updating ACL rules for CMDB tables, or increasing the MID Server max payload size are not directly related to the number of threads used by a MID Server. Reference = ServiceNow Discovery documentation, especially sections discussing MID Server configuration and performance tuning.

Answer : A, B, D

In a Merge Table pattern operation within ServiceNow Discovery, the editable fields typically include the Target Table, Second Table, and First Table. These fields are configurable and allow users to specify the tables involved in the merge operation. The Target Table is where the merged data will be stored, while the First and Second Tables are the source tables whose data is being merged. The Primary Table is not typically an editable field in this context. Reference = ServiceNow Discovery documentation, particularly the sections discussing pattern design and operations, including Merge Table operations within Discovery Patterns.

Answer : A, B, C

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.

Answer : B, D

In the ServiceNow Discovery module, under the Recommended Actions pane for an Automated Error Messages list within Discovery > Home, the possible options under ACTION ON ALL include 'View instructions' and 'Retry Discovery'. 'View instructions' allows users to see guidance on how to address the errors, while 'Retry Discovery' enables users to reinitiate the discovery process for the affected devices. 'Make Ranges' and 'Ping IP Addresses' are not standard options in this context. Reference = ServiceNow Discovery documentation and user guides, particularly those discussing the management of automated error messages and recommended actions in Discovery.

Answer : D

In ServiceNow Discovery, when encountering the error 'Active, couldn't classify' during the discovery of a new SNMP network device, it typically indicates an issue with the classification process. Classification is a crucial initial step in the Discovery process, where the system determines the type of device it is interacting with. If an SNMP Classification rule for the new device type does not exist or needs updating, Discovery will be unable to classify and thus properly discover the device. Incorrect SNMP credentials or firewall issues usually result in different types of errors, such as authentication failures or no response from the device.

Answer : B

The deletion strategy 'Mark as absent' means that when a related CI that was previously discovered by a pattern is no longer found, the install_status attribute of that CI is set to Absent. This indicates that the CI is missing or removed from the network.The main CI (in this case, the Linux Server CI) is not affected by the deletion strategy of the related CI (in this case, the Disk CI)12.

Reference 1: Set a deletion strategy - Product Documentation: San Diego - ServiceNow 2: Network adapter status setting to ''Absent'' in EMC ... - ServiceNow ...