CIS-HAM Exam Dumps : Certified Implementation Specialist - Hardware Asset Management

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.

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.

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.