10 free sample questions from a bank of 285, with the correct answers and explanations. No signup required — start practising right now.
1Which of the following data elements are key to an effective Software Asset Management practice within ServiceNow? (Choose four.)
Software allocations
Software models
Foundation data
Software contracts
Software entitlements
Answer: A, B, C, E
The short version
ABCE — Allocations, models, foundation data and entitlements power effective SAM. Four elements together give trustworthy normalization, ownership and rights data. The settled key is ABCE because contracts alone describe paperwork while the other four drive daily compliance.
Key concepts in this question
Software allocations: assignment of installs or rights to users and devices that proves who should consume a license.
Software models: normalized product definitions that map discovery to version, edition and suite structure.
Foundation data: company, department, location and user tables that anchor ownership and cost-center accuracy.
Entitlements: purchased rights from licenses that are reconciled against installs to show compliance.
Contracts: commercial terms that support renewals but do not by themselves normalize or allocate usage.
Why ABCE is correct
ABCE is correct because ServiceNow SAM Pro Fundamentals teaches trustworthy data as the base of all compliance. Models normalize discovery, foundation data fixes ownership, allocations tie consumption to people and devices, and entitlements state what was bought. Together they let reconciliation produce accurate effective license positions, which contracts alone cannot deliver.
Why the others are wrong
D. Software contracts record terms and renewals but are excluded here because they do not normalize installs or assign consumption.
CIS-SAM exam tip
For SAM trustworthy-data questions choose models plus foundation plus allocations plus entitlements; treat contracts as supporting paperwork.
2Which of the following are true of plugins? (Choose two.)
Plugins can be disabled or deactivated when no longer in use.
Plugins can be activated by default in the base ServiceNow system.
When a plugin is active you cannot hide its functionality.
Plugins are stand-alone and do not depend on other plugins being activated.
Plugins are software components that provide specific features and functionalities.
Answer: B, E
The short version
BE — Plugins ship as components and may be active by default in the base system. Some activate automatically while others need admin action or licensed request. The settled key is BE because it states the component nature plus default activation path.
Key concepts in this question
Plugins: packaged software components that add specific tables, roles and workflows to ServiceNow.
Active by default: many core plugins are on in a fresh instance without admin steps.
Admin activation: optional plugins turned on from the plugin list when the feature is needed.
Licensed request: subscription plugins that require ServiceNow entitlement before activation.
Dependencies: plugins may require other plugins, so standalone claims are often false.
Why BE is correct
BE is correct because ServiceNow docs list three enablement paths, including activated by default in the base system, and define plugins as components that provide features. B captures the default-on path while E captures the definitional nature. The other choices misstate lifecycle by claiming plugins never depend on others or can be hidden arbitrarily.
Why the others are wrong
A. Plugins generally cannot be simply disabled at will; deactivation rules and dependencies restrict removal.
C. Active plugin functionality can often be hidden or configured, so the absolute cannot-hide claim is false.
D. Many plugins depend on companion plugins, so standalone-without-dependency is incorrect.
CIS-SAM exam tip
Remember plugins as components with three paths: default on, admin on, or licensed request; dependencies are common.
3When receiving software related to a purchase order in ServiceNow, which data point is mandatory?
Serial Number
Assigned To
Cost
License key
Asset Tag
Answer: E
The short version
E — Asset Tag is mandatory when receiving software against a purchase order. Receiving creates asset records that must be uniquely trackable from day one. The settled key is E because only the tag guarantees that inventory identity.
Key concepts in this question
Purchase order receiving: workflow that converts ordered software into stock or asset records upon delivery.
Asset Tag: unique physical and logical identifier affixed to each asset for lifecycle tracking.
Serial Number: vendor hardware identifier that may be absent for volume software licenses.
Assigned To and Cost: useful fulfillment and finance data that can be completed later, not required to create identity.
License key: activation string that may arrive separately and need not exist at receipt time.
Why E is correct
E is correct because SAM receiving requires a durable key to distinguish each asset through stock, assignment and audit. Course material and receiving forms enforce Asset Tag as the mandatory point, ensuring later reconciliation can join purchase, asset and install. Serial, assignee, cost and license key remain optional at that moment because they vary by fulfillment path.
Why the others are wrong
A. Serial Number is hardware-centric and often missing for software, so it cannot be universally required.
B. Assigned To can be set after stocking, so receiving does not force immediate user assignment.
C. Cost aids finance but is not needed to establish asset identity at receipt.
D. License key may be delivered later or in bulk, so it is not the receiving gate.
CIS-SAM exam tip
For PO receiving think identity first: Asset Tag is mandatory while serial, user, cost and key can follow.
4Which of the following are NOT features of the Publisher workbench navigation tree? (Choose two.)
Expand and collapse tree links
List of all publishers
Software model compliance icons
Filter products
Compliance toggle switch
List of all publishers out of compliance
Answer: B, F
The short version
BF — Publisher lists are not navigation-tree features; filters and icons are. The workbench tree offers filtering, compliance toggle, expand plus collapse, and model icons. The settled key is BF because both B and F describe list pages, not tree controls.
Key concepts in this question
Publisher workbench: SAM view for normalizing publishers, products and compliance in one hierarchy.
Navigation tree: left pane with filter products, compliance toggle, expand and collapse, plus model icons.
List of all publishers: separate tabular view reached outside the tree control itself.
Out-of-compliance list: filtered result set, not a built-in tree node type.
Compliance icons: per-model badges that surface status directly inside the tree.
Why BF is correct
BF is correct because Vancouver docs enumerate tree features as filter products including collapsed items, compliance toggle, expand and collapse links, and software-model compliance icons. Neither a full publisher roster nor an out-of-compliance roster appears in that control list. Therefore B and F are the two items that are not features, matching the NOT-style stem.
Why the others are wrong
A. Expand and collapse links are explicitly documented as tree behavior.
C. Software model compliance icons are core tree badges for quick status.
D. Filter products with active filtering is a headline tree capability.
E. Compliance toggle switch is listed as a native tree control.
CIS-SAM exam tip
For workbench tree memorize filter plus toggle plus expand-collapse plus icons; publisher lists live outside the tree.
5Mechanism for mapping data from the import set table to the permanent table in ServiceNow is called:
Mapping Assist
Transform Map
Reconciliation Map
Discovery Map
Answer: B
The short version
B — Transform Map moves import-set rows to permanent tables. Staging data must be field-mapped before it becomes trustworthy. The settled key is B because transform maps define that import-to-target relationship.
Key concepts in this question
Import set table: staging area holding raw rows from file, JDBC or integration loads.
Transform Map: set of field maps plus scripts that dictate how staged fields populate target tables.
Mapping Assist: helper that suggests mappings but is not the mechanism name itself.
Reconciliation and Discovery maps: unrelated concepts for other matching or network tasks, not import staging.
Trustworthy data: SAM goal that depends on clean transforms from imports.
Why B is correct
B is correct because ServiceNow Fundamentals teaches transform maps as field-map collections linking import sets to existing tables. Admins choose source and target, map columns, add coalesce keys and run the transform to create or update assets and models. That is precisely the mechanism for mapping data from import set to permanent table.
Why the others are wrong
A. Mapping Assist aids creation of maps but is not the formal artifact that executes the row movement.
C. Reconciliation Map is not the import-set to target construct used in system import sets.
D. Discovery Map relates to network discovery patterns, not to import-set transformation.
CIS-SAM exam tip
When you see import set to permanent table think Transform Map with field maps and coalesce keys.
6In which stage of the ServiceNow Implementation Methodology (SIM) is the purpose to define processes and requirements for engagement and finalize delivery plan and user stories?
Transition
Close
Create
Prepare
Initiate
All of the above
Answer: D
The short version
D — Prepare defines processes and finalizes delivery plan plus user stories. SIM moves from initiate to prepare before building. The settled key is D because workshops plus story refinement are the prepare purpose.
Key concepts in this question
SIM stages: Initiate, Prepare, Create, Transition and Close as the ServiceNow delivery lifecycle.
Initiate: kickoff and scope framing that precedes detailed process design.
Prepare: workshops to understand process and platform needs plus timeline and story finalization.
Create: build, configure and test sprints that realize the prepared stories.
Transition and Close: rollout, adoption and handover after creation work.
Why D is correct
D is correct because documentation describes Prepare as holding workshops, finalizing engagement timelines and refining configuration requirements into stories. That matches the stem wording about defining processes and finalizing delivery plan plus user stories. Other stages either start the engagement or execute and deploy the already-prepared plan.
Why the others are wrong
A. Transition focuses on deployment readiness and go-live, not initial process definition.
B. Close wraps lessons learned and handover after delivery, not story shaping.
C. Create builds the solution from already-finalized stories rather than defining them.
E. Initiate launches scope and team, leaving detailed requirements to Prepare.
F. All of the above is too broad because only Prepare owns this definition purpose.
CIS-SAM exam tip
Link Prepare to workshops plus stories; Initiate starts, Create builds, Transition ships, Close ends.
7What is used to determine if installations are a part of a suite only when the suite parent is not discovered on a device?
inference percent
product results
software model
model bundles
Answer: A
The short version
A — Inference percent decides suite membership when the parent is undiscovered. Suites list components, and the percent sets how many must appear to infer the suite. The settled key is A because only that threshold applies in the parent-missing case.
Key concepts in this question
Software suites: bundles such as office productivity where parent plus children define licensing.
Suite parent: top-level product record that, when discovered, directly proves the suite.
Inference percent: percent of suite components required to recognize the suite without the parent.
Product results: discovery outputs that feed normalization but do not set the suite threshold.
Models and bundles: structures for product definitions, distinct from the inference calculation.
Why A is correct
A is correct because SAM suite logic uses inference criteria only when the suite parent is absent from the device. If enough child installs meet the inference percent, ServiceNow infers suite presence for compliance. That conditional threshold is documented in Practical Management and matches the stem exactly.
Why the others are wrong
B. Product results describe what was found, but they do not define the percent threshold for suite inference.
C. Software model is the normalized definition, not the numeric inference rule.
D. Model bundles group related models yet do not encode the parent-missing percent logic.
CIS-SAM exam tip
No parent on device means check inference percent; parent present means direct suite recognition.
8Which statements are true in regards to ServiceNow’s Client Software Distribution (CSD) functionality? (Choose two.)
Removes software daily utilizing a scheduled job.
ServiceNow does not have Client Software Distribution.
The first stage in the CSD process flow is configuration.
CSD can automatically distribute and reclaim software without a license for Orchestration.
Answer: A, C
The short version
AC — CSD removes software daily by job and starts with configuration. Distribution needs orchestration rights and follows a staged flow. The settled key is AC because daily removal plus configuration-first are the true CSD traits.
Key concepts in this question
Client Software Distribution: ServiceNow capability to distribute and reclaim desktop software using workflows.
Scheduled removal job: daily automation that reclaims installs no longer entitled or requested.
Configuration stage: first CSD flow step that defines targets, packages and approvals.
Orchestration license: separate subscription required for automated distribution actions.
Nonexistent CSD: incorrect claim; the feature exists with defined stages and licensing.
Why AC is correct
AC is correct because CSD docs show configuration as the opening stage before distribution and a daily scheduled job that removes software. D fails since automatic distribute and reclaim without Orchestration licensing is not allowed. That licensing nuance plus the staged flow makes A and C the jointly true statements.
Why the others are wrong
B. ServiceNow does provide Client Software Distribution, so denial of its existence is false.
D. Automatic distribution without Orchestration licensing is false because a separate subscription is needed.
CIS-SAM exam tip
For CSD remember config first plus daily reclaim job plus Orchestration license needed for auto actions.
9Which of the following SAM roles has permission to grant a user the script writing capability?
discover_admin
sam_admin
sam_developer
asset
Answer: C
The short version
C — sam_developer can grant script-writing capability. Higher SAM roles inherit lower rights, and developer sits above admin for customization. The settled key is C because only that role carries the grant power.
Key concepts in this question
SAM roles: tiered permissions from asset through admin to developer for increasing customization.
sam_developer: top SAM customization role that contains sam_admin and adds scripting rights.
sam_admin: operational admin without the developer-level script grant authority.
discover_admin: discovery-focused role unrelated to SAM script capability grants.
asset: inventory user role with no administrative grant power.
Why C is correct
C is correct because sam_developer inherits sam_admin and adds permission to allow script writing for users. Course and role docs position developer as the customization authority that can elevate scripting. The other roles lack that inheritance or scope, so only C satisfies the grant-capability requirement.
Why the others are wrong
A. discover_admin governs discovery schedules and credentials, not SAM script grants.
B. sam_admin manages SAM operations but does not include developer script-grant rights.
D. asset provides basic inventory access with no power to grant scripting.
CIS-SAM exam tip
For script-grant power in SAM choose sam_developer; it contains sam_admin plus customization rights.
10Within the Capability Blueprint there are 4 tiers identified. Which tier is identified as Tier 1?
Strategic Conformance
Operational Integration
Trustworthy Data
Practical Management
Answer: C
The short version
C — Trustworthy Data is Tier 1 of the Capability Blueprint. The blueprint stacks data first, then management, integration and conformance. The settled key is C because Tier 1 must be the data foundation.
Key concepts in this question
Capability Blueprint: four-tier SAM maturity model guiding implementation order.
Tier 1 Trustworthy Data: normalization, ownership and entitlement accuracy as the base.
Practical Management: higher-tier processes that consume trustworthy data for optimization.
Operational Integration: connecting SAM to procurement and ITSM flows after basics are solid.
Strategic Conformance: top-tier compliance and planning built on lower tiers.
Why C is correct
C is correct because the blueprint explicitly places Trustworthy Data at Tier 1. Without clean models, discovery and entitlements, later tiers cannot produce reliable compliance or savings. Training and blueprint diagrams consistently label that foundation as the first tier, so C matches the settled key.
Why the others are wrong
A. Strategic Conformance is an upper tier focused on audit readiness, not the Tier 1 base.
B. Operational Integration connects processes above the data base, so it cannot be Tier 1.
D. Practical Management optimizes suites and reclaim using data, placing it above Tier 1.