Text preview & study summary

Servicenow CIS-HAM - Readiness Assessment

A free sample of 5 questions from this quiz, shown in full with answer choices and explanations. No interactivity — everything is visible on this page for study and review.

Want to test your knowledge? Launch the Interactive Exam Simulator

Question 1

A HAM implementation goes live with catalog requests, stockrooms, receiving, discovery, model normalization, lifecycle flows, and dashboards. After the first month, leadership wants to know whether the implementation is healthy and where process or data issues remain.

Which reviews best support that assessment?

Answer choices

A. Review dashboard and workspace indicators for lifecycle exceptions, task backlogs, and inventory trends (Correct)
B. Review model normalization status for unresolved model quality issues (Correct)
C. Review asset-CI relationship quality where discovery and procurement both contribute records (Correct)
D. Review request, receiving, transfer, audit, return, and retirement outcomes against the intended capability blueprint (Correct)
E. Treat catalog item performance metrics as sufficient evidence, since technical and financial accuracy are assumed once procurement completes

Explanation

Review dashboard and workspace indicators is correct because leadership needs visibility into lifecycle exceptions, task backlogs, and inventory trends. These indicators help show whether daily operations are healthy. Review model normalization status is correct because unresolved model issues can damage reporting, sourcing, lifecycle content, and financial analysis. Review asset-CI relationship quality is correct because discovery and procurement can both contribute records for the same devices. Relationship quality helps reveal duplicates or disconnected operational and asset views. Review process outcomes against the blueprint is correct because the implementation should be assessed against the intended capabilities, not just whether individual features were turned on. Catalog metrics alone are sufficient is not correct. Catalog performance does not prove that discovery, normalization, inventory, financials, lifecycle flows, or asset-CI relationships are accurate.

Question 2

A project team begins implementation by scripting custom receiving, deployment, return, retirement, and disposal logic. Personas, standard flows, asset actions, lifecycle states, and the capability blueprint have not been reviewed.

What is the strongest recommendation?

Answer choices

A. Complete model normalization first so the standard flows can inherit hardware lifecycle dates
B. Implement procurement first and revisit lifecycle automation after purchasing is stable
C. Review recommended implementation practices and standard lifecycle automation before customizing (Correct)
D. Build the scripts and compare outcomes to standard flows during post-go-live optimization

Explanation

Review standard lifecycle automation first is the strongest answer because the team is customizing core lifecycle behavior before understanding the recommended process, personas, standard flows, asset actions, and capability blueprint. Customization should come after the standard approach is understood and gaps are clearly identified. Complete model normalization first may be important, but it does not address the main risk. The team is about to script major lifecycle processes without reviewing the standard lifecycle design. Implement procurement first creates another sequencing problem. Procurement matters, but lifecycle automation should not be postponed and custom-built without understanding the intended end-to-end design. Build the scripts first is the riskiest path. Comparing custom scripts after go-live means the team may discover too late that they bypassed standard controls, states, or downstream behavior.

Question 3

A preferred vendor contract includes pricing for standard laptops. The regional stockroom is below threshold, but the central warehouse has enough inventory. A procurement analyst wants to place a vendor order immediately to use the contract price before the month ends.

What is the best process decision?

Answer choices

A. Place the vendor order and keep warehouse stock for future requests with longer fulfillment windows
B. Use the contract price to update model cost, then fulfill the request from the central warehouse
C. Source from available internal stock according to stock rules, then purchase only when internal supply cannot meet demand (Correct)
D. Create a purchase order for the regional stockroom and transfer central warehouse inventory after receiving closes

Explanation

Source from internal stock first is the best answer because the central warehouse already has enough inventory. Stock rules should guide the process to use available internal supply before creating a vendor purchase. Place the vendor order may seem attractive because of the contract price, but it ignores existing stock. Buying more while internal inventory can satisfy the need can increase carrying costs and distort inventory planning. Update model cost from contract price does not solve the fulfillment need. The request still needs to be sourced from available inventory, and changing model cost is not the correct substitute for stock movement. Create a purchase order and transfer later is backwards. If the warehouse has inventory now, transfer or source that inventory first instead of purchasing and then moving warehouse stock after receiving.

Question 4

A monitor request is approved and sourced from stock. The request closes successfully, but the monitor still appears available in inventory and is not assigned to the requester. Technicians currently update asset records after closing fulfillment tasks.

Which paired change best addresses the process gap?

Answer choices

A. Add a stock threshold for monitors, then require requester confirmation after fulfillment
B. Connect fulfillment to the asset action that consumes stock, then update assignment through the lifecycle flow (Correct)
C. Normalize the monitor model, then republish the catalog item with the preferred model value
D. Add data certification for assigned monitors, then reconcile mismatches during the next audit

Explanation

Connect fulfillment to the asset action is the best answer because the process should update the physical asset when fulfillment happens. If a monitor is issued from stock, the asset should no longer appear available, and assignment should be updated through the lifecycle flow. Add a stock threshold helps with replenishment, not consumption. It can warn when inventory is low, but it does not assign the issued monitor or remove it from available stock. Normalize the monitor model may improve model consistency, but it does not fix the fulfillment gap. The issue is that the selected physical asset is not being consumed and assigned when the request closes. Add data certification catches bad records later, but it does not prevent the process from creating bad records in the first place. The fix belongs in fulfillment and lifecycle automation.

Question 5

A complex import loads serialized hardware from three sources: a vendor shipment file, a legacy asset spreadsheet, and a data center inventory export. Some rows conflict on assignment, location, lifecycle state, and purchase date. The team wants to reduce duplicates and avoid letting low-trust values overwrite controlled lifecycle data.

Which controls should be included?

Answer choices

A. Transform logic that uses reliable identifiers for matching (Correct)
B. Automatic overwrite of lifecycle state from the newest file timestamp
C. Review queues for uncertain matches and conflicting high-impact fields (Correct)
D. Field mapping rules that distinguish procurement data from operational CI data (Correct)
E. Creation of CIs for every imported row before asset records are created

Explanation

Match using reliable identifiers is correct because duplicate prevention starts with trustworthy matching, such as serial number or other reliable identifiers. Without that, the import can create duplicate records for the same physical device. Review uncertain matches is correct because conflicting assignment, location, lifecycle state, and purchase date values should not always be auto-applied. High-impact conflicts need review instead of blind overwrite. Separate procurement and operational data is correct because different sources are reliable for different kinds of data. Procurement fields and operational CI fields should be mapped and governed based on their purpose. Overwrite from newest timestamp is not safe. The newest file is not automatically the most trusted file, especially for controlled lifecycle data. Create CIs for every row first is a poor import strategy. Not every hardware row needs an immediate CI, and creating CIs before asset records can lose procurement and lifecycle intent while increasing duplicates.