CIS-PA Certification Exam Guide + Practice Questions

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

Explanation:
Dashboard filters retain their values across page refreshes and user navigation through session-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.

Explanation:
Historic Data Collection is designed to accurately reconstruct past indicator scores based on historical records. Indicators that rely on calculated age values, such as summed age of open problems, cannot be accurately reconstructed because age is a time-relative value that depends on the exact moment of calculation.
Count-based indicators (options A, B, and D) can be recalculated historically by evaluating record states at specific points in time. However, summing age values requires knowing the precise age of each record at each historical interval, which is not reliably reproducible. ServiceNow documentation explicitly warns against using historic data collection for age-based and duration-sum indicators, making option C the correct exclusion.

Explanation:
The PA Contributor role is designed for users who create and configure Indicators, Breakdowns, and Dashboards, but who should not have administrative control over data collection jobs, indicator sources, or system-level analytics settings.
PA Admin has full control, including job and source management. PA Data Collector is focused on executing collection jobs only. PA Power User is primarily for analysis and dashboard consumption rather than content creation. ServiceNow documentation defines PA Contributor as the correct role for content creation without administrative privileges, making option B correct.

Explanation:
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.