AFormula Indicatorin ServiceNow Platform Analytics allows you to calculate a derived score usingup to five other indicators(automated or manual) through a mathematical expression. These component indicators must already exist and have collected data.

Formula Indicators arenot calculated at view time; instead, they arepre-calculated during data collectionand 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 referenceindicator 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 forderived metrics, such as percentages, ratios, or normalized scores, making optionBthe only correct definition.

Performance AnalyticsContent Packsprovide prebuilt indicators, breakdowns, dashboards, and jobs for specific applications such as Incident, Problem, or Change Management. To activate these packs, administrators navigate toPerformance 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 identifiesPerformance Analytics > Add Content Packas the correct location to install analytics content, making option C the verified answer.

The pa.getRate() method is used in Platform Analytics to calculaterates of performance over time, such as incidents resolved per day, requests closed per week, or changes per reporting period. This method works ontime series dataand 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.

Ascripted Breakdown Mappingis required when there isno direct field relationshipbetween 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 forcomplex or indirect relationships, making option A the correct answer.

By default, a newly created Platform Analytics indicator isVisible to Just Me, andVisible by All Rolesis set toFalse. This ensures that indicators are private to their creator until explicitly shared.

No role is required by default, and visibility must be intentionally expanded by updating the access control settings. This design supports governance and prevents incomplete or experimental indicators from being exposed prematurely. ServiceNow documentation confirms this default behavior, making option A the correct answer.

User Experience Analyticsis the application designed to analyzeuser behavior, including new versus returning users, session frequency, navigation paths, page views, and interaction patterns across the ServiceNow platform. It provides insights into how users engage with the platform and helps organizations optimize usability, adoption, and performance.

Responsive Dashboards and Next Experience Dashboards are visualization and UI frameworks, not behavioral analytics tools. Platform Analytics Workspace focuses on KPI monitoring and process performance, not clickstream or navigation behavior. ServiceNow documentation clearly positions User Experience Analytics as the solution for understanding how users interact with the platform, making option D the correct answer.

During data collection, Platform Analytics first applies theIndicator Source conditionsto retrieve the base dataset. Once the source data is identified, the system then evaluates theAdditional conditionsdefined on the Indicator itself.

This separation allows indicator-specific filtering without duplicating logic in the indicator source, supporting reuse and performance optimization. Additional conditions do not run in parallel with source conditions and are not evaluated at visualization time. ServiceNow documentation explicitly explains that Indicator conditions refine the datasetafterthe source query executes, making option D the correct answer.