ServiceNow CIS-PA Dumps - Pass Certified Implementation Specialist - Platform Analytics Exam in 2026

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.

When a Bucket Group is used as a Breakdown Source in Platform Analytics, the required Facts table is Bucket [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 the pa_buckets table, which makes it the authoritative facts table for bucket-based breakdowns.

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

An Automated Breakdown is confirmed to be using a Bucket Group when the Facts table of the Breakdown Source is set to Bucket [pa_buckets]. Bucket Groups define how numeric or duration values are grouped, but the actual bucketed analytics data is stored in the pa_buckets table during data collection.

The Breakdown Source is responsible for defining where the breakdown facts originate. If its Facts table is pa_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 reference pa_buckets at the Breakdown Source level, making option C the correct and definitive answer.

In Platform Analytics data visualizations, the Metric tile is designed to display a single summarized value. By default, the aggregation used for a Metric tile is COUNT. This means the tile displays the total number of records or scores returned by the data source unless the aggregation is explicitly changed by the user.

COUNT is the most commonly used aggregation because Metric tiles are often used to show key headline numbers such as total incidents, open requests, or completed tasks. Other aggregations like AVERAGE, MIN, or SUM are available options, but they must be manually selected during configuration. ServiceNow documentation confirms that COUNT is the default aggregation applied to Metric visualizations, making option A the correct answer.

During a Daily Data Collection job, Platform Analytics executes one database query per Indicator Source, not per indicator. Multiple indicators can reference the same indicator source, allowing the platform to reuse the result set and calculate multiple scores from a single query.

This design is a key performance optimization in Platform Analytics. Executing queries per indicator would significantly increase database load, especially in large implementations. ServiceNow documentation explicitly states that indicator sources are the unit of data retrieval during collection, making option B the correct and documented answer.