CIS-HAM ServiceNow Certified Implementation Specialist - Hardware Asset Management Free Practice Exam Questions (2025 Updated)

The second tier of the capability blueprint in ServiceNow is Practical Management, focusing on managing operational tasks efficiently while aligning with strategic goals. It bridges the gap between foundational and advanced asset capabilities.

A component is considered an IT asset when you want to perform hardware asset management (HAM) activities on it1.

HAM is a subset of IT asset management (ITAM) that focuses on the physical components of IT systems2.

HAM helps you to manage the entire lifecycle of your hardware assets, from planning and acquisition to retirement and disposal1.

Some of the HAM activities that require a component to be an IT asset are:

Manage its procurement: This involves creating and fulfilling asset requests, purchase orders, and stock order tasks for the component1.

Track its incurred costs: This involves tracking the financial information of the component, such as cost, depreciation, budget, and chargeback1.

Manage its maintenance contracts: This involves managing the vendor, warranty, and contract details of the component, as well as the return merchandise authorization (RMA) processes for products to be returned, replaced, or repaired1.

Therefore, the options that are also HAM activities are A. Manage its procurement, D. Track its incurred costs, and E. Manage its maintenance contracts.

The other options that are not HAM activities are:

Know its relationships to a business service: This involves mapping the component to other components and services in the configuration management database (CMDB)2. This is a configuration management (CM) activity, not a HAM activity.

Track its operational information: This involves tracking the current status, location, owner, and other attributes of the component that reflect its operational state2. This is also a CM activity, not a HAM activity. References:

1: Hardware Asset Management

2: What is Hardware Asset Management?

According to the Hardware Asset Management documentation, non-consumable assets are assets that are not depleted or used up when they are applied or consumed, such as laptops, monitors, or routers.

Non-consumable assets are tracked individually in the ServiceNow platform, and each asset has a unique asset tag and serial number.

When transferring non-consumable assets between stockrooms, they must be transferred as a single entity with a quantity of one, as stated in the Hardware Asset Management documentation: “Non-consumable assets are transferred as a single entity with a quantity of one. For example, a laptop is transferred as a single entity with a quantity of one.”

Therefore, the correct answer is option C, as a single entity with a quantity of one. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

The core table that requires migration when extending ITSM Asset Management with Hardware Asset Management is the alm_asset table1.

The alm_asset table stores the records of all the assets in the system, regardless of their type or class1.

When you activate the Hardware Asset Management plugin, a migration script runs that converts the existing asset records in the alm_asset table to hardware asset records in the alm_hardware table2.

The alm_hardware table is a child table of the alm_asset table that stores the records of the hardware assets only2.

The migration script also updates the references and relationships of the migrated assets to the new table2.

The migration script runs only once and does not affect the future creation or update of asset records2. References:

Asset table - Product Documentation: San Diego - ServiceNow

Hardware Asset Management - Product Documentation: Tokyo - ServiceNow

A transfer order is a document that records the movement of assets from one location to another1.

A transfer order line is a record that specifies the quantity and type of assets to be transferred1.

When you cancel a transfer order line, the associated assets are released from the transfer order and their state changes from Pre-allocated to Available1.

The released assets can then be attached to another transfer order or used for other purposes1. References:

Transfer orders - Product Documentation: Rome - ServiceNow

The Normalization statuses are the indicators of how well the hardware and consumable models are standardized and normalized in the model catalog and the CMDB. The Normalization statuses are:

Manufacturer Normalized: The model has been normalized with the manufacturer name and the product name, but not the model number or the device type. For example, Dell Latitude.

Match Not Found: The model has not been normalized because no matching model was found in the Hardware Asset Management Content Service. For example, ABC XYZ.

Partially Normalized: The model has been normalized with the manufacturer name, the product name, and the model number, but not the device type. For example, Dell Latitude E7450.

Normalized: The model has been fully normalized with the manufacturer name, the product name, the model number, and the device type. For example, Dell Latitude E7450 (Laptop).

Manually Normalized: The model has been manually updated by the user with the normalization content, such as the manufacturer name, the product name, the model number, and the device type. For example, HP Pavilion 15 (Laptop).

New: The model has been created and has not yet run through the normalization process. For example, Lenovo ThinkPad T490.

Normalization is the process of standardizing the hardware model data by manufacturer name, model name, and model number1.

Normalization helps to maintain a clean and consistent configuration management database (CMDB) and to avoid duplicate or inaccurate hardware models1.

Normalization first runs to normalize the record when you save the hardware model record1.

This means that when you create or edit a hardware model record, the system automatically checks the record against the normalization rules and the Hardware Content Service Lifecycle data, and updates the record with the normalized values if applicable1.

Therefore, the answer that reflects when normalization first runs is C. When you save the hardware model record.

The other options are not the correct answer because they describe different scenarios or actions:

A. When the daily scheduled HAM – Daily job runs: This is not the correct answer, because the daily scheduled HAM – Daily job does not run normalization. The daily scheduled HAM – Daily job is a scheduled job that runs various tasks related to hardware asset management, such as updating the asset status, calculating the depreciation, and sending notifications2.

B. When the weekly scheduled HAM – Normalization job runs: This is not the correct answer, because the weekly scheduled HAM – Normalization job does not run normalization for the first time. The weekly scheduled HAM – Normalization job is a scheduled job that runs normalization for all the existing hardware models in the CMDB on a weekly basis1. It does not affect the newly created or edited hardware models, which are normalized when they are saved1.

D. When you click the Normalize Hardware Model link under Related Links: This is not the correct answer, because clicking the Normalize Hardware Model link under Related Links does not run normalization for the first time. Clicking the Normalize Hardware Model link under Related Links is a manual action that allows you to run normalization for a specific hardware model record at any time1. It does not affect the automatic normalization that runs when you save the hardware model record1. References:

1: Hardware Normalization

2: Daily Scheduled HAM – Daily Job

A transfer order is a document that is used to execute the movement of hardware assets from one stockroom location to another within the same organization1.

A transfer order is created when there is a need to replenish, share, or relocate hardware assets between different stockrooms1.

A transfer order consists of one or more transfer order lines, each containing the information about the asset to be moved, such as the model, quantity, source stockroom, destination stockroom, and expected delivery date1.

A transfer order can be created manually or automatically based on predefined rules or thresholds1.

A transfer order goes through several stages, such as draft, approved, shipped, received, and closed1.

A transfer order can be tracked and managed using the Hardware Asset Management Workspace or the Transfer Order form1. References:

Transfer orders

According to the ServiceNow Hardware Asset Management documentation, a business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried. Business rules can be used to enforce data consistency and integrity, such as preventing duplicate transfers of the same asset. The other options are not valid terms in ServiceNow Hardware Asset Management.

According to the ServiceNow Hardware Asset Management documentation, the Retired state indicates that the asset is no longer in use and is ready for disposal or reuse. The substates of the Retired state are:

Disposed: The asset has been discarded or recycled.

Donated: The asset has been given away to a charity or a non-profit organization.

Vendor Credit: The asset has been returned to the vendor for a credit or a refund.

Sold: The asset has been sold to a third party.

The substate Pending Disposal is not valid for the Retired state, as it is only available for the states In Stock and In Transit. The substate Destroyed is not valid for the Retired state, as it is only available for the state In Use. References:

ServiceNow Hardware Asset Management: Asset and CI management

ServiceNow Hardware Asset Management: Setting asset states and substates