ServiceNow CIS-HAM Certified Implementation Specialist - Hardware Asset Management Exam Practice Test

A consumable is a type of asset that is used up or depleted over time, such as printer cartridges, paper, or batteries1.

Before a consumable can be consumed, it must have a model record, a model category record, and a consumable record in ServiceNow12.

A model record defines the attributes of a consumable, such as its name, manufacturer, cost, and quantity12.

A model category record specifies the type of consumable, such as office supplies, hardware, or software12.

A consumable record tracks the current stock level, location, and status of a consumable12.

A stock order record is used to request new consumables from a vendor or supplier, but it is not required before a consumable can be consumed13.

A transfer order record is used to move consumables from one location to another, but it is not required before a consumable can be consumed14. References: 1: Consumables - Product Documentation: Vancouver - ServiceNow 2: Create a consumable model - Product Documentation: Vancouver - ServiceNow 3: Create a stock order - Product Documentation: Vancouver - ServiceNow 4: Create a transfer order - Product Documentation: Vancouver - ServiceNow

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 Service Catalog provides a user-friendly interface for requesting hardware assets and services from the IT department1

The Service Catalog facilitates the ability to source from existing stock by allowing users to select from a list of available hardware products that are in stock or reserved in a stockroom2

The Service Catalog also enables users to view the status of their requests, track the delivery and return of assets, and report any issues or incidents related to assets1

The Service Catalog is integrated with the Procurement Catalog, which contains the list of hardware products that are currently on order or have been received from vendors3

The Service Catalog is also linked to the Product Catalog, which contains the list of hardware products that are available for purchase from vendors or internal sources4

The Vendor Catalog contains the list of vendors that supply hardware products, but it does not facilitate the ability to source from existing stock

Inventory audits are the processes of verifying the accuracy and consistency of the hardware asset inventory across the enterprise1.

The Hardware Asset Management (HAM) application supports the following types of inventory audits1:

Stockroom audit: This is an audit that verifies the quantity and condition of the hardware assets in a stockroom. A stockroom is a physical location where hardware assets are stored before they are delivered to the end users or transferred to another stockroom2. A stockroom audit helps to optimize the inventory levels, avoid overstocking or understocking, and identify any discrepancies or issues with the stockroom assets1.

Location audit: This is an audit that verifies the presence and status of the hardware assets in a specific location, such as an office, a building, or a floor. A location audit helps to ensure that the hardware assets are assigned to the correct owners, locations, and departments, and to identify any missing, unknown, or unauthorized assets1.

Therefore, the types of inventory audits that are also options in the question are A. Stockroom audit and C. Location audit.

The other options that are not types of inventory audits supported by the HAM application are:

Vendor audit: This is not a type of inventory audit, but a type of vendor management activity. Vendor management is the process of managing the relationships and contracts with the vendors that provide hardware assets and services to the organization3. Vendor audit is an activity that evaluates the performance, quality, and compliance of the vendor based on predefined criteria and metrics3.

Discovery audit: This is not a type of inventory audit, but a type of configuration management activity. Configuration management is the process of maintaining the accuracy and consistency of the operational and relationship information of IT assets and services in the Configuration Management Database (CMDB)4. Discovery audit is an activity that compares the actual configuration items (CIs) in the IT environment with the expected CIs in the CMDB and identifies any differences or discrepancies4. References:

1: Hardware Asset Inventory Audit

2: Stockrooms

3: Vendor Management

4: Configuration Management

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.

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

The total cost of ownership (TCO) is a financial estimate that measures the direct and indirect costs of owning and operating an asset over its entire lifecycle. The TCO includes the following components:

Original cost: This is the initial purchase price of the asset, which may include taxes, fees, shipping, and installation costs. The original cost is also known as the acquisition cost or the capital expense.

Operational expense: This is the ongoing cost of maintaining and using the asset throughout its lifecycle, which may include repair, upgrade, maintenance, support, energy, consumables, and disposal costs. The operational expense is also known as the operating expense or the opex.

Depreciation expense: This is the reduction in the value of the asset over time due to wear and tear, obsolescence, or market changes. The depreciation expense is also known as the depreciation cost or the depreciation charge.

Delivery cost: This is the cost of transporting the asset from the supplier to the buyer, which may include freight, insurance, customs, and handling fees. The delivery cost is also known as the shipping cost or the transportation cost.

The TCO can be calculated by adding the original cost, the operational expense, and the depreciation expense, and subtracting the delivery cost. Alternatively, the TCO can be calculated by multiplying the annual cost of ownership by the expected lifespan of the asset.

According to the Hardware Asset Management documentation, the hardware model normalization process is a process of comparing the model data in the ServiceNow platform with the data from the Content Library, which is a cloud-based service that provides normalized and enriched hardware model data.

The hardware model normalization process helps customers identify and manage their hardware models more effectively, as well as plan for hardware refreshes based on end-of-life (EOL) and end-of-service (EOS) dates1.

The hardware model normalization process assigns a status to each hardware model, such as Fully Normalized, Partially Normalized, Match Not Found, or Not Normalized1.

The status of Fully Normalized means that the hardware model data in the ServiceNow platform matches the data from the Content Library, indicating a complete and accurate model record1.

The status of Partially Normalized means that the hardware model data in the ServiceNow platform partially matches the data from the Content Library, indicating a missing or incorrect model field1.

In order for a hardware model to be fully normalized rather than partially normalized, the hardware model record must have the following fields populated correctly1:

Manufacturer: The name of the company that produces the hardware product.

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.

Therefore, the correct answer is option E, model number, as it is the field that is required in the hardware model record for full normalization.

The ServiceNow asset lifecycle defines and describes the series of stages involved in managing an IT asset throughout its useful life1.

The asset lifecycle usually follows a formalized process and is often tracked and supported by software tools1.

Although different organizations in different industries may have their own versions of the asset lifecycle, most follow the same basic format1.

Here, we explore the six stages of the asset lifecycle: Request, Fulfill, Deploy, Monitor, Service, and Retire1.

Out of these six stages, three are also components of the asset lifecycle: Order, Install, and Receive2.

Order: This is the stage where an asset is purchased or acquired from a vendor or supplier. The order stage involves creating purchase orders, tracking shipments, and updating the asset records2.

Install: This is the stage where an asset is physically installed or configured in a location. The install stage involves scanning asset tags, updating asset status, and assigning asset owners2.

Receive: This is the stage where an asset is received and verified by the organization. The receive stage involves checking the asset condition, validating the asset information, and updating the asset inventory2. References:

1: What is the IT Asset Lifecycle? - ServiceNow

2: ITAM Lifecycle Management: How does it all work?

Normalization mappings are a feature of the Hardware Asset Management (HAM) application that allow you to standardize the manufacturer name, model name, and model number of hardware assets in the Configuration Management Database (CMDB)1.

Normalization mappings are created by matching the values from the discovery source to the values in the Product Catalog2.

Normalization mappings help you to fully normalize hardware models by ensuring that the asset data is consistent, accurate, and complete3. References:

Hardware Normalization

Create normalization mappings

What is Hardware Asset Management?

A component is considered an IT asset when you want to perform hardware asset management (HAM) activities on it1.

HAM is a subset of IT asset management (ITAM) that focuses on the physical components of IT systems2.

HAM helps you to manage the entire lifecycle of your hardware assets, from planning and acquisition to retirement and disposal1.

Some of the HAM activities that require a component to be an IT asset are:

Manage its procurement: This involves creating and fulfilling asset requests, purchase orders, and stock order tasks for the component1.

Track its incurred costs: This involves tracking the financial information of the component, such as cost, depreciation, budget, and chargeback1.

Manage its maintenance contracts: This involves managing the vendor, warranty, and contract details of the component, as well as the return merchandise authorization (RMA) processes for products to be returned, replaced, or repaired1.

Therefore, the options that are also HAM activities are A. Manage its procurement, D. Track its incurred costs, and E. Manage its maintenance contracts.

The other options that are not HAM activities are:

Know its relationships to a business service: This involves mapping the component to other components and services in the configuration management database (CMDB)2. This is a configuration management (CM) activity, not a HAM activity.

Track its operational information: This involves tracking the current status, location, owner, and other attributes of the component that reflect its operational state2. This is also a CM activity, not a HAM activity. References:

1: Hardware Asset Management

2: What is Hardware Asset Management?

According to the ServiceNow Hardware Asset Management overview document1, the total cost of ownership (TCO) of an asset is the sum of all direct and indirect costs incurred throughout its lifecycle, from acquisition to disposal1.

The original costs are the costs involved in purchasing an asset and putting it into use, such as lease, delivery, and spare parts12.

Lease is the cost of renting or leasing an asset from a vendor or a third party for a fixed period of time12. Lease costs can vary depending on the terms and conditions of the contract, such as duration, frequency, and interest rate2.

Delivery is the cost of transporting or shipping an asset from the vendor or the warehouse to the end user or the location where it will be used12. Delivery costs can include fees, taxes, customs, and insurance2.

Spare parts are the cost of purchasing or stocking additional or replacement parts for an asset in case of failure, damage, or wear and tear12. Spare parts costs can depend on the availability, quality, and compatibility of the parts2.

The other options are not original costs, but rather ongoing or disposal costs. Maintenance is the cost of repairing, servicing, or upgrading an asset to keep it in good working condition12. Storage is the cost of storing an asset that is not in use or waiting for disposal12.

The Hardware Asset dashboard is a collection of data visualizations that show key metrics on your hardware and consumable models and assets for the entire asset life cycle1.

The tabs in the Hardware Asset dashboard are updated in real time, meaning that they reflect the latest data from the Hardware Asset Management application2.

The tabs in the Hardware Asset dashboard are not based on scheduled jobs, hourly intervals, or 15-minute intervals, as these options would not provide the most accurate and up-to-date information on your hardware assets. References: 1: Hardware Asset dashboard - Product Documentation: San Diego - ServiceNow 2: Hardware Asset Management overview - ServiceNow - Now Support

Contract Management notifications are sent to contract administrators to remind them of contract expiration dates so they can renew or renegotiate the contract1.

The expire date is the most important contract date to be aware of because it indicates when the contract is no longer valid and the service or product is no longer covered2.

If a contract expires without renewal or extension, it can result in penalties, service downtime, or loss of warranty or maintenance3.

Therefore, the expire date is the most critical date for contract management and should be monitored closely. References:

1: Product Documentation | ServiceNow

2: Contract and renewal management - ServiceNow

3: Hardware Asset Management overview - ServiceNow - Now Support

4: Use a hardware asset request flow - ServiceNow

According to the Hardware Asset Management documentation, residual value is the estimated value of an asset at the end of its useful life.

Residual value is calculated by subtracting the depreciation from the cost of the asset, as stated in the Hardware Asset Management documentation: “Residual value = Cost - Depreciation”.

Depreciation is the amount of value that an asset loses over time due to wear and tear, obsolescence, or other factors.

Therefore, the correct answer is option C, subtract the depreciation from the cost of the asset. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

 Hardware Model Normalization is a feature that enables users to standardize the data of hardware and consumable models, such as manufacturer, product, model, and device type. Hardware Model Normalization requires the activation of the Hardware Model Normalization (com.sn_hwnorm) plugin, which also activates the Normalization Data Services Client (com.glide.data_services_canonicalization.client) plugin. These plugins install several tables that store the normalized data and the rules for normalization. The tables that are installed with Hardware Model Normalization are:

Device Type: This table contains the device types that are used to categorize the hardware models, such as laptop, desktop, server, printer, etc.

Hardware Manufacturer: This table contains the normalized names of the hardware manufacturers, such as Dell, HP, Lenovo, etc.

Hardware Model Library: This table contains the normalized data of the hardware models, such as manufacturer, product, model, device type, UNSPSC code, etc. This table is populated by the Hardware Model Normalization Content Service, which is a subscription-based service that provides the latest and most accurate data for hardware models.

Hardware Normalize Key: This table contains the rules for generating the normalize key, which is a unique identifier for each hardware model based on its manufacturer, product, and model. The normalize key is used to match the hardware models with the Hardware Model Library data.

The other options, C. Hardware Normalize Key and E. Device Name, are not tables that are installed with Hardware Model Normalization. Hardware Normalize Key is a field in the Hardware Model [cmdb_model] table, not a separate table. Device Name is a field in the Configuration Item [cmdb_ci] table, not a separate table. References: Hardware Model Normalization, Demo - HAM Professional - Hardware Model Normalization, 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

Consumables are hardware assets that are not tracked individually, but as a quantity of items in a stockroom, such as keyboards, mice, cables, etc.1

When a stock manager receives a new delivery of consumables, they can use the Mobile Asset Receiving feature to scan the barcode of the purchase order and receive multiple assets against it using a mobile device2

If the received consumables match another record in the stockroom based on the following fields: Assigned to, Model, Model category, State, Stockroom, and Substate, then the data is automatically merged to create a blended quantity and cost3

This means that the system calculates the average cost per item and the total quantity of the consumables in the stockroom, and updates the existing record accordingly3

This feature helps to reduce duplicate records and simplify inventory management of consumables3

The plugin that helps alleviate inconsistencies in company names is the Normalization Data Services plugin, which is part of the ServiceNow IT Asset Management suite1.

The Normalization Data Services plugin provides a set of features and capabilities that enable you to standardize and normalize data across various tables and fields in ServiceNow, such as manufacturer names, model names, software names, and company names12.

The Normalization Data Services plugin uses a combination of rules, dictionaries, and algorithms to identify and correct data inconsistencies, such as spelling errors, abbreviations, synonyms, and duplicates12.

The Normalization Data Services plugin can help you improve the quality and accuracy of your data, reduce manual efforts and errors, and enhance reporting and analysis12. References:

1: Normalization Data Services - Product Documentation: San Diego - ServiceNow

2: Normalization Data Services - ServiceNow

According to the ServiceNow Hardware Asset Management documentation, the ServiceNow Content Service is a cloud-based service that provides content updates for hardware models, such as manufacturer, model category, and lifecycle information. The ServiceNow Content Service also collects unrecognized data from customers, such as new or custom hardware models, to improve the content quality and coverage. Customers can opt out of sending unrecognized data to the ServiceNow Content Service for specific models, but this will also prevent them from receiving content updates for those models.

According to the ServiceNow Hardware Asset Management documentation, an asset is defined as "any tangible, physical company technology asset, including those currently in use, those in storage, and support equipment"1. Throughout the life of an asset, the following data are tracked2:

Financial data: This includes the cost, depreciation, and value of the asset, as well as the budget and expenses related to the asset. Financial data helps to optimize the return on investment (ROI) and total cost of ownership (TCO) of the asset.

Contractual data: This includes the terms and conditions, warranties, service level agreements (SLAs), and renewals of the contracts associated with the asset. Contractual data helps to manage the vendor relationships and compliance obligations of the asset.

Lifecycle data: This includes the status, location, ownership, and history of the asset, as well as the events and actions that occur during the asset lifecycle. Lifecycle data helps to monitor the performance and utilization of the asset and plan for its retirement or replacement.

The other options, configuration data and hardware data, are not tracked throughout the life of an asset, but rather at specific stages or levels. Configuration data is the information about the technical attributes and relationships of the asset, which is stored in the configuration management database (CMDB) and managed by the configuration management process3. Hardware data is the information about the physical characteristics and specifications of the asset, such as manufacturer, model, serial number, and barcode4. References:

ServiceNow Hardware Asset Management: Hardware Asset Management overview

ServiceNow Hardware Asset Management: What is the IT Asset Lifecycle?

ServiceNow Hardware Asset Management: Asset and CI management

ServiceNow Hardware Asset Management: Hardware Normalization

The capability blueprint is a framework that helps organizations assess their current and desired state of hardware asset management maturity.

The capability blueprint consists of five tiers, each representing a different level of capability and value.

The five tiers are:

Trustworthy data: The foundation of hardware asset management, ensuring data accuracy, completeness, and consistency.

Practical management: The basic level of hardware asset management, enabling visibility, control, and compliance of hardware assets.

Operational integration: The intermediate level of hardware asset management, enhancing efficiency, effectiveness, and collaboration of hardware asset processes.

Strategic conformance: The advanced level of hardware asset management, achieving best-in-class performance, optimization, and alignment of hardware assets with business goals.

Business transformation: The ultimate level of hardware asset management, enabling innovation, agility, and competitive advantage through hardware asset management.

The tier that focuses on achieving best-in-class is the strategic conformance tier, which aims to optimize the cost, quality, and value of hardware assets, as well as align them with the business strategy and objectives. References:

Hardware Asset Management Capability Blueprint

Hardware Asset Management Maturity Model

According to the ServiceNow documentation, an asset is "any tangible or intangible item that might have value for an organization"1.

The default asset classes in ServiceNow are Hardware, Software License, Consumable, Bundle, Software Entitlement, and Facility1.

These general classes can be used to manage various assets, such as computers, printers, software licenses, office supplies, software subscriptions, and buildings1.

Therefore, facilities, hardware, and software entitlements are considered assets, while contracts and software distributions are not. References:

Asset and configuration item (CI) management - ServiceNow

 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]

The Asset Operations view consolidates tasks such as RMAs, audits, disposals, and stock orders into a single workspace, enabling managers to streamline operations efficiently.

The ServiceNow Mobile App is a native app that enables users to access various ServiceNow features and functions from their mobile devices12.

One of the features of the ServiceNow Mobile App is to provide end users visibility to their assigned hardware. This means that end users can view and report issues around their assets, such as laptops, tablets, or phones, from the app34.

Another feature of the ServiceNow Mobile App is to enable end users to log incidents for their assigned assets. This means that end users can create and update incidents related to their assets, such as hardware failures, software errors, or network problems, from the app34.

The other options are not features of the ServiceNow Mobile App. The app does not enable reclamation of mobile devices, which is a process of recovering and reusing devices that are no longer needed or used. The app also does not provide users visibility to their disposed consumables, which are items that are used up or depleted over time, such as toner cartridges, batteries, or paper.

The lifecycle management tab provides details about the normalization status, models nearing end of life, and lease end timelines. Expenditure by vendor and pending purchase orders are unrelated to lifecycle tracking and would typically be found in financial reports or procurement dashboards.

Stock rules are a feature of ServiceNow Hardware Asset Management that allow you to automate the replenishment of stock levels in your stockrooms1.

Stock rules define the minimum and maximum quantities of a specific model that you want to keep in a stockroom, as well as the reorder point and quantity1.

When the stock level of a model falls below the reorder point, a stock order is automatically generated to replenish the stockroom to the maximum quantity1.

You can create and manage stock rules by navigating to Hardware Asset Management > Model Management > Stock Rules1. References:

1: Stock rules - ServiceNow Docs.

Stock rules are rules that define the minimum and maximum quantities of assets that should be maintained in a stockroom1.

Automatic restocking actions are actions that trigger the creation of stock orders when the quantity of an asset falls below the minimum threshold or exceeds the maximum threshold1.

A daily scheduled job runs every day to check the stock levels of assets and execute the automatic restocking actions based on the stock rules1.

The plugin that must be activated in order to configure and use the scheduled job is the Procurement plugin2.

The Procurement plugin enables the procurement of assets and consumables through purchase orders, stock orders, and vendor management2.

The Procurement plugin also provides the Stock Order [Order] table, which stores the stock orders created by the automatic restocking actions2.

According to the ServiceNow Product Documentation on Stock Rules1, stock rules are records that define the conditions and actions for replenishing the stock of assets in a stockroom when they drop below a specified threshold1.

According to the ServiceNow GlideFast blog post on Stock Rules in ServiceNow2, when creating a stock rule that replenishes from a vendor, the primary requirement for the warehouse stockroom is that it must have an assigned manager and the manager must have a valid email address2.

The reason for this requirement is that the stock rule will generate a purchase order for the procurement of additional assets from the vendor, and the purchase order will be sent to the stockroom manager’s email address for approval2.

The other options are not primary requirements for the warehouse stockroom when creating a stock rule that replenishes from a vendor. The stockroom does not need to have an assignment group, a valid mobile phone, or a valid time zone for the stock rule to work.

Fixed assets in ServiceNow are classified as long-term assets that are used in operations and have a useful life exceeding one year, such as equipment, buildings, and vehicles. They are distinct from intangible and short-term assets.

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.

Create transform map: A transform map is a set of field mappings that determine how the source data in the import set table is transformed into the target data in the hardware asset table. You can create a transform map by using the Load Data UI page, or by navigating to System Import Sets > Create Transform Map. You need to specify the source table, the target table, and the field mappings between them. You can also define coalesce fields, which are used to prevent duplicate records from being created or updated. For example, you can use the asset tag or the serial number as a coalesce field.

Load data: To load data into the import set table, you need to select a data source, such as a file, a JDBC data source, or a web service. You can use the Load Data UI page, or navigate to System Import Sets > Load Data. You need to specify the source type, the file name or the connection URL, the sheet number and the header row (if using a file), and the import set table name. You can also preview the data before loading it into the table.

Run transform map: To run the transform map, you need to navigate to System Import Sets > Transform Maps, and select the transform map that you created. You can then click on the Run Transform button, which will execute the field mappings and transform the data from the import set table to the hardware asset table. You can also view the transformation history, the transformation statistics, and the transformation log to monitor the progress and the results of the transformation.

A model category is a classification of models that defines how they are managed in the system1. It determines the behavior and attributes of the models and the assets or configuration items (Cls) that are created from them1.

Model categories can be used to group consumables, assets, or services in the product catalog or the service catalog, but this is not their primary function. Their primary function is to define the relationship between configuration management and asset management1.

Configuration management is the process of identifying, tracking, and verifying the configuration items (Cls) in an IT environment and their relationships2. Asset management is the process of tracking and managing the financial, contractual, and inventory details of IT assets throughout their lifecycle3.

Model categories determine when to create assets from configuration items (Cls) based on the asset tracking strategy1. For example, some model categories, such as Computer, create assets automatically when Cls are discovered or imported1. Other model categories, such as Consumable, require manual creation of assets from the product catalog1.

Model categories also provide the link between configuration management and asset management by allowing asset managers to view the configuration data of the assets and configuration managers to view the asset data of the Cls1. This enables better visibility, control, and alignment of IT assets and services1.

To utilize the contract rate cards features, you need to activate the Rate Management plugin, which provides the ability to define and manage rates for various types of costs and expenses1.

The contract rate cards features allow you to capture operating costs by generating expense lines representing the cost of a contract. You can associate a contract to certain assets and costs of those assets are tied to the contract. This is similar to a rate card cost, except the contract contains all the costs2.

The other plugins are not required to use the contract rate cards features. The Financial Management plugin provides the ability to track and manage the financial performance of your IT services3. The Contract Management plugin provides the ability to create and manage contracts for assets, services, and vendors4. The Cost Management plugin provides the ability to track and allocate costs for configuration items, tasks, and projects5. References: 1: Rate Management 2: Cost Management — ServiceNow Elite 3: Financial Management 4: Contract Management 5: Cost Management

According to the ServiceNow Hardware Asset Management documentation, advanced risk assessment is a process of identifying, analyzing, and evaluating the risks associated with hardware assets and configuration items (CIs) in the configuration management database (CMDB)1. Advanced risk assessment uses the Advanced Risk Assessment engine, which is built to address risk through an integrated risk framework2. The advanced risk assessment process consists of the following steps1:

Create a risk assessment scope: This step defines the scope and criteria of the data to be assessed, such as the asset class, category, or attribute. The risk assessment scope also specifies the frequency and duration of the assessment.

Create a risk assessment schedule: This step determines when and how often the assessment runs, based on the risk assessment scope. The risk assessment schedule also defines the assessment owner, who is responsible for overseeing the assessment process and approving the results.

Assign the assessment tasks: This step assigns the assessment tasks to the appropriate assessors, who are the users or groups who have the knowledge and authority to evaluate and update the data. The assessment tasks can be assigned manually or automatically, based on predefined rules or workflows.

Run the assessment: This step executes the assessment process, which involves sending notifications and reminders to the assessors, displaying the data to be assessed in a user-friendly interface, allowing the assessors to review and modify the data, and tracking the progress and status of the assessment tasks.

Review the assessment results: This step allows the assessment owner to verify and approve the results of the assessment, before applying the changes to the CMDB. The assessment owner can also view the risk scores, risk indicators, and risk heat maps of the assessed data.

Handle the risk response: This step involves creating and managing risk response tasks to address the identified risks. Risk response tasks are records that track the actions taken to mitigate, transfer, avoid, or accept the risks. Risk response tasks can be created manually by the assessment owner or automatically by the system based on predefined rules or workflows.

For advanced risk assessment, risk response can be handled in the following ways:

Create multiple risk response tasks: This option allows the assessment owner to create more than one risk response task for each assessed data, depending on the complexity and severity of the risk. For example, the assessment owner can create a mitigation task to reduce the impact or likelihood of the risk, and a transfer task to shift the responsibility or ownership of the risk to another party3.

Create at least one risk response task: This option requires the assessment owner to create at least one risk response task for each assessed data, regardless of the complexity and severity of the risk. This ensures that every risk is addressed and documented in the system3.

The other options are not correct because:

Skipped entirely based on attributes defined in the RAM: This option is not a valid way to handle risk response for advanced risk assessment. The RAM (Risk Assessment Matrix) is a tool that helps to calculate the risk score and risk indicator of the assessed data, based on the impact and likelihood attributes defined in the risk assessment scope1. The RAM does not determine whether to skip the risk response or not.

Must create a mitigation response task: This option is not a mandatory way to handle risk response for advanced risk assessment. A mitigation response task is one of the possible types of risk response tasks, but not the only one. Depending on the risk appetite and strategy of the organization, the assessment owner can choose other types of risk response tasks, such as transfer, avoid, or accept3.