Free CIS-HAM sample questions

Correct answer: State: In Maintenance, Substate: Pending Repair

The 'In Maintenance' state is the correct choice for an asset that is temporarily unavailable for its primary function due to service, repair, or calibration. The 'Pending Repair' substate accurately describes that work is being performed. This combination correctly reflects the asset's status for operational and compliance tracking without incorrectly classifying it as 'In Stock' or 'In Use'.

Correct answer: False

The statement is false. While Procurement is a critical and tightly integrated part of the full asset lifecycle, the Procurement plugin is not a mandatory dependency for the core HAM plugin. It can be activated separately to add procurement functionalities like purchase orders and receiving. HAM can function without it, focusing on inventory and in-life management of existing assets.

Correct answers: Asset state; Install date

To determine the three-year refresh cycle, the 'Install Date' is the most accurate starting point, as it represents when the asset was put into service. The 'Asset State' (e.g., 'In Use') is also crucial to ensure the report only includes currently active devices and excludes those already in stock or retired. Purchase date is less accurate as devices can sit in storage, and warranty expiration may not align with the company's internal refresh policy.

Correct answer: The CI class `cmdb_ci_netgear` is not mapped to an Asset class in the 'Asset-CI Class Mapping'.

The synchronization between assets and CIs is governed by the 'Asset-CI Class Mapping' (`asset_class_mapping`) table. If a specific CI class like `cmdb_ci_netgear` is not explicitly mapped to an asset class (typically `alm_hardware`), the business rules responsible for keeping the records in sync will not trigger for CIs of that class. This is the foundational configuration that enables the two records to be linked and updated together.

Correct answer: To prevent an asset from being moved to the 'In Use' state if it is not linked to a corresponding CI.

The 'Enforce CI verification' option is a data integrity control. When checked for a specific model category (e.g., Servers), it prevents any asset of that category from being set to the 'In Use' state unless its 'Configuration item' field is populated. This ensures that operationally critical assets have a corresponding CI record in the CMDB before they are considered actively deployed.

Correct answer: State: In Stock, Substate: Pre-Deployment

The 'In Stock' state is appropriate because the asset is not yet in productive use. The 'Pre-Deployment' substate is specifically designed for this scenario, indicating that the asset is undergoing configuration or preparation before being assigned and moved to the 'In Use' state. This provides a clear and accurate status for tracking assets in the staging phase.

Correct answer: 1. Activate core HAM plugins. 2. Define hardware models and normalize them. 3. Import the spreadsheet data to create asset records. 4. Configure asset-CI synchronization rules. 5. Build a service catalog item for hardware requests.

This sequence follows the crawl-walk-run methodology. It starts with the foundational step of activating HAM (1), then establishes data integrity by defining and normalizing models (2). With a clean model structure, importing existing data is effective (3). Next, it addresses the CTO's requirement by linking assets to the CMDB (4). Finally, it automates future processes by creating a catalog item (5). This logical progression builds a trustworthy data foundation before automating processes, which is a core principle of successful HAM implementation.

Correct answer: Closing the 'Deploy' Asset Task [asset_task] associated with the request.

The standard fulfillment process uses an Asset Task with the type 'Deploy'. When this specific task is closed (set to 'Closed Complete'), out-of-the-box business rules are triggered. These rules update the associated asset record, changing its state to 'In Use', setting the substate to 'Deployed', and populating the 'Assigned to' field with the user from the original request. This automates the final step of the deployment process.

Correct answer: The manufacturer name was recognized, but the model name was not found in the Content Library.

'Partially Normalized' means the system successfully matched the discovered manufacturer to a standard manufacturer name in the Content Library, but it could not find a matching model name associated with that manufacturer. This requires manual intervention to either correct the discovered model name or add a new model to the library.

Correct answers: The 'ITAM Mobile' plugin (com.snc.asset.mobile) must be activated.; The user performing the audit must have the 'inventory_user' role.; Asset records must have a value in the 'Asset tag' or other designated barcode field.

To use the mobile app for scanning, the core 'ITAM Mobile' plugin must be active, the user needs the appropriate permissions ('inventory_user' or similar), and the asset records themselves must have barcode data (like an asset tag) populated. The mobile app uses the device's camera, so a dedicated scanner is not required.