Free ServiceNow Certified Implementation Specialist - Platform Analytics CIS-PA Exam Questions

Formula Indicators in Platform Analytics are pre-calculated during data collection and their results are stored in the Indicator Facts table, just like automated indicators. They are not calculated in real time when a dashboard is viewed. Instead, they use the previously collected scores of their component indicators to compute a derived value at collection time.

This design ensures consistent historical analysis, predictable performance, and accurate trending. Real-time calculation would undermine historical integrity and dashboard performance, which is why ServiceNow explicitly avoids it for formula indicators. The stored results can then be reused across dashboards and reports without recalculation. ServiceNow documentation clearly states that formula indicators behave like other indicators in that they are persisted for future analysis, making option C correct.

In Platform Analytics, dashboards are shared through the dashboard Share action. In the Share Dashboard dialog, the Grant access to field explicitly allows you to enter one or more users, groups, or roles to share the dashboard with. This sharing controls whether recipients can view the dashboard or edit it, depending on whether you add them as a viewer or editor. Sharing can also optionally allow recipients to manage (add/edit/remove) sharing permissions if that option is enabled. ServiceNow further notes that only certain privileged roles (such as admin, dashboard_admin, pa_admin, or pa_power_user) can see roles in the sharing panel in some configurations, and sharing with roles may require read access to the Roles [sys_user_role] table. This means access can be granted at the individual level (user), team level (group), or permission level (role), making ''user, group, or role'' the correct and complete choice.

In Platform Analytics, a Target defines the desired performance level for an indicator. The Review Date property specifies the recommended date to evaluate progress toward that target. This date is used for governance and performance review purposes, helping stakeholders determine when to assess whether the indicator is trending appropriately toward its goal.

The Baseline Date marks the starting point for measurement, while the End Date defines when the target expires or is no longer valid. The Improvement Date indicates when improvement efforts begin, not when performance should be evaluated. ServiceNow documentation clearly identifies the Review Date as the point in time when the target's effectiveness and achievement should be assessed, making option D the correct answer.

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.

The KPI Details application provides an exploratory, in-depth view of individual indicators. It allows users to analyze trends, targets, forecasts, breakdowns, and historical performance beyond what is shown in high-level dashboards.

KPI Details is not a content pack and does not consist of predefined reports. While Analytics Hub displays summary KPI information, KPI Details is a dedicated application for deeper investigation and performance review. ServiceNow documentation clearly describes KPI Details as a drill-down analysis tool, making option B the correct answer.

In ServiceNow Platform Analytics, the Precision setting controls how numeric values are rounded and abbreviated when displayed in Score widgets. When Precision is set to 0, the platform displays values using compact notation (such as k for thousands or M for millions) with no decimal places.

For a stored value of 7423.3, Precision 0 causes the value to be rounded to the nearest thousand and displayed as 7k. Platform Analytics does not display the full raw number unless compact notation is disabled or precision is increased. Option B (7000) and option D (7423) represent numeric rounding but not the compact display format used by score widgets. Option C is incorrect because Precision 0 explicitly removes decimals and applies abbreviation.

ServiceNow documentation confirms that score widgets use precision-based compact formatting, making 7k the correct displayed value when Precision is set to 0.

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.

Performance Analytics Spotlight is a feature that provides a ranked list of records based on multiple weighted conditions, helping users focus on the most critical records that require attention. Spotlight differs from traditional reports and time-series analytics because it evaluates records dynamically using scoring logic rather than historical aggregation.

Option A describes dashboard visualizations such as time series or scorecards. Option B refers to record views, not analytics. Option D describes Performance Analytics indicators, which track trends over time. ServiceNow documentation clearly defines Spotlight as a prioritization tool that ranks records using configurable rules and weights, making option C the correct and complete description.

Breakdown element security determines which users are allowed to see specific breakdown elements (such as certain categories or values) when viewing analytics data. In Platform Analytics, this security is configured directly on the Automated Breakdown record.

Automated Breakdowns include properties that allow administrators to define element-level access control, typically by specifying roles that are required to view certain breakdown elements. This ensures sensitive analytics data is only visible to authorized users. The Breakdown Source defines how data is mapped and categorized but does not control visibility. Automated Indicators control score collection and aggregation, not breakdown element security. Manual Breakdowns are static and do not support dynamic element security in the same way.

ServiceNow documentation explicitly states that breakdown element security settings---such as restricting elements by role---are part of the Automated Breakdown configuration, making option D the correct answer.

Historical Data Collection is intended to accurately reconstruct past indicator scores. Age-based breakdowns must be excluded because age is a time-relative value that cannot be reliably recalculated for historical points in time.

For the indicator Number of open and overdue incidents, breakdowns such as Location, Category, and State can be historically recalculated by evaluating record attributes at specific points in time. However, Age depends on the exact moment of evaluation and changes continuously, making it unsuitable for historical backfilling.

ServiceNow documentation explicitly warns against using age or duration-based breakdowns in historical data collection jobs, as they lead to inaccurate or misleading results. Therefore, option A is the correct and documented exclusion.