Important ServiceNow CIS-PA Exam Questions

Answer: A

Explanation:

A scripted Breakdown Mapping is required when the breakdown value cannot be obtained through a direct field mapping or simple reference relationship. Categorizing requests based on the number of times they were updated requires 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 uses age ranges, which are handled through Bucket Groups and the pa_buckets table, not scripted mappings. ServiceNow documentation clearly states that scripted mappings are intended for calculated, derived, or indirect values, making option A the correct answer.

Answer: B

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.

Answer: D

Explanation:

In ServiceNow Platform Analytics, a Breakdown Source is automatically disabled when the number of generated breakdown elements exceeds the maximum element limit defined in system properties (for example, properties controlling the maximum allowed breakdown elements during data collection). This safeguard exists to protect system performance and prevent excessive storage and processing during data collection jobs.

When this error occurs, the recommended and documented resolution is not to increase the system property arbitrarily. Increasing the global limit can negatively impact performance across all analytics workloads and is discouraged unless there is a strong architectural justification.

Instead, ServiceNow best practice is to refine the Breakdown Source conditions---for example, by adding filters, narrowing scope, or excluding unnecessary records---so that the number of returned elements falls below the configured system threshold. Once the conditions are optimized, you can safely re-enable DC active, and the breakdown will participate in data collection successfully.

Simply re-enabling DC active without reducing elements will cause the breakdown to be disabled again, and deleting/recreating the source does not address the root cause. Therefore, option D is the correct and fully supported resolution according to ServiceNow Platform Analytics documentation and best practices.

Answer: D

Explanation:

In Platform Analytics, dashboards are shared through the dashboard Share action. In the Share Dashboard dialog, the Grant access to field explicitly allows you to enter one or more users, groups, or roles to share the dashboard with. This sharing controls whether recipients can view the dashboard or edit it, depending on whether you add them as a viewer or editor. Sharing can also optionally allow recipients to manage (add/edit/remove) sharing permissions if that option is enabled. ServiceNow further notes that only certain privileged roles (such as admin, dashboard_admin, pa_admin, or pa_power_user) can see roles in the sharing panel in some configurations, and sharing with roles may require read access to the Roles [sys_user_role] table. This means access can be granted at the individual level (user), team level (group), or permission level (role), making ''user, group, or role'' the correct and complete choice.

Answer: D

Explanation:

In Platform Analytics, a Breakdown is used to group or filter indicator scores based on specific attributes, such as priority, category, assignment group, or age ranges. Breakdowns allow users to analyze how different segments contribute to overall performance and to compare trends across those segments over time.

Breakdowns operate on indicator scores, not on raw report data. While reports can also be grouped or filtered, that functionality is separate from Performance Analytics. A Breakdown does not define the source table itself (that is the role of the Breakdown Source), nor is it merely a choice list. ServiceNow documentation clearly defines Breakdowns as a core analytics concept used to slice indicator data for deeper performance insight, making option D the correct answer.