ServiceNow CIS-HAM Practice Test - Questions Answers, Page 14

According to the ServiceNow Hardware Asset Management documentation, a loaner asset is a temporary asset that is provided to a user for a specific period of time, such as when their primary asset is being repaired or replaced1.Users can request loaner assets from the Service Catalog, where they can select the type, quantity, and duration of the loaner asset they need2.If the requested asset is not available in the local stockroom, the request is wait-listed until the asset becomes available3. Users may request loaner assets even when the requested asset is not available in the local stockroom because the wait-listed loaner asset requests provide visibility to the demand for loaner orders. This visibility helps the asset managers to plan and optimize the loaner asset pool, as well as to identify and address any gaps or bottlenecks in the loaner asset fulfillment process.

The other options are not correct because:

The request does not create an automatic transfer order to move assets from a warehouse with in stock assets. Transfer orders are created manually by the stock manager to move assets between stockrooms.

The wait-listed loaner asset requests do not provide visibility to streamline internal transfer order flows. Transfer order flows are managed by the stock manager using the Transfer Order Management module.

The request does not automatically create a purchase order to obtain the assets from a vendor. Purchase orders are created manually by the procurement manager to order assets from vendors.

ServiceNow Hardware Asset Management: Loaner Asset Requests

ServiceNow Hardware Asset Management: Request a loaner asset

ServiceNow Hardware Asset Management: Waitlist a loaner asset request

[ServiceNow Hardware Asset Management: Asset Reservations and Loaner Asset Requests]

[ServiceNow Hardware Asset Management: Transfer orders]

[ServiceNow Hardware Asset Management: Transfer Order Management]

[ServiceNow Hardware Asset Management: Purchase orders]

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.

1: ServiceNow Product Documentation: Stock Rules

2: Stock Rules in ServiceNow - GlideFast ServiceNow

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 thestrategic conformancetier, which aims to optimize the cost, quality, and value of hardware assets, as well as align them with the business strategy and objectives.Reference:

Hardware Asset Management Capability Blueprint

Hardware Asset Management Maturity Model

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 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.Reference:

1:What is the IT Asset Lifecycle? - ServiceNow

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

According to theHardware 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.

Normalization is the process of standardizing the hardware model data by manufacturer name, model name, and model number1.

Normalization helps to maintain a clean and consistent configuration management database (CMDB) and to avoid duplicate or inaccurate hardware models1.

Normalization first runs to normalize the record when you save the hardware model record1.

This means that when you create or edit a hardware model record, the system automatically checks the record against the normalization rules and the Hardware Content Service Lifecycle data, and updates the record with the normalized values if applicable1.

Therefore, the answer that reflects when normalization first runs is C. When you save the hardware model record.

The other options are not the correct answer because they describe different scenarios or actions:

A) When the daily scheduled HAM -- Daily job runs: This is not the correct answer, because the daily scheduled HAM -- Daily job does not run normalization.The daily scheduled HAM -- Daily job is a scheduled job that runs various tasks related to hardware asset management, such as updating the asset status, calculating the depreciation, and sending notifications2.

B) When the weekly scheduled HAM -- Normalization job runs: This is not the correct answer, because the weekly scheduled HAM -- Normalization job does not run normalization for the first time.The weekly scheduled HAM -- Normalization job is a scheduled job that runs normalization for all the existing hardware models in the CMDB on a weekly basis1.It does not affect the newly created or edited hardware models, which are normalized when they are saved1.

D) When you click the Normalize Hardware Model link under Related Links: This is not the correct answer, because clicking the Normalize Hardware Model link under Related Links does not run normalization for the first time.Clicking the Normalize Hardware Model link under Related Links is a manual action that allows you to run normalization for a specific hardware model record at any time1.It does not affect the automatic normalization that runs when you save the hardware model record1.Reference:

1: Hardware Normalization

2: Daily Scheduled HAM -- Daily Job