- What You Are Actually Studying For
- Exam Mechanics: Format, Fee, Timing and Retakes
- Where the Points Live: The Six Domains
- Application Development: The 30% Anchor
- Case Management and Data and Integration: The 40% Pair
- User Experience, System Administration and Security
- Handling the Question Styles
- A Domain-Ordered Study Plan
- Choosing Preparation Materials Honestly
- Exam Day Logistics
- After the Exam: Retakes, Validity and Career Use
- Frequently Asked Questions
- The exam is PEGACPSSA25V1 for Pega Platform '25: 60 questions, 90 minutes, 70% to pass.
- Application Development is 30% of the exam; Case Management and Data and Integration are 20% each.
- You need a Certified Pega System Architect credential, in any version, before attempting this exam.
- Pega publishes no official practice exams, so treat mission quizzes and third-party questions as practice only.
What You Are Actually Studying For
On this site, CSSA is shorthand for the Certified Pega Senior System Architect credential issued by Pegasystems. If you are still orienting yourself, the explainer on what CSSA certification is covers the basics. This guide focuses on how to prepare for the current version of the exam and walk out with a pass on your first sitting.
The version matters. The exam covered here is PEGACPSSA25V1, aligned to Pega Platform '25. Pega also maintains an earlier exam for Platform '24.2 with a different, eight-domain outline. If you pull a study outline from an older source, check which platform version it targets before you trust the domain weights. Likewise, do not confuse this exam with the System Architect exam you took to qualify or with the Lead System Architect exam that sits above it. Each has its own scope, and mixing them is one of the quickest ways to study the wrong material.
The Senior System Architect level is where Pega candidates stop being judged on whether they can build a rule and start being judged on whether they can choose the right rule, the right data pattern and the right integration approach for a given business scenario. That shift in expectation should shape how you study from day one.
Exam Mechanics: Format, Fee, Timing and Retakes
Knowing the logistics removes avoidable stress. Here is the verified snapshot for the Platform '25 exam.
| Item | Detail |
|---|---|
| Exam code | PEGACPSSA25V1 |
| Questions | 60 |
| Time allowed | 90 minutes |
| Passing score | 70% |
| Fee | USD 190 per attempt plus applicable taxes (subject to change) |
| Languages | English and Japanese |
| Delivery | Pearson VUE test centers or OnVUE remote proctoring |
| Book policy | Closed book |
| Prerequisite | Certified Pega System Architect, any version |
A few details deserve extra attention:
- The NDA counts against your clock. You must accept a non-disclosure agreement before the exam starts, and under Pega's general guidance that time is included in the allotted exam time. Do not assume you get a full, untouched 90 minutes for questions.
- Extra time for some candidates. Candidates registered in Pearson VUE in an eligible non-native-English-speaking country who take the English exam automatically receive 30 additional minutes, shown in the registration confirmation. Check your confirmation rather than requesting it separately.
- Retake rules are strict. After a first failure you must wait three calendar days; after a second, 14 days. Each exam version can be attempted three times in the 12 months beginning with your first attempt, and every attempt costs the full fee. A careless first try is expensive.
- Identification. Acceptable ID is required, and the rules differ slightly between test center and remote delivery, so read the delivery-specific Pearson VUE requirements before exam day.
For a fuller breakdown of money and scheduling, see the CSSA certification cost guide, the exam dates and scheduling overview and the explanation of the CSSA passing score. If you are verifying eligibility first, the CSSA requirements article walks through the prerequisite.
Where the Points Live: The Six Domains
The six domains and their weights come directly from the official exam objectives. Use them to decide where your hours go.
| Domain | Weight | Approximate share of 60 questions |
|---|---|---|
| Application Development | 30% | About 18 |
| Case Management | 20% | About 12 |
| Data and Integration | 20% | About 12 |
| System Administration | 15% | About 9 |
| Security | 10% | About 6 |
| User Experience | 5% | About 3 |
The question counts above are simple arithmetic on the published percentages, offered as a planning aid. Actual counts on your form may vary. For a deeper tour of every area, the complete guide to all six CSSA domains goes topic by topic.
The strategic read is clear: Application Development, Case Management and Data and Integration together account for 70% of the exam. A candidate who is excellent in those three and merely adequate elsewhere is in a much stronger position than one who spreads effort evenly. Even so, the 30% outside those domains is more than enough to sink you if you ignore it, because the pass line is 70%.
Application Development: The 30% Anchor
Domain 1: Application Development (30%)
This is the biggest domain and the one that touches nearly everything else. Expect scenario questions that ask which design decision is best, not just which feature exists.
- How rules are organized across layers, rulesets and the class structure, and why reuse through inheritance and specialization matters
- Choosing among rule types for decisioning, validation and conditional behavior in a given requirement
- Reuse and maintainability decisions: where a rule belongs so that it can be shared without being overridden accidentally
- Debugging and tracing behavior when a rule does not resolve the way you expected
At the Senior level, the recurring question is "where should this live and why?" Practice explaining your choice of class, ruleset and rule type out loud. If you can defend the decision against two plausible alternatives, you are ready for the scenario format. If you can only recite the definition of a rule type, you will struggle when two answer options both look workable.
Because this domain is so heavily weighted, hands-on time in a Pega environment is not optional. Reading about rule resolution is far less effective than breaking it on purpose and watching what happens. The Senior System Architect mission on Pega Academy is the issuer's preparation pathway and is the natural place to build that muscle memory.
Case Management and Data and Integration: The 40% Pair
Domain 2: Case Management (20%)
Case design is where business process meets platform structure. Questions tend to describe a business scenario and ask how to model it.
- Designing case types with appropriate stages, steps and processes, including parent and child case relationships
- Controlling how work moves, routes and waits, including service-level expectations and escalation behavior
- Deciding what belongs in a stage versus a process versus a step, and why
- Case data modeling and how information flows between a parent case and its children
Domain 3: Data and Integration (20%)
This domain rewards candidates who understand data as a first-class design concern, not an afterthought bolted onto cases.
- Data modeling choices, including how data types are defined and where data is sourced from
- Connecting to external systems and deciding between integration approaches for a stated requirement
- Handling data access patterns, refresh behavior and the consequences of each for performance and accuracy
- Mapping and transforming data as it moves in and out of the application
These two domains are linked in practice, because most real cases depend on data from somewhere else. When you study them, build a small case that pulls in external data and watch how the pieces interact. Questions often bridge both areas, for example asking how a case should obtain and hold the data it needs at a particular stage.
User Experience, System Administration and Security
These three domains total 30% of the exam. They are individually smaller but not safe to skip.
Domain 5: System Administration (15%)
At 15%, this is worth roughly as much as a large slice of Case Management, and it is often under-studied because it feels less like development.
- Monitoring application health and understanding what the platform's diagnostic tools reveal
- Managing how applications are packaged, moved between environments and kept consistent
- Background processing and operational behavior that affects a running system
Domain 6: Security (10%)
Security questions test whether you can translate an access requirement into the right configuration.
- Authentication and authorization, and how access to data and functions is granted or restricted
- Role-based access and the principle of giving users only what they need
- Protecting sensitive data and recognizing misconfigurations that expose it
Domain 4: User Experience (5%)
The smallest domain, but a few questions can still decide a borderline result.
- Building and configuring user interfaces so they are reusable and consistent
- Controlling what users see and when, based on context and permissions
- Accessibility and responsiveness considerations in interface design
Because User Experience is only 5%, a sensible approach is to learn it efficiently, cover the core concepts, and avoid sinking disproportionate hours into it. Security and System Administration deserve a real, scheduled block each.
Handling the Question Styles
Pega lists several possible question styles for its exams: single-response multiple choice, multiple-response multiple choice, matching or drag-and-drop, and reading-passage or scenario questions. The distribution across these styles is not specified for this exam version, so do not count on any particular mix. Prepare for all of them.
Single and multiple response
Multiple-response questions are where partial knowledge hurts. If a question asks you to select more than one answer, you need to recognize every correct option and reject the near-misses. Practice by writing out why each wrong option is wrong, not just why the right one is right.
Matching and drag-and-drop
These test whether you can pair concepts correctly, such as a requirement with the feature that satisfies it. They reward clean mental categories. Flashcards that pair a scenario with a rule type or configuration area are a good fit here.
Reading-passage and scenario questions
Scenarios consume more time because you must read, extract the relevant constraints and then choose. Train yourself to underline the requirement words: what must be reusable, what must be restricted, what must happen automatically. Then eliminate options that violate any stated constraint. With 60 questions in 90 minutes, and the NDA coming out of that time, you have only a modest cushion per question, so do not let one dense scenario eat your clock. Flag it and move on.
Key Takeaway
Because the exam is closed book, your goal is recall plus judgment. Know the vocabulary cold so you spend your minutes on the judgment calls rather than decoding terms.
A Domain-Ordered Study Plan
Generic study methods are not the point here; the ordering is. The schedule below sequences domains by weight and by dependency, so earlier material supports later material. Adjust the length to your own availability, and compress or stretch weeks as needed.
Application Development foundations
- Work through rule organization, class structure and rule resolution in a live environment
- Practice explaining where a given rule should live and why
Application Development depth and Case Management
- Finish decisioning and reuse topics from Domain 1
- Build a multi-stage case with a child case to see parent-child behavior
Data and Integration
- Model data types and connect to an external source
- Compare integration approaches and note when each is the right choice
System Administration, Security and User Experience
- Give Security and System Administration their own focused sessions
- Cover User Experience efficiently, concentrating on reusable interface configuration
Integration review and timed practice
- Revisit your weakest domain first, then do timed sets across all six
- Rehearse flagging and skipping long scenario questions
The logic is straightforward. Application Development goes first and gets the most time because it is 30% and because Case Management and Data and Integration both depend on understanding how rules resolve and are organized. Security and System Administration come later because they are easier to learn once you have built something worth securing and administering. If you already hold System Architect experience, you can compress the early weeks; if your build experience is thin, extend them rather than skimming.
For a sense of how demanding this will feel against your background, the difficulty guide is a useful calibration, and the one-page CSSA cheat sheet makes a good final-week review document.
Choosing Preparation Materials Honestly
Be precise about what exists and what does not. The issuer's own preparation route is the Senior System Architect mission on Pega Academy, which is the recommended pathway for this exam. Beyond that, two cautions apply.
- Pega does not provide official practice certification exams. Anything labeled as an "official practice exam" for this credential should be treated with suspicion.
- Pega does not endorse third-party preparation materials. Mission quizzes and independent practice questions are study aids. They must not be treated, or represented, as actual certification questions.
Use independent practice questions the way they are meant to be used: to find gaps and rehearse the question formats, not to memorize answers. A candidate who memorizes a question bank without understanding the underlying design reasoning is exposed the moment the real exam phrases a scenario differently. If you want structured practice to find your weak domains, the CSSA practice tests are built for exactly that diagnostic purpose, and you can browse more training options and approaches to round out your plan.
Exam Day Logistics
Choose your delivery mode based on where you perform best. Pearson VUE test centers offer a controlled environment with no technical surprises from your own setup. OnVUE remote proctoring is convenient but requires a compliant room, working equipment and strict adherence to proctoring rules. Whichever you pick:
- Confirm the acceptable identification for your delivery method well before the day.
- Check your registration confirmation for the exact time allowance, particularly if you may qualify for the extra 30 minutes.
- Arrive, or log in, early enough to complete check-in without rushing, remembering that the NDA is part of your exam time.
- Plan your pacing: with 60 questions and 90 minutes, aim to leave a buffer at the end for flagged items.
The exam is closed book, so there is nothing to bring except your identification and, for remote delivery, a properly prepared space. For scheduling windows and practical booking guidance, see the exam dates and deadlines article.
After the Exam: Retakes, Validity and Career Use
If you do not pass, the retake rules above govern your next move: three calendar days after a first failure and 14 after a second, with three attempts per version in a 12-month window from your first attempt. Use the waiting period to study your weakest domain rather than simply re-reading everything.
On validity, certifications currently do not expire, but Pega reserves the right to impose recertification requirements, so treat that as subject to change and check the current policy periodically. Pega also provides a way to verify a certification, which is useful when employers ask for proof.
Employers who hire for Pega skills, typically organizations running Pega-based case management and workflow applications and the consultancies that implement them for clients, often look for senior-level credentials when staffing design-heavy roles. If you are weighing the career side, the ROI analysis, the salary guide and the overview of CSSA-related jobs cover it in more detail. As always, treat any salary figure you see elsewhere cautiously, because pay varies widely by region, employer and experience.
Frequently Asked Questions
You need a Certified Pega System Architect credential in any version. The Senior System Architect mission on Pega Academy is the issuer's preparation pathway for the exam itself.
The Platform '25 exam has 60 questions in 90 minutes, and the passing score is 70%. Accepting the NDA is required and, under Pega's general guidance, counts toward the allotted time.
Application Development carries 30%, the most of any domain, so it deserves the largest share of study time. Case Management and Data and Integration follow at 20% each, then System Administration at 15%, Security at 10% and User Experience at 5%.
No. Pega does not provide official practice certification exams and does not endorse third-party materials. Mission quizzes and independent practice questions are useful for study but are not actual certification questions.
You can retake after three calendar days following the first failure and 14 days after the second. Each exam version allows three attempts in the 12 months starting from your first attempt, and each attempt costs the full USD 190 fee plus applicable taxes.
Preparing deliberately, weighting your time by the official domain percentages and practicing the scenario-style reasoning the Senior level demands gives you the best chance of passing on the first try. For a consolidated starting point, the main CSSA study guide and the practice test site are good places to begin your diagnostic work.