CIS-PA Certified Implementation Specialist - Platform Analytics Questions and Answers

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.

InPerformance Analytics Formula Indicators, indicator references must followstrict syntax rules:

Indicator names must be enclosed insingle square brackets:[Indicator name]

Mathematical operators must be valid

Parentheses must be properly paired

Curly braces { } and double square brackets [[ ]] arenot validfor indicator references

Let’s evaluate each option:

Option A – IncorrectUses indicator nameswithout square brackets, which is invalid syntax.

Option B – IncorrectUsescurly braces { }, which are not supported for indicator references, and also has ambiguous operator precedence.

Option C – CorrectUses propersingle square brackets, valid arithmetic operators, and correctly nested parentheses. This is a common and documented formula pattern for calculating percentage improvement against a baseline.

Option D – CorrectUses valid square-bracket indicator references and proper arithmetic. Even though it is logically redundant, it issyntactically valid, which is what the question asks.

Option E – IncorrectUsesdouble square bracketsand mismatched braces { ), which is invalid syntax.

In ServiceNow Platform Analytics, thePrecisionsetting controls how numeric values arerounded and abbreviatedwhen displayed inScore widgets. When Precision is set to0, the platform displays values usingcompact notation(such askfor thousands orMfor millions) withno decimal places.

For a stored value of7423.3, Precision 0 causes the value to be rounded to the nearest thousand and displayed as7k. 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 thecompact display formatused by score widgets. Option C is incorrect because Precision 0 explicitly removes decimals and applies abbreviation.

ServiceNow documentation confirms that score widgets useprecision-based compact formatting, making7kthe correct displayed value when Precision is set to 0.

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.

ABucket Groupin Platform Analytics is used togroup large sets of numeric or time-based values into a smaller, more meaningful number of ranges. Common examples include grouping ages into ranges (0–5 days, 6–10 days), durations into bands, or hours of the day into segments. This simplifies analysis and improves dashboard readability by reducing excessive breakdown elements.

Bucket Groups do not log incidents, manage roles, or control integrations. Instead, they support analytics by enabling structured classification of non-categorical data. ServiceNow documentation clearly positions Bucket Groups as a mechanism for transforming raw numeric or duration data into consumable breakdowns, making option B 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.

Breakdown element securitydetermines 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 theAutomated Breakdownrecord.

Automated Breakdowns include properties that allow administrators to defineelement-level access control, typically by specifyingrolesthat 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 theAutomated Breakdown configuration, making option D the correct answer.

When a Performance Analytics dashboard is opened, ServiceNow loadsonly 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 supportsperformance 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 loadedper tab, reducing unnecessary data processing and improving load times. Therefore, option A is the correct and documented behavior.

Performance Analytics Spotlightis a feature that provides aranked list of recordsbased onmultiple 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.

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.

When aBucket Groupis used as a Breakdown Source in Platform Analytics, the requiredFacts tableisBucket [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 thepa_bucketstable, which makes it the authoritative facts table for bucket-based breakdowns.

Thepa_bucket_groupstable only stores configuration metadata for bucket definitions. Thesys_choicetable 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 thepa_bucketstable to ensure accurate historical analysis and proper breakdown rendering. Therefore, option C is the only correct answer.

ServiceNow best practice recommends running Performance Analytics data collections using a dedicated service account specifically created for analytics processing. This ensures consistent permissions, predictable access to data, and improved auditability.

Running collections as individual admins can introduce permission inconsistencies if roles change. The maint account is intended for system upgrades and maintenance, not scheduled analytics jobs. A dedicated Performance Analytics service account minimizes operational risk and aligns with ServiceNow security and governance guidelines.

ServiceNow documentation emphasizes the importance of service accounts for background processing, making option C the correct and recommended choice.

TheShow real-time scoreoption is available only fornon-scripted Automated Indicators. These indicators are based on standard indicator sources and conditions that can be safely recalculated on demand without scripting complexity.

Scripted automated indicators and formula indicators depend on stored historical values and custom logic, which cannot be reliably recalculated in real time. Manual indicators rely on user-entered values and also do not support real-time calculation. ServiceNow documentation explicitly limits real-time scoring to non-scripted automated indicators to preserve performance and data integrity. Therefore, option D is the correct answer.

Dashboard filters retain their values across page refreshes and user navigation throughsession-based persistence. When this option is enabled, filter selections are stored for the duration of the user’s session and automatically reapplied as the user navigates or refreshes the page.

Favorites and global defaults define starting values, not persistence behavior. Applying a filter to the entire dashboard controls scope, not retention. ServiceNow documentation explains that session persistence is the mechanism that maintains filter state, making option C the correct answer.

TheAllow formula component to be NULLsetting 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.