Operational Integration of Software Processes
About 13% of the CIS-SAM exam — see all 5 domains.
This domain connects SAM to ongoing IT operations and other ServiceNow processes.
Inventory and usage integrations
- SCCM integration: import software inventory and usage via the Service Graph Connector for SCCM; the SCCM Software Usage plugin brings metering/usage data used for reclamation.
- Intune integration: import modern/remote-endpoint inventory via the Service Graph Connector for Intune.
- Reclamation rules: rules (including SCCM-usage-driven rules) identify unused installs and can trigger software installation optimization and removal (reclaim) workflows, often via Flow or requests to uninstall.
Cadence and operations
- Run discovery, content updates, and reconciliation on a regular cadence so the ELP stays current; content changes only take effect on the next normalization/reconciliation run.
- Troubleshoot failed SCCM/Intune imports by checking source-record completeness (missing required fields), connector configuration, and import/transform logs.
Procurement and contracts
Entitlements link to contracts and procurement records (purchase orders, software contracts, maintenance/support agreements). This ties owned rights to commercial reality, supports renewal management, and feeds true-up decisions.
Exam traps (Domain 4)
- Usage/metering for reclamation typically comes from the SCCM Software Usage data, not bare inventory.
- Content/discovery changes require a rerun to affect results; scheduling cadence matters.
- First troubleshooting step for failed imports is usually source data / required fields, then connector config.
Sample questions from this domain
Three of the 39 in this domain, with the reasoning. The full set is in the question bank.
When a new employee is onboarded and requests software through the service catalog, how can SAM be involved?
- A. SAM runs reconciliation when the request is submitted and auto-approves it if compliant
- B. SAM can check entitlement availability and allocate a license as part of fulfillment ✓
- C. SAM creates a new software model for each request so the install can be normalized
- D. SAM logs the request as a reclamation candidate until Discovery finds the install
Why: A fulfillment flow can call SAM to check whether rights are available for the requested product and then create an allocation for the new employee, so the request stays compliant. Reconciliation is a scheduled or on-demand calculation that produces product results; it does not approve catalog requests. Software models are defined once per product and reused by every install that matches their criteria, not created per request. Reclamation candidates come from reclamation rules that find unused or underused installs, not from new requests.
How does integrating SAM with the procurement process improve license data?
- A. Purchases of software automatically create or update entitlements, keeping owned rights accurate ✓
- B. Purchase orders automatically create software installation records, keeping consumption accurate
- C. Purchase requests automatically update the normalization library, keeping discovery models accurate
- D. Purchase orders automatically set product results to Compliant, keeping reconciliation data current
Why: Procurement integration turns software purchases into new or updated entitlements, which keeps the owned rights side of reconciliation accurate without manual re-entry. Software installation records come from discovery and inventory sources, not from purchase orders. The normalization library is maintained out of the box and kept current by the Content Service, not by purchasing. Compliant or Not Compliant product results are produced by reconciliation comparing rights with consumption; a purchase order cannot set them.
When an employee is offboarded, what SAM action helps optimize licenses?
- A. Retire the software model so the departing user's installs stop counting
- B. Reclaim the licenses allocated to that user so they can be reused ✓
- C. Transfer the user's allocations to their manager's department instead
- D. Increase the entitlement quantity to cover the replacement hire
Why: Offboarding should reclaim the rights allocated to the departing user (remove the allocation and the installs) so they return to the available pool and can be reused, for example by a replacement hire. Retiring the software model affects every install of the product across the organization, not one user. Allocations are made to a specific user or device, not to a department, and moving them to a manager does not free anything. Increasing the entitlement quantity buys rights the organization is about to get back for free.