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

The retirement of an IT asset is the final stage of the hardware asset lifecycle, where the asset is removed from service and disposed of in a secure and compliant manner1.

The retirement of an IT asset should be done according to the company-defined policies and procedures, which may vary depending on the type, condition, and value of the asset, as well as the business needs and regulatory requirements1.

The company-defined policies and procedures should specify the criteria, process, and documentation for retiring an IT asset, such as the following1:

The trigger events or conditions that indicate the need for retirement, such as end-of-life, end-of-service, end-of-warranty, obsolescence, damage, theft, or loss

The approval workflow and roles involved in the retirement decision, such as the asset manager, the asset owner, the finance department, and the security department

The disposal methods and vendors available for the retirement, such as recycling, reselling, donating, or destroying

The certificate of destruction or disposal that verifies the secure and compliant disposal of the asset by the vendor

The update of the asset record and the configuration management database (CMDB) to reflect the retirement status and date of the asset

Therefore, the answer that reflects the company-defined policies and procedures is B. At any point that it is recommended by your company-defined policies and procedures.

The other options are not the correct answer because they are either too vague or too specific:

A. At any point it is recommended by the HAM-defined asset policy: This is too vague, as the HAM-defined asset policy may not cover all the aspects and scenarios of the retirement process. The HAM-defined asset policy is a general guideline that defines the objectives, scope, roles, and responsibilities of hardware asset management2. It does not necessarily provide the detailed criteria, process, and documentation for retiring an IT asset.

C. At any point it is recommended by the HAM-defined asset disposal procedure: This is too specific, as the HAM-defined asset disposal procedure is only one part of the retirement process. The HAM-defined asset disposal procedure is a step-by-step instruction that describes how to dispose of an IT asset through a vendor3. It does not necessarily cover the trigger events, approval workflow, and record update for retiring an IT asset.

D. When the Hardware Content Service Lifecycle data reports the asset is nearing end-of-service: This is too specific, as the Hardware Content Service Lifecycle data is only one possible source of information for the retirement decision. The Hardware Content Service Lifecycle data is a subscription-based service that provides the end-of-life, end-of-service, and end-of-support dates for hardware models4. It does not necessarily reflect the actual condition, value, and usage of the individual IT asset.

E. When the Hardware Content Service Lifecycle data reports the asset is nearing end-of-life: This is also too specific, for the same reasons as option D. References:

1: Hardware Asset Retirement

2: Hardware Asset Policy

3: Hardware Asset Disposal

4: Hardware Content Service Lifecycle

The ServiceNow Agent mobile app allows the user to scan and create assets in ServiceNow in various scenarios123.

One scenario is to create a single asset via barcode scan. The user can scan the barcode or QR code of an asset and fill in the required fields to create an asset record in ServiceNow1.

Another scenario is to receive one or multiple assets from a purchase order. The user can scan the barcode or QR code of a purchase order and view the list of assets to be received. The user can then scan the assets and confirm the receipt in ServiceNow1.

The other scenarios, such as creating multiple assets listed on a contract PDF scan or creating a single asset via Name search, are not supported by the ServiceNow Agent mobile app123. References:

ServiceNow Agent app - Product Documentation: San Diego - Now Support Portal

Hardware Asset Inventory Management - ServiceNow

Automation Simplifies Hardware Asset Management - ServiceNow Blog

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

A stock rule is a record that defines the minimum and maximum quantity of a model or an asset in a stockroom12.

The Stock Rule Runner is a scheduled job that runs every hour and checks the stock levels of models and assets in stockrooms against the stock rules13.

If the stock level of a model or an asset is less than the minimum quantity specified in the stock rule, the Stock Rule Runner creates a stock order to replenish the stock from another stockroom or from a vendor13.

Therefore, the correct answer is A. When stock is less than the threshold specified in the stock rule.

 According to the ServiceNow Hardware Asset Management documentation, the Now Agent Mobile App is a mobile application that enables users to perform various asset management tasks on the go, such as creating assets, performing inventory audits, and receiving assets1. The Now Agent Mobile App provides access to the following features2:

Asset Receiving: Users can receive multiple assets against a purchase order using a mobile device. Users can scan barcodes or QR codes to identify assets and update their status and location.

Asset Inventory Audit: Users can manage assets across locations with simplified mobile inventory processes. Users can scan barcodes or QR codes to verify assets and update their information. Users can also view audit results and resolve discrepancies.

Asset Creation: Users can create new assets using a mobile device. Users can scan barcodes or QR codes to populate asset fields and assign them to stockrooms or users.

The other options, Now Procurement App, Now Mobile App, and Now Onboarding App, are not related to hardware asset management. The Now Procurement App is a mobile application that enables users to manage purchase orders, requisitions, and contracts3. The Now Mobile App is a mobile application that enables users to access ServiceNow services and information, such as requesting items, viewing incidents, and checking assigned assets. The Now Onboarding App is a mobile application that enables users to complete onboarding tasks, such as signing documents, enrolling in benefits, and setting up devices. References:

ServiceNow Hardware Asset Management: Now Agent Mobile App

ServiceNow Hardware Asset Management: Mobile Asset Management

ServiceNow Hardware Asset Management: Now Procurement App

[ServiceNow Hardware Asset Management: Now Mobile App]

[ServiceNow Hardware Asset Management: Now Onboarding App]

Delegated Developers are granted access only to scopes in which they are working1. A scope is a set of application files and data that are isolated from other applications on the same instance2.

Scopes allow developers to create and modify applications without affecting the functionality or security of other applications or the platform2.

Delegated Developers can be assigned developer permissions for specific scopes by an application administrator or a system administrator1. These permissions determine what types of files and data they can access and modify within the scope1.

Delegated Developers can also request cross-scope access to access resources from another scope, which must be approved or denied by the owner of the target scope1.

Delegated Developers do not have access to interfaces, APIs, or instances, unless they are explicitly granted by an administrator or a cross-scope request1. References:

1: Delegated Development - Product Documentation: San Diego - ServiceNow

2: Application Scoping - Product Documentation: San Diego - ServiceNow