According to the ServiceNow Hardware Asset Management documentation, a loaner asset is a temporary asset that is provided to a user for a specific period of time, such as when their primary asset is being repaired or replaced1. Users can request loaner assets from the Service Catalog, where they can select the type, quantity, and duration of the loaner asset they need2. If the requested asset is not available in the local stockroom, the request is wait-listed until the asset becomes available3. Users may request loaner assets even when the requested asset is not available in the local stockroom because the wait-listed loaner asset requests provide visibility to the demand for loaner orders. This visibility helps the asset managers to plan and optimize the loaner asset pool, as well as to identify and address any gaps or bottlenecks in the loaner asset fulfillment process.
The other options are not correct because:
The request does not create an automatic transfer order to move assets from a warehouse with in stock assets. Transfer orders are created manually by the stock manager to move assets between stockrooms.
The wait-listed loaner asset requests do not provide visibility to streamline internal transfer order flows. Transfer order flows are managed by the stock manager using the Transfer Order Management module.
The request does not automatically create a purchase order to obtain the assets from a vendor. Purchase orders are created manually by the procurement manager to order assets from vendors.
Reference:
ServiceNow Hardware Asset Management: Loaner Asset Requests
ServiceNow Hardware Asset Management: Request a loaner asset
ServiceNow Hardware Asset Management: Waitlist a loaner asset request
[ServiceNow Hardware Asset Management: Asset Reservations and Loaner Asset Requests]
[ServiceNow Hardware Asset Management: Transfer orders]
[ServiceNow Hardware Asset Management: Transfer Order Management]
[ServiceNow Hardware Asset Management: Purchase orders]

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. Reference:
1: Hardware Asset Inventory Audit

The End of Life tab of the Hardware Asset dashboard shows key metrics on the hardware assets that have reached or are nearing the end of their life cycle12.
The tab includes the following reports1:
Hardware asset disposal status: This report shows the number of hardware assets that are in different stages of disposal, such as pending, in progress, or completed1.
Hardware assets disposed (YTD): This report shows the number of hardware assets that have been disposed in the current year, grouped by month1.
Hardware assets up for end of life: This report shows the number of hardware assets that are due for end of life in the next 12 months, grouped by month1.
Hardware assets up for end of support: This report shows the number of hardware assets that are due for end of support in the next 12 months, grouped by month1.
Therefore, the correct answer is A. Hardware asset disposal status and C. Hardware assets disposed (YTD), as these are the only two reports that are shown on the End of Life tab of the Hardware Asset dashboard.

Operational expenses are the costs incurred by an organization to maintain and use an asset throughout its lifecycle. These costs include the expenses related to the repair, maintenance, upgrade, and disposal of the asset. Some examples of operational expenses are:
Replacement parts: These are the costs of purchasing and installing new parts or components for an asset that is damaged, worn out, or obsolete. For example, replacing a hard drive, a battery, or a keyboard for a laptop.
Maintenance agreements: These are the costs of contracting with a vendor or a service provider to perform regular or preventive maintenance on an asset. For example, paying a monthly fee for a technician to check and service a printer or a scanner.
Other examples of operational expenses are:
Storage costs: These are the costs of renting or owning a space to store an asset that is not in use or awaiting disposal. For example, paying for a warehouse, a locker, or a shelf to keep unused or surplus computers or monitors.
Warranty costs: These are the costs of extending or renewing the warranty coverage for an asset that is still under the manufacturer's warranty or has expired. For example, paying an extra fee for a one-year or a three-year warranty extension for a tablet or a smartphone.
Reference:
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 Management, which gives an overview of the benefits and features of the Hardware Asset Management solution, such as reducing costs, improving compliance, optimizing asset utilization, and enhancing service delivery.
Hardware Asset Management - ServiceNow, which provides a data sheet with the key capabilities and benefits of the Hardware Asset Management application.

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. Reference: Hardware Model Normalization, Demo - HAM Professional - Hardware Model Normalization, Hardware Asset Management