Free CAS-PA Practice Test

In ServiceNow Performance Analytics, KPI Signals enables users to manage signal notifications, such as dismissing a signal or resetting an indicator baseline. To execute these actions, a user must either be assigned as a responsible user for the indicator (and have workspace access) or possess specific administrative permissions. Specifically, users holding the admin, paadmin, or pakpisignaladmin role are granted explicit authority to act on signals across indicators, even if they are not designated as responsible users for the particular KPI being evaluated.

A: Responsible users must have access to the workspace environment to navigate to the KPI Signals interface and interact with or act on signals. C: Permission is not restricted solely to the admin role; users possessing the paadmin or pakpisignaladmin roles also have full rights to manage signals. D: Access control rules prevent unassigned or unauthorized users from taking actions on signals; specific responsibilities or administrative roles are required.

1. ServiceNow Product Documentation (Utah/Vancouver/Washington DC): Performance Analytics — Act on a KPI signal, Section: "KPI Signals roles and permissions."

Document Identifier: ServiceNow Product Docs - KPI Signals Administration

2. ServiceNow Developer & Product Documentation: Roles configured with Performance Analytics, Section: pakpisignaladmin role capabilities and signal workflow actions.

Document Identifier: Performance Analytics Setup and Administration Guide

In ServiceNow Performance Analytics, viewing indicator data and detailed scores is controlled primarily by Indicator and Breakdown Access Control Lists (ACLs). Users do not require the paviewer role (or any Performance Analytics role) to access KPI Details or the Analytics Hub, provided that the indicator and breakdown ACLs explicitly permit access to the requested indicator data. Conversely, administrative and diagnostic utilities are restricted to elevated Performance Analytics roles and cannot be accessed by general users even if indicator ACLs are satisfied.

Option A: Diagnostic Results requires administrative roles such as paadmin or padiagnostic to execute and inspect Performance Analytics diagnostic health checks.
Option D: Widget Statistics is a technical troubleshooting tool requiring paadmin or papoweruser roles to analyze widget rendering performance and execution metrics.

1. ServiceNow Product Documentation: Performance Analytics roles, Washington DC Release. (Document Identifier: analytics-data-governance/concept/pa-roles.html)

2. ServiceNow Product Documentation: Indicator and breakdown Access Control Lists (ACLs), Performance Analytics Administration. (Document Identifier: analytics-data-governance/concept/pa-acls.html)

3. ServiceNow Product Documentation: KPI Details, Next Experience Components, Performance Analytics. (Document Identifier: par-next-gen/concept/kpi-details-workspace.html)

4. ServiceNow Product Documentation: Performance Analytics Diagnostics, Performance Analytics Setup. (Document Identifier: analytics-data-governance/concept/pa-diagnostics.html)

On the ServiceNow Performance Analytics Formula Indicator form, the system provides related lists to configure and manage the indicator's context and component metrics. The available related lists on a Formula Indicator record include Targets (to set specific performance goals for the calculated formula), Contributing Indicators (to display and manage the underlying automated, manual, or formula indicators referenced within the formula expression), and Breakdowns (to map breakdown relations and enable formula score filtering across breakdown elements). Signals (KPI Signals) rely on historical automated data collection continuous analysis and are supported exclusively on automated indicators, making them unavailable on formula indicator forms.

D. Signals: KPI Signals are supported strictly for automated indicators to monitor statistical anomalies; they are not supported or available as a related list on formula indicator forms.

1. ServiceNow Product Documentation (Utah / Washington DC / Xanadu releases) – "Create a formula indicator": Performance Analytics > Indicators > Formula Indicators. Document ID: servicenow-docs-pa-formula-indicators.

2. ServiceNow Product Documentation – "KPI Signals": Performance Analytics > KPI Signals > KPI Signals requirements and limitations. Section: "Supported indicator types for KPI Signals".

3. ServiceNow Developer & Product Docs – "Performance Analytics indicator forms and related lists": System Administration & Performance Analytics Guide, Section: paindicators form layout and related lists (patargets, paindicatorbreakdowns, pacontributingindicators).

Analytics Q&A leverages Natural Language Query (NLQ) capabilities within ServiceNow Performance Analytics to help users query data using plain language. As a user types into the Analytics Q&A search bar, the system provides real-time autocomplete suggestions to streamline query building. These suggestions fall into three primary categories: Recent searches (a history of the user's previously submitted queries), Indicators (defined Performance Analytics key performance indicators), and Breakdowns (attributes used to slice, filter, or aggregate indicator data). This auto-completion mechanism ensures users can easily leverage established Performance Analytics metadata and past searches.

B. Tables and columns: Analytics Q&A autocomplete suggestions specifically surface Performance Analytics business metadata—namely Indicators, Breakdowns, and past search history—rather than direct raw database table and column names.

ServiceNow Product Documentation: Analytics Q&A / Natural Language Query in Performance Analytics, Section: "Ask questions with Analytics Q&A - Query Suggestions", Doc ID: cAnalyticsQandA.html.

ServiceNow Official Product Documentation (Washington DC / Vancouver Releases): Performance Analytics and Reporting > Analytics Q&A, Topic: "Analytics Q&A search suggestions and auto-complete".

In ServiceNow Performance Analytics, KPI Signals applies Statistical Process Control (SPC) to monitor automated indicator scores. While a standard signal alerts process owners to a statistically significant change or process shift, an anti-signal explicitly indicates long-term stability. It notifies process owners that a process has consistently remained within expected variation limits over a prolonged period (typically 7 or more consecutive points on a single side of the mean without breaching control limits), confirming that no significant change has occurred.

A. No signal has been detected: An anti-signal is an actively calculated pattern confirming consistent stability, whereas "no signal detected" merely means no threshold rules or stability conditions were triggered.
C. Abnormal variation in the scores of a KPI: Abnormal or special-cause variation triggers a standard signal (such as an out-of-bounds score or unexpected trend), not an anti-signal.
D. A workflow has changed: A workflow or process change leads to variation that manifests as a signal. An anti-signal confirms that the workflow and underlying process have remained unchanged.

1. ServiceNow Official Documentation (Xanadu Release): Performance Analytics & KPI Signals — KPI Signals concepts: Signals and anti-signals. Section: "KPI Signals definitions".

(Identifier: ServiceNow Product Documentation, Performance Analytics Administration Guide)

2. ServiceNow Official Documentation (Washington DC Release): KPI Signals process control rules and signal generation. Section: "Anti-signal detection rules".

(Identifier: ServiceNow Docs, Product Analytics & Process Mining)

In ServiceNow Next Experience Workspaces, data visualization components (Pie, Donut, and Single Score) offer specific display configurations: Data labels (Pie/Donut): Can be configured to display as pure values, percentages, or both simultaneously. Legend (Pie/Donut): Legend settings allow toggling and displaying legend percentages alongside actual values. Metric label (Single Score): Allows displaying the metric label name near/adjacent to the metric value to provide clear context for the displayed aggregated data. Gradient or texture options are not supported features for data display in workspace visualizations.

D: ServiceNow workspace data visualizations use defined color palettes, single colors, or threshold rules; they do not support gradient or texture display options.

1. ServiceNow Product Documentation (Washington DC) – Configure Pie and Donut data visualizations: "Component properties > Data labels: Select whether to show values, percentages, or both."

2. ServiceNow Product Documentation (Washington DC) – Data visualization component configuration in Next Experience: "Legend configuration > Display legend percentages alongside values."

3. ServiceNow Product Documentation (Xanadu) – Single score visualization component: "Header and Labels configuration > Metric label display settings near metric values."

In ServiceNow Performance Analytics, a Breakdown Source defines the unique set of elements used to group indicator data. When viewing an existing Breakdown Source record form (pacubes), associated breakdowns are displayed in the 'Breakdowns' related list at the bottom of the form. To create a new breakdown that uses this specific breakdown source, click the 'New' button on the 'Breakdowns' related list. This action opens a new Breakdown form with the Breakdown Source field automatically populated with the current breakdown source record, allowing you to create and associate the breakdown directly.

B: The 'Additional actions' menu provides standard record operations (like Save or Reload Form) and does not contain options to create or associate breakdowns. C: There is no standard 'Create Breakdowns' related link on the Breakdown Source form for creating or linking breakdowns. D: A Breakdown Source is defined using a single facts table and field; adding multiple facts tables is structurally invalid and does not create breakdowns.

1. ServiceNow Product Documentation (Washington DC): Performance Analytics > Create a breakdown source (Doc ID: pacreatebreakdownsource).

2. ServiceNow Product Documentation (Washington DC): Performance Analytics > Create a breakdown (Doc ID: pacreatebreakdown).

3. ServiceNow Product Documentation (Vancouver): Performance Analytics Setup and Configuration Guide > Linking Breakdowns to Breakdown Sources.

ServiceNow Performance Analytics allows organizations to collect, aggregate, and analyze indicator scores across tailored time frames using Custom Business Calendars. While default data collection relies on standard Gregorian calendar periods (such as standard months or quarters), Custom Business Calendars enable score analysis aligned with non-standard business time structures, such as 4-4-5 retail calendars, custom fiscal quarters, or operational shift cycles. By associating a business calendar with an indicator or widget, Performance Analytics aggregates historical scores according to defined business time periods rather than standard calendar boundaries.

A. Team Calendars manage member availability, shifts, and leave within IT Service Management and HR Service Delivery, and cannot serve as time-period structures for aggregating Performance Analytics scores.
B. Maintenance Calendars define blackout and change windows for IT infrastructure maintenance, providing scheduling governance rather than analytics time-period frameworks for score aggregation.
D. On-Call Calendars manage duty rosters and escalation schedules for support teams and lack integration for bucketing or evaluating Performance Analytics indicator scores over time periods.

1. ServiceNow Documentation: Performance Analytics – Section: "Apply business calendars to Performance Analytics". Product Documentation, Washington DC / Vancouver Releases.

2. ServiceNow Documentation: Core Configuration – Section: "Business Calendars". Product Documentation, System Administration Guide.

3. ServiceNow Product Documentation: Performance Analytics Setup – Section: "Indicator source calendar configuration and frequency settings".

When configuring a target for an indicator on the Analytics Hub in ServiceNow Performance Analytics, users can define target goals flexibly. A target can be defined as a specific numerical value or as an improvement percentage relative to a baseline score. To support performance planning, ServiceNow allows setting a start date in the future for when the target takes effect. Additionally, targets include a review date field, allowing process owners to set a scheduled date to evaluate indicator performance and consider updating or extending the target baseline.

C. Thresholds and targets are separate constructs in Performance Analytics; thresholds trigger notifications when boundaries are reached and are not configured as target options.

1. ServiceNow Official Documentation (Washington DC Release) - Create a target on the Analytics Hub: https://docs.servicenow.com/bundle/washingtondc-now-intelligence/page/use/performance-analytics/task/tCreateATargetInAnalyticsHub.html

2. ServiceNow Official Documentation - Target fields in Performance Analytics: Section "Target configuration properties and review dates", Performance Analytics Administration Guide.

3. ServiceNow Product Documentation - Difference between targets and thresholds in Performance Analytics: Performance Analytics Architecture & Usage Reference.

KPI Signals supports notifications by utilizing scheduled background jobs known as automated signal detection jobs. These jobs run periodically to analyze Performance Analytics indicator data using Statistical Process Control rules (such as Process Behavior Charts). When a signal detection job identifies a statistically significant shift, trend, or anomaly in the indicator scores, the system creates a signal record and automatically dispatches notifications to designated indicator owners and subscribed users.

A. By forwarding email notifications KPI Signals generates native system notifications triggered directly by signal detection events rather than forwarding external or pre-existing email notifications.
C. Through regular back-ups System back-ups serve data preservation and disaster recovery purposes and have no role in analyzing performance indicator scores or triggering signal notifications.
D. By setting auto-reply responses Auto-reply responses are automated inbound email handling mechanisms and are not used by KPI Signals to notify stakeholders of statistical anomalies.

1. ServiceNow Official Product Documentation (Xanadu Release): Performance Analytics — KPI Signals Overview and Configuration

Section: "KPI Signals process" & "Signal detection jobs"

URL: https://docs.servicenow.com/bundle/xanadu-performance-analytics-and-reporting/page/use/performance-analytics/concept/kpi-signals.html

2. ServiceNow Product Documentation (Washington DC Release): Managing KPI Signals Notifications

Section: "Setting up KPI Signals notifications and subscriptions"

Doc ID: KPI-Signals-Jobs-Sub-v1

URL: https://docs.servicenow.com/bundle/washingtondc-performance-analytics-and-reporting/page/use/performance-analytics/task/kpi-signals-notifications.html