PowerExams Prepare. Practice. Pass.

CIS-SAM Study Guide — Certified Implementation Specialist, Software Asset Management (SAM Professional)

Trademark disclaimer: ServiceNow, Now Platform, and all related product and release names are trademarks of ServiceNow, Inc. This guide is an independent, original commercial exam-preparation work and is not affiliated with, endorsed by, or sponsored by ServiceNow, Inc. All factual content is grounded in publicly available official ServiceNow documentation and learning resources; see grounding.md for source URLs.

How to use this guide. Domains below are ordered by exam weight (heaviest first), so your study time tracks the blueprint. The two largest domains — Practical Management of Software Compliance (30%) and Data Integrity (28%) — together account for well over half the exam, so master those first. Each section gives the concepts in original prose, followed by the platform mechanics and the common exam traps. A consolidated Fast-recall cheat list sits at the end.

Domain 3 — Practical Management of Software Compliance (30%)

This is the largest domain and the heart of SAM Professional. The goal is to turn raw data into a defensible, reconciled license position and then act on it.

Entitlements, allocations, and use rights

An entitlement records what your organization is legally permitted to do with a software product: how many rights you purchased, the license metric that governs counting, the publisher/product, the purchase and contract references, and any upgrade, downgrade, or second-use rights. Entitlements are matched to software models so that rights line up with the licensable units that installations normalize to.

An allocation assigns specific rights from an entitlement to a particular user or device. Allocations matter most for named-user and per-device metrics, where the question "who/what is this license assigned to?" determines compliance. Use rights (upgrade/downgrade rights, multi-use, virtualization rights, and product use rights published by the vendor) modify how raw consumption is counted — for example, a license for a newer edition may cover an older installed edition through downgrade rights.

Reconciliation and the Effective License Position (ELP)

Reconciliation is the engine that compares rights owned (entitlements) against rights consumed (normalized installations and measured usage) for each software model, then produces a software model result with a compliance status: compliant, over-licensed (surplus), or non-compliant (shortfall/exposure). The reconciled output is the Effective License Position — the single number that tells you, per publisher and product, whether you have enough licenses.

Reconciliation depends on three things being correct: (1) installs normalized to the right software model, (2) each model carrying the correct license metric, and (3) entitlements matched to those models. If a model has installs but no license metric, reconciliation cannot count consumption for it — a frequent exam trap.

True-up is the corrective purchase that closes a shortfall surfaced by the ELP; the reconciled position is what you take into a vendor true-up or audit defense. Surplus positions feed cost-optimization (harvesting and not re-buying).

License metrics

A license metric defines how consumption is counted. You must recognize the major families:

  • Per-device / per-installation — one right per installed copy or per machine.
  • Named user — one right per uniquely identified user; usage and allocation to users drive the count.
  • Concurrent user — rights consumed by simultaneous active users.
  • Per-core — count physical (or virtual) cores on the host; requires accurate CPU/core data on the device CI.
  • Core factor (Oracle) — physical cores multiplied by a core factor taken from the vendor's core factor table (processor-type-dependent), then rounded per vendor rules. Oracle Processor licensing for Database and options (Partitioning, RAC, etc.) uses this.
  • IBM PVU (Processor Value Unit) — cores multiplied by a per-core PVU value from IBM's PVU table; total PVUs determine licenses. RVU (Resource Value Unit) is a related IBM metric.
  • Sub-capacity — licensing only the virtual capacity actually allocated (e.g., vCPUs in a VM) rather than full host (full-capacity) capacity, subject to vendor eligibility and tooling rules. Accurate VM-to-host relationships are essential.

Per-core, core-factor, PVU, and sub-capacity all break if the host's core count, processor type, or virtualization topology is wrong — which is why this domain leans heavily on the host CI being accurate.

Remediation

When the ELP shows exposure or waste, remediation closes the gap: reclaim unused installs (uninstall/harvest where usage data shows software unused), reassign harvested rights, purchase additional entitlements (true-up) where reclamation is insufficient, or apply use rights you had not been crediting. Software usage data (last-used date, run frequency) is the primary evidence for reclamation candidates.

Exam traps (Domain 3)

  • A software model with installs but no license metric cannot be counted — fix the model, not the entitlement.
  • Allocation (to a user/device) is distinct from entitlement (what you own). Multi-select questions test the difference.
  • Sub-capacity is not automatic; it requires correct virtualization data and vendor eligibility.
  • True-up is a purchase action driven by the reconciled shortfall, not a recount.

Domain 2 — Data Integrity: Attributes and Sources (28%)

Compliance is only as trustworthy as the data feeding it. This domain is about getting clean, normalized, de-duplicated data into SAM.

Software discovery and normalization

Raw software is collected from inventory sources and lands as discovered software in installation records. Normalization maps each raw record (raw publisher/product/version strings, often messy like "Msft Corp") to a curated, canonical software model via the software discovery model (the discovery map). Normalization standardizes publisher, product, version, and edition so that one real product no longer appears under many slightly different names.

Records the Content Service cannot match automatically are flagged for review (a normalization queue / "needs review" state) and can be manually normalized. Best practice is to subscribe to Content Service updates and publisher packs so the bulk of normalization happens automatically and ongoing.

The Content Service

The SAM Content Service (Content Library) is a ServiceNow cloud service delivering curated, regularly updated publishers, products, software models, discovery maps, and license metrics, plus publisher packs (deeper, publisher-specific content, e.g., Microsoft, Oracle, IBM, Adobe) and lifecycle (EOL/EOS) data. Subscribing means customers do not hand-build normalization content. Newly enabled content normalizes future and re-processed installs; it does not retroactively change already-completed reconciliation results until reconciliation reruns — a common exam point.

Data sources

SAM consumes software inventory and usage from multiple sources:

  • ServiceNow Discovery (agentless, MID Server–based) and Agent Client Collector.
  • Microsoft SCCM / Configuration Manager via the Service Graph Connector for SCCM (and the SCCM Software Usage plugin for usage/metering data).
  • Microsoft Intune via the Service Graph Connector for Intune (modern/mobile and remote endpoints).
  • Other third-party inventory tools.

When the same device arrives from multiple sources (e.g., Discovery and SCCM), CMDB Identification and Reconciliation (IRE) uses identification rules to match and de-duplicate so you do not get duplicate CIs or double-counted installs. Data source precedence decides which source "wins" for a given attribute.

Attributes that drive counting

  • License metric on the model — without it, no count.
  • Host/device CI link on each install — ties consumption to a machine; essential for per-core.
  • CPU / core count and processor type on the host — essential for per-core, core-factor, and PVU.
  • VM-to-host relationship — essential for sub-capacity and cluster-wide Oracle/IBM counts.
  • User reference on the install — essential for named-user metrics.
  • Edition and version — affect which model/metric applies and which use rights are available.

Exam traps (Domain 2)

  • Unnormalized installs cause undercounting; the root cause of a low count is usually "installs not normalized," not "entitlement missing."
  • Duplicate installs from two sources inflate counts; resolve via IRE/identification rules, not by deleting one source blindly.
  • Missing core/CPU data on hosts silently corrupts per-core/PVU/Oracle positions.
  • Missing user reference breaks named-user reconciliation.
  • Enabling a publisher pack normalizes data but does not rewrite past reconciliation results automatically.

Domain 1 — Software Asset Core Overview & Fundamentals (14%)

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 to software models (using Content Service + discovery maps) → 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.

Domain 5 — Extending SAM (15%)

SAM for SaaS / SaaS License Management

SAM extends beyond on-prem installs to SaaS subscriptions. SaaS License Management integrates with cloud providers — most notably Microsoft 365 (Office 365) and Adobe Creative Cloud — to pull subscription entitlements and actual usage (active vs. inactive accounts, last-activity). The value is identifying unused or under-used SaaS subscriptions for reclamation/downgrade and right-sizing renewals, mirroring on-prem reconciliation but for subscription seats. Dashboards (e.g., the Office 365 & Adobe Cloud dashboard) and the license usage view / workbench surface optimization candidates.

Publisher packs

Publisher packs are content extensions in the Content Service that add deep, publisher-specific normalization, license-metric, and product-use-rights logic for major vendors (Microsoft, Oracle, IBM, Adobe, SAP, etc.), improving reconciliation accuracy for complex licensing (e.g., Oracle options, Microsoft 365 mappings).

Software model lifecycle and retirement

Software models carry lifecycle data — End of Life (EOL) and End of Support (EOS) dates, often supplied by the Content Service as calculated lifecycles. This drives risk reporting (unsupported software), refresh planning, and model retirement. Lifecycle states should align to CSDM standard lifecycle values.

CMDB / CSDM alignment

SAM data must align to the Common Service Data Model (CSDM): software installs reference host CIs, software models map cleanly, and lifecycle states use CSDM standard values. Good CSDM/CMDB alignment is what makes per-core, virtualization, and reclamation calculations trustworthy.

Exam traps (Domain 5)

  • SaaS management uses actual usage / activity to find waste, not just seat counts.
  • Publisher packs improve accuracy for specific vendors; they are not generic.
  • Lifecycle (EOL/EOS) is largely content-driven, and should map to CSDM lifecycle values.

Domain 4 — Operational Integration of Software Processes (13%)

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

Fast-recall cheat list

  • Hierarchy: Publisher → Product → Software model (licensable unit = edition/version).
  • Pipeline: Discover/import → normalize to software model → match entitlements → reconcile → Effective License Position (ELP) → remediate.
  • Content Service = ServiceNow cloud library of publishers, products, software models, discovery maps, license metrics, publisher packs, and EOL/EOS lifecycle data. Subscribe for automatic, ongoing normalization.
  • Normalization maps messy raw strings to canonical models; unmatched records go to a needs-review queue for manual normalization.
  • Entitlement = what you own (with metric, use rights). Allocation = rights assigned to a specific user/device. Use rights = upgrade/downgrade/multi-use that change the count.
  • Reconciliation compares owned vs. consumed per model → compliant / surplus / shortfall. No license metric on a model → cannot count.
  • Metrics: per-device, named user, concurrent user, per-core, Oracle core factor (core factor table), IBM PVU (PVU table) / RVU, sub-capacity (virtual capacity, needs VM-host data).
  • ELP drives true-up (close shortfall) and harvesting (use surplus).
  • Reclamation uses usage data (last-used) to find unused installs; SCCM Software Usage is the common usage source.
  • Data sources: ServiceNow Discovery (MID Server), Agent Client Collector, SCCM (Service Graph Connector + Software Usage), Intune (Service Graph Connector), third-party tools.
  • De-dup across sources via CMDB IRE / identification rules; data source precedence decides winning attributes.
  • Per-core / Oracle / PVU require accurate CPU/core count, processor type, VM-to-host on the host CI.
  • Named user requires the user reference on the install.
  • SAM for SaaS: integrates Microsoft 365 and Adobe Creative Cloud; uses actual usage/activity to find unused subscriptions for reclamation/right-sizing.
  • Lifecycle: EOL/EOS largely content-driven (calculated lifecycles); align to CSDM standard lifecycle values.
  • CSDM/CMDB alignment underpins trustworthy per-core, virtualization, and reclamation results.
  • Enabling new content/publisher pack normalizes future/re-processed installs but does not rewrite completed reconciliation until it reruns.
  • Cadence: schedule discovery + content updates + reconciliation regularly to keep the ELP accurate.