* 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 References: 1: Creating New Transform Maps - ServiceNow 2: [Coalesce - ServiceNow]

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

* 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.
References: 1: Normalization Data Services Client - Product Documentation: Tokyo - ServiceNow 2:
Normalization Data Services - ServiceNow 3: Hardware Model Normalization - Product Documentation:
Tokyo - ServiceNow