ServiceNow CIS-HAM Exam With Confidence Using Practice Dumps

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]

The itil role enables the user to perform actions related to incident, problem, change, and configuration management. This role is part of the ITIL framework, which is a set of best practices for delivering IT services. According to the ServiceNow documentation1, the itil role can do the following:

Create and update incidents, problems, and change requests

View configuration items (CIs) and their relationships

Add comments and work notes to tasks

Approve or reject change requests

Close resolved incidents and problems

Reopen closed incidents and problems

The other roles listed in the question have different functions and permissions. For example, the procurement_user role can request and track hardware purchases2, the inventory_admin role can manage stockrooms and transfer orders3, the discovery_admin role can configure and run Discovery to populate the CMDB4, and the asset role can view and edit asset records5.

According to the Hardware Asset Management documentation, a transfer order is a record that tracks the movement of assets from one stockroom to another.

A transfer order line is a record that specifies the quantity and type of assets to be transferred, as well as the source and destination stockrooms1.

When using the HAM application, what happens when you create a new transfer order line on a transfer order is that a transfer order line task is automatically created to move the transfer order line from one stage to another1.

A transfer order line task is a record that tracks the progress of the transfer order line through the following stages1:

Requested: The transfer order line is created and waiting for approval.

Approved: The transfer order line is approved and ready for fulfilment.

Fulfilled: The transfer order line is fulfilled and the assets are shipped from the source stockroom.

Received: The transfer order line is received and the assets are checked in at the destination stockroom.

Closed: The transfer order line is closed and the transfer is complete.

Therefore, the correct answer is option C, a transfer order line task is automatically created to move the transfer order line from one stage to another, as it describes what happens when you create a new transfer order line on a transfer order. References:

Hardware Asset Management documentation

What is Hardware Asset Management?