Free and Premium ServiceNow CIS-HAM Dumps Questions Answers

According to the Hardware Asset Management documentation, non-consumable assets are assets that are not depleted or used up when they are applied or consumed, such as laptops, monitors, or routers.

Non-consumable assets are tracked individually in the ServiceNow platform, and each asset has a unique asset tag and serial number.

When transferring non-consumable assets between stockrooms, they must be transferred as a single entity with a quantity of one, as stated in the Hardware Asset Management documentation: “Non-consumable assets are transferred as a single entity with a quantity of one. For example, a laptop is transferred as a single entity with a quantity of one.”

Therefore, the correct answer is option C, as a single entity with a quantity of one. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

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

To find the answer, I searched for “ServiceNow Hardware Asset Management IT asset vs. CI” using my search_web tool.

I found several relevant web pages that explain the difference between an IT asset and a CI in ServiceNow.

I learned that an IT asset is any financially valuable component that can contribute to the delivery of an IT product or service, while a CI is any component that needs to be managed in order to deliver an IT service12.

I also learned that an IT asset is often a CI, but not all CIs are IT assets12.

Therefore, a component is considered an IT asset vs. a CI when you want to do the following:

Manage its procurement, maintenance, or retirement

Track its monetary value or costs

Manage its associated license, warranty, or lease contracts

These are the aspects that relate to the financial value and lifecycle of the component, which are relevant for IT asset management34.

The other options, such as tracking its operational information and knowing its relationships to other assets in the CMDB, are more relevant for CI management, which is part of configuration management35.

The itil role enables the user to perform actions related to incident, problem, change, and configuration management. This role is part of the ITIL framework, which is a set of best practices for delivering IT services. According to the ServiceNow documentation1, the itil role can do the following:

Create and update incidents, problems, and change requests

View configuration items (CIs) and their relationships

Add comments and work notes to tasks

Approve or reject change requests

Close resolved incidents and problems

Reopen closed incidents and problems

The other roles listed in the question have different functions and permissions. For example, the procurement_user role can request and track hardware purchases2, the inventory_admin role can manage stockrooms and transfer orders3, the discovery_admin role can configure and run Discovery to populate the CMDB4, and the asset role can view and edit asset records5.

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

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 used to track the financial, contractual, and inventory details of hardware and devices, not to perform audits. References:

1: Audit your inventory - Product Documentation: San Diego - ServiceNow

2: Enterprise Asset Inventory Management - ServiceNow

3: My Assets mobile app - Product Documentation: San Diego - ServiceNow

4: Software Asset Management - ServiceNow

: IT Asset Management - ServiceNow

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

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

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

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

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

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

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

Hardware Asset Inventory Management - ServiceNow

Automation Simplifies Hardware Asset Management - ServiceNow Blog

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.

Managing the Hardware Asset Management (HAM) Content Service involves enabling the service explicitly (opting in). Organizations can choose to enable it for receiving updates about normalized hardware models and lifecycle information. If the service is not needed anymore, it allows opting out at any time, providing flexibility for organizations.

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

A transfer order is a document that is used to execute the movement of hardware assets from one stockroom location to another within the same organization1.

A transfer order is created when there is a need to replenish, share, or relocate hardware assets between different stockrooms1.

A transfer order consists of one or more transfer order lines, each containing the information about the asset to be moved, such as the model, quantity, source stockroom, destination stockroom, and expected delivery date1.

A transfer order can be created manually or automatically based on predefined rules or thresholds1.

A transfer order goes through several stages, such as draft, approved, shipped, received, and closed1.

A transfer order can be tracked and managed using the Hardware Asset Management Workspace or the Transfer Order form1. References:

Transfer orders

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

Classes are represented as tables in the ServiceNow database that define the attributes and relationships of a specific type of record1

The base asset class is the alm_asset table, which contains the common fields and properties for all types of assets, such as hardware, software, consumable, etc.2

The alm_asset table is extended by other asset classes, such as alm_hardware, alm_software, alm_consumable, etc., which add more specific fields and properties for each asset type2

The cmdb_asset table is not a class, but a view that joins the alm_asset table and the cmdb_ci table, which is the base configuration item (CI) class3

The cmdb_hardware table is a CI class, not an asset class, that contains the common fields and properties for all types of hardware CIs, such as computers, devices, network equipment, etc.4

 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

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?

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

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:

To automatically transfer assets when a low quantity threshold is detected in a stockroom: This means that when the quantity of a hardware asset in a stockroom falls below the minimum threshold defined by the stock rule, the system automatically creates a transfer order to replenish the stockroom from another stockroom that has excess quantity of the same asset1.

To send notifications when a low quantity threshold is detected in a stockroom: This means that when the quantity of a hardware asset in a stockroom falls below the minimum threshold defined by the stock rule, the system sends an email notification to the stockroom manager or other stakeholders to alert them of the low inventory level1.

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:

To track stock orders from a vendor: This is not a purpose of stock rules, but a function of purchase orders. Purchase orders are the records that capture the details of the vendor contracts for procuring hardware assets2. Purchase orders help to track the status, quantity, and cost of the stock orders from a vendor2.

To track stock movement between stockrooms: This is not a purpose of stock rules, but a function of transfer orders. Transfer orders are the records that track the movement of hardware assets between stockrooms3. Transfer orders help to track the source, destination, quantity, and status of the stock transfers between stockrooms3.

To send notifications when a stock shipment arrives at a stockroom: This is not a purpose of stock rules, but a function of stock order tasks. Stock order tasks are the tasks that track the fulfillment of asset requests from stockrooms4. Stock order tasks help to send notifications when a stock shipment arrives at a stockroom and when the assets are received and verified4. References:

1: Stock Rules

2: Purchase Orders

3: Transfer Orders

4: Stock Order Tasks

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

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:

Reduces manual intervention: By automating the retirement process, you can eliminate the need for manual data entry, human errors, and delays. You can also ensure compliance with policies and regulations by following a standardized procedure12.

Increases speed of updates: By using the ServiceNow Agent mobile app, you can scan asset tags and barcodes, update asset status and inventory, and complete asset tasks on the go. This can increase the speed and accuracy of asset updates and reduce the risk of data loss or duplication13. References:

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 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]

According to the Hardware Asset Management page, the HAM application includes the following features: Hardware Asset Workspace, Hardware Normalization, Asset Lifecycle Automation, Return Merchandise Authorization, Asset Reservations, Asset Onboarding and Offboarding, Mobile Asset Receiving, Mobile My Locker, Asset Inventory Audit, and Hardware Asset Dashboard.

Among these features, Mobile Asset Receiving, Hardware Model Normalization, and Hardware Asset Dashboard are the ones that expand the baseline ITSM Asset Management, which only covers Asset & Model Records and Stockrooms.

Mobile Asset Receiving allows users to receive multiple assets against a purchase order using a mobile device, which simplifies the asset receiving process and reduces errors.

Hardware Model Normalization standardizes asset data by manufacturer name, model name, and model number, which improves data quality and accuracy in the CMDB.

Hardware Asset Dashboard provides a comprehensive view of hardware asset data, such as asset counts, costs, compliance, and lifecycle stages, which helps users make informed decisions and optimize asset performance. References:

Hardware Asset Management

What is Hardware Asset Management?

[Hardware Asset Management - ServiceNow Docs]

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.

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.

The Normalization statuses are the indicators of how well the hardware and consumable models are standardized and normalized in the model catalog and the CMDB. The Normalization statuses are:

Manufacturer Normalized: The model has been normalized with the manufacturer name and the product name, but not the model number or the device type. For example, Dell Latitude.

Match Not Found: The model has not been normalized because no matching model was found in the Hardware Asset Management Content Service. For example, ABC XYZ.

Partially Normalized: The model has been normalized with the manufacturer name, the product name, and the model number, but not the device type. For example, Dell Latitude E7450.

Normalized: The model has been fully normalized with the manufacturer name, the product name, the model number, and the device type. For example, Dell Latitude E7450 (Laptop).

Manually Normalized: The model has been manually updated by the user with the normalization content, such as the manufacturer name, the product name, the model number, and the device type. For example, HP Pavilion 15 (Laptop).

New: The model has been created and has not yet run through the normalization process. For example, Lenovo ThinkPad T490.

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

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

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

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

According to the Now Create ebook, the Now Create methodology consists of five phases: initiate, plan, execute, deliver, and close. Each phase has a specific purpose, outcome, and set of tasks that guide the project team to successful delivery. The other options are not valid phases of the Now Create methodology.

According to the ServiceNow Product Documentation on Document Templates1, document templates are records that define the layout and content of a document that can be generated from a table record, such as an HR case1. They can include information such as fields, variables, images, and signatures1.

According to the ServiceNow Product Documentation on Generate Documents from Templates2, when a document template is created from an HR case, the name of the person who created the document is added to the name of the attachment2. For example, if John Smith created a document from the template Employee Termination Letter, the attachment name would be Employee Termination Letter - John Smith.docx2.

The reason for this naming convention is to indicate who generated the document, which can be useful for auditing and tracking purposes2. It can also help to avoid confusion or duplication if multiple documents are generated from the same template by different users2.

The other options are not the correct explanation for why the name of the person who created the document is added to the name of the attachment. It does not indicate who should sign the document, as the signature can be added as a variable in the template1. It does not indicate the Opened for user, as the document can be generated for any HR case, not necessarily the one that the user opened2. It does not indicate who the document is about, as the document can contain information about multiple parties, such as the employee, the manager, and the HR representative2.

The End of Life tab of the Hardware Asset dashboard shows key metrics on the hardware assets that have reached or are nearing the end of their life cycle12.

The tab includes the following reports1:

Hardware asset disposal status: This report shows the number of hardware assets that are in different stages of disposal, such as pending, in progress, or completed1.

Hardware assets disposed (YTD): This report shows the number of hardware assets that have been disposed in the current year, grouped by month1.

Hardware assets up for end of life: This report shows the number of hardware assets that are due for end of life in the next 12 months, grouped by month1.

Hardware assets up for end of support: This report shows the number of hardware assets that are due for end of support in the next 12 months, grouped by month1.

Therefore, the correct answer is A. Hardware asset disposal status and C. Hardware assets disposed (YTD), as these are the only two reports that are shown on the End of Life tab of the Hardware Asset dashboard.

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.

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

According to the Hardware Model Normalization document, normalization status is the level of normalization match based on the characteristics of the hardware model data in the ServiceNow platform and the Content Library, which is a cloud-based service that provides normalized and enriched hardware model data.

The normalization status shows how well the hardware model data matches the Content Library data, and it can be one of the following1:

Fully Normalized: The hardware model data matches the Content Library data completely, indicating a complete and accurate model record.

Partially Normalized: The hardware model data partially matches the Content Library data, indicating a missing or incorrect model field.

Match Not Found: The hardware model data does not match any of the Content Library data, indicating a discrepancy or a gap in the model normalization process.

Not Normalized: The hardware model data has not been compared with the Content Library data yet, indicating a pending or incomplete model normalization process.

The characteristics that are used to determine the normalization status are the following1:

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

Manufacturer: The name of the company that produces the hardware product, such as Dell or HP.

Therefore, the correct answers are options A, C, and E, as they are the characteristics that are used to determine the normalization status. References:

Hardware Model Normalization

What is Hardware Asset Management?

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.

To exclude certain types of CIs from the CI lists on the Incident, Problem, and Change forms, you can use the Principal CI class checkbox, which is available on the Class Manager module under Configuration1.

The Principal CI class checkbox allows you to specify which CI classes are considered as principal CIs, meaning they are the most relevant and important CIs for the business services and processes1. By default, only the CI classes that have this checkbox selected are displayed on the CI lists on the Incident, Problem, and Change forms2.

To use this feature, you need to navigate to the Class Manager module, select the CI class that you want to exclude or include, and check or uncheck the Principal CI class checkbox accordingly1. You can also use the Filter option to search for the CI classes by name or label1.

The other options are not recommended or valid ways to exclude certain types of CIs from the CI lists. Adding a Show field to the base cmdb table would require modifying the table schema and creating a reference qualifier, which could affect the performance and integrity of the CMDB3. Creating an Access control to hide the unnecessary CIs from the itil users would require defining the conditions and roles for the access rule, which could be complex and error-prone4. Making a show/hide UI action to show only the desired CIs to the itil users would require creating a custom script and UI element, which could be incompatible with the existing UI and functionality. References: 1: Principal configuration item classes 2: Configuration item lists 3: CMDB table schema 4: Access control rules : [UI actions]

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