According to the Hardware Asset Management documentation, a transfer order is a record that tracks the movement of assets from one stockroom to another.

A transfer order line is a record that specifies the quantity and type of assets to be transferred, as well as the source and destination stockrooms1.

When using the HAM application, what happens when you create a new transfer order line on a transfer order is that a transfer order line task is automatically created to move the transfer order line from one stage to another1.

A transfer order line task is a record that tracks the progress of the transfer order line through the following stages1:

Requested: The transfer order line is created and waiting for approval.

Approved: The transfer order line is approved and ready for fulfilment.

Fulfilled: The transfer order line is fulfilled and the assets are shipped from the source stockroom.

Received: The transfer order line is received and the assets are checked in at the destination stockroom.

Closed: The transfer order line is closed and the transfer is complete.

Therefore, the correct answer is option C, a transfer order line task is automatically created to move the transfer order line from one stage to another, as it describes what happens when you create a new transfer order line on a transfer order. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

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.

Operational: The current status, performance, availability, and capacity of the CI, as well as any incidents, problems, or changes that affect it.

Relationship: The dependencies and connections between the CI and other CIs, services, processes, and users.

The information that you would track for an asset includes:

Financial: The cost, depreciation, ownership, and warranty of the asset, as well as any procurement or disposal activities.

Lifecycle: The stages and transitions of the asset from request to retirement, as well as any inventory or stock management.

The information that you would not track for a CI versus an asset are:

Contractual: This information is relevant for both CIs and assets, as it relates to the agreements and obligations between the service provider and the customer or vendor.

Lifecycle: This information is relevant for both CIs and assets, as it relates to the stages and transitions of the component from request to retirement.

An asset is a record that represents any tangible or intangible object that is tracked by the organization12.

There are different types of assets, depending on their nature, usage, and lifecycle12.

The types of assets are12:

Model: A model is a record that defines the common attributes and specifications of a group of assets, such as manufacturer, product, category, and device type12. For example, Dell Latitude E7450 is a model of a laptop.

Software entitlement: A software entitlement is a record that defines the rights and obligations of using a software product, such as license type, quantity, expiration date, and cost13. For example, Microsoft Office 365 is a software entitlement that grants access to various

 Hardware Model Normalization is a feature that enables users to standardize the data of hardware and consumable models, such as manufacturer, product, model, and device type. Hardware Model Normalization requires the activation of the Hardware Model Normalization (com.sn_hwnorm) plugin, which also activates the Normalization Data Services Client (com.glide.data_services_canonicalization.client) plugin. These plugins install several tables that store the normalized data and the rules for normalization. The tables that are installed with Hardware Model Normalization are:

Device Type: This table contains the device types that are used to categorize the hardware models, such as laptop, desktop, server, printer, etc.

Hardware Manufacturer: This table contains the normalized names of the hardware manufacturers, such as Dell, HP, Lenovo, etc.

Hardware Model Library: This table contains the normalized data of the hardware models, such as manufacturer, product, model, device type, UNSPSC code, etc. This table is populated by the Hardware Model Normalization Content Service, which is a subscription-based service that provides the latest and most accurate data for hardware models.

Hardware Normalize Key: This table contains the rules for generating the normalize key, which is a unique identifier for each hardware model based on its manufacturer, product, and model. The normalize key is used to match the hardware models with the Hardware Model Library data.

The other options, C. Hardware Normalize Key and E. Device Name, are not tables that are installed with Hardware Model Normalization. Hardware Normalize Key is a field in the Hardware Model [cmdb_model] table, not a separate table. Device Name is a field in the Configuration Item [cmdb_ci] table, not a separate table. References: Hardware Model Normalization, Demo - HAM Professional - Hardware Model Normalization, Hardware Asset Management

According to the ServiceNow Hardware Asset Management documentation, the Scanned Assets related list displays the assets that have been scanned using the ServiceNow Agent mobile app during an audit. The Scanned Assets related list is updated each time scans are submitted from the app, which can be done manually or automatically based on the app settings

When disposing of an IT asset through a vendor, the asset manager should attach a certificate of destruction to the retired asset’s record1.

A certificate of destruction is a document that verifies that the asset has been destroyed in a secure and compliant manner by the vendor1.

A certificate of destruction should include information such as the asset tag, serial number, model, manufacturer, date of destruction, method of destruction, and signature of the authorized person1.

A certificate of destruction helps the asset manager to ensure that the asset is no longer in use, that the data on the asset is erased, and that the asset is disposed of in accordance with environmental, regulatory, and legal requirements1. References:

1: Hardware Asset Disposal