CIS-HAM Questions and Answers

According to the ServiceNow Hardware Asset Management documentation, original cost is the amount paid to acquire an asset, including any taxes, fees, shipping, installation, or other expenses directly related to the purchase. Original cost is used to calculate depreciation and amortization of an asset over its useful life. The other options are not the type of cost that taxes paid at the time of purchase are. Operating expense, operating cost, and capital expense are different ways of classifying the costs of using and maintaining an asset after it is purchased.

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.

Once a catalog item has been requested, the mechanism that determines the approvals and tasks that are triggered in the application is the flow12.

A flow is a graphical representation of a business process that consists of one or more actions, such as approvals, tasks, notifications, scripts, etc., that are executed based on certain conditions and triggers12.

A flow can be associated with a catalog item to define the fulfillment process for that item, such as who needs to approve it, what tasks need to be performed, and what notifications need to be sent12.

A flow can be created and managed using the Flow Designer, a low-code development tool that allows users to design and test flows without writing any code12.

A flow can be activated or deactivated, versioned, and published to make it available for use12.

A flow can be monitored and debugged using the Flow Execution Details and the Flow Logs12. References:

Flow Designer

Service Catalog Request Fulfillment

The current value of an asset is the amount that the asset is worth at the present time, based on its original cost and the accumulated depreciation1.

The current value of an asset is also known as the residual value or the book value12.

The residual value is the estimated value of the asset at the end of its useful life2.

The residual value is used to calculate the depreciation expense of the asset over its useful life2.

The residual value is different from the salvage value, which is the estimated value of the asset if it is sold or disposed of2.

The cost of ownership is the total amount of money spent on acquiring, maintaining, and operating an asset over its lifetime3.

The current balance is the amount of money available in an account at a given time4.

According to the ServiceNow Hardware Asset Management documentation1, when a hardware asset is retired, the system property glide.ham.retire_reclaim_sw() determines whether the software allocations on that asset are automatically reclaimed or not. If the property is set to true, the software allocations are returned to the inventory. If the property is set to false, the software allocations remain with the hardware asset and need to be reclaimed manually. References: 1: Hardware Asset Management - ServiceNow2

The Identification and Reconciliation process in ServiceNow ensures that configuration items (CIs) are correctly matched during the import process. This prevents duplication by validating unique identifiers, such as serial numbers or UUIDs, ensuring CMDB integrity.

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

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

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.

According to the ServiceNow Product Documentation on Transfer Orders1, transfer orders are records that define the movement of assets from one stockroom to another1. They can be used to replenish the stock of assets, fulfill asset requests, or relocate assets1.

According to the ServiceNow Product Documentation on Transfer Order Line Tasks2, transfer order line tasks are records that define the actions that need to be performed for each transfer order line2. A transfer order line is a record that defines the quantity and model of the assets that are being transferred1.

The main purposes of transfer order line tasks are2:

To help track service levels and the time frame needed to complete a transfer order: Transfer order line tasks have a due date and a state that indicate the progress and completion of the transfer order line. They also have a priority and an assignment group that determine the urgency and the responsibility of the transfer order line. These fields help users to monitor and manage the service levels and the time frame needed to complete a transfer order.

To move transfer order lines from one stage to another: Transfer order line tasks have a type that defines the action that needs to be performed for the transfer order line, such as pick, pack, ship, or receive. As transfer order line tasks are completed, the transfer order line moves from one stage to another, such as requested, in transit, or received. These stages reflect the status and location of the assets that are being transferred.

 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 Hardware Asset Management documentation, the hardware asset management content service is a cloud-based service that provides normalized and enriched hardware model data to the ServiceNow platform, such as manufacturer name, model name, model number, and product lifecycle information.

The hardware asset management content service helps customers identify and manage their hardware assets more effectively, as well as plan for hardware refreshes based on end-of-life (EOL) and end-of-service (EOS) dates1.

The elements that are provided by the hardware asset management content service are as follows1:

Manufacturer lifecycle dates: The dates when the manufacturer stops selling, supporting, or servicing a hardware product.

Manufacturer: The name of the company that produces the hardware product.

Model name: The name of the hardware product, such as Dell Latitude E7450 or HP ProLiant DL380 Gen10.

Therefore, the correct answers are options A, D, and E, as they are the elements that are provided by the hardware asset management content service. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

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.

Assets are tangible items tracked for lifecycle management and financial purposes. Facilities (e.g., buildings), servers, and network cables are physical assets. Software licenses and distributions are intangible and treated differently in ServiceNow Asset Management.

The total cost of ownership (TCO) is a financial estimate that measures the direct and indirect costs of owning and operating an asset over its entire lifecycle. The TCO includes the following components:

Original cost: This is the initial purchase price of the asset, which may include taxes, fees, shipping, and installation costs. The original cost is also known as the acquisition cost or the capital expense.

Operational expense: This is the ongoing cost of maintaining and using the asset throughout its lifecycle, which may include repair, upgrade, maintenance, support, energy, consumables, and disposal costs. The operational expense is also known as the operating expense or the opex.

Depreciation expense: This is the reduction in the value of the asset over time due to wear and tear, obsolescence, or market changes. The depreciation expense is also known as the depreciation cost or the depreciation charge.

Delivery cost: This is the cost of transporting the asset from the supplier to the buyer, which may include freight, insurance, customs, and handling fees. The delivery cost is also known as the shipping cost or the transportation cost.

The TCO can be calculated by adding the original cost, the operational expense, and the depreciation expense, and subtracting the delivery cost. Alternatively, the TCO can be calculated by multiplying the annual cost of ownership by the expected lifespan of the asset.

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. References:

Audit your inventory

What is Hardware Asset Management?

Deploying asset tasks during the retirement of an asset means using the ServiceNow Enterprise Asset Workflow Automation feature, which automates the end-of-life procedures for assets that are no longer needed or functional1.

This feature allows you to flag assets as retired pending disposal, triggering a workflow that verifies the asset condition, determines the disposal method, and saves the disposal certificates1.

The two primary benefits of deploying asset tasks during the retirement of an asset are:

Reduces manual intervention: By automating the retirement process, you can eliminate the need for manual data entry, human errors, and delays. You can also ensure compliance with policies and regulations by following a standardized procedure12.

Increases speed of updates: By using the ServiceNow Agent mobile app, you can scan asset tags and barcodes, update asset status and inventory, and complete asset tasks on the go. This can increase the speed and accuracy of asset updates and reduce the risk of data loss or duplication13. References:

1: Enterprise Asset Workflow Automation - ServiceNow

2: Asset and CI management - Product Documentation: San Diego - ServiceNow

3: Enterprise Asset Management - ServiceNow

A model category is a classification of models that defines how they are managed in the system1. It determines the behavior and attributes of the models and the assets or configuration items (Cls) that are created from them1.

Model categories can be used to group consumables, assets, or services in the product catalog or the service catalog, but this is not their primary function. Their primary function is to define the relationship between configuration management and asset management1.

Configuration management is the process of identifying, tracking, and verifying the configuration items (Cls) in an IT environment and their relationships2. Asset management is the process of tracking and managing the financial, contractual, and inventory details of IT assets throughout their lifecycle3.

Model categories determine when to create assets from configuration items (Cls) based on the asset tracking strategy1. For example, some model categories, such as Computer, create assets automatically when Cls are discovered or imported1. Other model categories, such as Consumable, require manual creation of assets from the product catalog1.

Model categories also provide the link between configuration management and asset management by allowing asset managers to view the configuration data of the assets and configuration managers to view the asset data of the Cls1. This enables better visibility, control, and alignment of IT assets and services1.

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

During an inventory audit, if you accidentally scan the same asset twice, the Hardware Asset Management (HAM) application will automatically remove the duplicate records and only import the unique scans. This is because the HAM application uses the asset tag or the serial number as a coalesce field, which prevents duplicate records from being created or updated in the hardware asset table. Therefore, you do not need to worry about scanning the same asset twice, as the HAM application will handle the duplicates for you. References:

Audit your inventory, which provides a step-by-step guide on how to perform scheduled or blind audits of asset stockrooms and other locations using the Agent mobile app and the Now Platform.

Hardware Asset States, which describes the different states and substates of hardware assets and how they are used to track the asset lifecycle.

Importing Hardware Assets into ServiceNow, which provides a step-by-step guide on how to import hardware assets into ServiceNow using an excel spreadsheet, an import set table, and a transform map.

 According to the ServiceNow Hardware Asset Management documentation, ITAM personas and ITAM roles are different concepts that relate to the types and access of users of the product. The difference between them are as follows:

ITAM personas are user profiles that represent the typical users of the ITAM product and their business needs. They are not tied to any specific role or permission, but rather describe the goals, challenges, and expectations of the users. For example, some of the ITAM personas are IT Asset Manager, IT Asset Analyst, IT Procurement Manager, and IT Finance Manager1.

ITAM roles are access controls that determine what features and functions a user can access in the ITAM product. They are assigned to users or groups based on their responsibilities and tasks. They can also be combined to grant multiple levels of access to a user. For example, some of the ITAM roles are asset, asset_admin, asset_tagging, and procurement2.

Therefore, a user may have multiple roles, but a single persona (A), roles control access to features in the product (B), personas represent types of users of the product ©, and a user may have multiple roles and personas (F) are the correct statements that describe the difference between ITAM personas and ITAM roles. References:

1: ITAM personas 2: ITAM roles

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.

Stock rules are the rules that define the minimum and maximum quantities of hardware assets in a stockroom1.

Stock rules help to optimize the inventory levels and avoid overstocking or understocking of hardware assets1.

Stock rules have the following purposes:

To automatically transfer assets when a low quantity threshold is detected in a stockroom: This means that when the quantity of a hardware asset in a stockroom falls below the minimum threshold defined by the stock rule, the system automatically creates a transfer order to replenish the stockroom from another stockroom that has excess quantity of the same asset1.

To send notifications when a low quantity threshold is detected in a stockroom: This means that when the quantity of a hardware asset in a stockroom falls below the minimum threshold defined by the stock rule, the system sends an email notification to the stockroom manager or other stakeholders to alert them of the low inventory level1.

Therefore, the purposes of stock rules that are also options in the question are A. To automatically transfer assets when a low quantity threshold is detected in a stockroom and C. To send notifications when a low quantity threshold is detected in a stockroom.

The other options that are not purposes of stock rules are:

To track stock orders from a vendor: This is not a purpose of stock rules, but a function of purchase orders. Purchase orders are the records that capture the details of the vendor contracts for procuring hardware assets2. Purchase orders help to track the status, quantity, and cost of the stock orders from a vendor2.

To track stock movement between stockrooms: This is not a purpose of stock rules, but a function of transfer orders. Transfer orders are the records that track the movement of hardware assets between stockrooms3. Transfer orders help to track the source, destination, quantity, and status of the stock transfers between stockrooms3.

To send notifications when a stock shipment arrives at a stockroom: This is not a purpose of stock rules, but a function of stock order tasks. Stock order tasks are the tasks that track the fulfillment of asset requests from stockrooms4. Stock order tasks help to send notifications when a stock shipment arrives at a stockroom and when the assets are received and verified4. References:

1: Stock Rules

2: Purchase Orders

3: Transfer Orders

4: Stock Order Tasks

The itil role enables the user to perform actions related to incident, problem, change, and configuration management. This role is part of the ITIL framework, which is a set of best practices for delivering IT services. According to the ServiceNow documentation1, the itil role can do the following:

Create and update incidents, problems, and change requests

View configuration items (CIs) and their relationships

Add comments and work notes to tasks

Approve or reject change requests

Close resolved incidents and problems

Reopen closed incidents and problems

The other roles listed in the question have different functions and permissions. For example, the procurement_user role can request and track hardware purchases2, the inventory_admin role can manage stockrooms and transfer orders3, the discovery_admin role can configure and run Discovery to populate the CMDB4, and the asset role can view and edit asset records5.

According to the ServiceNow Hardware Asset Management documentation, asset management is the practice of managing the lifecycle and optimization of physical assets to meet the needs and goals of an organization. Asset management involves the balancing of costs, opportunities and risks against the desired performance of assets to achieve an organization’s objectives. The other options are not the focus of asset management.

https://docs.servicenow.com/bundle/utah-it-asset-management/page/product/hardware-asset-management/reference/audit-results.html

 According to the ServiceNow Hardware Asset Management documentation, assets can be moved between stockrooms by using transfer orders. A transfer order is a record that tracks the movement of assets from one stockroom to another. A transfer order can be created manually by the stock manager or automatically by the system based on predefined rules or workflows1. A transfer order contains information such as the source and destination stockrooms, the assets to be transferred, the shipment details, and the status of the transfer2.

The other options are not correct because:

Stock orders are records that track the procurement of assets from vendors, not the movement of assets between stockrooms3.

Stock rules are rules that define the minimum and maximum stock levels for each asset model in a stockroom, not the movement of assets between stockrooms.

Transfer rules are rules that define the conditions and actions for creating transfer orders automatically, not the records that track the movement of assets between stockrooms.

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

Contract Management notifications are sent to contract administrators to remind them of contract expiration dates so they can renew or renegotiate the contract1.

The expire date is the most important contract date to be aware of because it indicates when the contract is no longer valid and the service or product is no longer covered2.

If a contract expires without renewal or extension, it can result in penalties, service downtime, or loss of warranty or maintenance3.

Therefore, the expire date is the most critical date for contract management and should be monitored closely. References:

1: Product Documentation | ServiceNow

2: Contract and renewal management - ServiceNow

3: Hardware Asset Management overview - ServiceNow - Now Support

4: Use a hardware asset request flow - ServiceNow

According to the Hardware Asset Management documentation, the Hardware Model Normalization Content Service is a cloud-based service that provides normalized and enriched hardware model data to the ServiceNow platform, such as manufacturer name, model name, model number, and product lifecycle information.

The Hardware Model Normalization Content Service helps customers identify and manage their hardware models more effectively, as well as plan for hardware refreshes based on end-of-life (EOL) and end-of-service (EOS) dates1.

The Hardware Model Normalization Content Service updates the content library weekly with new and updated model data1.

To determine if the content has been downloaded, you can review the Hardware Model Content Service Download section on the Model Management tab of the Hardware Asset dashboard1.

The Hardware Model Content Service Download section shows the status of the content download, such as the last download date, the number of models downloaded, and the number of models normalized1.

Therefore, the correct answer is option C, review the Hardware Model Content Service Download section on the Model Management tab of the Hardware Asset dashboard, as it is the way to determine if the content has been downloaded. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

According to the ServiceNow Hardware Asset Management overview document1, contracts are records that define the terms and conditions for the acquisition, maintenance, or disposal of assets1. They can include information such as vendor, start date, end date, cost, and renewal options1.

According to the ServiceNow Data Sheet on Contract and Renewal Management2, some of the critical information that should be tracked for contracts are2:

What each contract costs: This information helps users to monitor and optimize the total cost of ownership (TCO) of their assets, as well as to plan and budget for future contract renewals or negotiations2.

What assets each contract covers: This information helps users to identify and manage the assets that are under contract, such as software licenses, hardware devices, or enterprise assets2. It also helps users to align their asset investments to their business outcomes and avoid penalties or service disruptions2.

The other options are not critical information that should be tracked for contracts. Who purchased the assets and what needs to be cancelled are not relevant to the contract management process, as they do not affect the contract terms, conditions, or performance2.

According to the Hardware Model Normalization document, normalization status is the level of normalization match based on the characteristics of the hardware model data in the ServiceNow platform and the Content Library, which is a cloud-based service that provides normalized and enriched hardware model data.

The normalization status shows how well the hardware model data matches the Content Library data, and it can be one of the following1:

Fully Normalized: The hardware model data matches the Content Library data completely, indicating a complete and accurate model record.

Partially Normalized: The hardware model data partially matches the Content Library data, indicating a missing or incorrect model field.

Match Not Found: The hardware model data does not match any of the Content Library data, indicating a discrepancy or a gap in the model normalization process.

Not Normalized: The hardware model data has not been compared with the Content Library data yet, indicating a pending or incomplete model normalization process.

The characteristics that are used to determine the normalization status are the following1:

Model name: The name of the hardware product, such as Dell Latitude E7450 or HP ProLiant DL380 Gen10.

Model number: The unique identifier of the hardware product, such as 210-AFZC or 875671-B21.

Manufacturer: The name of the company that produces the hardware product, such as Dell or HP.

Therefore, the correct answers are options A, C, and E, as they are the characteristics that are used to determine the normalization status. References:

Hardware Model Normalization

What is Hardware Asset Management?

Managing the Hardware Asset Management (HAM) Content Service involves enabling the service explicitly (opting in). Organizations can choose to enable it for receiving updates about normalized hardware models and lifecycle information. If the service is not needed anymore, it allows opting out at any time, providing flexibility for organizations.

According to the Hardware Asset Management documentation, the hardware model normalization process is a process of comparing the model data in the ServiceNow platform with the data from the Content Library, which is a cloud-based service that provides normalized and enriched hardware model data.

The Content Library automatically populates your inventory with non-discoverable asset metadata, which are the data that cannot be obtained from discovery tools or manual entry, such as manufacturer name, model name, model number, and product lifecycle information1.

The product lifecycle information includes the manufacturer lifecycle dates, which are the dates when the manufacturer stops selling, supporting, or servicing a hardware product1.

The manufacturer lifecycle dates are important for hardware asset management, as they help customers plan for hardware refreshes based on end-of-life (EOL) and end-of-service (EOS) dates2.

Therefore, the correct answer is option C, manufacturer lifecycle dates, as they are the non-discoverable asset metadata that the Content Library automatically populates your inventory with as part of the hardware model normalization process. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

The Expected Assets list is populated when the asset manager starts the audit by clicking the Scan button on the asset audit form1.

This list shows the assets that are expected to be found in the audit location based on the asset records in the CMDB1.

The asset manager can then use a barcode scanner or a mobile device to scan the actual assets in the location and compare them with the expected assets1.

The asset manager can also manually add or remove assets from the expected assets list if needed1. References:

1: Hardware Asset Inventory Audit