- There Is No Official CSSA Pass Rate
- Passing Score vs. Pass Rate: Two Different Things
- What We Can Measure Instead
- How the Exam Format Shapes Outcomes
- Domain Weights as a Proxy for Where Candidates Lose Points
- The Prerequisite Filter and Who Actually Sits the Exam
- Retake Rules and the Cost of a Failed Attempt
- How to Spot Fabricated Pass-Rate Claims
- A Domain-Weighted Preparation Schedule
- Frequently Asked Questions
- No official pass rate for Certified Pega Senior System Architect was found in the reviewed Pega sources.
- The 70% figure is the passing score on a 60-question, 90-minute exam, not the share of candidates who pass.
- Application Development carries 30% of the exam, so it is the single largest lever on your result.
- A failed attempt costs USD 190 plus taxes, and the three attempts per version allowed in 12 months each cost the full fee.
There Is No Official CSSA Pass Rate
Search for the pass rate of the Certified Pega Senior System Architect exam and you will find confident numbers on forums, in training-vendor marketing, and in social posts. None of them trace back to Pega. In the sources reviewed for this article (the Pega Academy exam page for Platform '25, the certification FAQs, the exam policies FAQs, and the preparation pages), Pega does not publish how many candidates pass or fail. That is the honest starting point for any discussion of CSSA pass rates in 2026.
On this site, "CSSA" is shorthand for the Certified Pega Senior System Architect credential (exam code PEGACPSSA25V1, scoped to Pega Platform '25). Other credentials in the industry share the same acronym, and their published statistics have no bearing on this exam. If you land on a page quoting a pass percentage, check which credential it is actually describing before you let it shape your expectations.
Passing Score vs. Pass Rate: Two Different Things
The most common confusion is treating "70%" as a pass rate. It is not. The two terms measure completely different things:
| Term | What it means | Published for CSSA? |
|---|---|---|
| Passing score | The minimum performance an individual candidate must reach on the exam | Yes: 70% |
| Pass rate | The share of all candidates who pass across a given period | No official figure found |
| Exam length | Number of questions and time allowed | Yes: 60 questions, 90 minutes |
| Attempt fee | Cost per sitting | Yes: USD 190 plus applicable taxes, subject to change |
The passing score tells you how well you personally must perform: roughly 42 of 60 questions correct if every question were weighted equally. Pega does not state that all items carry equal weight, so treat that arithmetic as a planning heuristic rather than a guarantee. For a deeper look at the threshold itself, see our guide to the CSSA passing score.
What We Can Measure Instead
Without an official pass rate, the useful question becomes: what facts about this exam can actually be verified, and what do they imply about difficulty? Several can:
- Closed book. You cannot look anything up during the exam.
- Time pressure is moderate but real. Ninety minutes for 60 questions is an average of 90 seconds per question, and the NDA acceptance step is included in the allotted time under Pega's general guidance.
- Question types are varied. Pega lists possible single-response and multiple-response multiple-choice, matching/drag-and-drop, and reading-passage/scenario questions. The distribution is not specified for this version.
- A prerequisite gates entry. You need to already hold Certified Pega System Architect in any version.
These facts say more about what you will face than any unverified percentage could. For a fuller assessment of difficulty, read How Hard Is the CSSA Exam?
How the Exam Format Shapes Outcomes
Multiple-response and scenario questions
Single-response questions let you reason by elimination. Multiple-response questions are less forgiving, because you must identify every correct option rather than the best one. Scenario and reading-passage items add a different burden: you have to extract the relevant requirement from a block of text, then map it to a Pega capability. Candidates who learned the platform by clicking through missions sometimes struggle here, because they know how to build a feature but not how to justify one design over another in prose.
Drag-and-drop and matching
Matching items reward precise terminology. If you only recognize a concept visually in Dev Studio, you may not be able to pair it with its correct definition or use case under timed conditions. This is a good reason to review official terminology deliberately rather than relying on hands-on familiarity alone.
Extra time for some English-language 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. The exam is offered in English and Japanese. If you are in an eligible country, confirm the extra time appears on your confirmation before exam day rather than assuming it.
Domain Weights as a Proxy for Where Candidates Lose Points
Pega publishes the six exam domains and their percentages as official objectives. They are the closest thing to hard data on where the points are, and they tell you where a weak area will hurt most. Here is the breakdown for Platform '25:
| Domain | Weight | Approx. questions of 60* |
|---|---|---|
| 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 |
*Illustrative arithmetic only. Pega publishes percentages, not exact item counts per domain.
Application Development (30%)
The heaviest domain, and the one where a gap is hardest to absorb. Expect questions on how rules are organized, reused, and specialized across an application, and on choosing the right construct for a requirement.
- Rule resolution and how the platform selects among rule versions
- Application structure, layering, and reuse decisions
- Choosing between competing implementation approaches for a stated need
Case Management (20%)
Case design is core to Pega. Be ready to reason about how a business process is modeled as a case type and how work moves through it.
- Case life cycle design, stages, and steps
- Routing, assignments, and service-level expectations
- Parent and child case relationships
Data and Integration (20%)
This domain tests whether you can get data into and out of an application cleanly, and decide how and where data should live.
- Data modeling and data sources
- Connecting to external systems and exposing services
- Handling integration failures and data transformation
System Administration (15%)
Operational knowledge that is easy to neglect if your day job is purely development.
- Deployment and application packaging concepts
- Monitoring and diagnosing behavior in a running system
- Background processing and operational configuration
Security (10%)
A smaller domain but a precise one. Questions tend to hinge on knowing which mechanism governs which kind of access.
- Authentication versus authorization concepts
- Role-based access and what it controls
- Protecting data and restricting actions appropriately
User Experience (5%)
The lightest domain. Worth covering, but a poor place to spend your first weeks of study.
- Designing interfaces that fit the case and data model
- Reusing user interface components consistently
Because Application Development alone is 30%, a weak showing there makes the 70% threshold very difficult to reach through the other domains. For a full walk-through of each content area, see our complete guide to the six CSSA exam domains.
The Prerequisite Filter and Who Actually Sits the Exam
One reason any pass rate would be hard to interpret is that the candidate pool is pre-filtered. To attempt this exam you must already hold Certified Pega System Architect in any version, and Pega's preparation pathway for the Senior System Architect exam is the Senior System Architect mission. That means everyone in the room has already cleared one Pega exam and has hands-on exposure to the platform.
A pre-qualified pool can cut either way. It tends to remove complete beginners, yet it also means you are measured against peers who already know the fundamentals, so the exam is pitched above entry level. Details on eligibility are covered in CSSA requirements and how to qualify.
Version awareness matters
Your prerequisite certification can be from any version, but the Senior exam is version-specific. This article concerns Platform '25 (PEGACPSSA25V1). An earlier outline for Platform '24.2 uses a different eight-domain structure. Make sure the study material you use matches the version you are registering for, because mixing the two outlines is an easy way to study the wrong weights.
Retake Rules and the Cost of a Failed Attempt
Since no pass rate exists, plan around the rules you do know. Each attempt costs USD 190 plus applicable taxes (subject to change), and you pay the full fee every time. The retake policy is:
- Wait three calendar days after your first failure before retaking.
- Wait 14 calendar days after your second failure.
- Each exam version may be attempted three times in the 12 months beginning with your first attempt.
Key Takeaway
Treat your first attempt as the one you intend to pass. The three-day gap after a first failure is short enough to tempt a rushed second try, but the fee is full price each time and the attempt limit is finite. Use any failed attempt as diagnostic information about your weakest domain, then close that gap before rebooking. For the complete money picture, see the CSSA certification cost breakdown.
Delivery and ID logistics can sink an attempt
You can test at a Pearson VUE test center or through OnVUE remote proctoring. Acceptable identification is required, and the requirements differ by delivery method. A candidate who arrives without suitable ID, or whose remote environment fails the proctor's checks, loses the attempt through no fault of their knowledge. Check the delivery-specific requirements well before your date, and review scheduling and exam date guidance to plan your booking.
How to Spot Fabricated Pass-Rate Claims
Because this topic attracts invented numbers, it helps to know the warning signs. Be skeptical of any source that:
- Quotes a precise percentage without naming Pega as the source. Pega has not released one in the reviewed materials.
- Promises "real exam questions" or "official practice exams." Pega does not provide official practice certification exams and does not endorse third-party preparation materials. Mission quizzes and independent practice questions must not be represented as actual certification questions.
- Confuses the credential. If a page mixes in fees, dates, or domains that do not match Certified Pega Senior System Architect, it is describing something else.
- Guarantees a pass. No honest provider can, especially without any published outcome data.
Independent practice questions are still useful for building recall and pacing, as long as you understand what they are. If you want structured drills, you can try the practice tests on our main site, and keep in mind they are study aids, not leaked or official content.
A Domain-Weighted Preparation Schedule
This is the one place where scheduling advice belongs, and it should follow the exam weights rather than generic habit. Front-load the heavy, foundational domains, then circle back to the lighter ones. The sequence below assumes you already hold the System Architect certification and are working through the Senior System Architect mission.
Application Development (30%)
- Work through rule resolution, reuse, and application structure
- Practice justifying one design choice over another in writing
Case Management and Data and Integration (20% each)
- Model case life cycles and routing for sample scenarios
- Trace how data is sourced, transformed, and exchanged with external systems
System Administration and Security (25% combined)
- Review deployment, monitoring, and operational concepts
- Sort authentication, authorization, and access mechanisms precisely
User Experience, then timed review
- Cover the 5% domain briefly
- Do timed sets mixing multiple-response and scenario items to rehearse the 90-minute pace
For a broader plan that covers materials and sequencing, see the CSSA study guide, and keep the CSSA cheat sheet handy for last-minute review of must-know facts. The closed-book format means recall matters, so rehearse without notes in the final stretch.
If you are still deciding whether the effort pays off, the ROI analysis and the CSSA salary guide lay out the career side of the decision.
Frequently Asked Questions
No official pass rate for the Certified Pega Senior System Architect exam was found in the reviewed Pega sources. Any specific percentage you see quoted is unverified unless it cites Pega directly.
No. Seventy percent is the passing score, the performance level an individual candidate must reach. It says nothing about what share of all candidates pass.
The exam has 60 questions and a 90-minute time limit, with the NDA acceptance included in that time under Pega's general guidance. Eligible non-native-English-speaking candidates taking the English exam through Pearson VUE automatically receive 30 additional minutes.
Each exam version can be attempted three times in the 12 months beginning with your first attempt. You must wait three calendar days after the first failure and 14 after the second, and you pay the full USD 190 fee plus applicable taxes each time.
No. Pega does not provide official practice certification exams and does not endorse third-party preparation materials. Independent practice questions can help you build recall and pacing, but they cannot predict your result or represent actual exam content.