Pass the ServiceNow CIS-Platform Analytics CIS-PA Questions and answers with CertsForce

An Automated Breakdown is confirmed to be using aBucket Groupwhen theFacts table of the Breakdown Sourceis set toBucket [pa_buckets]. Bucket Groups define how numeric or duration values are grouped, but the actual bucketed analytics data is stored in thepa_bucketstable during data collection.

The Breakdown Source is responsible for defining where the breakdown facts originate. If its Facts table ispa_buckets, this indicates that the breakdown is based on bucketed values generated by a Bucket Group. The Breakdown record itself does not define the facts table, and default element filters or related list conditions do not establish the use of bucket data.

ServiceNow Platform Analytics documentation clearly states that all bucket-based breakdowns must referencepa_bucketsat the Breakdown Source level, making option C the correct and definitive answer.

AHistorical Collection Jobis designed to collect past data for a defined historical period and is typically executedone timeoron 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 isOnce or On Demand, making option A 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.

A Bucket Group is used in Platform Analytics to categorize numeric or time-based values into ranges. The Hour of day breakdown is a classic example of this usage, as it groups records into defined hourly ranges (for example, 00–01, 01–02, and so on).

Priority, Business Service, and Assignment Group are categorical fields that use direct field mappings and do not require bucket logic. Bucket Groups are specifically intended for non-categorical data such as time, age, duration, or numeric ranges. ServiceNow documentation explicitly identifies time-based breakdowns, such as hour of day or age ranges, as appropriate use cases for Bucket Groups. Therefore, option A is 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.

WhenCollect recordsis enabled on an Automated Indicator, Platform Analytics stores thesys_ids of the recordsthat contributed to each indicator score at collection time. This capability enablesdrill-down functionality, allowing users to view the exact records behind a score directly from analytics widgets and dashboards. Importantly, Platform Analytics doesnot store full copies of records—only the identifiers—ensuring historical accuracy while maintaining storage efficiency.

Option A describes thepreview featureavailable when defining indicator conditions, not record collection. Option B refers tomanual data collection, which is triggered separately. Option C is incorrect because Platform Analytics does not retain full record snapshots. ServiceNow documentation clearly states that enabling Collect records allows analytics users to drill into the contributing records for any given score, making option D the correct and precise 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 predefined filter condition is selected during data source configuration, Platform Analytics applies the filter immediately and displays it in the Conditions section, where it can be reviewed, modified, or extended. This allows administrators to start with a standard filter and refine it to meet specific analytics requirements.

The filter is not automatically saved for future use, nor does it automatically select the data source without user confirmation. ServiceNow documentation clarifies that predefined filters act as starting templates, not locked or persistent filters. Administrators retain full control to adjust conditions before saving the indicator or data source. Therefore, option D accurately describes the behavior.