CIS-HAM Certified Implementation Specialist - Hardware Asset Management Questions and Answers

• 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 Hardware Asset Management page, the three tiers of Lifecycle Management are:
• These three tiers correspond to the options C, D, and E in the question.
• The options A and B are not part of the Lifecycle Management framework, and are not mentioned in the ServiceNow Hardware Asset Management documents. References:
• Hardware Asset Management
• What is Hardware Asset Management?
• Your asset lifecycle: How to manage it all

 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

• Hardware normalization is a process that standardizes the data of hardware and consumable models by using the United Nations Standard Products and Services Code (UNSPSC) and a set of rules12.
• Normalization can be performed manually or automatically on models in the model catalog12.
• If a model has been normalized, it will have a check mark in the Normalized column in the model list1.
• To revert the normalization of a model, you can use the Revert Normalization UI action, which is available on the model form13.
• The Revert Normalization UI action will restore the original values of the model attributes that were changed by the normalization process13.
• The Revert Normalization UI action will also clear the Normalized check mark and the Normalization Source field on the model form13. References: Work with hardware normalization - ServiceNow - Now Support, Hardware Asset Management builds onCore Asset Management - ServiceNow, Automation Simplifies Hardware Asset Management - ServiceNow Blog, Product Documentation | 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?

• Configuration items (CIs) are the records that represent the IT assets and services in the Configuration Management Database (CMDB).
• CIs track the following types of information:
• Therefore, the types of information that are also options in the question are B. Operational and E. Relationship.
• The other types of information that are not tracked by CIs are:
• : Configuration Item

• 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.
• The asset audit results show 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”.
• The status of “Scanned and expected” means that the asset was both expected to be in the inventory and scanned during the audit, indicating a match between the physical and the logical inventory.
• Therefore, if you receive the result of 10 “Scanned and expected” assets, it means that you expected 10 assets in your inventory and scanned these 10 assets during your audit, as stated in option B. References:
• Hardware Asset Management documentation
• What is Hardware Asset 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.

References:

• ServiceNow Hardware Asset Management: Advanced Risk Assessment
• ServiceNow Hardware Asset Management: Risk response tasks
• ServiceNow Hardware Asset Management: ServiceNow Risk Management

 According to the ServiceNow Hardware Asset Management documentation, assets can be moved between stockrooms by using transfer orders. A transfer order is a record that tracks the movement of assets from one stockroom to another. A transfer order can be created manually by the stock manager or automatically by the system based on predefined rules or workflows1. A transfer order contains information such as the source and destination stockrooms, the assets to be transferred, the shipment details, and the status of the transfer2.

The other options are not correct because:

• Stock orders are records that track the procurement of assets from vendors, not the movement of assets between stockrooms3.
• Stock rules are rules that define the minimum and maximum stock levels for each asset model in a stockroom, not the movement of assets between stockrooms.
• Transfer rules are rules that define the conditions and actions for creating transfer orders automatically, not the records that track the movement of assets between stockrooms.

References:

• ServiceNow Hardware Asset Management: Transfer orders
• ServiceNow Hardware Asset Management: Create a transfer order
• ServiceNow Hardware Asset Management: Stock orders
• [ServiceNow Hardware Asset Management: Stock rules]
• [ServiceNow Hardware Asset Management: Transfer rules]

• 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:
• 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:
• 1: Hardware Asset Inventory Audit
• 2: Stockrooms
• 3: Vendor Management
• 4: Configuration Management

• Operational: The current status, performance, availability, and capacity of the CI, as well as any incidents, problems, or changes that affect it.
• Relationship: The dependencies and connections between the CI and other CIs, services, processes, and users.

The information that you would track for an asset includes:

• Financial: The cost, depreciation, ownership, and warranty of the asset, as well as any procurement or disposal activities.
• Lifecycle: The stages and transitions of the asset from request to retirement, as well as any inventory or stock management.

The information that you would not track for a CI versus an asset are:

• Contractual: This information is relevant for both CIs and assets, as it relates to the agreements and obligations between the service provider and the customer or vendor.
• Lifecycle: This information is relevant for both CIs and assets, as it relates to the stages and transitions of the component from request to retirement.

References: 3: Asset and CI management - Product Documentation: San Diego - ServiceNow 2: What is the difference between an Asset and a Configuration Item? 1: [ITIL 4 Foundation] IT Assets vs. Configuration Items (CI’s) - CertiBanks

According to the ServiceNow Hardware Asset Management documentation, a business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried. Business rules can be used to enforce data consistency and integrity, such as preventing duplicate transfers of the same asset. The other options are not valid terms in ServiceNow Hardware Asset Management.

 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]

During an inventory audit, if you accidentally scan the same asset twice, the Hardware Asset Management (HAM) application will automatically remove the duplicate records and only import the unique scans. This is because the HAM application uses the asset tag or the serial number as a coalesce field, which prevents duplicate records from being created or updated in the hardware asset table. Therefore, you do not need to worry about scanning the same asset twice, as the HAM application will handle the duplicates for you. References:

• Audit your inventory, which provides a step-by-step guide on how to perform scheduled or blind audits of asset stockrooms and other locations using the Agent mobile app and the Now Platform.
• Hardware Asset States, which describes the different states and substates of hardware assets and how they are used to track the asset lifecycle.
• Importing Hardware Assets into ServiceNow, which provides a step-by-step guide on how to import hardware assets into ServiceNow using an excel spreadsheet, an import set table, and a transform map.

• 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.

References:

• Importing Hardware Assets into ServiceNow, which provides a step-by-step guide on how to import hardware assets into ServiceNow using an excel spreadsheet, an import set table, and a transform map.
• Hardware Asset Inventory Management, which explains how to streamline inventory stock orders, empower employees with a robust asset catalog, monitor stock depletions, track shipments, scan assets with a mobile device, and plan asset refresh cycles.
• Getting Started with ServiceNow Hardware Asset Management, which provides general procedures and forms for performing asset lifecycle management activities in ServiceNow.

• The Product Catalog is a table that contains all the hardware and consumable models that are available in your organization12.
• The Service Catalog is a portal that allows users to browse and request items and services that are approved by the IT department13.
• Publishing an item to the Service Catalog means making it visible and available for users to request13.
• To publish an item to the Service Catalog, you need to use the “Publish to Hardware Catalog” related link in the Product Catalog1 .
• This related link creates a catalog item for the selected model and adds it to the Hardware Catalog category in the Service Catalog1 .
• Therefore, the correct answer is A. Product Catalog, as this is where you can use the “Publish to Hardware Catalog” related link to publish an item to the Service Catalog.

References: 1: Use a hardware asset request flow - ServiceNow 2: Hardware Asset Inventory Management - ServiceNow 3: Service Catalog - Product Documentation: Tokyo - ServiceNow : Publish models to the hardware or software catalog - ServiceNow

• When disposing of an IT asset through a vendor, the asset manager should attach a certificate of destruction to the retired asset’s record1.
• A certificate of destruction is a document that verifies that the asset has been destroyed in a secure and compliant manner by the vendor1.
• A certificate of destruction should include information such as the asset tag, serial number, model, manufacturer, date of destruction, method of destruction, and signature of the authorized person1.
• A certificate of destruction helps the asset manager to ensure that the asset is no longer in use, that the data on the asset is erased, and that the asset is disposed of in accordance with environmental, regulatory, and legal requirements1. References:
• 1: Hardware Asset Disposal

• A blind audit is a type of inventory audit that does not provide any information about the expected assets in a location. The auditor scans all the assets in the location and compares them with the records in ServiceNow1.
• To perform a blind audit, you need the Hardware Asset Management (HAM) application, which enables you to manage the lifecycle of your hardware assets, and the ServiceNow Agent mobile app, which allows you to scan asset tags and barcodes using your mobile device12.
• The ServiceNow My Assets mobile app is used to view and request assets from the enterprise asset catalog, not to perform audits3.
• The Software Asset Management (SAM) application is used to optimize software licenses and compliance, not to perform audits4.
• The ITSM Asset Management application is the legacy application for managing assets, which has been replaced by the Hardware Asset Management application. References: 1: Audit your inventory - Product Documentation: San Diego - ServiceNow 2: Hardware Asset Management - ServiceNow 3: ServiceNow My Assets mobile app - Product Documentation: San Diego - ServiceNow 4: Software Asset Management - ServiceNow : Asset Management - Product Documentation: San Diego - ServiceNow

According to the ServiceNow Hardware Asset Management documentation, a hardware asset is defined as "any tangible, physical company technology asset, including those currently in use, those in storage, and support equipment"1. Websites are not tangible or physical assets, but rather digital or virtual assets that are hosted on servers or other hardware devices. Therefore, websites are not considered hardware assets by ServiceNow. The other options, switches, routers, buildings, and software entitlements, are all examples of hardware assets or related items that can be managed by ServiceNow Hardware Asset Management. References:

• What is Hardware Asset Management?

According to the ServiceNow Hardware Asset Management documentation, an asset record should track the following information:

• Financial information: This includes the cost, depreciation, and residual value of the asset. This information helps to calculate the total cost of ownership (TCO) and return on investment (ROI) of the asset.
• Contractual information: This includes the warranty, support, lease, and maintenance contracts associated with the asset. This information helps to manage the lifecycle of the asset and ensure compliance with the terms and conditions of the contracts.

Other information that can be tracked in an asset record are:

• Physical resources: This includes the location, status, and condition of the asset. This information helps to monitor the inventory and availability of the asset.
• Operational details: This includes the configuration, performance, and usage of the asset. This information helps to optimize the functionality and efficiency of the asset.
• Logical relationships: This includes the dependencies, associations, and impacts of the asset. This information helps to understand the connections and interactions of the asset with other assets, services, and processes.

References: Asset form, Hardware Asset Management: Record Keeping, Hardware Asset Inventory Management, Hardware Asset Workspace, Getting Started with ServiceNow Hardware Asset Management

• 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.

References: 1: Stock rules 2: Procurement

According to the ServiceNow Hardware Asset Management documentation1, when a hardware asset is retired, the system property glide.ham.retire_reclaim_sw() determines whether the software allocations on that asset are automatically reclaimed or not. If the property is set to true, the software allocations are returned to the inventory. If the property is set to false, the software allocations remain with the hardware asset and need to be reclaimed manually. References: 1: Hardware Asset Management - ServiceNow2

Normalization is the process of aligning hardware asset data with the ServiceNow Content Library, which provides standardized values for manufacturer, product name, and model number. During normalization, the system compares the hardware model data with the content library and assigns a status to indicate the level of match. The status of Match Not Found means that the system could not find any matching record in the content library for the hardware model. The most common cause for this status is missing data, such as an empty manufacturer field or a generic product name. To resolve this issue, the user can manually edit the hardware model record and provide the missing data, or use the lookup feature to search for a matching record in the content library. Alternatively, the user can create a new content library record for the hardware model and link it to the asset record. References:

• Hardware model normalization
• Normalize hardware models
• Create a content library record

• According to the ServiceNow IT Asset Management (ITAM) Hardware Asset Management (HAM) learning path, the Hardware Asset dashboard is a feature that shows key metrics on your hardware and consumable models and assets for the entire asset life cycle.
• The Hardware Asset dashboard is available with the Hardware Asset Management (HAM) application, which is a licensable application that provides advanced workflow, automation, and mobile capabilities to maintain your assets1.
• To access the Hardware Asset dashboard, you need to have the ham_user role, which is the minimum role required to use the HAM application1.
• The ham_user role grants you the permission to view and update hardware and consumable assets, transfer orders, disposal orders, and RMA requests1.
• Therefore, the correct answer is option C, ham_user, as it is the minimum role required to use the Hardware Asset dashboard. References:
• ServiceNow IT Asset Management (ITAM) Hardware Asset Management (HAM) learning path
• 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

• According to the ServiceNow Hardware Asset Management overview document1, contracts are records that define the terms and conditions for the acquisition, maintenance, or disposal of assets1. They can include information such as vendor, start date, end date, cost, and renewal options1.
• According to the ServiceNow Data Sheet on Contract and Renewal Management2, some of the critical information that should be tracked for contracts are2:
• The other options are not critical information that should be tracked for contracts. Who purchased the assets and what needs to be cancelled are not relevant to the contract management process, as they do not affect the contract terms, conditions, or performance2.

References:

• 1: Hardware Asset Management overview - ServiceNow - Now Support
• 2: Contract and renewal management - ServiceNow

According to the ServiceNow Hardware Asset Management documentation, the Scanned Assets related list displays the assets that have been scanned using the ServiceNow Agent mobile app during an audit. The Scanned Assets related list is updated each time scans are submitted from the app, which can be done manually or automatically based on the app settings

• Deploying asset tasks during the retirement of an asset means using the ServiceNow Enterprise Asset Workflow Automation feature, which automates the end-of-life procedures for assets that are no longer needed or functional1.
• This feature allows you to flag assets as retired pending disposal, triggering a workflow that verifies the asset condition, determines the disposal method, and saves the disposal certificates1.
• The two primary benefits of deploying asset tasks during the retirement of an asset are:
• 1: Enterprise Asset Workflow Automation - ServiceNow
• 2: Asset and CI management - Product Documentation: San Diego - ServiceNow
• 3: Enterprise Asset Management - ServiceNow

• 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.

References:

• 1: Hardware Asset Management overview - ServiceNow - Now Support
• 2: Asset Management - ServiceNow - Now Support

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.

• Stock rules are the rules that define the minimum and maximum quantities of hardware assets in a stockroom1.
• Stock rules help to optimize the inventory levels and avoid overstocking or understocking of hardware assets1.
• Stock rules have the following purposes:
• Therefore, the purposes of stock rules that are also options in the question are A. To automatically transfer assets when a low quantity threshold is detected in a stockroom and C. To send notifications when a low quantity threshold is detected in a stockroom.
• The other options that are not purposes of stock rules are:
• 1: Stock Rules
• 2: Purchase Orders
• 3: Transfer Orders
• 4: Stock Order Tasks

• Once a catalog item has been requested, the mechanism that determines the approvals and tasks that are triggered in the application is the flow12.
• A flow is a graphical representation of a business process that consists of one or more actions, such as approvals, tasks, notifications, scripts, etc., that are executed based on certain conditions and triggers12.
• A flow can be associated with a catalog item to define the fulfillment process for that item, such as who needs to approve it, what tasks need to be performed, and what notifications need to be sent12.
• A flow can be created and managed using the Flow Designer, a low-code development tool that allows users to design and test flows without writing any code12.
• A flow can be activated or deactivated, versioned, and published to make it available for use12.
• A flow can be monitored and debugged using the Flow Execution Details and the Flow Logs12. References:
• Flow Designer
• Service Catalog Request Fulfillment