The Software Model Lifecycle Report is the specific tool within ServiceNow Software Asset Management (SAM) designed to address this requirement. This report provides a comprehensive view of all software models and their associated lifecycle phases, including General Availability, End of Life (EOL), and End of Support (EOS) dates. By running this report, an organization can proactively identify software that is, or will soon become, unsupported. This visibility is crucial for planning upgrades and mitigating the security vulnerabilities associated with using EOL/EOS software.

A. Software Models with deactivated discovery maps: This indicates which software models are no longer being actively discovered, which is a configuration status, not a direct report on lifecycle risk.

B. License Position Report: This report focuses on license compliance, showing whether an organization is over-licensed or under-licensed. It does not primarily report on software lifecycle status.

D. Software Product Lifecycle Report: While related, this report operates at the higher 'Product' level (e.g., Microsoft Office). The 'Model' level report (e.g., Microsoft Office 2016) is more granular and actionable for identifying specific vulnerable versions.

E. License Workbench Report: The License Workbench is an interactive dashboard for managing and remediating license compliance issues, not a static report designed to show lifecycle information.

1. ServiceNow Product Documentation - Software lifecycle reports: "View the lifecycle information for all software models in your environment. Use this report to determine which software is nearing end-of-life

end-of-support

or is already expired. You can use this information to mitigate any risks to your organization." (ServiceNow. (2024). Software lifecycle reports. Washington DC release documentation. Section: Software Model Lifecycle Report).

2. ServiceNow Product Documentation - License Position Report: "The License Position Report shows the compliance status of all software models that are in use." (ServiceNow. (2024). License Position Report. Washington DC release documentation. Section: License Position Report). This confirms its purpose is compliance

not lifecycle.

The ServiceNow Software Asset Management (SAM) integration with Microsoft System Center Configuration Manager (SCCM) specifically imports software metering data to facilitate reclamation analysis. According to official ServiceNow documentation, the two key data points imported from the SCCM database for this purpose are the Last used date and the Total usage time (measured in minutes). This data populates the Software Usage [sampswusage] table and is then used by reclamation rules to identify software that is installed but not being used, or is used infrequently, making it a candidate for license harvesting.

A. Number of Times Used: While SCCM may collect a usage count, the standard ServiceNow SAM integration for reclamation focuses on the last usage date and total duration, not the frequency count.

B. Average Use Time: The integration imports the cumulative total usage time, not a calculated average. Reclamation rules are based on the total duration over a period.

D. Last Used Only: This option is incomplete. The total usage time is also a critical data point imported from SCCM and used in reclamation rules to determine underutilization.

1. ServiceNow Product Documentation - Microsoft SCCM software usage import: "The software usage import brings in software usage data from the SCCM database. The software usage data that is imported is Last used date

and Total usage time (in minutes)." (This statement is found in the documentation for recent ServiceNow releases

such as Vancouver

Utah

and Tokyo

under the Software Asset Management product section).

2. ServiceNow Product Documentation - Data imported by the SCCM integration: The documentation details the data sources for the integration. The "SCCM 2016 Software Usage" data source maps the LastUsage field from SCCM to the lastusedtime field in ServiceNow and the UsageTime field to totalusagetime.

3. ServiceNow Product Documentation - Create a software reclamation rule: When creating a reclamation rule

the conditions can be configured based on "Total usage duration (days)" and "Last used date

" which directly correspond to the data imported from SCCM.

When reviewing a normalization suggestion in ServiceNow Software Asset Management, an asset manager has two primary actions. They can Accept the suggestion, which automatically updates the associated discovery model with the suggested, normalized values for Publisher, Product, and Version. Alternatively, they can Reject the suggestion. Rejecting a suggestion prevents the same normalization rule from being applied to that specific software package in future normalization runs, effectively ignoring it permanently unless manually addressed.

C. Save: "Save" is a generic UI action to save changes to a record form but is not a specific workflow action for processing a normalization suggestion.

D. Ignore: The correct term for this action is "Reject." The description of making fields read-only is also inaccurate.

E. Create: The "Accept" action performs the update, which may result in the creation of a new discovery model if one doesn't exist, but "Create" is not the name of the action itself.

1. ServiceNow Product Documentation - Review and act on normalization suggestions:

"When you review a normalization suggestion

you can either accept or reject it."

Accept a normalization suggestion: "When you accept a suggestion

the discovery model is updated with the suggested values. The state of the suggestion changes to Accepted."

Reject a normalization suggestion: "When you reject a suggestion

the suggestion is ignored. The next time the scheduled job is executed

it does not pick the same package or rule that was rejected previously. The state of the suggestion changes to Rejected."

Source: ServiceNow Product Documentation

"Software Asset Management workspace > Normalization > Review and act on normalization suggestions".

The Vendor Catalog in ServiceNow is specifically designed to maintain a list of products and services offered by a particular third-party vendor. It is used within the Procurement application to streamline the purchasing process. When a user needs to request an item, they can browse the Vendor Catalog to see what is available from approved suppliers, including vendor-specific part numbers and pricing. This directly aligns with the concept of a listing of goods offered by a third party.

A. Service Catalog: This catalog contains services and items offered internally by an organization to its employees, such as IT support or new hardware requests, not a list of goods from an external vendor.

B. Model Catalog: This is a component of the Product Catalog. It defines specific versions or configurations of a product but is not a list of all items a particular vendor offers for sale.

C. Item Catalog: This is a generic term. In ServiceNow, it typically refers to the individual "Catalog Items" that make up the Service Catalog, which are for internal consumption.

E. Product Catalog: This is a master repository of all product models that an organization owns or may procure. It is a broader, centralized list, whereas a Vendor Catalog is specific to one vendor's offerings.

1. ServiceNow Product Documentation - Vendor Catalog Items: "Vendor catalog items are the goods and services that a vendor offers. You can add items to a vendor catalog and then use the catalog to make purchases." This directly defines the Vendor Catalog as a list of goods from a third party. (ServiceNow Product Documentation

"Create a vendor catalog item

" Quebec release).

2. ServiceNow Product Documentation - Product Catalog: "The Product Catalog contains model information for products from various manufacturers... The catalog is a central repository of information about products that your company uses." This highlights its role as a master repository

distinct from a vendor-specific list. (ServiceNow Product Documentation

"Product Catalog

" Rome release).

3. ServiceNow Product Documentation - Service Catalog: "The Service Catalog application enables you to set up one or more service catalogs. You can offer different sets of services to your users." This confirms its purpose is for offering internal services. (ServiceNow Product Documentation

"Service Catalog

" San Diego release).

Lead-time is evaluated by the pre-built “Insufficient lead time” risk-condition record (table changeriskcondition). Its script checks whether the planned start date is less than the default three-day threshold; changing that threshold to five days is accomplished by editing that specific risk-condition record, not by altering matrices, UI actions, or properties.

A. No system property exists for lead-time; properties control enable/disable of overall risk calculator, not thresholds.

B. Risk Assessment Matrix maps questionnaire scores; it is unrelated to time-based lead-time logic.

C. UI Action only triggers the calculator; it does not contain threshold logic.

D. Risk Matrices are used by the Risk application, not Change Management’s risk-condition engine.

1. ServiceNow Product Documentation

“Change Risk Assessment – Predefined risk conditions

” Orlando/Paris release

§‘Insufficient lead time’ (“…high risk if planned start date is less than 3 days… Edit this condition to change the threshold.”).

2. ServiceNow Product Documentation

“Modify change risk condition definitions

” §Procedure step 2 (“Open the risk condition record to adjust the script or threshold value.”).

3. ServiceNow Product Documentation

“Change Risk Assessment properties

” §Overview (lists available properties; no property for lead-time threshold).

A ServiceNow software model is designed to have a one-to-one relationship with a service catalog item. This is implemented through the "Product catalog item" field on the Software Model [cmdbsoftwareproductmodel] form, which is a reference field pointing to the Service Catalog Item [sccatitem] table. A reference field can only store a single value (sysid), thereby limiting the association to exactly one catalog item. This design ensures a clear and direct path for software requests, which is essential for automating the procurement and license allocation processes within the Software Asset Management application.

B, C, D, E: These options are incorrect because the underlying data structure of the software model record only allows for a single reference to a catalog item, not multiple. There is no related list or other mechanism to associate a software model with more than one catalog item.

1. ServiceNow Product Documentation: "Create a software model". In the procedure for creating a software model

step 10 explicitly states: "In the Product catalog item field

select the catalog item that you want to associate with the software model." The use of the singular "the catalog item" confirms a single association. (ServiceNow Vancouver release documentation).

2. ServiceNow Product Documentation: "Software model fields". The documentation describes the "Product catalog item" field as the "Catalog item that is associated with the software model

" again implying a singular relationship. (ServiceNow Vancouver release documentation).

3. ServiceNow Now Learning: Software Asset Management (SAM) Professional Fundamentals. The "Software Models" module explains that linking a software model to a product catalog item enables users to request the software. The training material and labs consistently demonstrate populating this single reference field

reinforcing the one-to-one design.

The Normalization Data Services (NDS) plugin is a fundamental component of Software Asset Management (SAM) Professional. It is automatically activated when the SAM Professional plugin is enabled. Its primary function is to standardize raw software discovery data by comparing it against the ServiceNow Content Library, ensuring consistency in publisher names, product titles, and versions. The guided setup for SAM Professional includes specific tasks to configure and schedule normalization jobs, making it an integral part of the initial setup process required for accurate license compliance and reconciliation.

A. Vendor Procurement: This is a separate application for managing the purchasing lifecycle and is not a core dependency configured during the initial SAM Professional setup.

B. Asset Cost Management: While related to the financial aspects of assets, this is not a foundational plugin that is specifically configured during the core SAM Professional setup process.

D. Asset Management: This is a prerequisite base application. SAM Professional builds upon its foundation, but it is not the specific plugin configured during the specialized SAM setup.

E. ITSM Software Asset Management: This refers to a legacy, non-scoped version of the Software Asset Management application. The modern SAM Professional uses a different architecture and set of plugins.

1. ServiceNow Product Documentation: "Components installed with Software Asset Management". This document explicitly lists the "Normalization Data Services (com.snc.normalization)" plugin as a component installed with the core SAM Professional plugin (com.snsampmaster).

Reference: ServiceNow Product Documentation > Software Asset Management > Reference > Components installed with Software Asset Management.

2. ServiceNow Product Documentation: "Set up Software Asset Management". The official guided setup process for SAM Professional includes a dedicated category named "Normalization and Content Service". This section contains tasks for configuring the Content Service and scheduling normalization jobs

confirming it is a key part of the setup.

Reference: ServiceNow Product Documentation > Software Asset Management > Getting started > Set up Software Asset Management > Guided setup for Software Asset Management.

When creating a bar chart report in ServiceNow's Report Designer to visualize license metrics, both 'Group by' and 'Stacked by' are available and distinct configuration options. The 'Group by' option is mandatory and sets the primary categorization for the bars on the x-axis (e.g., by Department, Cost Center). The 'Stacked by' option is an additional refinement that segments each bar into sub-categories (e.g., by Compliance Status, Model), providing a more granular, multi-dimensional view of the data within a single chart. Using both options together offers the most refined view.

A. The 'or' is logically incorrect. You cannot use 'Stacked by' without first defining a 'Group by', so they are not equivalent alternatives.

C. This is incorrect because 'Stacked by' is a secondary grouping option that is dependent on a primary 'Group by' field being selected first.

D. This option is incomplete. While 'Group by' is a fundamental option for creating a bar chart, it is not the only refinement tool available; 'Stacked by' is also a key option.

1. ServiceNow Product Documentation - Report types and creation details (Bar report): The official documentation for creating bar reports explicitly lists both 'Group by' and 'Stacked by' as separate configuration fields. It states

"Group by: Select a field to group data by... Stacked by: Select a field to stack the bars in the chart by." This confirms both are available options for refining the report. (ServiceNow Product Documentation

Washington D.C. Release

Doc ID: KB1513378).

2. ServiceNow Product Documentation - View license usage: The documentation for the Software Asset Management License Usage view shows a bar chart that is both grouped and stacked. While the primary interactive filter on this specific page is "Group by

" the resulting visualization is a stacked bar chart (e.g.

stacked by compliance status)

demonstrating that both grouping and stacking are used in combination to report on license metrics. (ServiceNow Product Documentation

Washington D.C. Release

Doc ID: KB1213090).

The Exploration phase is the final stage in the ServiceNow Discovery process. After a device has been scanned, classified (e.g., as a Windows Server), and identified (matched to an existing CI or determined to be new), the Exploration phase begins. This phase launches additional, more specific probes to gather detailed attributes about the configuration item (CI). This includes information such as running processes, installed software, memory, CPU, network adapters, and other granular data, effectively asking the device, "What else can you tell me about yourself?".

A. Are you there? How will I classify you?

This statement combines the purpose of the Scanning phase ("Are you there?") and the Classification phase ("How will I classify you?"), not the Exploration phase.

C. Have I seen you before?

This question represents the core purpose of the Identification phase, which uses unique identifiers to check if the device already exists as a CI in the CMDB.

D. How should I classify you specifically?

This is a more detailed way of describing the Classification phase, where Discovery determines the device's type (e.g., server, router) to decide which probes to use next.

1. ServiceNow Product Documentation (Washington DC): Discovery phases.

Reference: In the section describing the four phases

the "Exploration phase" is defined as the stage where "Discovery uses exploration probes to gather more detailed information about the device

such as the applications running on it." This directly supports the correct answer's explanation.

2. ServiceNow Product Documentation (Washington DC): Horizontal discovery.

Reference: The documentation outlines the four phases in order. It states that after Identification

"The Exploration phase launches the exploration probes that are appropriate for the device type to gather additional information." This confirms Exploration is about gathering "additional information."

3. ServiceNow Now Learning: IT Operations Management (ITOM) Visibility and Governance Fundamentals.

Reference: Module: "Discovery Fundamentals". This courseware explains that the Exploration phase is responsible for collecting in-depth details and relationships for the discovered CI

which aligns with asking the device for more information about itself.

The Service Catalog is the user-facing portal where an organization lists the services, goods, and products it provides to its users for request.

The Product Catalog is a backend repository for asset management, containing the specific models (e.g., "Dell Latitude 5440," "Apple iPhone 15") that define the items.

The Vendor Catalog contains items offered by external, third-party suppliers, including their specific part numbers and pricing, which is used for procurement.

ServiceNow Official Documentation. (2024). Product Catalog. "The product catalog is a set of information about models. Models are specific versions or configurations of an asset." (Relates Product Catalog to models).

ServiceNow Official Documentation. (2024). Service Catalog. "Give people access to any business service they need through a single, easy-to-use portal... Let employees and customers request catalog items such as service and product offerings on their own." (Relates Service Catalog to what the organization provides).

ServiceNow Official Documentation. (2024). Manage vendor catalog items. "Create vendor catalog items to identify the products that a specific vendor supplies... Vendor items associate products in the Product Catalog with a vendor." (Relates Vendor Catalog to third-party suppliers).