Architecture and Deployment
About 9% of the CIS-PA exam — see all 6 domains.
- Back end and front ends: the PA back end (indicators, sources, jobs, scores, snapshots) is shared; the Platform Analytics experience and the Core UI are two front ends over it. In Zurich, Core UI and Platform Analytics experience dashboards sit side by side in the Platform Analytics library, and the Migration Center moves Core UI content into Platform Analytics.
- Platform Analytics Solutions: prebuilt sets of indicators, sources, breakdowns, dashboards, and data collection jobs for a product area (some still named "content packs", for example Performance Analytics Content Pack for Procurement Service Management). Activating a solution installs its data collector jobs; a solution's periodic job must be activated before it collects.
- Licensing: without a paid Performance Analytics subscription, use is limited to 180 days of data collection (five months for monthly indicators) and specific ServiceNow-provided indicators (for example Complimentary Performance Analytics for Incident Management), and Data snapshots cannot be activated. Custom indicators and breakdowns need the subscription.
- Implementation flow: identify the business questions and KPIs → choose or build indicator sources → define indicators → add breakdowns → set up data collection (historical once, then periodic) → build visualizations and dashboards → set targets and thresholds → grant roles.
- KPI design tooling such as KPI Composer helps translate a business question into indicator and breakdown structure.
Sample questions from this domain
Three of the 27 in this domain, with the reasoning. The full set is in the question bank.
Which ServiceNow capability is designed to capture data over time so that administrators can analyze trends, set targets, and forecast future performance?
- A. Performance Analytics ✓
- B. Reporting in the Core UI
- C. Spotlight record ranking
- D. KPI Signals change alerts
Why: Performance Analytics (part of Platform Analytics) collects indicator scores on a schedule and stores them over time, which is what enables trend analysis, targets, thresholds, and forecasting. Reporting in the Core UI queries live data and shows the current state without keeping a history of scores. Spotlight ranks individual records by weighted criteria rather than capturing a time series. KPI Signals detects statistically significant changes in indicators that already have scores; it consumes collected scores rather than capturing them or setting targets.
What is the fundamental difference between a standard report and a Performance Analytics indicator?
- A. A report stores collected snapshots over time while an indicator queries the live table on each view
- B. An indicator and a report both query live data, but an indicator adds targets and thresholds on top
- C. An indicator stores collected scores over time while a report shows the current real-time state ✓
- D. An indicator is calculated from other indicators when viewed, while a report keeps stored totals
Why: Indicators are collected by data collection jobs and their scores persist in the scores tables (Scores Level 1 and Level 2), so history accumulates. Standard reports query live data and reflect only the current state. The statement that reports store snapshots while indicators query live data reverses the two. Saying both query live data ignores that indicator scores are collected and stored; targets and thresholds sit on top of stored scores. Calculation when viewed applies only to formula indicators, and reports do not keep collected totals.
An organization wants to begin using Performance Analytics quickly with predefined indicators, breakdowns, and dashboards for ITSM. What should they deploy?
- A. A custom indicator source built from scratch
- B. A KPI Signals definition per ITSM indicator
- C. A Performance Analytics content pack (solution) ✓
- D. A historical data collection job for ITSM data
Why: A content pack (Platform Analytics Solution) delivers out-of-the-box indicators, breakdowns, widgets, and dashboards for an application such as Incident Management, which is the fast path described in the stem. A custom indicator source built from scratch is the slow, manual approach and contains no dashboards. KPI Signals definitions detect changes in indicators that must already exist. A historical data collection job backfills scores for indicators that already exist; it does not create indicators, breakdowns, or dashboards.