- The Short Answer: What CSSA Means
- Why the Credential Is Really "PCSSA" at Pega
- What the Credential Actually Proves
- Where It Sits on the Pega Certification Ladder
- The Exam at a Glance
- The Six Domains and What They Test
- Who Looks for This Credential
- The Version Trap: '25 vs. '24.2
- A Domain-Weighted Prep Sequence
- Frequently Asked Questions
- On this site, CSSA means Certified Senior System Architect, issued by Pegasystems; Pega's formal name is Certified Pega Senior System Architect (PCSSA).
- The current exam is PEGACPSSA25V1 for Pega Platform '25: 60 questions, 90 minutes, 70% to pass.
- Application Development carries 30%; Case Management and Data and Integration carry 20% each.
- You need Certified Pega System Architect in any version before you can sit for it.
The Short Answer: What CSSA Means
CSSA stands for Certified Senior System Architect. On this site, the abbreviation refers to one specific credential: the senior-level architect certification from Pegasystems, the vendor behind the Pega Platform for case management, workflow automation, and customer engagement applications. If you arrived here after searching the acronym, note that other credentials elsewhere in the technology world use similar letters. Nothing on this page applies to them. Everything here concerns the Pega credential only.
If you want the fastest orientation on the term itself, our shorter explainers on what CSSA stands for and the meaning of CSSA cover the basics. This article goes further: it explains what the letters represent in practice, how the exam is built, and what a candidate must master to earn the title.
Why the Credential Is Really "PCSSA" at Pega
Pega's official name for the exam is Certified Pega Senior System Architect, which abbreviates to PCSSA. The "P" distinguishes it from the many other "senior system architect" titles in the industry. The site abbreviation CSSA is retained here because it is the shorthand that candidates, recruiters, and job postings commonly use for this certification.
The distinction matters in two practical ways:
- Searching and verification. When you look for the exam in the Pega Academy catalog or verify someone's credential, search by the full Pega-branded name rather than the acronym alone.
- Exam codes. The current exam code is PEGACPSSA25V1. The code embeds the platform version ("25"), which tells you the exam is tied to Pega Platform '25.
What the Credential Actually Proves
A System Architect certification shows you can build Pega applications using the platform's low-code rules and guardrails. The Senior System Architect goes further. It signals that you can design with more depth: structuring applications for reuse, modeling case lifecycles properly, integrating with external systems, shaping user experience, administering the environment, and securing the application. In team terms, a senior architect is the person others expect to make sound design decisions rather than simply configure a given requirement.
Where It Sits on the Pega Certification Ladder
The Senior System Architect credential is not an entry point. Pega requires Certified Pega System Architect in any version as a prerequisite, and the Senior System Architect mission on Pega Academy is the issuer's recommended preparation pathway. That makes the CSSA the second rung for most people who start on the architect track.
Be careful not to conflate neighboring exams. The System Architect exam and the Lead System Architect exam are separate certifications with their own objectives. Studying for one does not substitute for another, and this article's facts apply only to the Senior System Architect exam. For a full breakdown of eligibility, see our guide to CSSA requirements and prerequisites.
| Credential level | Role in the path | Relationship to CSSA |
|---|---|---|
| Certified Pega System Architect | Foundation-level architect certification | Required before attempting CSSA (any version) |
| Certified Pega Senior System Architect | Senior-level design and build competence | This is the CSSA |
| Lead System Architect | Separate, higher-level examination | Not covered by CSSA objectives; do not mix preparation |
The Exam at a Glance
Here are the mechanics for the current Platform '25 exam, drawn from Pega's published certification information:
| Item | Detail |
|---|---|
| Exam code | PEGACPSSA25V1 (Pega Platform '25) |
| Questions | 60 |
| Time allowed | 90 minutes |
| Passing score | 70% |
| Languages | English and Japanese |
| Fee | USD 190 per attempt plus applicable taxes (subject to change) |
| Delivery | Pearson VUE test centers or OnVUE remote proctoring |
| Format | Closed book |
Question styles you may see
Pega lists several possible formats: single-response multiple choice, multiple-response multiple choice, matching or drag-and-drop, and reading-passage or scenario-based questions. The distribution across those formats is not specified for this exam version, so avoid any source that claims a precise breakdown. What you should expect is that scenario questions reward people who have actually built applications, because the right answer often depends on knowing how Pega behaves rather than recalling a definition.
Test-day logistics worth knowing
- NDA time. Accepting the non-disclosure agreement is required and, under Pega's general guidance, is included in the allotted examination time. Do not assume you get 90 minutes of pure question time.
- Identification. Acceptable ID is required; follow the Pearson VUE requirements for whichever delivery method you choose.
- Extra time. 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.
- Retakes. You must wait three calendar days after a first failure and 14 days after a second. Each exam version may be attempted three times in the 12 months beginning with the first attempt, at the full fee each time.
For the pricing picture in more detail, read our CSSA certification cost breakdown, and for the scoring threshold see what you need to pass.
The Six Domains and What They Test
The six domain names and percentages below are official exam objectives. They tell you where the questions come from and, by extension, where your study time should go. Our complete guide to all six CSSA domains goes deeper on each; this section gives you the working summary.
| Domain | Weight |
|---|---|
| Application Development | 30% |
| Case Management | 20% |
| Data and Integration | 20% |
| User Experience | 5% |
| System Administration | 15% |
| Security | 10% |
Application Development (30%)
The heaviest domain, and the one that most defines "senior." Expect questions on how applications are structured and how rules are organized, reused, and resolved at runtime.
- Application layering and how rulesets and class structure support reuse
- Rule resolution: why one version of a rule runs instead of another
- Building reusable components rather than one-off configurations
- Choosing the right rule type for a requirement
Case Management (20%)
Pega's signature capability. This domain tests whether you can model a business process as a case life cycle rather than a flowchart of screens.
- Case types, stages, steps, and how they map to a real business process
- Child cases, parent-child relationships, and coordinating work across cases
- Service-level agreements, routing, and assignment behavior
- Deciding when to split work into separate cases versus keeping it in one
Data and Integration (20%)
Tied for second-largest. Senior architects are expected to connect Pega applications to data and external systems cleanly.
- Data modeling and data types, including how data is sourced and refreshed
- Integrating with external systems through connectors and services
- Handling errors and responses from external calls
- Choosing where data should live and how often it should be fetched
User Experience (5%)
The smallest domain, but not one to skip. Questions are typically about configuring forms and interfaces appropriately for the audience and task.
- Building and configuring user-facing views
- Reusing interface components consistently
System Administration (15%)
Operational knowledge: how the environment is managed and how applications are moved and monitored.
- Application deployment and promotion across environments
- Monitoring, troubleshooting, and basic performance awareness
- Background processing and operational configuration
Security (10%)
Access control is a recurring theme in real projects, and the exam reflects that.
- Access groups, roles, and privileges
- Controlling who can see and do what within an application
- Securing data and integrations appropriately
Who Looks for This Credential
Pega Platform is used by large organizations that run complex, regulated, process-heavy operations, so demand for certified practitioners tends to concentrate in a few places:
- Enterprises running Pega in-house that staff internal architect and development teams, commonly in sectors such as financial services, insurance, healthcare, and telecommunications.
- Consulting and systems-integration firms that implement Pega for clients and often use certification levels to staff projects and demonstrate partner competence.
- Pega itself and its ecosystem partners, where certification is a natural expectation for technical roles.
Job postings for Pega roles frequently list certification levels in their requirements, and a Senior System Architect certification is commonly named for senior developer and architect positions. We don't quote salary figures here because none are published in the sources we rely on; for a qualitative discussion of earning potential, see our CSSA salary guide, our look at CSSA jobs, and the ROI analysis. One reassuring detail on durability: Pega certifications currently do not expire, although Pega reserves the right to impose recertification requirements in the future.
The Version Trap: '25 vs. '24.2
This is the single most common way candidates misprepare. Pega publishes a separate Senior System Architect exam for Platform '24.2 (PEGACPSSA24V1), and its outline is organized into eight domains, not six. The '25 exam described in this article uses the six-domain structure above. If you pull a study outline, a set of notes, or a forum post that lists eight domains, it belongs to the older exam and will steer your time toward the wrong proportions.
| Item | Platform '25 exam | Platform '24.2 exam |
|---|---|---|
| Exam code | PEGACPSSA25V1 | PEGACPSSA24V1 |
| Domain count | Six | Eight |
| Use in this article | Primary scope | Comparison only |
Always confirm which version you are registering for in the Pega Academy catalog before you commit to a study plan.
A Domain-Weighted Prep Sequence
Rather than a generic schedule, sequence your study by how the domains depend on each other and how heavily they are weighted. One reasonable ordering:
Application Development (30%)
- Start here: layering, rulesets, and rule resolution underpin everything else
- Work through the Senior System Architect mission on Pega Academy
Case Management (20%)
- Build and rebuild case types with stages, child cases, and SLAs
- Practice explaining why a design choice beats the alternative
Data and Integration (20%)
- Model data and wire up connectors, then break them and handle the errors
Administration, Security, and User Experience (30% combined)
- Cover System Administration (15%), Security (10%), and User Experience (5%) in proportion
- Finish with timed, scenario-style review
Key Takeaway
Hands-on practice in a Pega environment matters more than memorization, because scenario questions test how the platform behaves. Use the official mission content for preparation, and treat any third-party question set as practice only. Pega does not provide official practice certification exams and does not endorse third-party materials, so no practice question should be treated as a real exam question.
For a fuller plan, see our CSSA study guide, the one-page CSSA cheat sheet, and our assessment of how hard the exam is. To test yourself against exam-style scenarios, try the CSSA practice tests on the main site, and explore our training overview for structured learning options. A note on expectations: no official pass rate was found in the sources we reviewed, and the 70% figure is the passing score, not a pass rate. Our pass rate article explains the distinction.
Frequently Asked Questions
On this site, CSSA stands for Certified Senior System Architect, the senior-level architect certification from Pegasystems. Pega's formal name for it is Certified Pega Senior System Architect (PCSSA). See also our page on what CSSA stands for.
Yes. Pega requires Certified Pega System Architect in any version as a prerequisite. The Senior System Architect mission on Pega Academy is the issuer's preparation pathway.
The Platform '25 exam (PEGACPSSA25V1) has 60 questions in 90 minutes, and the passing score is 70%. The exam is closed book and available in English and Japanese.
The fee is USD 190 per attempt plus applicable taxes, subject to change. After a first failure you wait three calendar days; after a second, 14. Each exam version allows three attempts in the 12 months starting from your first attempt, at the full fee each time.
Pega certifications currently do not expire, but this is subject to change, and Pega reserves the right to impose recertification requirements. Check the Pega Academy certification pages for the latest policy.