Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
What option on the breakdown source record helps provide views into whether you need to create additional breakdowns or adjust data values?
When you select an indicator as the data source, you can filter the results by breakdown and breakdown element.
If you have the 'Label for unmatched' field defined on the breakdown source for a selected breakdown, this label appears in your choice of Elements.
Select the label to display scores that do not match any of the elements.
This option helps provide views into whether you need to create additional breakdowns or adjust data values.
Which of the following can you do when you set a target for an indicator on the Analytics Hub? (Choose three.)
You can set target values for indicators. When you set a target for an indicator on the Analytics Hub, you can now do the following:
* Set a start date in the future.
* Set a review date on which to consider updating the target.
* Set the target as an improvement on the average score or on the previous target. You can set the improvement as a percentage.
You can have the targets apply only to specific breakdown elements and time series. The target starts to apply at a selected date and continues to apply until you set the next target. However, you can set a review date on which to reconsider the target.
Which of the following styling options is NOT available with the data visualisation component configuration in workspaces?
The data visualisation component configuration adds more options and an enhanced user interface.
You can configure new visualisations in Workspace from tables and indicators using the Data Visualisation configuration.
From the UI Builder, you can add visualisations to your landing page based on Performance Analytics and Reporting data. Configure a new visualisation by dragging the Data Visualisation configuration icon onto the Stage pane.
The following styling options are added in the Quebec release:
* Show or hide a visualisation component header on a landing page, along with its label and icons.
* Change score sizes of single score visualisations.
* Set default, palette, or single colour options for data display.
* Sort on categories in bar, pie, and donut visualisations based on table data sources.
* Define data label positions and show labels that overlap on bar visualisations.
Creating a new visualisation type is not an available styling option.
How do you create and associate breakdowns on the breakdown source form?
A breakdown source is defined as a set of records from a table or database view or as a bucket group. Multiple breakdowns can use the same breakdown source.
Breakdown sources specify which unique values, called breakdown elements, a breakdown contains.
Breakdown source records have a related list that lists the breakdowns that are based on that source. You can create a breakdown by selecting the 'New' button while in this list. The list works like the Indicators list on indicator source records.
Other options in this question do not exist on the breakdown source form.
After you create breakdowns that use this source, these breakdowns are listed in the Breakdowns tab.
How are responsible users reminded when a signal remains unresolved?
As a responsible user, you receive email reminders about signals that have not been resolved.
You can configure how frequently you get these reminders and the maximum number of reminders to get for a signal.
Responsible users get email notifications about the following:
* New signals
* Unresolved signals
* Actions to resolve signals
* 'Anti-signals,' which indicate that a KPI is long-term stable
Even responsible users without workspace access get these email notifications.
What condition do you use on the Elements Filter record for the 'Groups' Breakdown Source to get only groups that had an incident assigned to them?
When you create an element filter, you can include conditions on a related field in a different table than the breakdown source table.
Element filters enable you to limit the displayed breakdown elements on an Analytics Hub or widget using filter conditions, including personalised visuals.
You can select an element filter when viewing breakdowns on an Analytics Hub or configuring a breakdown widget.
For example, you could create an element filter on the Groups breakdown source, which uses the Group [sys_user_group] table. If you added a related list condition on Incident [incident]->Assignment group, you would get only groups that had an incident assigned to them. If this condition included [[Created][on][Last 6 Months]], you would get groups that were assigned an incident that was created within the last six months.
Exam domains verified against: Official ServiceNow CAS-PA exam guide, last checked October 2026.
Performance Analytics consists of multiple integrated components that work together to collect, process and visualize data. You need to understand how these components connect and the typical sequence of steps when deploying a new instance. Start by mapping out the data flow from collection through to the dashboard, and practice identifying which component handles each step.
Indicators are the core metrics that Performance Analytics tracks and displays. This domain covers how to set up data sources, define what data to collect, choose between different indicator types, and write scripts that transform raw data into meaningful metrics. This is the heaviest-weighted area, so spend time working hands-on with indicator configuration in a test environment and understand aggregation logic.
Breakdowns let you split metrics into subcategories for deeper analysis. You need to map source data to breakdown dimensions, handle edge cases with exclusions and bucket groups, and write custom scripts when standard mappings do not work. Practice building breakdown matrices and understand how breakdowns interact with indicators.
Sample question from this domain above: Q2
Data collection is how Performance Analytics pulls information from your systems. You need to understand the collection workflow, configure what gets collected and how often, and troubleshoot when data does not flow correctly. Walk through real data collection jobs in your environment and learn to read collection logs to spot problems.
Visualization is how end users see and interact with data. This covers choosing the right chart type for your data story, building responsive dashboards, applying filters that let users explore results, and tuning dashboard performance so pages load quickly. Design a few different dashboard layouts and test how they perform with large data sets.
Administration covers day-to-day management and troubleshooting of Performance Analytics. You need to know how to use the admin console to manage configurations, speed up deployments using content packs, and diagnose common issues when things break. Familiarize yourself with the admin tools and learn to read diagnostic output to pinpoint problems.
Common questions about the exam itself
