According to the ServiceNow Hardware Asset Management documents, a hardware asset’s lifecycle consists of the following stages: Procure, Receive, Deploy, Maintain, and Dispose1. These stages correspond to the options A, D, and E in the question. The option B, Request, is also a valid stage in the hardware asset management process, as it involves identifying the hardware needs and initiating the procurement process2. However, the option C, Consume, is not a component of a hardware asset’s lifecycle, as it is not mentioned in the ServiceNow documents. Consume is more relevant to software assets, which are used or consumed by end-users or applications3. Therefore, the correct answer is C. Consume. References:

ServiceNow Hardware Asset Management landing page

ServiceNow Hardware Asset Management overview

ServiceNow Software Asset Management overview

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

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

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

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.

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.

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

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

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