Free ServiceNow CIS-HAM Practice Exam with Questions & Answers | Set: 5

• According to the ServiceNow Hardware Asset Management overview document1, the lease contract expiration flow sends notifications to the contract administrator before a lease contract expires and helps them act on the leased assets to return the asset or extend the contract.
• According to the ServiceNow Elite blog post on contract management2, when the contract.expiration event runs on the Contract [ast.contract] table each night, an email message is sent to the person identified as the contract administrator at the following times:
• Therefore, the correct answer is C, D, E, and F.

References:

• 1: Hardware Asset Management overview - ServiceNow - Now Support
• 2: Contract and renewal management - ServiceNow
• 3: Contract Management — ServiceNow Elite
• 4: Email notification condition for contract expiration - ServiceNow

• 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

• 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

References: 1: Tables and Classes - ServiceNow 2: Asset [alm_asset] table - ServiceNow 3: Asset and Configuration Item [cmdb_asset] view - ServiceNow 4: Hardware [cmdb_ci_hardware] class - ServiceNow

• 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. References:
• 1: What is the IT Asset Lifecycle? - ServiceNow
• 2: ITAM Lifecycle Management: How does it all work?

• 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

https://docs.servicenow.com/bundle/sandiego-it-service-management/page/product/incident-management/task/track-ci.html

• Contract Management notifications are sent to contract administrators to remind them of contract expiration dates so they can renew or renegotiate the contract1.
• The expire date is the most important contract date to be aware of because it indicates when the contract is no longer valid and the service or product is no longer covered2.
• If a contract expires without renewal or extension, it can result in penalties, service downtime, or loss of warranty or maintenance3.
• Therefore, the expire date is the most critical date for contract management and should be monitored closely. References:
• 1: Product Documentation | ServiceNow
• 2: Contract and renewal management - ServiceNow
• 3: Hardware Asset Management overview - ServiceNow - Now Support
• 4: Use a hardware asset request flow - ServiceNow

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

References:

• 1: ServiceNow Product Documentation: Model Category
• 2: ServiceNow Product Documentation: Configuration Management
• 3: ServiceNow Product Documentation: Asset Management