According to the ServiceNow Hardware Asset Management documentation, an asset is defined as "any tangible, physical company technology asset, including those currently in use, those in storage, and support equipment"1. Throughout the life of an asset, the following data are tracked2:
* Financial data: This includes the cost, depreciation, and value of the asset, as well as the budget and expenses related to the asset. Financial data helps to optimize the return on investment (ROI) and total cost of ownership (TCO) of the asset.
* Contractual data: This includes the terms and conditions, warranties, service level agreements (SLAs), and renewals of the contracts associated with the asset. Contractual data helps to manage the vendor relationships and compliance obligations of the asset.
* Lifecycle data: This includes the status, location, ownership, and history of the asset, as well as the events and actions that occur during the asset lifecycle. Lifecycle data helps to monitor the performance and utilization of the asset and plan for its retirement or replacement.
The other options, configuration data and hardware data, are not tracked throughout the life of an asset, but rather at specific stages or levels. Configuration data is the information about the technical attributes and relationships of the asset, which is stored in the configuration management database (CMDB) and managed by the configuration management process3. Hardware data is the information about the physical characteristics and specifications of the asset, such as manufacturer, model, serial number, and barcode4. References:
* ServiceNow Hardware Asset Management: Hardware Asset Management overview
* ServiceNow Hardware Asset Management: What is the IT Asset Lifecycle?
* ServiceNow Hardware Asset Management: Asset and CI management
* ServiceNow Hardware Asset Management: Hardware Normalization

According to the ServiceNow Hardware Asset Management documentation, advanced risk assessment is a process of identifying, analyzing, and evaluating the risks associated with hardware assets and configuration items (CIs) in the configuration management database (CMDB)1. Advanced risk assessment uses the Advanced Risk Assessment engine, which is built to address risk through an integrated risk framework2. The advanced risk assessment process consists of the following steps1:
* Create a risk assessment scope: This step defines the scope and criteria of the data to be assessed, such as the asset class, category, or attribute. The risk assessment scope also specifies the frequency and duration of the assessment.
* Create a risk assessment schedule: This step determines when and how often the assessment runs, based on the risk assessment scope. The risk assessment schedule also defines the assessment owner, who is responsible for overseeing the assessment process and approving the results.
* Assign the assessment tasks: This step assigns the assessment tasks to the appropriate assessors, who are the users or groups who have the knowledge and authority to evaluate and update the data. The assessment tasks can be assigned manually or automatically, based on predefined rules or workflows.
* Run the assessment: This step executes the assessment process, which involves sending notifications and reminders to the assessors, displaying the data to be assessed in a user-friendly interface, allowing the assessors to review and modify the data, and tracking the progress and status of the assessment tasks.
* Review the assessment results: This step allows the assessment owner to verify and approve the results of the assessment, before applying the changes to the CMDB. The assessment owner can also view the risk scores, risk indicators, and risk heat maps of the assessed data.
* Handle the risk response: This step involves creating and managing risk response tasks to address the identified risks. Risk response tasks are records that track the actions taken to mitigate, transfer, avoid, or accept the risks. Risk response tasks can be created manually by the assessment owner or automatically by the system based on predefined rules or workflows.
For advanced risk assessment, risk response can be handled in the following ways:
* Create multiple risk response tasks: This option allows the assessment owner to create more than one risk response task for each assessed data, depending on the complexity and severity of the risk. For example, the assessment owner can create a mitigation task to reduce the impact or likelihood of the risk, and a transfer task to shift the responsibility or ownership of the risk to another party3.
* Create at least one risk response task: This option requires the assessment owner to create at least one risk response task for each assessed data, regardless of the complexity and severity of the risk. This ensures that every risk is addressed and documented in the system3.
The other options are not correct because:
* Skipped entirely based on attributes defined in the RAM: This option is not a valid way to handle risk response for advanced risk assessment. The RAM (Risk Assessment Matrix) is a tool that helps to calculate the risk score and risk indicator of the assessed data, based on the impact and likelihood attributes defined in the risk assessment scope1. The RAM does not determine whether to skip the risk response or not.
* Must create a mitigation response task: This option is not a mandatory way to handle risk response for advanced risk assessment. A mitigation response task is one of the possible types of risk response tasks, but not the only one. Depending on the risk appetite and strategy of the organization, the assessment owner can choose other types of risk response tasks, such as transfer, avoid, or accept3.
References:
* ServiceNow Hardware Asset Management: Advanced Risk Assessment
* ServiceNow Hardware Asset Management: Risk response tasks
* ServiceNow Hardware Asset Management: ServiceNow Risk Management

Explanation
Create transform map: A transform map is a set of field mappings that determine how the source data in the import set table is transformed into the target data in the hardware asset table. You can create a transform map by using the Load Data UI page, or by navigating to System Import Sets > Create Transform Map. You need to specify the source table, the target table, and the field mappings between them. You can also define coalesce fields, which are used to prevent duplicate records from being created or updated. For example, you can use the asset tag or the serial number as a coalesce field.
Load data: To load data into the import set table, you need to select a data source, such as a file, a JDBC data source, or a web service. You can use the Load Data UI page, or navigate to System Import Sets > Load Data. You need to specify the source type, the file name or the connection URL, the sheet number and the header row (if using a file), and the import set table name. You can also preview the data before loading it into the table.
Run transform map: To run the transform map, you need to navigate to System Import Sets > Transform Maps, and select the transform map that you created. You can then click on the Run Transform button, which will execute the field mappings and transform the data from the import set table to the hardware asset table. You can also view the transformation history, the transformation statistics, and the transformation log to monitor the progress and the results of the transformation.
References:
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.
Hardware Asset Inventory Management, which explains how to streamline inventory stock orders, empower employees with a robust asset catalog, monitor stock depletions, track shipments, scan assets with a mobile device, and plan asset refresh cycles.
Getting Started with ServiceNow Hardware Asset Management, which provides general procedures and forms for performing asset lifecycle management activities in ServiceNow.