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

According to the Hardware Asset Management documentation, non-consumable assets are assets that are not depleted or used up when they are applied or consumed, such as laptops, monitors, or routers.

Non-consumable assets are tracked individually in the ServiceNow platform, and each asset has a unique asset tag and serial number.

When transferring non-consumable assets between stockrooms, they must be transferred as a single entity with a quantity of one, as stated in the Hardware Asset Management documentation: “Non-consumable assets are transferred as a single entity with a quantity of one. For example, a laptop is transferred as a single entity with a quantity of one.”

Therefore, the correct answer is option C, as a single entity with a quantity of one. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

Normalization is the process of restructuring data to maintain consistency, accuracy, and completeness across different sources and systems. Normalization helps to eliminate data duplication, conflicts, and errors, and to ensure that the data conforms to predefined standards and rules. Normalization is especially important for hardware asset management, as it enables users to have a clear and unified view of their hardware models, manufacturers, product names, device types, and other attributes. ServiceNow Hardware Asset Management provides a feature called Hardware Model Normalization, which allows users to normalize the details of their hardware and consumable models using predefined or custom rules, data sources, and schedules. Hardware Model Normalization can be accessed from the Hardware Asset Management application menu in the ServiceNow platform1. References: Hardware Asset Management - ServiceNow, Hardware Asset Management - Product Documentation: Tokyo - ServiceNow, Hardware Asset Management Implement - Customer Success - ServiceNow, Work with hardware normalization - ServiceNow - Now Support, Getting Started with ServiceNow Hardware Asset Management

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]