CIS-Hardware Asset Management CIS-HAM Exam Dumps

According to the Hardware Model Normalization document, normalization status is the level of normalization match based on the characteristics of the hardware model data in the ServiceNow platform and the Content Library, which is a cloud-based service that provides normalized and enriched hardware model data.

The normalization status shows how well the hardware model data matches the Content Library data, and it can be one of the following1:

Fully Normalized: The hardware model data matches the Content Library data completely, indicating a complete and accurate model record.

Partially Normalized: The hardware model data partially matches the Content Library data, indicating a missing or incorrect model field.

Match Not Found: The hardware model data does not match any of the Content Library data, indicating a discrepancy or a gap in the model normalization process.

Not Normalized: The hardware model data has not been compared with the Content Library data yet, indicating a pending or incomplete model normalization process.

The characteristics that are used to determine the normalization status are the following1:

Model name: The name of the hardware product, such as Dell Latitude E7450 or HP ProLiant DL380 Gen10.

Model number: The unique identifier of the hardware product, such as 210-AFZC or 875671-B21.

Manufacturer: The name of the company that produces the hardware product, such as Dell or HP.

Therefore, the correct answers are options A, C, and E, as they are the characteristics that are used to determine the normalization status. References:

Hardware Model Normalization

What is Hardware Asset Management?

According to the ServiceNow Hardware Asset Management documentation, a configuration item (CI) is an entity or thing that you wish to track that is required for the delivery of a service. A CI can be a hardware asset, a software asset, a service, a document, or any other component that is part of the IT infrastructure1. A CI is different from an IT asset in that a CI focuses on the technical attributes and relationships of the component, while an IT asset focuses on the financial and contractual aspects of the component2. Therefore, a component is considered a CI as opposed to an IT asset when you want to track its relationship information, such as its dependencies, impacts, and interactions with other CIs. Relationship information helps to manage the configuration and performance of the IT services and to identify and resolve incidents and problems3.

The other options are not correct because:

Track its incurred costs: This is a function of an IT asset, not a CI. An IT asset tracks the cost, depreciation, and value of the component, as well as the budget and expenses related to the component2.

Manage its retirement: This is also a function of an IT asset, not a CI. An IT asset tracks the status, location, ownership, and history of the component, as well as the events and actions that occur during the asset lifecycle, including its retirement or replacement2.

Manage its license contracts: This is another function of an IT asset, not a CI. An IT asset tracks the terms and conditions, warranties, service level agreements (SLAs), and renewals of the contracts associated with the component. Contract management helps to manage the vendor relationships and compliance obligations of the component2.

Know who is using it: This is not a specific function of either an IT asset or a CI, but rather a common attribute that can be shared by both. Both an IT asset and a CI can have a user or owner field that indicates who is using or responsible for the component4.

To exclude certain types of CIs from the CI lists on the Incident, Problem, and Change forms, you can use the Principal CI class checkbox, which is available on the Class Manager module under Configuration1.

The Principal CI class checkbox allows you to specify which CI classes are considered as principal CIs, meaning they are the most relevant and important CIs for the business services and processes1. By default, only the CI classes that have this checkbox selected are displayed on the CI lists on the Incident, Problem, and Change forms2.

To use this feature, you need to navigate to the Class Manager module, select the CI class that you want to exclude or include, and check or uncheck the Principal CI class checkbox accordingly1. You can also use the Filter option to search for the CI classes by name or label1.

The other options are not recommended or valid ways to exclude certain types of CIs from the CI lists. Adding a Show field to the base cmdb table would require modifying the table schema and creating a reference qualifier, which could affect the performance and integrity of the CMDB3. Creating an Access control to hide the unnecessary CIs from the itil users would require defining the conditions and roles for the access rule, which could be complex and error-prone4. Making a show/hide UI action to show only the desired CIs to the itil users would require creating a custom script and UI element, which could be incompatible with the existing UI and functionality. References: 1: Principal configuration item classes 2: Configuration item lists 3: CMDB table schema 4: Access control rules : [UI actions]