Free Practice Questions for the ServiceNow CIS-Platform Analytics CIS-PA Exam (2026 Updated)

A scripted Breakdown Mapping is required when there is no direct field relationship between the Indicator source data and the Breakdown source table. In such cases, standard field mapping cannot resolve how indicator records should be categorized, so a script is needed to programmatically determine the correct breakdown value.

Mapping to a Sys ID field (option B) is supported through standard mappings. Database views (option C) can still be mapped if fields are accessible. Dot-walked fields (option D) are commonly supported without scripting. According to ServiceNow Platform Analytics documentation, scripted mappings are specifically intended for complex or indirect relationships , making option A the correct answer.

When a Bucket Group is used as a Breakdown Source in Platform Analytics, the required Facts table is Bucket [pa_buckets] . Bucket Groups define how numeric or duration values (such as age, time, or cost ranges) are grouped, but they do not store analytics facts themselves. The actual bucketed values generated during data collection are stored in the pa_buckets table, which makes it the authoritative facts table for bucket-based breakdowns.

The pa_bucket_groups table only stores configuration metadata for bucket definitions. The sys_choice table is used exclusively for choice list values and is unrelated to bucket analytics. The Indicator Facts table stores indicator scores but does not contain bucket-level breakdown data. ServiceNow documentation explicitly states that any breakdown based on bucket groups must reference the pa_buckets table to ensure accurate historical analysis and proper breakdown rendering. Therefore, option C is the only correct answer.

Performance Analytics Content Packs provide prebuilt indicators, breakdowns, dashboards, and jobs for specific applications such as Incident, Problem, or Change Management. To activate these packs, administrators navigate to Performance Analytics > Add Content Pack . This interface lists all available analytics content packs and allows administrators to preview and activate them.

Option A refers to Solution activation, which is unrelated to Performance Analytics content. Option B is used for application plugins, not analytics packs. Option D does not exist as a valid navigation path for Performance Analytics. ServiceNow documentation explicitly identifies Performance Analytics > Add Content Pack as the correct location to install analytics content, making option C the verified answer.

In ServiceNow Platform Analytics, the color of the score displayed in a Score widget is determined by the Indicator’s relationship to its target in combination with the Direction setting (Maximize or Minimize) of the Indicator. This behavior is part of the KPI evaluation logic and is consistent across dashboards and KPI Details.

When an indicator has a defined target, Platform Analytics compares the current score against that target. Based on whether the indicator is configured to maximize (higher is better) or minimize (lower is better), the platform automatically assigns a visual status—such as green (on track), yellow (warning), or red (off track). This status directly controls the color of the score value shown in the widget.

Chart colors, field styles, or widget-specific settings do not influence the score color. Those options may affect line charts or visual styling, but not KPI status coloring. ServiceNow documentation clearly states that KPI status and score coloring are driven by target evaluation logic , making option A the correct and verified answer.

To track how long an incident remains assigned to a specific group, the correct Metric Definition type is Field value duration . This type measures the amount of time a record spends with a particular value in a specified field, such as assignment_group.

State change metrics track transitions between states, not time spent in a field value. Script calculations are used only when duration cannot be calculated through standard field tracking. “Assignment group” is a field, not a metric type. ServiceNow documentation specifies that Field value duration metrics are designed for tracking time spent in a given field value, making option A the correct choice.

Platform Analytics supports unit conversion for duration-based indicators through the Unit field on the Indicator record. When an indicator stores duration values (such as milliseconds), setting the Unit to Hours automatically converts and displays the values correctly without modifying the underlying data or recollecting scores.

Using formulas or scripts is unnecessary and discouraged when a built-in unit conversion is available. The Formula box is intended for mathematical aggregation logic, not unit conversion. ServiceNow documentation explicitly states that duration indicators should rely on the Unit setting to control how values are displayed, making option A the correct and supported approach.

The analytics_filter_admin role is responsible for governing dashboard filters within Analytics Center. Users with this role can create, edit, delete, and manage filters , as well as add filters to the filter library for reuse across dashboards.

This role does not control visualization design, breakdown security, or data validation. Its purpose is to ensure consistent and controlled use of filters across analytics experiences. ServiceNow documentation explicitly associates this role with filter administration, making option B the correct answer.

A Breakdown Source defines how data is classified into distinct breakdown elements for analysis. It identifies the table and field (or script) used to generate the unique values—such as categories, priorities, assignment groups, or buckets—that segment indicator scores.

Default element filters are configured on the Breakdown, not the Breakdown Source. Indicators are linked to Breakdowns through Breakdown Mappings, not selected at the source level. While bucket-based sources support non-categorical data, their core purpose remains identifying unique breakdown elements. ServiceNow documentation emphasizes that the Breakdown Source is responsible for defining where breakdown values come from and how they are identified , making option C the correct answer.

A Historical Collection Job is designed to collect past data for a defined historical period and is typically executed one time or on demand . Unlike scheduled collection jobs (daily, weekly, or monthly), historical jobs are not intended to run repeatedly.

ServiceNow documentation specifies that historical collections are initiated manually to backfill data for indicators that were created after records already existed. Running them on a recurring schedule could lead to duplicated or incorrect data. Therefore, the correct configuration is Once or On Demand , making option A the correct answer.

Historic Data Collection is designed to accurately reconstruct past indicator scores based on historical records. Indicators that rely on calculated age values , such as summed age of open problems , cannot be accurately reconstructed because age is a time-relative value that depends on the exact moment of calculation.

Count-based indicators (options A, B, and D) can be recalculated historically by evaluating record states at specific points in time. However, summing age values requires knowing the precise age of each record at each historical interval, which is not reliably reproducible. ServiceNow documentation explicitly warns against using historic data collection for age-based and duration-sum indicators , making option C the correct exclusion.

In Platform Analytics, a Breakdown is used to group or filter indicator scores based on specific attributes, such as priority, category, assignment group, or age ranges. Breakdowns allow users to analyze how different segments contribute to overall performance and to compare trends across those segments over time.

Breakdowns operate on indicator scores , not on raw report data. While reports can also be grouped or filtered, that functionality is separate from Performance Analytics. A Breakdown does not define the source table itself (that is the role of the Breakdown Source), nor is it merely a choice list. ServiceNow documentation clearly defines Breakdowns as a core analytics concept used to slice indicator data for deeper performance insight, making option D the correct answer.

In Performance Analytics scripted indicators, certain system-provided variables are automatically available without being explicitly defined in the Fields list. The variables score_start and score_end represent the start and end timestamps of the reporting period for which the indicator score is being calculated. These variables are essential for time-aware calculations and historical accuracy.

Fields such as sys_created_on and sys_updated_on must be explicitly added to the Fields list if they are used in scripts. collection_job_start and collection_job_end are not available script variables in indicator calculations. ServiceNow documentation clearly identifies score_start and score_end as built-in variables available to Performance Analytics scripts, making options B and F the correct answers.

In Responsive Canvas dashboards, when a Time Series widget contains multiple elements, the Show multiple elements as property controls how those elements are visualized. Setting this property to Aggregate combines the values of all returned elements into a single trend line , which is exactly the desired outcome when viewing a combined trend for High and Critical priority incidents.

Applying an elements filter (option D) limits which elements are displayed but does not combine them into one trend. Setting the property to Separate (option C) explicitly shows individual trend lines for each element. Manually adding elements (option B) still results in multiple distinct series unless aggregation is enabled. According to ServiceNow Platform Analytics documentation, aggregation is the correct method for consolidating multiple indicator elements into one unified visualization on a dashboard.

In ServiceNow Performance Analytics, Indicator Sources and Indicators are distinct objects with different responsibilities, and understanding their behavior is essential for correct architecture and deployment.

Option A is correct.

Indicator Sources define how and when raw data is queried , but they can be reused by multiple data collection jobs. Even if an Indicator Source is configured with a Monthly frequency , it can still be executed by a Daily data collection job . The job frequency controls execution timing, not the source frequency itself. This reuse is a documented performance optimization in Platform Analytics.

Option C is correct.

The Indicator frequency is independent of the Indicator Source frequency . For example, an Indicator Source may collect daily raw data, while the Indicator aggregates and stores scores weekly or monthly. This separation allows flexible aggregation strategies and is explicitly supported by Platform Analytics design.

Option B is incorrect because Breakdowns require a Breakdown Mapping , but they are not inherently tied only to Automated Indicators, nor is this statement describing object behavior accurately in isolation.

Option D is incorrect because Breakdowns can be assigned to an Indicator before or after data collection ; they are applied when the next collection runs.

ServiceNow best practice recommends running Performance Analytics data collections using a dedicated service account specifically created for analytics processing. This ensures consistent permissions, predictable access to data, and improved auditability.

Running collections as individual admins can introduce permission inconsistencies if roles change. The maint account is intended for system upgrades and maintenance, not scheduled analytics jobs. A dedicated Performance Analytics service account minimizes operational risk and aligns with ServiceNow security and governance guidelines.

ServiceNow documentation emphasizes the importance of service accounts for background processing, making option C the correct and recommended choice.