ServiceNow CIS-PA Exam Dumps

A Formula Indicator in ServiceNow Platform Analytics allows you to calculate a derived score using up to five other indicators (automated or manual) through a mathematical expression. These component indicators must already exist and have collected data.

Formula Indicators are not calculated at view time; instead, they are pre-calculated during data collection and stored like other indicator scores. This ensures consistent historical trending and optimal dashboard performance. Aggregates such as count or sum are handled by automated indicators, not formula indicators. Formula indicators also cannot reference indicator threshold values, as thresholds are used only for KPI status evaluation and visualization, not for calculations.

ServiceNow documentation clearly states the five-indicator limit and emphasizes that Formula Indicators are meant for derived metrics, such as percentages, ratios, or normalized scores, making option B the only correct definition.

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.

The Allow formula component to be NULL setting controls how a Formula Indicator behaves when one or more component indicators return NULL values. When enabled, the formula continues to calculate using the available components instead of aborting the calculation.

If this setting is disabled and any component returns NULL, the entire formula result becomes NULL. The setting does not automatically convert NULLs to zero, nor does it skip calculation entirely. ServiceNow documentation explains that this option provides flexibility in environments where some component indicators may not have data for every period, ensuring the formula can still produce meaningful results. Therefore, option D accurately describes the behavior.

An Automated Indicator in Platform Analytics is defined as a series of measurements collected over time that represent the performance of a process. These measurements are stored as time series data, allowing organizations to analyze trends, patterns, and historical performance. Automated indicators rely on indicator sources and scheduled data collection jobs to collect data at defined intervals, such as daily or hourly.

Option B describes a snapshot report, which represents data at a single point in time and does not support trending. Option C refers to breakdowns, which categorize indicator scores for deeper analysis but do not define the indicator itself. Option D describes the data collection job, which is a mechanism used by automated indicators but not the indicator definition. ServiceNow documentation explicitly states that indicators represent performance over time, making option A the correct and most complete description of an Automated Indicator.

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.