Software Asset Core Overview & Fundamentals
About 14% of the CIS-SAM exam — see all 5 domains.
SAM Professional is the dedicated application that ingests software discovery data, manages entitlements, and produces a reconciled compliance position. It sits on top of the CMDB (which stores the CIs SAM consumes) and works alongside Hardware Asset Management (HAM) and ITSM, but only SAM reconciles software licenses.
The data hierarchy: Publisher → Product → Software Model. One publisher offers many products; one product can have many software models (different versions/editions). A software model is the licensable unit (a specific edition/version of a product) and is what both installations (via normalization) and entitlements link to.
The pipeline: discover/import software → normalize discovered software (normalization library, kept current by the Content Service) and match it to software models → match entitlements to models → reconcile → produce the Effective License Position → remediate. The business outcome of reconciliation is the comparison of owned vs. consumed, revealing compliance, surplus, or audit exposure.
Core capabilities of SAM Pro include software normalization, entitlement and contract management, license reconciliation/ELP, software usage and reclamation, lifecycle (EOL/EOS) insight, and SaaS license management.
Exam traps (Domain 1)
- The CMDB stores CI data SAM consumes; it does not itself reconcile licenses.
- Software model = edition/version (licensable unit), not a server, contract line, or discovery probe.
- Know the direction of the hierarchy (publisher → product → model), not the inverse.
Sample questions from this domain
Three of the 42 in this domain, with the reasoning. The full set is in the question bank.
Which ServiceNow application is the primary engine for managing software entitlements, reconciling license positions, and identifying compliance risk?
- A. Hardware Asset Management (HAM) Professional
- B. Contract Management for software agreements
- C. Configuration Management Database (CMDB)
- D. Software Asset Management (SAM) Professional ✓
Why: SAM Professional is the application that manages software entitlements, reconciles them against normalized installation and usage data, and produces the compliance position that shows license risk. HAM Professional manages the lifecycle of hardware assets, not software license positions. Contract Management stores vendor agreement terms and renewal dates, but it does not reconcile rights against consumption. The CMDB holds the hardware and software installation data that SAM consumes, but it does not calculate license positions itself.
In the ServiceNow SAM data model, what does a software model primarily represent?
- A. A raw install record that discovery captures for one software title on one device
- B. A purchased quantity of license rights recorded from a vendor order
- C. A license metric definition that controls how a product is counted
- D. A specific edition and version of a software product that can be licensed ✓
Why: A software model represents a licensable product at the level of publisher, product, version and edition. Entitlements reference it, and normalized discovery models are matched to it by its model criteria. A raw install of one title on one device is a software installation record, which references a discovery model. A purchased quantity of rights is the software entitlement. The license metric is also a field on the entitlement; the software model form has no license metric field.
A SAM administrator wants to understand the relationship between publishers, products, and software models. Which statement is correct?
- A. A publisher has many products, and a product can have many software models ✓
- B. A software model can span many products, and a product can have many publishers
- C. Each product has one software model, and a publisher can have many products
- D. A product can have many publishers, and each publisher has one software model
Why: The hierarchy runs publisher to product to software model: one publisher offers many products, and one product can be represented by many software models for its different versions and editions. Saying a model spans many products, or that a product has many publishers, inverts the hierarchy, since each product belongs to one publisher and each model to one product. Limiting a product to a single software model ignores that versions and editions are modeled separately, so it is also wrong.