The Pega Certified Senior System Architect (CPSSA) exam gives you 60 questions in 90 minutes, and Application Development alone takes 30% of them. That leaves 70% spread across five other domains that rarely get the same attention. This guide covers the exam format, the mission you must clear first, and a 30-day plan that gives every domain its fair share of study time.
The CPSSA sits above the standard System Architect credential in Pega's certification path. According to Pega Academy, it confirms that you can design and build Pega applications that go beyond a single team, with the structure to support reuse across an organization.
That framing matters. A System Architect proves they can build a working application. A Senior System Architect proves they can build one that other teams can safely extend, without breaking what came before. The exam checks for that judgment through scenario questions, not simple recall.
The official CPSSA exam page lists the current version as PEGACPSSA25V1, built on Pega Platform '25. It is offered in English and Japanese. If your study material references an older platform version, check that it still matches the current blueprint before you rely on it.
Most candidates who sit the CPSSA already hold the standard System Architect certification and have spent real time building Pega applications. The exam assumes you have configured case types, built data pages and worked with security models before, not that you are meeting them for the first time.
That assumption shows up in how the questions are written. A standard System Architect question might ask you to identify a rule type. A CPSSA question is more likely to describe a case that already exists, note a constraint the business has added, and ask which change respects both the constraint and the application's existing structure. You are being tested on judgment under realistic conditions, not isolated facts.
Before you can register for the CPSSA exam, Pega requires you to complete the Senior System Architect mission inside Pega Academy. This is not a suggestion. It is a stated prerequisite on the official exam page.
The mission walks through the same ground the exam covers, but at a slower pace and with guided exercises. Pega Academy hosts several versions of it, including the Senior System Architect mission, v8, which lines up with the current PEGACPSSA25V1 exam version. Older versions, down to v1, still exist on the platform for reference, but you should complete the version that matches your exam.
Treat the mission as your first study block, not a formality to click through. The exercises inside it use the same vocabulary and the same kind of multi-step scenarios you will see on exam day. Candidates who rush the mission to "unlock" the exam often find they have to relearn the same material a second time during their real prep.
Budget real hours for this step. It is reasonable to spend one to two weeks on the mission alone before you move into the domain-by-domain plan later in this guide.
The mission is also the cheapest way to find out where your real gaps are before you commit to a full study schedule. If a section of the mission feels unfamiliar even after you work through it, that is a strong signal about which domain in the plan below deserves extra days, not fewer.
The CPSSA format is straightforward to state. You get 90 minutes to answer 60 questions, which works out to 90 seconds per question on average. The passing score is 70%.
The exam is proctored through Pearson VUE, with two delivery choices: a physical test center or an online proctored session from your own computer. Both options follow the same question set and time limit.
Here is the format at a glance:
| Item | Detail |
|---|---|
| Questions | 60 |
| Time | 90 minutes |
| Passing score | 70% |
| Exam code | PEGACPSSA25V1 |
| Languages | English, Japanese |
| Delivery | Pearson VUE, test center or online proctored |
| Prerequisite | Senior System Architect mission |
Unlike some vendor exams, Pega publishes a flat 70% cut score rather than a hidden or scaled one. That makes planning simpler: you need roughly 42 correct answers out of 60, and every domain's questions count the same toward that total.
Pega splits the CPSSA blueprint into six domains, each with its own share of the 60 questions. Knowing the exact split changes how you should spend your study hours.
| Domain | Weight | About how many questions |
|---|---|---|
| Application Development | 30% | 18 |
| Case Management | 20% | 12 |
| Data and Integration | 20% | 12 |
| System Administration | 15% | 9 |
| Security | 10% | 6 |
| User Experience | 5% | 3 |
Application Development is the largest single domain, covering class hierarchy, modular architecture, the New Application wizard, rule resolution, circumstancing, queue processors, activities, property automation, versioning and ruleset migration. If you want a deeper walk through why that one domain deserves outsized attention, this breakdown of the CPSSA's 30% domain is worth reading alongside this guide.
What that article does not spend much time on is everything else, and everything else is still 70% of your score. Case Management and Data and Integration together match Application Development in size. System Administration, Security and User Experience add another 30% on top. A candidate who masters Application Development and treats the rest as an afterthought is still gambling with 42 of the 60 questions.
There is a reason the blueprint is shaped this way. A Senior System Architect is not only expected to write good Application Development rules, but to make sure those rules keep working once real cases, real data and real users are layered on top. Case Management and Data and Integration are where that layering actually happens, which is why Pega gives them as much combined weight as the domain most candidates treat as the whole exam.
These two domains sit tied for second place at 20% each, 12 questions apiece. Together they outweigh Application Development, yet they get far less attention in most prep discussions because neither one is the single biggest line on the chart.
Case Management on the CPSSA blueprint covers work groups, parallel processing, concurrent access management, flow action configuration and service-level agreements. This is the domain that tests whether you can design a case that several people can work on at once without stepping on each other.
Concurrent access management deserves particular attention. Questions in this area often describe two users opening the same case, and ask what the platform does to prevent one from silently overwriting the other's changes. Work groups and parallel processing extend that same idea to teams, not just individuals.
Service-level agreements round out the domain. Know how an SLA escalates a case, what happens when a deadline passes, and how flow actions can be configured to respond to that escalation rather than just record it.
This domain covers data validation, data pages, application exchange, connector error handling and field value rules. It is the most technical of the six, and it rewards candidates who have actually built and tested a data page rather than just read about one.
Connector error handling is a common source of scenario questions. Expect questions that describe a connector failing partway through a transaction and ask what the correct handling pattern is, rather than questions that simply ask you to define a connector.
Field value rules and data validation often appear together. A typical question might describe a field that should only accept certain values, then ask which rule type enforces that constraint without requiring custom code. Application exchange, Pega's packaging mechanism for sharing components, is smaller within this domain but still tested directly.
If you have only ever consumed data pages that someone else built, spend extra time building your own from scratch, including at least one that fails on purpose so you can watch the error handling path play out. Reading about a failure pattern and watching it happen are two different levels of understanding, and the exam is written to separate candidates who have only done the former.
The last three domains add up to 30% of the CPSSA exam, roughly 18 questions. They are the ones most likely to get squeezed out when candidates run low on time, which is exactly why they decide close results.
This domain covers performance measurement, debugging, log file review and application settings configuration. It tests whether you can find and explain the cause of a problem in a running application, not just whether you can build a new feature from scratch.
Practice reading a log file end to end, not just skimming for error keywords. Many CPSSA scenario questions describe symptoms, such as a slow case or a rule that silently fails to fire, and ask you to identify which log or performance tool would reveal the cause.
Security on the CPSSA blueprint covers access control types, case attachments, data encryption and audit tracking. Access control questions typically describe a user who can see more or less than they should, and ask which control type explains the gap.
Case attachments and encryption are smaller topics inside this domain but still directly tested. Know how Pega secures an attachment at rest and in transit, and how audit tracking records who changed what and when. These are the kinds of details that are easy to skip in a general review and easy to lose a point on if you do.
The smallest domain on the blueprint, User Experience still carries real questions worth real points. It covers how an application looks and behaves to the people actually using it, separate from the backend logic tested elsewhere.
Because it is the smallest domain, a short, focused review session near the end of your plan is usually enough. Do not skip it entirely. Three questions out of 60 is still 5% of your total score, and they are often some of the more straightforward points on the exam if you have spent any time in a live application.
Candidates sometimes assume a 5% domain cannot be worth planning around. On a 60 question exam with a 70% cut score, though, three careless mistakes in a domain you ignored can be the exact margin between passing and retaking the exam.
This plan gives each domain study days roughly in proportion to its weight, after you finish the Senior System Architect mission described earlier. It assumes one to two focused hours a day, with hands-on practice in a Pega application whenever you can get access to one.
Start with the heaviest domain while your energy and focus are highest. Work through class hierarchy and modular architecture first, since later topics like rule resolution and circumstancing build on that structure. Finish the block with queue processors, activities, property automation and ruleset migration.
Build a case from scratch that involves more than one work group. Configure a flow action that triggers under a specific condition, then set up an SLA on the same case and watch what happens when it escalates. Doing this hands-on, rather than only reading about it, is what the study guide for certified system architects also recommends for the underlying System Architect skills this domain builds on.
Create a data page, then deliberately break a connector to see how error handling behaves. Practice writing field value rules and validation conditions until you can explain, out loud, why a given rule is the right tool for a given constraint.
Spend these days split between the two domains. Review log files from a real or practice application, and trace at least one performance problem back to its cause. Then shift to access control: set up two roles with different permissions on the same case type and confirm the restriction behaves as expected.
A shorter block for the smallest domain. Review how portal layouts, case views and user-facing configuration decisions affect what an end user actually sees and can do.
Sit a complete timed practice set of 60 questions in 90 minutes. Review every wrong answer and note which domain it came from, then spend your final evening on light review of your weakest areas rather than new material.
With 90 seconds per question on average, pacing is part of the test. Check your progress at the halfway point. If you have answered roughly 30 questions in about 45 minutes, you are on track to finish with time to review flagged items.
Scenario questions on the CPSSA often describe a situation rather than asking for a simple definition. Read the full scenario before looking at the answer choices, since two options will often sound plausible and only one matches how Pega actually behaves in that situation.
These are the most common pitfalls candidates report:
If you are taking the online proctored option, test your webcam and connection ahead of time so a technical issue does not eat into your 90 minutes.
The scenario format itself is worth getting comfortable with before exam day. Because most CPSSA questions describe a situation rather than ask for a definition, you are reading more words per question than on many other certification exams. Practicing with timed, scenario-style questions trains your reading speed for this specific format, which matters as much as knowing the material once you are under the clock.
Practice questions are most useful for two things: getting used to the scenario-style format, and finding out which of the six domains is actually your weakest, rather than which one you feel least confident about. They work best alongside the mission and hands-on practice, not as a replacement for either.
The Pega CPSSA practice questions on ProcessExam let you test yourself in a similar format to the real exam. ProcessExam is an independent practice provider, not Pega, and a good practice score is a signal to keep studying in the right direction, not a guarantee of an exam result.
A short video can help you see how a Senior System Architect candidate thinks through this kind of exam before you start your own timed practice.
Use each wrong practice answer as a pointer back to one of the six domains in your plan, and adjust your remaining study days toward whichever domain keeps showing up in your mistakes.
The CPSSA is a step above the standard System Architect credential, and it signals something specific to employers: you can design for reuse across teams, not just build one working application in isolation. That distinction matters more as organizations run more of their case work on a shared Pega platform rather than isolated applications.
For architects already working in Pega environments, the credential formalizes skills many are already using day to day, from managing concurrent case access to handling connector failures gracefully. For those earlier in their Pega career, preparing for the CPSSA is also a structured way to close gaps before a senior-level role expects that knowledge already.
It also changes the kind of work you get handed. Teams tend to route the harder, cross-application decisions, the ones with real consequences if reuse breaks down, toward whoever already holds the senior credential. Preparing for the CPSSA properly, across all six domains rather than just the biggest one, is as much about being ready for that work as it is about passing the exam itself.
If you are still building the foundation this exam assumes, the guaranteed-success guide to system architect exam questions is a reasonable place to shore up the base System Architect material first, before layering the CPSSA's senior-level scenarios on top.
The CPSSA exam has 60 questions, and you have 90 minutes to complete them. That works out to an average of 90 seconds per question, so pacing matters as much as knowledge.
The passing score is 70%. Since the exam has 60 questions, that means you need roughly 42 correct answers to pass, and every domain's questions count equally toward that total.
Yes. Pega requires candidates to complete the Senior System Architect mission in Pega Academy before registering for the CPSSA exam. Treat it as the first block of your study plan, not a step to rush through.
Application Development carries the most weight at 30% of the exam, about 18 of the 60 questions. Case Management and Data and Integration follow, tied at 20% each, so together they match Application Development in size.
The exam is proctored through Pearson VUE. You can choose a physical test center or an online proctored session from your own computer, and both follow the same 60 question, 90 minute format.
The Pega CPSSA exam gives you 60 questions in 90 minutes with a flat 70% passing score, and it requires the Senior System Architect mission before you can even register. Application Development carries the most weight at 30%, but Case Management and Data and Integration together match it, and System Administration, Security and User Experience still add up to 30% more.
Study the mission first, then move through all six domains in proportion to their weight rather than stopping once Application Development feels solid. Practice hands-on in a real application, use timed practice questions to find your weakest domain, and leave room in your final days for a full timed review before exam day.