ServiceNow CIS-PA Exam Guide - Indicators, Breakdowns, Dashboards

A ServiceNow Platform Analytics specialist spends the week turning table data into numbers people are willing to act on. That means defining indicator sources, building indicators, mapping breakdowns so a score can be sliced by assignment group or priority, scheduling collection jobs and assembling dashboards leaders actually open. The CIS-PA exam asks about that work directly, over 60 questions in 90 minutes.

Almost nothing on this exam rewards a memorised definition. The questions describe a situation that a real implementation throws up — a score that collects no data, a breakdown that double-counts records, a dashboard that takes half a minute to load — and ask what you would configure next. That is why candidates who have built analytics content in an instance tend to find CIS-PA fair, while candidates who have only read about it find it slippery.

This guide walks through the job the credential describes, what changed when ServiceNow folded Performance Analytics into Platform Analytics, the exam facts you need before booking, how the blueprint distributes its weight, and the practice that actually moves your score.

What does a ServiceNow Platform Analytics implementer actually do?

Strip the exam away and the role comes down to four repeating questions: what should we measure, where does that number come from, what should we compare it against, and who reads it. Every configuration object in Platform Analytics exists to answer one of those.

Deciding what is worth measuring

The work starts away from the platform. A service desk manager wants to know whether first-line resolution is improving. A change manager wants emergency changes to stop creeping upward. The implementer's job is to translate that into something the platform can count — a record set, a condition, a unit and a frequency — and to push back when a request cannot be measured honestly. CIS-PA scenarios often start here, describing a stakeholder request and asking which analytics object you would create first.

Building the data behind a number

Once the question is agreed, the configuration follows a predictable chain. An indicator source names the table and the conditions that define the population of records. An indicator sits on that source and says what to do with the population — count it, sum a field, average a duration — and how often. Formula indicators combine other indicators into a rate or a percentage. Getting the source right matters more than anything downstream, because an indicator built on a badly scoped source produces a number that is wrong in a way nobody notices for months.

Making a score answer "compared to what"

A single number is rarely useful. Breakdowns are what let one indicator be read by assignment group, by priority, by location or by category, and breakdown sources are how those dimensions are defined and mapped. This is where implementations most often go wrong: a mapping that joins on the wrong field, a breakdown left without exclusions so retired groups keep appearing, or a matrix combination that multiplies the collection job beyond what the instance can finish overnight. Expect the exam to test the difference between a breakdown source, a breakdown mapping and a bucket group, and to ask which one you would change to fix a described symptom.

Publishing something people keep opening

The last stretch is presentation. Platform Analytics dashboards assemble visualizations over indicators and reports, with unified filters that apply across a whole tab, and KPI Details for the drill-down that answers "why is this number moving". The implementer chooses the visualization that matches the question — a trend for movement over time, a bar for comparison across groups, a single score for a target — and keeps the dashboard fast enough that people do not abandon it. ServiceNow's product documentation is the reference to keep open while you learn these objects, because it uses the exact terminology the exam uses.

Why is the certification now called Platform Analytics instead of Performance Analytics?

Many candidates still search for "ServiceNow Performance Analytics certification", and for years that was the right name. ServiceNow has since consolidated reporting, dashboards and Performance Analytics into a single Platform Analytics experience, and the implementation specialist credential moved with it: the current name is the ServiceNow Certified Implementation Specialist – Platform Analytics, code CIS-PA.

The capabilities you already know did not disappear. Indicators, indicator sources, breakdowns and collection jobs are still the engine; they now sit under Platform Analytics administration rather than in a standalone Performance Analytics application, alongside the newer dashboard and visualization experience. At the same time ServiceNow has been steering customers away from the older Core UI reporting and dashboards toward the new experience, which is why so much of the exam's dashboard content reads as new even to experienced Performance Analytics users. The timeline for retiring older content differs by instance, so confirm what applies to yours in ServiceNow's documentation rather than in a forum post.

For the platform version itself, ServiceNow's documentation shows the Australia release as current when this guide was checked in September 2026, and Platform Analytics is one of that release's headline areas. Two practical consequences follow. First, study material written before the change may describe menus and dashboard features that no longer match what you see. Second, screenshots and step-by-step walkthroughs age faster than concepts, so anchor your preparation in what each object does and why, then check the current interface in an instance you can open.

What are the CIS-PA exam facts before you book a seat?

The logistics are short, and they shape how you prepare more than most candidates expect. Sixty questions in ninety minutes is a comfortable ninety seconds each, which sounds generous until you meet a scenario with a five-line setup and four plausible answers.

Exam detail	CIS-PA
Certification	ServiceNow Certified Implementation Specialist - Platform Analytics
Exam code	CIS-PA
Vendor	ServiceNow
Category	Platform and AI
Number of questions	60
Duration	90 minutes
Exam fee	USD $450
Result	Pass / Fail

Two points deserve emphasis. The result is reported as Pass or Fail, not as a percentage, so there is no published pass mark to aim at and no meaningful "pass percentage" to look up; any number you find quoted on a forum is somebody's estimate. And the fee is per attempt, which is the strongest argument there is for sitting the exam only once you are scoring consistently under timed conditions.

Before you register, read ServiceNow's official CIS-PA exam blueprint, which lists the domains and the objectives inside each one, and check the CIS-PA credential path on ServiceNow University for the current prerequisites, training expectations and voucher arrangements. ServiceNow updates exams alongside platform releases, so treat those two pages as the source of truth for anything that might have moved since this article was written.

How much of the CIS-PA blueprint is indicators, breakdowns and dashboards?

Three-quarters of it. The blueprint spreads across six areas, and three of them — indicators, breakdowns and visualization — carry a quarter of the weight each. Plan your study time in that proportion rather than dividing it evenly across topics.

Exam area	Weight
Architecture and Deployment	10%
Configure Indicators and Indicator Sources	25%
Configure Breakdowns and Breakdown Sources	25%
Data Collection	10%
Data Visualization and Dashboards	25%
Administration and Advanced Implementation Solutions	5%

The full objective list under each of those areas is set out on our CIS-PA certification exam syllabus page, which is worth reading beside the blueprint as you plan.

Architecture and deployment

This area covers what Platform Analytics is made of and the order in which an implementation is delivered: the solution components, who the stakeholders are, what a typical deployment sequence looks like, and which use cases the platform is a good fit for. It is a small slice of the exam but it frames everything else, because several scenario questions are really asking "at which stage of the deployment does this belong".

Configuring indicators and indicator sources

The heaviest area alongside breakdowns and dashboards. Know the indicator types and when each applies, how an indicator source's table and conditions define the record population, how facts tables relate to what is collected, and how aggregation and scripted calculations change the number produced. Questions here are often diagnostic: a score returns zero, or a value nobody can reconcile with the list view, and you must name the setting responsible.

Configuring breakdowns and breakdown sources

The other quarter, and the area that separates candidates who have implemented from candidates who have read. You need breakdown sources and mappings, manual and scripted breakdown mappings, the breakdown matrix and what it costs to collect, breakdown exclusions, and bucket groups for turning a continuous value such as age or duration into readable bands. Be able to explain, in one sentence each, when you would use a scripted mapping instead of a direct one and what an exclusion is protecting you from.

Data collection

Smaller in weight but central to troubleshooting. Collection jobs, their scheduling and order, historical data collection when a customer wants the first dashboard to show a trend rather than a single point, and the log evidence you use when a job fails or runs long. Many "no data on the dashboard" scenarios resolve here rather than in the indicator.

Data visualization and dashboards

The third quarter. Which visualization suits which question, how dashboards and tabs are built and shared, unified filters and how they interact with what each widget already filters, KPI Details for drill-down, and the choices that keep a dashboard responsive. Since this is the part of the product that changed most in the move to Platform Analytics, it is the part where old notes mislead most often.

Administration and advanced implementation solutions

The smallest slice covers the settings and edge cases an implementer meets after go-live: analytics properties, roles and who can see what, and the advanced configurations that solve requirements the standard objects do not. Do not skip it — five per cent of sixty questions is still three questions, and they are usually easy marks if you have read the property list once.

How does a Platform Analytics implementation run from data source to dashboard?

Studying the six blueprint areas separately leaves a gap the exam exploits, because real scenarios cross them. It helps to hold one end-to-end path in your head and locate each question on it.

Step 1 — scope the source

Choose the table and write the conditions that define exactly which records count. If the question is about resolved incidents, decide now whether reopened records are in or out. Everything downstream inherits this decision, and a source that is 5% wrong makes every breakdown of it 5% wrong.

Step 2 — define the indicator

Attach the indicator to the source, pick the type, choose the aggregate and set the frequency. A formula indicator is the right tool when the number people actually want is a ratio of two counts, not a count itself. Write down the unit, because a percentage presented as a count is the most common reason a dashboard gets quietly ignored.

Step 3 — map the breakdowns

Decide the two or three dimensions people will slice by and configure the sources and mappings for them. Apply exclusions so inactive groups and test categories do not clutter the axis, and use bucket groups where a continuous value needs bands. Resist the urge to enable every combination in the matrix; each one has a collection cost.

Step 4 — collect and verify

Schedule the collection job, run it, and then do the step candidates skip: check the collected scores against a list view for one day and one group. If the numbers disagree, the fault is almost always in the source conditions or the breakdown mapping, and finding that now is far cheaper than finding it after a steering-group meeting.

Step 5 — build the dashboard

Assemble the visualizations, add unified filters at the tab level rather than repeating the same filter on every widget, configure KPI Details so a viewer can drill from a number into the records behind it, and share it with the right roles. Then watch what people click; a dashboard nobody opens is a failed implementation, whatever the configuration looks like.

How do you build hands-on practice that matches CIS-PA scenarios?

A free personal developer instance is enough to reproduce nearly everything the exam describes, and an hour spent building beats an evening spent reading. The trick is to practise in the shape the questions take: start from a symptom, not from a feature.

Give yourself concrete exercises. Build an indicator source on the incident table and count resolved incidents per week. Break it down by assignment group, then by priority, then by both, and watch what the matrix does to the collection job. Deliberately break something — point the source at the wrong condition, remove an exclusion, misalign a breakdown mapping — and then diagnose it from the dashboard backwards, the way an exam scenario makes you. Create a bucket group for incident age and see how the bands change the story the chart tells. Build a formula indicator for first-line resolution rate and check the result by hand against a list view.

When you can do those without looking anything up, move on to measuring readiness under a clock. Sixty questions in ninety minutes is its own skill: scenario stems are long, and the habit of reading a stem twice will run you out of time. Work through a full-length CIS-PA practice test in one sitting, keep every question you got wrong or guessed, and group those by blueprint area — the area with the longest list tells you exactly where the next instance session should go. Repeat until a fresh set of questions stops surprising you.

One caution about study material generally. The rename means a good deal of what you will find online describes the earlier Performance Analytics interface. Concepts carry over almost entirely; menus, dashboard building and visualization options do not. When a resource and your instance disagree, believe the instance and ServiceNow's documentation.

Where do CIS-PA candidates lose marks they could have kept?

These patterns turn up in post-exam debriefs over and over, and none of them needs more study time to fix — only differently aimed study time.

• Learning objects instead of symptoms. You will rarely be asked what a breakdown source is. You will often be asked why a breakdown shows duplicate rows.
• Underrating breakdowns. They carry a quarter of the exam and are the hardest area to understand without configuring one. Candidates who skim them lose marks across several questions at once.
• Treating data collection as background plumbing. A large share of troubleshooting scenarios resolve in the job schedule, the historical collection or the logs.
• Studying the old interface. Material written for the Performance Analytics dashboards will mislead you on the visualization and dashboard questions, which are a quarter of the paper.
• Guessing at a pass mark. Results are Pass or Fail; chasing an imagined percentage is a distraction from the only useful signal, which is your own score on fresh timed questions.
• Reading every stem twice. With ninety minutes for sixty questions, read the final sentence first so you know what is being asked, then read the setup once with that in mind, and flag anything that takes more than two minutes.

Who should sit CIS-PA, and where does the credential lead?

The exam suits people who already work in the platform and want the analytics layer to be their specialism. ServiceNow administrators who are asked for reports and end up owning dashboards. Implementation consultants who deliver analytics as part of a wider programme. Service delivery and process owners who define the KPIs and want to configure them properly rather than describe them to somebody else. Data and reporting analysts moving onto ServiceNow from another tool, who know the analysis but not the platform's objects.

It also fits neatly beside other ServiceNow implementation credentials. Analytics sits on top of whatever a customer has already built, so an implementer who can measure a process is more useful on a project than one who can only configure it — and the questions analytics raises about data quality frequently loop back into the configuration work itself.

As a career step, the value is less about the certificate than about what preparing for it forces you to learn. Organisations are steadily moving reporting onto the newer Platform Analytics experience, and that migration needs people who understand indicators and breakdowns rather than people who can only rebuild an old report in a new chart. Being demonstrably one of those people is what the credential signals, and it is the reason CIS-PA has held its value through the rename.

If you are weighing it up, a fair test is this: could you sit with a manager tomorrow, turn their vague request into an indicator source, a breakdown and a dashboard tab, and explain your choices? If yes, book the exam. If not, you now know which of those three to practise first.

Frequently Asked Questions

How many questions are on the CIS-PA exam?

The ServiceNow CIS-PA exam has 60 questions with a 90-minute time limit, which works out at about ninety seconds each. The scenario stems are long, so practise reading the question first and the setup second, and flag anything that takes more than two minutes.

What is the passing score for CIS-PA?

ServiceNow reports the CIS-PA result as Pass or Fail and publishes no numeric pass mark. Any percentage quoted on forums is an estimate. Judge your readiness instead by your score on fresh, timed questions and by being able to explain why each wrong option is wrong.

How much does the CIS-PA exam cost?

The CIS-PA exam fee is USD $450 per attempt. ServiceNow sometimes issues vouchers through its training programmes, so check the credential path on ServiceNow University for current pricing and any voucher arrangements before you register for a date.

Is CIS-PA the same as the old Performance Analytics certification?

It is the successor to it. ServiceNow consolidated reporting and Performance Analytics into Platform Analytics, and the implementation specialist credential is now the Certified Implementation Specialist - Platform Analytics. Indicators, breakdowns and collection jobs still apply; the dashboard and visualization side changed most.

Which CIS-PA topics carry the most weight?

Indicators and indicator sources, breakdowns and breakdown sources, and data visualization and dashboards each carry a quarter of the exam. Architecture and deployment and data collection take ten per cent each, with administration and advanced solutions making up the remaining five.

Do I need hands-on experience to pass CIS-PA?

Practically, yes. Most questions describe a symptom and ask what you would configure, which is hard to answer from reading alone. A free personal developer instance lets you build indicator sources, breakdowns and dashboards, and deliberately break them so you learn to diagnose.

How long does it take to prepare for CIS-PA?

Candidates who already administer ServiceNow and have built reports usually need a few focused weeks. Allow longer if breakdowns, collection jobs or the newer dashboard experience are unfamiliar, since those areas together account for most of the exam's weight.

Select ratingPoorOkayGoodGreatAwesome

Rating: 5 / 5 (75 votes)