Pass Your Next CIS-HAM Certification Exam Easily & Hassle Free [Q61-Q80]

Normalization mappings are a feature of the Hardware Asset Management (HAM) application that allow you to standardize the manufacturer name, model name, and model number of hardware assets in the Configuration Management Database (CMDB)1.
Normalization mappings are created by matching the values from the discovery source to the values in the Product Catalog2.
Normalization mappings help you to fully normalize hardware models by ensuring that the asset data is consistent, accurate, and complete3. References:
Hardware Normalization
Create normalization mappings
What is Hardware Asset Management?

Hardware normalization is a process that standardizes the data of hardware and consumable models by using the United Nations Standard Products and Services Code (UNSPSC) and a set of rules12.
Normalization can be performed manually or automatically on models in the model catalog12.
If a model has been normalized, it will have a check mark in the Normalized column in the model list1.
To revert the normalization of a model, you can use the Revert Normalization UI action, which is available on the model form13.
The Revert Normalization UI action will restore the original values of the model attributes that were changed by the normalization process13.
The Revert Normalization UI action will also clear the Normalized check mark and the Normalization Source field on the model form13. Reference: Work with hardware normalization – ServiceNow – Now Support, Hardware Asset Management builds onCore Asset Management – ServiceNow, Automation Simplifies Hardware Asset Management – ServiceNow Blog, Product Documentation | ServiceNow

Explanation
Consumables are hardware assets that are not tracked individually, but as a quantity of items in a stockroom, such as keyboards, mice, cables, etc.1 When a stock manager receives a new delivery of consumables, they can use the Mobile Asset Receiving feature to scan the barcode of the purchase order and receive multiple assets against it using a mobile device2 If the received consumables match another record in the stockroom based on the following fields:
Assigned to, Model, Model category, State, Stockroom, and Substate, then the data is automatically merged to create a blended quantity and cost3 This means that the system calculates the average cost per item and the total quantity of the consumables in the stockroom, and updates the existing record accordingly3 This feature helps to reduce duplicate records and simplify inventory management of consumables3 References: 1: Hardware Asset Management – ServiceNow 2: [Mobile Asset Receiving – ServiceNow] 3:
[Consumable Hardware Assets – ServiceNow]

Transform maps are used to transform imported hardware model data from an import set table to a target table, such as the Product Catalog or the Asset table1 Coalesce is an option that you can set on a field mapping to uniquely identify the same asset in order to merge or update records2 Coalesce means that the field is used as a unique key. If a match is found using the coalesce field, the existing record is updated with the imported information. If no match is found, a new record is inserted2 Coalesce helps to prevent duplicate records and ensure data consistency2 You can set coalesce on one or more fields in a transform map, but at least one coalesce field is required2 The other options, B. Consolidate, C. Unique identifier, D. Unique source, E. Unique target, and F. Combine, are not valid options for setting the unique identification of assets in transform maps

Explanation
When an asset is manually created from a purchase order before it has been shipped by the supplier, the default state of the asset is set to On order. This state indicates that the asset has been ordered but not yet received. The asset state will change to Awaiting delivery when the asset is shipped by the supplier, and to In stock when the asset is received by the stockroom. The asset state will change to In use when the asset is deployed to a user or a location, and to Pending transfer when the asset is ready to be transferred to another stockroom or location. The asset state will change to Retired when the asset is disposed of or returned to the supplier. References:
Hardware Asset States, which describes the different states and substates of hardware assets and how they are used to track the asset lifecycle.
Hardware Asset Management overview, which describes the functionalities of the Hardware Asset Management application, including the dashboard, model normalization, hardware refresh, lease contract expiration, disposal orders, and RMA requests.
Hardware Asset Lifecycle Automation, which explains how to automate the workflows and tasks for managing the assets throughout their lifecycle stages, from request to retire.

According to the ServiceNow Hardware Asset Management documentation, the system property glide.ham.
retire_sw() determines the behavior of software allocations when a hardware asset is retired. The possible values are:
*Reclaim: The software allocations are automatically returned to inventory and the software installation records are deleted.
*Retain: The software allocations remain with the hardware asset and need to be reclaimed manually.
*Remove: The software allocations are removed from the asset, but not returned to inventory.

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 Audit your inventory document, a blind inventory audit is a type of audit that hides the expected asset list from the auditor, so that the auditor has to physically scan each asset in the location and compare it with the actual asset list1.
A blind inventory audit helps ensure data integrity and accuracy, as it prevents the auditor from “cheating on the test” by relying on the expected asset list1.
A blind inventory audit is typically initiated via the Now Agent Mobile app, which is a mobile application that enables users to perform various tasks related to hardware asset management, such as scanning assets, creating audits, and viewing audit results1.
The Now Agent Mobile app allows users to create an audit on the mobile device, select the location and type of audit, and scan the assets using the device camera or a Bluetooth scanner1.
Therefore, the correct answer is option C, Now Agent Mobile app, as it is the interface that is typically used to initiate a blind inventory audit. Reference:
Audit your inventory
What is Hardware Asset Management?

Explanation
Hardware normalization is the process of standardizing the details of your hardware models, such as manufacturer, product, model, and device type, by comparing them with the data from the Hardware Model Normalization Content Service12.
Hardware normalization runs by default on an hourly basis, as part of the Stock Rule Runner scheduled job13.
The Stock Rule Runner job also checks the stock levels of your models and assets in stockrooms and creates stock orders to replenish them if they are below the minimum quantity specified in the stock rules13.
Therefore, the correct answer is A. On an hourly basis, as this is the default frequency of the hardware normalization process.
References: 1: Hardware Model Normalization – Product Documentation: Tokyo – ServiceNow 2: Hardware Asset Inventory Management – ServiceNow 3: Stock Rules in ServiceNow – GlideFast ServiceNow

Explanation
According to the ServiceNow Hardware Asset Management documentation, a configuration item (CI) is an entity or thing that you wish to track that is required for the delivery of a service. A CI can be a hardware asset, a software asset, a service, a document, or any other component that is part of the IT infrastructure1. A CI is different from an IT asset in that a CI focuses on the technical attributes and relationships of the component, while an IT asset focuses on the financial and contractual aspects of the component2. Therefore, a component is considered a CI as opposed to an IT asset when you want to track its relationship information, such as its dependencies, impacts, and interactions with other CIs. Relationship information helps to manage the configuration and performance of the IT services and to identify and resolve incidents and problems3.
The other options are not correct because:
Track its incurred costs: This is a function of an IT asset, not a CI. An IT asset tracks the cost, depreciation, and value of the component, as well as the budget and expenses related to the component2.
Manage its retirement: This is also a function of an IT asset, not a CI. An IT asset tracks the status, location, ownership, and history of the component, as well as the events and actions that occur during the asset lifecycle, including its retirement or replacement2.
Manage its license contracts: This is another function of an IT asset, not a CI. An IT asset tracks the terms and conditions, warranties, service level agreements (SLAs), and renewals of the contracts associated with the component. Contract management helps to manage the vendor relationships and compliance obligations of the component2.
Know who is using it: This is not a specific function of either an IT asset or a CI, but rather a common attribute that can be shared by both. Both an IT asset and a CI can have a user or owner field that indicates who is using or responsible for the component4.
References:
ServiceNow Hardware Asset Management: Asset and CI management
ServiceNow Hardware Asset Management: Configuration Management
ServiceNow Hardware Asset Management: Configuration item (CI)
ServiceNow Hardware Asset Management: Asset and CI fields

Explanation
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?

When an asset is manually created from a purchase order before it has been shipped by the supplier, the default state of the asset is set to On order. This state indicates that the asset has been ordered but not yet received. The asset state will change to Awaiting delivery when the asset is shipped by the supplier, and to In stock when the asset is received by the stockroom. The asset state will change to In use when the asset is deployed to a user or a location, and to Pending transfer when the asset is ready to be transferred to another stockroom or location. The asset state will change to Retired when the asset is disposed of or returned to the supplier. References:
* Hardware Asset States, which describes the different states and substates of hardware assets and how they are used to track the asset lifecycle.
* Hardware Asset Management overview, which describes the functionalities of the Hardware Asset Management application, including the dashboard, model normalization, hardware refresh, lease contract expiration, disposal orders, and RMA requests.
* Hardware Asset Lifecycle Automation, which explains how to automate the workflows and tasks for managing the assets throughout their lifecycle stages, from request to retire.

Explanation
According to the ServiceNow Hardware Asset Management documents, a hardware asset’s lifecycle consists of the following stages: Procure, Receive, Deploy, Maintain, and Dispose1. These stages correspond to the options A, D, and E in the question. The option B, Request, is also a valid stage in the hardware asset management process, as it involves identifying the hardware needs and initiating the procurement process2.
However, the option C, Consume, is not a component of a hardware asset’s lifecycle, as it is not mentioned in the ServiceNow documents. Consume is more relevant to software assets, which are used or consumed by end-users or applications3. Therefore, the correct answer is C. Consume. References:
ServiceNow Hardware Asset Management landing page
ServiceNow Hardware Asset Management overview
ServiceNow Software Asset Management overview