The pa.getRate() method is used in Platform Analytics to calculate rates of performance over time , such as incidents resolved per day, requests closed per week, or changes per reporting period. This method works on time series data and applies aggregation logic to derive a rate rather than a raw count or sum.

pa.getChange() is used to calculate the difference between two data points, not a rate. pa.getIndicator() retrieves indicator metadata and does not perform calculations. gs.getDuration() is a general-purpose GlideSystem utility for calculating durations and is unrelated to analytics time series processing. ServiceNow documentation clearly identifies pa.getRate() as the appropriate API for rate-based calculations using historical indicator scores, making option D 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.

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.

Fiscal Calendars allow Platform Analytics to aggregate and visualize indicator data using fiscal periods such as fiscal years, quarters, and accounting periods. This is essential for organizations that do not follow standard calendar years for reporting and performance measurement.

Gregorian calendars use standard date boundaries, while Business Calendars define working and non-working time for duration calculations. Timecard calendars are unrelated to analytics aggregation. ServiceNow documentation clearly states that fiscal period-based analysis is enabled through Fiscal Calendars, making option B the correct answer.

In Platform Analytics score widgets, the Precision setting controls how numeric values are abbreviated and rounded for display. When precision is set to 2 , large numbers are displayed using compact notation (such as k for thousands) with two significant digits.

A stored value of 42,502 is therefore displayed as 4.25k , improving readability while preserving meaningful precision. Full numeric formatting or fixed decimal display is not the default behavior for score widgets. ServiceNow documentation confirms that precision affects abbreviated score presentation , making option B the correct answer.

When a Performance Analytics dashboard is opened, ServiceNow loads only the widgets configured on the currently active tab . Widgets on other tabs are not loaded until the user clicks those tabs. This behavior is intentional and supports performance optimization , especially for dashboards containing many analytics widgets or complex queries.

Widgets are not limited by view rules alone, and ServiceNow does not preload widgets from all tabs. Additionally, widgets that require scrolling are still loaded as long as they are part of the active tab. ServiceNow documentation confirms that dashboard widgets are loaded per tab , reducing unnecessary data processing and improving load times. Therefore, option A is the correct and documented behavior.

In a Performance Analytics Job Log , the Inserts value represents the number of analytics score records written to the database during that job run. These inserts typically correspond to new indicator scores added to the Indicator Facts table.

This value does not represent business records such as incidents, nor does it indicate how many source records were evaluated. Records examined and calculations performed may be far greater than the number of inserts, as only final score results are stored. ServiceNow documentation confirms that Job Log insert counts reflect stored analytics results , making option B the correct interpretation.

In ServiceNow Platform Analytics, a Breakdown Source is automatically disabled when the number of generated breakdown elements exceeds the maximum element limit defined in system properties (for example, properties controlling the maximum allowed breakdown elements during data collection). This safeguard exists to protect system performance and prevent excessive storage and processing during data collection jobs.

When this error occurs, the recommended and documented resolution is not to increase the system property arbitrarily. Increasing the global limit can negatively impact performance across all analytics workloads and is discouraged unless there is a strong architectural justification.

Instead, ServiceNow best practice is to refine the Breakdown Source conditions —for example, by adding filters, narrowing scope, or excluding unnecessary records—so that the number of returned elements falls below the configured system threshold . Once the conditions are optimized, you can safely re-enable DC active , and the breakdown will participate in data collection successfully.

Simply re-enabling DC active without reducing elements will cause the breakdown to be disabled again, and deleting/recreating the source does not address the root cause. Therefore, option D is the correct and fully supported resolution according to ServiceNow Platform Analytics documentation and best practices.

When creating a breakdown based on the age of a task , the correct Facts table for the Breakdown Source is Bucket [pa_buckets] . In Platform Analytics, age-based breakdowns (such as 0–5 days, 6–10 days, etc.) are not derived directly from the Task table. Instead, they use bucketed data , which is generated by bucket groups during data collection.

The pa_buckets table stores the calculated bucket values for records at collection time, making it the authoritative facts table for age, duration, and numeric range breakdowns. Bucket Groups define how values are grouped, while the Bucket table stores the actual bucket assignments used in analytics. The Task table itself cannot be used as the facts table for age breakdowns because Platform Analytics requires pre-aggregated, time-aware bucket data to ensure historical accuracy. The Choice table is only used for choice list values and is unrelated to numeric or age-based breakdowns. ServiceNow documentation clearly states that bucket-based breakdowns must reference the pa_buckets table to function correctly and produce accurate time series analytics.

The PA Admin role provides full administrative access to Platform Analytics. Users with this role can create and configure indicators , define breakdowns and breakdown sources , manage data collection jobs , activate content packs, and administer analytics security and settings.

PA Contributors typically create content within limited scopes, while PA Power Users focus on analysis and dashboards rather than core configuration. The PA Data Collector role is limited to running data collection jobs. ServiceNow documentation clearly identifies PA Admin as the role required for full analytics configuration and administration, making option B the correct answer.