Free Practice Questions for ServiceNow CIS-HAM Exam

Normalization is the process of standardizing the hardware model data by manufacturer name, model name, and model number1.

Normalization helps to maintain a clean and consistent configuration management database (CMDB) and to avoid duplicate or inaccurate hardware models1.

Normalization first runs to normalize the record when you save the hardware model record1.

This means that when you create or edit a hardware model record, the system automatically checks the record against the normalization rules and the Hardware Content Service Lifecycle data, and updates the record with the normalized values if applicable1.

Therefore, the answer that reflects when normalization first runs is C. When you save the hardware model record.

The other options are not the correct answer because they describe different scenarios or actions:

A. When the daily scheduled HAM – Daily job runs: This is not the correct answer, because the daily scheduled HAM – Daily job does not run normalization. The daily scheduled HAM – Daily job is a scheduled job that runs various tasks related to hardware asset management, such as updating the asset status, calculating the depreciation, and sending notifications2.

B. When the weekly scheduled HAM – Normalization job runs: This is not the correct answer, because the weekly scheduled HAM – Normalization job does not run normalization for the first time. The weekly scheduled HAM – Normalization job is a scheduled job that runs normalization for all the existing hardware models in the CMDB on a weekly basis1. It does not affect the newly created or edited hardware models, which are normalized when they are saved1.

D. When you click the Normalize Hardware Model link under Related Links: This is not the correct answer, because clicking the Normalize Hardware Model link under Related Links does not run normalization for the first time. Clicking the Normalize Hardware Model link under Related Links is a manual action that allows you to run normalization for a specific hardware model record at any time1. It does not affect the automatic normalization that runs when you save the hardware model record1. References:

1: Hardware Normalization

2: Daily Scheduled HAM – Daily Job

A configuration item (CI) is a record that represents an IT asset or service in the Configuration Management Database (CMDB)1.

A CI tracks the operational and relationship information of the asset or service, such as its current status, location, owner, and dependencies1.

A hardware asset is a physical component of an IT system, such as a laptop, server, or router2.

A hardware asset attribute is a property or characteristic of the hardware asset, such as its model, serial number, or warranty2.

Some hardware asset attributes are also part of the CI, such as IP address, CPU, operating system, and memory1. These attributes reflect the operational state of the hardware asset and are relevant for configuration management purposes1.

However, some hardware asset attributes are not part of the CI, such as cost2. Cost is a financial information of the hardware asset that is tracked by the Asset Management application2. Cost is not relevant for configuration management purposes and is not stored in the CMDB2.

Therefore, the hardware asset attribute that should be tracked that is not part of the CI is C. Cost. References:

1: Configuration Item

2: Hardware Asset Management

Operational: The current status, performance, availability, and capacity of the CI, as well as any incidents, problems, or changes that affect it.

Relationship: The dependencies and connections between the CI and other CIs, services, processes, and users.

The information that you would track for an asset includes:

Financial: The cost, depreciation, ownership, and warranty of the asset, as well as any procurement or disposal activities.

Lifecycle: The stages and transitions of the asset from request to retirement, as well as any inventory or stock management.

The information that you would not track for a CI versus an asset are:

Contractual: This information is relevant for both CIs and assets, as it relates to the agreements and obligations between the service provider and the customer or vendor.

Lifecycle: This information is relevant for both CIs and assets, as it relates to the stages and transitions of the component from request to retirement.

According to the ServiceNow Hardware Asset Management documentation, an advanced shipment notification (ASN) is a document that provides detailed information about a pending delivery. The purpose of an ASN is to notify the customer when shipping occurs and provide physical characteristics about the shipment so the customer can be prepared to accept delivery. You can use ASNs to automatically create asset records in ServiceNow Hardware Asset Management by importing the data from the ASN document.

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

According to the Hardware Asset Management documentation, an asset audit is a process of verifying the physical existence and location of assets in an organization, such as a stockroom or a warehouse.

The asset audit form shows the details of the audit, such as the name, description, status, start date, end date, and location of the audit1.

The asset audit form also shows the audit results, which are the status of each scanned asset, such as “Scanned and expected”, “Scanned and not expected”, “Expected and not scanned”, or "Not expected and not scanned"1.

The scanned assets are the assets that were found at the stockroom or warehouse that is being audited, regardless of whether they were expected or not1.

The scanned assets are displayed in the Scanned Assets related list on the asset audit form1.

Therefore, the correct answer is option B, scanned assets, as they are the list of all assets that were found at the stockroom or warehouse that is being audited. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

The first tier of the capability blueprint emphasizes building Trustworthy Data. Without accurate and reliable data, further optimization in asset or service management is impossible. It sets the foundation for all other tiers.