CIS-PA Sample Questions Answers

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.

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.

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.

Ascripted Breakdown Mappingis required when the breakdown value cannot be obtained through adirect field mappingor simple reference relationship. Categorizing requests based onthe number of times they were updatedrequires calculating a value dynamically (for example, counting updates from the audit history), which is not stored as a single field on the record. Because this value must be derived programmatically, a scripted mapping is necessary.

Options B and C use existing fields (category, priority) that can be mapped directly without scripting. Option D usesage ranges, which are handled throughBucket Groupsand thepa_bucketstable, not scripted mappings. ServiceNow documentation clearly states that scripted mappings are intended forcalculated, derived, or indirect values, making option A the correct answer.

ABreakdown Sourcedefines how data isclassified into distinct breakdown elementsfor analysis. It identifies the table and field (or script) used to generate the unique values—such as categories, priorities, assignment groups, or buckets—that segment indicator scores.

Default element filters are configured on the Breakdown, not the Breakdown Source. Indicators are linked to Breakdowns through Breakdown Mappings, not selected at the source level. While bucket-based sources support non-categorical data, their core purpose remains identifying unique breakdown elements. ServiceNow documentation emphasizes that the Breakdown Source is responsible for definingwhere breakdown values come from and how they are identified, making option C 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.

TheVisualization Libraryis the Platform Analytics feature that enables visualizations to be reused and shared acrossany dashboard. When a visualization (such as a time series, scorecard, or breakdown visualization) is saved to the Visualization Library, it becomes areusable analytics componentthat can be added to multiple dashboards without duplicating configuration. This ensures consistency in metrics, reduces maintenance overhead, and supports centralized governance of analytics content.

Dashboard Sharing, by contrast, controlswho can view or edit a dashboard, not how individual visualizations are reused across dashboards. Roles such as pa_kpi_signals_admin or report_admin provide administrative capabilities but do not enable cross-dashboard visualization reuse. According to ServiceNow Platform Analytics documentation, the Visualization Library is specifically designed to store, manage, and distribute analytics visualizations so they can be embedded in dashboards throughout the platform. This feature is essential in enterprise analytics implementations where the same KPIs and indicators must appear consistently across multiple dashboards and user audiences.

Platform Analytics supports unit conversion for duration-based indicators through the Unit field on the Indicator record. When an indicator stores duration values (such as milliseconds), setting the Unit to Hours automatically converts and displays the values correctly without modifying the underlying data or recollecting scores.

Using formulas or scripts is unnecessary and discouraged when a built-in unit conversion is available. The Formula box is intended for mathematical aggregation logic, not unit conversion. ServiceNow documentation explicitly states that duration indicators should rely on the Unit setting to control how values are displayed, making option A the correct and supported approach.

Formula Indicators in Platform Analytics arepre-calculated during data collectionand their results arestoredin 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 arepersisted for future analysis, making option C correct.

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.

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.

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.

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.

A single Breakdown can be reused across multiple indicators—even when those indicators are based on different facts tables—by creating aseparate Breakdown Mapping for each indicator facts table.

The Breakdown defineswhatis being analyzed, while the Breakdown Mapping defineshowthe indicator facts relate to the breakdown source. Because different facts tables may store data differently, each requires its own mapping configuration. A scripted mapping is only required when no direct relationship exists, not simply because facts tables differ. ServiceNow documentation clearly states that reuse across facts tables is achieved through multiple mappings, 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.