ServiceNow CIS-HAM Dumps

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

Assets are tangible items tracked for lifecycle management and financial purposes. Facilities (e.g., buildings), servers, and network cables are physical assets. Software licenses and distributions are intangible and treated differently in ServiceNow Asset Management.

The Hardware Asset Management (HAM) plugin is a plugin that enables the Hardware Asset Management application, which helps to track and manage the end-to-end lifecycle of hardware assets, physical and consumable1.

The HAM plugin provides the following baseline asset lifecycle automation flows2:

Hardware asset order: This is a flow that automates the process of ordering new hardware assets from a vendor. It creates purchase orders, stock order tasks, and catalog tasks based on the asset requests and the stock rules2.

Hardware deployment: This is a flow that automates the process of delivering and installing hardware assets to the end users. It creates catalog tasks and updates the asset records and the configuration management database (CMDB) based on the stock order tasks and the asset reservations2.

Hardware disposal: This is a flow that automates the process of disposing of retired hardware assets through a vendor. It creates return merchandise authorization (RMA) records and updates the asset records and the CMDB based on the asset retirements and the vendor contracts2.

Therefore, the baseline asset lifecycle automation flows that are also options in the question are A. Hardware asset order, E. Hardware deployment, and F. Hardware disposal.

The other options that are not baseline asset lifecycle automation flows provided by the HAM plugin are:

B. Hardware bulk stock order: This is not a baseline asset lifecycle automation flow, but a manual action that allows the user to create multiple stock order tasks for different hardware models at once3.

C. Hardware swap order: This is not a baseline asset lifecycle automation flow, but a manual action that allows the user to swap a hardware asset with another hardware asset of the same model4.

D. Hardware retire order: This is not a baseline asset lifecycle automation flow, but a manual action that allows the user to retire a hardware asset and update its status and substatus. References:

1: Hardware Asset Management

2: Asset Lifecycle Automation Flows

3: Create a Bulk Stock Order

4: Swap a Hardware Asset

: Retire a Hardware Asset

The ServiceNow Agent mobile app allows the user to conduct asset audits by scanning asset barcodes or QR codes1.

The user can perform audits offline when they are in areas without connectivity1.

The app automatically compares the scanned assets against the expected assets based on the inventory records to identify discrepancies1.

The user can also view the audit results and generate reports from the app2. References:

Audit your inventory - Product Documentation: San Diego - ServiceNow

Hardware Asset Inventory Management - ServiceNow

Hardware Asset Management - 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.

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.

 Operational expenses are the costs incurred by an organization to maintain and use an asset throughout its lifecycle. These costs include the expenses related to the repair, maintenance, upgrade, and disposal of the asset. Some examples of operational expenses are:

Replacement parts: These are the costs of purchasing and installing new parts or components for an asset that is damaged, worn out, or obsolete. For example, replacing a hard drive, a battery, or a keyboard for a laptop.

Maintenance agreements: These are the costs of contracting with a vendor or a service provider to perform regular or preventive maintenance on an asset. For example, paying a monthly fee for a technician to check and service a printer or a scanner.

Other examples of operational expenses are:

Storage costs: These are the costs of renting or owning a space to store an asset that is not in use or awaiting disposal. For example, paying for a warehouse, a locker, or a shelf to keep unused or surplus computers or monitors.

Warranty costs: These are the costs of extending or renewing the warranty coverage for an asset that is still under the manufacturer’s warranty or has expired. For example, paying an extra fee for a one-year or a three-year warranty extension for a tablet or a smartphone.

According to the ServiceNow Hardware Asset Management documentation, a contract is a record of the terms and conditions that govern the relationship between a vendor and an organization. A contract can have different states that indicate its status and lifecycle. The states are:

Draft: The contract is being created or modified and has not been submitted for approval.

Requested: The contract has been submitted for approval but has not been approved yet.

Active: The contract has been approved and is in effect. You can cancel the contract in this state, if you want to terminate it before its end date due to various reasons, such as breach of contract, mutual agreement, or vendor performance1.

Expired: The contract has reached its end date and is no longer valid. You cannot cancel the contract in this state, but you can renew it or extend it.

Renewed: The contract has been renewed for another term with the same or modified terms and conditions. You cannot cancel the contract in this state, but you can renew it or extend it again.

Extended: The contract has been extended beyond its original end date with the same terms and conditions. You cannot cancel the contract in this state, but you can renew it or cancel it.

Canceled: The contract has been terminated before its end date. You cannot cancel the contract in this state, but you can reactivate it or delete it.

Rejected: The contract has been rejected by the approver. You cannot cancel the contract in this state, but you can edit it or delete it.

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

According to the ServiceNow Hardware Asset Management documentation, asset management is the practice of managing the lifecycle and optimization of physical assets to meet the needs and goals of an organization. Asset management involves the balancing of costs, opportunities and risks against the desired performance of assets to achieve an organization’s objectives. The other options are not the focus of asset management.

To activate HAM, navigate to System Definition > Plugins and search for Hardware Asset Management. Click Activate/Upgrade and follow the instructions1.

To run the scheduled job “Asset - Create FSM asset tasks”, navigate to System Definition > Scheduled Jobs and search for the job name. Click Execute Now to run the job immediately or set a schedule for it to run periodically2.

The scheduled job will create asset tasks for existing incidents, changes, and work orders that have assets associated with them. The asset tasks will be linked to the parent records and will have the same state and assignment group as the parent records2.

The asset tasks will allow the asset managers to track and manage the assets involved in the service delivery processes3. References:

1: Hardware Asset Management - ServiceNow

2: Asset - Create FSM asset tasks scheduled job

3: Hardware Asset Management and Field Service Management integration

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

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?

According to the Audit your inventory document, a blind inventory audit is a type of audit that hides the expected asset list from the auditor, so that the auditor has to physically scan each asset in the location and compare it with the actual asset list1.

A blind inventory audit helps ensure data integrity and accuracy, as it prevents the auditor from “cheating on the test” by relying on the expected asset list1.

A blind inventory audit is typically initiated via the Now Agent Mobile app, which is a mobile application that enables users to perform various tasks related to hardware asset management, such as scanning assets, creating audits, and viewing audit results1.

The Now Agent Mobile app allows users to create an audit on the mobile device, select the location and type of audit, and scan the assets using the device camera or a Bluetooth scanner1.

Therefore, the correct answer is option C, Now Agent Mobile app, as it is the interface that is typically used to initiate a blind inventory audit. References:

Audit your inventory

What is Hardware Asset 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.

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:

Operational: This includes the current status, location, owner, and other attributes of the CI that reflect its operational state.

Relationship: This includes the connections and dependencies between the CI and other CIs, such as parent-child, peer-peer, or service-component relationships.

Lifecycle: This includes the history of changes, incidents, problems, and other events that affect the CI throughout its lifecycle.

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:

Financial: This includes the cost, depreciation, and budget of the CI. This information is tracked by the Asset Management application.

Contractual: This includes the vendor, warranty, and contract details of the CI. This information is also tracked by the Asset Management application. References:

: Configuration Item

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 Content Library automatically populates your inventory with non-discoverable asset metadata, which are the data that cannot be obtained from discovery tools or manual entry, such as manufacturer name, model name, model number, and product lifecycle information1.

The product lifecycle information includes the manufacturer lifecycle dates, which are the dates when the manufacturer stops selling, supporting, or servicing a hardware product1.

The manufacturer lifecycle dates are important for hardware asset management, as they help customers plan for hardware refreshes based on end-of-life (EOL) and end-of-service (EOS) dates2.

Therefore, the correct answer is option C, manufacturer lifecycle dates, as they are the non-discoverable asset metadata that the Content Library automatically populates your inventory with as part of the hardware model normalization process. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

A field service management (FSM) change task is a task that is created from a change request and assigned to a field service agent to perform work on a configuration item (CI) or an asset1.

An asset task is a task that is created from an asset record and linked to an FSM change task to track the work done on the asset2.

When an asset task is completed, the asset record associated to the task is automatically updated with the latest information, such as location, status, assignment group, assigned to, and so on2.

This feature removes the need to manually update the asset record after completing the FSM change task, saving time and ensuring accuracy2.

The Normalization Data Services Client plugin enables you to use the Normalization Data Services (NDS) to provide consistent, good, clean data for the company names of vendors or manufacturers12.

The NDS is a cloud-based service that provides a comprehensive and up-to-date list of canonical company names for vendors and manufacturers, as well as other data such as product categories, models, and versions12.

The NDS helps you to avoid data duplication, inconsistency, and inaccuracy in your CMDB and asset management processes12.

The NDS integrates with the Hardware Model Normalization plugin, which standardizes the details of your hardware models by comparing them with the data from the Hardware Model Normalization Content Service13.

Therefore, the correct answer is D. Normalization Data Services Client (com.glide.data_services_canonicalization.client), as this is the plugin that offers consistent, good, clean data for the company names of vendors or manufacturers.

A transfer order is a record of all asset transfers that happen to and from company-owned stockrooms1. A transfer order can have one or more transfer order lines, which represent the individual assets or asset models that are being transferred2.

A transfer order line can have one or more transfer order tasks, which are the actual work items that need to be performed to complete the transfer, such as packing, shipping, receiving, and unpacking2.

The structure of a transfer order is shown in the following diagram2:

Transfer Order

|

+-- Transfer Order Line 1

| |

| +-- Transfer Order Task 1.1

| |

| +-- Transfer Order Task 1.2

|

+-- Transfer Order Line 2

|

+-- Transfer Order Task 2.1

|

+-- Transfer Order Task 2.2

Transform maps are used to transform imported hardware model data from an import set table to a target table, such as the Product Catalog or the Asset table1

Coalesce is an option that you can set on a field mapping to uniquely identify the same asset in order to merge or update records2

Coalesce means that the field is used as a unique key. If a match is found using the coalesce field, the existing record is updated with the imported information. If no match is found, a new record is inserted2

Coalesce helps to prevent duplicate records and ensure data consistency2

You can set coalesce on one or more fields in a transform map, but at least one coalesce field is required2

The other options, B. Consolidate, C. Unique identifier, D. Unique source, E. Unique target, and F. Combine, are not valid options for setting the unique identification of assets in transform maps

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

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.

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

The reclamation process allows managers to select assets to be reclaimed from the asset service catalog, including hardware, software, and consumables. Only selected items will be processed for return.

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?

Hardware model normalization is a feature that enables users to normalize the details, such as manufacturer, product, model, and device type, of hardware and consumable models1

Hardware model normalization uses the data from the models and compares it against the data in the Hardware Model Normalization Content Service, which is a cloud-based service that provides standardized and enriched information about hardware models1

Hardware model normalization sets the normalized display name for each model record based on three attributes: Name, Manufacturer, and Model number2

The Model Management tab of the Hardware Asset dashboard shows the status of the hardware models in the Product Catalog, such as Matched, Match Not Found, or Not Normalized3

Several of your models are listed as Match Not Found on the Model Management tab of the Hardware Asset dashboard. This means that the normalization process could not find a matching rule in the Content Service for those models3

The potential causes of this are34:

The hardware model content has not yet been downloaded from the Content Service. The Content Service is updated periodically with new and updated rules for hardware models. You need to download the latest content from the Content Service to ensure that your models are normalized with the most accurate and complete information. You can download the content manually or schedule it to run automatically.

Normalization could not match any of the three key fields in the hardware model form with a rule in the Content Service. The three key fields are Name, Manufacturer, and Model number. If any of these fields are missing, incorrect, or inconsistent with the data in the Content Service, the normalization process will fail to find a matching rule. You need to review and correct the data in these fields to ensure that they match the data in the Content Service.

A normalization rule for the hardware model does not exist in the Content Service. The Content Service may not have a rule for some hardware models, especially if they are new, rare, or custom-made. In this case, you can create a custom rule for the hardware model in the Hardware Model Normalization Rules module, or submit a request to the Content Service team to add a rule for the hardware model.

According to the ServiceNow Hardware Asset Management documentation, original cost is the amount paid to acquire an asset, including any taxes, fees, shipping, installation, or other expenses directly related to the purchase. Original cost is used to calculate depreciation and amortization of an asset over its useful life. The other options are not the type of cost that taxes paid at the time of purchase are. Operating expense, operating cost, and capital expense are different ways of classifying the costs of using and maintaining an asset after it is purchased.

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?

Hardware asset management, Procurement, and Cost management are the plugins which are not active by default in base Servicenow System

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 Hardware Asset Management documentation, the hardware asset management content service is a cloud-based service that provides normalized and enriched hardware model data to the ServiceNow platform, such as manufacturer name, model name, model number, and product lifecycle information.

The hardware asset management content service helps customers identify and manage their hardware assets more effectively, as well as plan for hardware refreshes based on end-of-life (EOL) and end-of-service (EOS) dates1.

The elements that are provided by the hardware asset management content service are as follows1:

Manufacturer lifecycle dates: The dates when the manufacturer stops selling, supporting, or servicing a hardware product.

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

Model name: The name of the hardware product, such as Dell Latitude E7450 or HP ProLiant DL380 Gen10.

Therefore, the correct answers are options A, D, and E, as they are the elements that are provided by the hardware asset management content service. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

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?

To fully normalize a model, you need to add the model number to the model record, which is a unique identifier for the model based on the United Nations Standard Product and Services Code (UNSPSC). The model number helps to standardize the display name and remove duplicates in the model catalog and the CMDB. The other fields, such as version, owner, and manufacturer, are optional or can be derived from the model number. References:

Hardware Model Normalization, which explains how to normalize the details of the hardware and consumable models using the Hardware Model Normalization Content Service.

Hardware Asset Management overview, which describes the functionalities of the Hardware Asset Management application, including the model normalization feature.

[Hardware Asset Management - Customer Success], which provides a success map that outlines the processes and best practices for implementing, running, and optimizing the Hardware Asset Management applications, based on the Capability Blueprint framework.

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.

A configuration item (CI) is a record that represents an IT asset or service in the Configuration Management Database (CMDB)1.

A CI tracks the operational and relationship information of the asset or service, such as its current status, location, owner, and dependencies1.

A hardware asset is a physical component of an IT system, such as a laptop, server, or router2.

A hardware asset attribute is a property or characteristic of the hardware asset, such as its model, serial number, or warranty2.

Some hardware asset attributes are also part of the CI, such as IP address, CPU, operating system, and memory1. These attributes reflect the operational state of the hardware asset and are relevant for configuration management purposes1.

However, some hardware asset attributes are not part of the CI, such as cost2. Cost is a financial information of the hardware asset that is tracked by the Asset Management application2. Cost is not relevant for configuration management purposes and is not stored in the CMDB2.

Therefore, the hardware asset attribute that should be tracked that is not part of the CI is C. Cost. References:

1: Configuration Item

2: Hardware Asset Management

To prevent normalization information for a specific hardware model from being sent to the ServiceNow Content Service, you need to select the Exclude from content service check box on the Normalization tab of the hardware model record1.

The ServiceNow Content Service is a cloud-based service that provides normalized data for hardware and consumable models. It helps you to keep your model data consistent and up to date2.

The other options are not valid ways to exclude a hardware model from the content service. There is no Exclude or Opt-out button on the hardware model record. There is also no Opt-out from content service check box on the Normalization tab of the hardware model record. References: 1: Work with hardware normalization 2: ServiceNow Content Service

A transfer order is a document that records the movement of assets from one location to another1.

A transfer order line is a record that specifies the quantity and type of assets to be transferred1.

When you cancel a transfer order line, the associated assets are released from the transfer order and their state changes from Pre-allocated to Available1.

The released assets can then be attached to another transfer order or used for other purposes1. References:

Transfer orders - Product Documentation: Rome - ServiceNow

When an asset is manually created from a purchase order before it has been shipped by the supplier, the default state of the asset is set to On order. This state indicates that the asset has been ordered but not yet received. The asset state will change to Awaiting delivery when the asset is shipped by the supplier, and to In stock when the asset is received by the stockroom. The asset state will change to In use when the asset is deployed to a user or a location, and to Pending transfer when the asset is ready to be transferred to another stockroom or location. The asset state will change to Retired when the asset is disposed of or returned to the supplier. References:

Hardware Asset States, which describes the different states and substates of hardware assets and how they are used to track the asset lifecycle.

Hardware Asset Management overview, which describes the functionalities of the Hardware Asset Management application, including the dashboard, model normalization, hardware refresh, lease contract expiration, disposal orders, and RMA requests.

Hardware Asset Lifecycle Automation, which explains how to automate the workflows and tasks for managing the assets throughout their lifecycle stages, from request to retire.

 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.