Free ServiceNow CIS-HAM Practice Exam with Questions & Answers | Set: 5

The CMDB Health Dashboard is a tool that monitors and reports the health of the Configuration Management Database (CMDB) data based on four key performance indicators (KPIs): completeness, compliance, correctness, and relationship accuracy12.

Completeness measures the percentage of configuration items (CIs) that have the required and recommended attributes populated12.

Compliance measures the percentage of CIs that adhere to predefined regulatory requirements, internal governance, and certificates12.

Correctness measures the percentage of CIs that pass the predefined data integrity rules, such as identification rules, orphan CI rules, and stale CI rules12.

Relationship accuracy measures the percentage of CIs that have the expected relationships with other CIs12.

The CMDB Health Dashboard focuses on the first three areas of data quality: completeness, compliance, and correctness12. These areas are also reflected in the overall CMDB health score, which is calculated as the weighted average of the three KPIs12.

The other options, configuration, conciseness, and conformity, are not the areas of data quality that the CMDB Health Dashboard focuses on12.

Configuration is the process of defining and managing the characteristics of CIs, such as their attributes, relationships, dependencies, and status3.

Conciseness is the quality of being clear and brief, without unnecessary words or details4.

Conformity is the quality of being consistent with a set of rules, standards, or expectations5.

A consumable is a type of asset that is used up or depleted over time, such as printer cartridges, paper, or batteries1.

Before a consumable can be consumed, it must have a model record, a model category record, and a consumable record in ServiceNow12.

A model record defines the attributes of a consumable, such as its name, manufacturer, cost, and quantity12.

A model category record specifies the type of consumable, such as office supplies, hardware, or software12.

A consumable record tracks the current stock level, location, and status of a consumable12.

A stock order record is used to request new consumables from a vendor or supplier, but it is not required before a consumable can be consumed13.

A transfer order record is used to move consumables from one location to another, but it is not required before a consumable can be consumed14. References: 1: Consumables - Product Documentation: Vancouver - ServiceNow 2: Create a consumable model - Product Documentation: Vancouver - ServiceNow 3: Create a stock order - Product Documentation: Vancouver - ServiceNow 4: Create a transfer order - Product Documentation: Vancouver - ServiceNow

Create transform map: A transform map is a set of field mappings that determine how the source data in the import set table is transformed into the target data in the hardware asset table. You can create a transform map by using the Load Data UI page, or by navigating to System Import Sets > Create Transform Map. You need to specify the source table, the target table, and the field mappings between them. You can also define coalesce fields, which are used to prevent duplicate records from being created or updated. For example, you can use the asset tag or the serial number as a coalesce field.

Load data: To load data into the import set table, you need to select a data source, such as a file, a JDBC data source, or a web service. You can use the Load Data UI page, or navigate to System Import Sets > Load Data. You need to specify the source type, the file name or the connection URL, the sheet number and the header row (if using a file), and the import set table name. You can also preview the data before loading it into the table.

Run transform map: To run the transform map, you need to navigate to System Import Sets > Transform Maps, and select the transform map that you created. You can then click on the Run Transform button, which will execute the field mappings and transform the data from the import set table to the hardware asset table. You can also view the transformation history, the transformation statistics, and the transformation log to monitor the progress and the results of the transformation.

To perform hardware model normalization, you need to use the Hardware Model Normalization Content Service, which is a data service that provides standardized information about hardware models from various manufacturers. You can access this service from the Hardware Model Normalization module under Asset Management. To set the normalized display name for a hardware model, you need to use the following three fields from the hardware model record:

Name: This is the name of the hardware model as it appears in the model catalog or the CMDB. For example, “iPhone 12 Pro”.

Manufacturer: This is the name of the manufacturer of the hardware model. For example, “Apple”.

Model number: This is the unique identifier of the hardware model assigned by the manufacturer. For example, “A2341”.

The normalized display name is a combination of these three fields, separated by commas. For example, “iPhone 12 Pro, Apple, A2341”. The normalized display name helps you to easily identify and compare hardware models across different sources and platforms. References: Hardware Model Normalization, Demo - HAM Professional - Hardware Model Normalization, Work with hardware normalization, Hardware Asset Management - ServiceNow

The Hardware Asset Management (HAM) plugin is a plugin that enables the Hardware Asset Management application, which helps to track and manage the end-to-end lifecycle of hardware assets, physical and consumable1.

The HAM plugin provides the following baseline asset lifecycle automation flows2:

Hardware asset order: This is a flow that automates the process of ordering new hardware assets from a vendor. It creates purchase orders, stock order tasks, and catalog tasks based on the asset requests and the stock rules2.

Hardware deployment: This is a flow that automates the process of delivering and installing hardware assets to the end users. It creates catalog tasks and updates the asset records and the configuration management database (CMDB) based on the stock order tasks and the asset reservations2.

Hardware disposal: This is a flow that automates the process of disposing of retired hardware assets through a vendor. It creates return merchandise authorization (RMA) records and updates the asset records and the CMDB based on the asset retirements and the vendor contracts2.

Therefore, the baseline asset lifecycle automation flows that are also options in the question are A. Hardware asset order, E. Hardware deployment, and F. Hardware disposal.

The other options that are not baseline asset lifecycle automation flows provided by the HAM plugin are:

B. Hardware bulk stock order: This is not a baseline asset lifecycle automation flow, but a manual action that allows the user to create multiple stock order tasks for different hardware models at once3.

C. Hardware swap order: This is not a baseline asset lifecycle automation flow, but a manual action that allows the user to swap a hardware asset with another hardware asset of the same model4.

D. Hardware retire order: This is not a baseline asset lifecycle automation flow, but a manual action that allows the user to retire a hardware asset and update its status and substatus. References:

1: Hardware Asset Management

2: Asset Lifecycle Automation Flows

3: Create a Bulk Stock Order

4: Swap a Hardware Asset

: Retire a Hardware Asset

Classes are represented as tables in the ServiceNow database that define the attributes and relationships of a specific type of record1

The base asset class is the alm_asset table, which contains the common fields and properties for all types of assets, such as hardware, software, consumable, etc.2

The alm_asset table is extended by other asset classes, such as alm_hardware, alm_software, alm_consumable, etc., which add more specific fields and properties for each asset type2

The cmdb_asset table is not a class, but a view that joins the alm_asset table and the cmdb_ci table, which is the base configuration item (CI) class3

The cmdb_hardware table is a CI class, not an asset class, that contains the common fields and properties for all types of hardware CIs, such as computers, devices, network equipment, etc.4

The Normalization Data Services Client plugin enables you to use the Normalization Data Services (NDS) to provide consistent, good, clean data for the company names of vendors or manufacturers12.

The NDS is a cloud-based service that provides a comprehensive and up-to-date list of canonical company names for vendors and manufacturers, as well as other data such as product categories, models, and versions12.

The NDS helps you to avoid data duplication, inconsistency, and inaccuracy in your CMDB and asset management processes12.

The NDS integrates with the Hardware Model Normalization plugin, which standardizes the details of your hardware models by comparing them with the data from the Hardware Model Normalization Content Service13.

Therefore, the correct answer is D. Normalization Data Services Client (com.glide.data_services_canonicalization.client), as this is the plugin that offers consistent, good, clean data for the company names of vendors or manufacturers.

 According to the ServiceNow Hardware Asset Management documentation, the asset lifecycle defines and describes the series of stages involved in managing an asset throughout its useful life. The first stage of the asset lifecycle is the request stage, where stakeholders get together, discuss their objectives, and determine which assets are needed and why. The culmination of this stage is a formal request for an asset. The asset lifecycle begins when the asset is requested, not when it is procured, deployed, or fulfilled. References:

ServiceNow Hardware Asset Management: Hardware Asset Management overview

ServiceNow Hardware Asset Management: What is the IT Asset Lifecycle?