Text preview & study summary

ServiceNow CIS-SAM - Software Asset Management Implementation - License Compliance Discovery Optimization

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 ServiceNow SAM administrator is configuring a Publisher Pack for Microsoft. After installing the pack, what capabilities does it provide that are NOT available in standard SAM?

Answer choices

  • A. Discovery of Microsoft software installations on Windows endpoints

  • B. Pre-built software models, normalization rules, license metric definitions, and compliance rules specific to Microsoft's licensing terms, including SA (Software Assurance) downgrade rights (Correct)

  • C. Integration with Microsoft License Center for automatic entitlement import via API

  • D. Custom dashboards for Microsoft spending analytics and renewal forecasting

Explanation

Publisher Packs (formerly Technology Packs) provide pre-built, publisher-specific content including: normalized software models for all major Microsoft products, license metric types aligned with Microsoft's actual licensing (User CAL, Device CAL, Core, Server+CAL), SA (Software Assurance) benefit rules including downgrade rights and version upgrade rights, and compliance calculation logic that reflects Microsoft's actual licensing policies. This content would take months to manually configure. Option A (discovery) works independently of Publisher Packs — discovery is handled by MID Server probes. Option C (License Center API) is a separate integration capability. Option D (spending dashboards) is an analytics feature, not a core Publisher Pack feature.

Question 2

During a Microsoft EA (Enterprise Agreement) reconciliation, a SAM manager finds that the compliance dashboard shows 2,400 Office 365 E3 licenses consumed but only 2,000 licenses purchased. The organization bought 2,000 E3 seats with a true-up clause. Which ServiceNow SAM component tracks the purchased entitlements and triggers the compliance shortfall alert?

Answer choices

  • A. Software Installation records linked to the CI class "Software"

  • B. License Entitlements associated with the software model, with quantity set to 2,000 and a recalculation schedule (Correct)

  • C. Contract records in the Contract Management module with license count fields

  • D. Discovery schedules set to count active Office 365 user accounts via API

Explanation

In ServiceNow SAM Pro, License Entitlements are the records that define the number of rights (licenses) purchased for a software model. When the compliance engine runs, it compares entitlement quantity (2,000) against consumption (2,400) and calculates a shortfall of 400, triggering compliance alerts. The recalculation schedule ensures the position is kept current. Option C (Contract records) stores financial and vendor terms but isn't the compliance calculation driver — entitlements are linked to contracts but drive the SAM compliance engine separately. Option A (installations) represents consumption, not entitlement. Option D (API counts) is how you might discover consumption but doesn't represent purchased rights.

Question 3

A global financial institution is implementing ServiceNow SAM Pro. They have Oracle Database licenses purchased under a Processor metric. During setup, which software model configuration correctly represents Oracle Database under Processor licensing?

Answer choices

  • A. Create a software model with metric type "Per Installation," set processor multiplier to 0.5 for Intel cores

  • B. Create a software model with metric type "Processor," configure the core factor table based on Oracle's Core Factor Table, and associate the model with discovered Oracle DB software installations (Correct)

  • C. Create a software model with metric type "Named User Plus" and set the minimum per-processor user count to 25

  • D. Create a software model with metric type "Per Device" and rely on CMDB hardware records for processor counts

Explanation

Oracle Processor licensing requires a software model with metric type "Processor." ServiceNow SAM Pro includes Oracle's Core Factor Table, which adjusts core counts based on processor type (Intel = 0.5 factor, SPARC = 0.25–1.0). The model must be associated with discovered Oracle DB installations so the compliance engine can correctly calculate license consumption. Option A incorrectly uses "Per Installation" metric and applies a flat 0.5 factor without the Core Factor Table. Option C applies a Named User Plus metric which is a different Oracle licensing model. Option D uses "Per Device" which doesn't account for processor/core calculations.

Question 4

A SAM analyst is reconciling Autodesk AutoCAD licenses. The organization has moved from perpetual licenses to Autodesk's subscription model (Flex tokens). How should ServiceNow SAM model Autodesk Flex token consumption?

Answer choices

  • A. Model each user as a Named User license and track by department

  • B. Create a Flex token software model with "Token" metric type, configure token entitlements based on purchased token pack, and integrate with Autodesk's usage reporting to track token consumption per product (Correct)

  • C. Use the standard "Per Installation" metric since all Autodesk products are perpetual

  • D. Create one software model per AutoCAD feature (2D Drafting, 3D Modeling, etc.) with separate entitlements

Explanation

Autodesk Flex (formerly Token Flex) uses a consumption-based model where tokens are consumed per product per day. SAM Pro models this with a Token metric type, where the entitlement represents total purchased tokens and consumption is tracked based on actual usage reports from Autodesk. Integration with Autodesk's reporting API or regular import of usage data shows token burn rate and remaining balance. This is fundamentally different from perpetual (per-installation) or subscription (per-user) licensing. Option A (Named User) applies to Autodesk's individual subscription model, not Flex tokens. Option C incorrectly assumes perpetual licensing. Option D creates unnecessary fragmentation — Flex tokens span all Autodesk products from a single pool.

Question 5

A SAM team wants to implement software reclamation for Adobe Acrobat Pro. They need to identify installations where the software has not been launched in 90 days and automatically uninstall it. Which ServiceNow SAM Pro features work together to accomplish this?

Answer choices

  • A. Software Usage Rights table + Scheduled Report + Email Notification to IT for manual uninstall

  • B. Software Usage data from the usage metering agent, Reclamation Candidate identification in SAM Workspace, and integration with a software distribution tool (SCCM/Intune) to execute uninstall (Correct)

  • C. Discovery schedule with "Application Usage" probe + Business Rule to set Installation Status = "Unused" + manual review

  • D. Normalization Data Services + License Entitlement recalculation + Contract reconciliation workflow

Explanation

Software reclamation in SAM Pro requires three components: (1) Usage data — collected via usage metering agents (or integrated tools) that record last-used timestamps and launch counts; (2) Reclamation Candidate identification — SAM Workspace applies configurable thresholds (e.g., 90 days no use) to flag installations as reclamation candidates; (3) Distribution tool integration — ServiceNow connects to SCCM, Intune, or similar tools via IntegrationHub to trigger automated uninstall workflows. Option A lacks the automated execution and relies on manual IT intervention. Option C uses Discovery (which handles hardware/software inventory, not usage metering) and manual review. Option D describes license compliance activities, not reclamation.