You can get 21 questions wrong on the Pega CPSA exam and still pass. The Certified Pega System Architect exam has 60 questions, a 90-minute limit and a 65% pass mark, so 39 correct answers is the line. This guide shows how to spend your study time where the marks are, topic by topic, so those 21 misses land on questions that matter least.
Most candidates do not fail because they skipped the material. They fail because they gave every topic the same attention. Case Management alone is a quarter of the exam, while DevOps and Insights together are a tenth. If your hours do not follow those numbers, your score will not either.
Below you will find the exam facts, the topic weights, a four-week plan built on those weights, and a way to use practice tests that actually moves your score.
What the Pega CPSA Exam Is and Who It Is For
The Certified Pega System Architect credential is the entry point for people who build applications on Pega Platform. Pega lists the exam at a beginner level. It is aimed at developers, business architects moving into build work, and new graduates joining a Pega practice.
The current exam is version '25, and it applies to Pega Platform '25. Its exam code is PEGACPSA25V1. You can check the live details, including the prerequisite learning path, on the Certified Pega System Architect exam page at Pega Academy.
Pega lists the System Architect mission as the prerequisite. That mission is the guided course that walks you through building a real application. Treat it as the base of your preparation, not an optional extra.
The exam is not only for full-time developers. Testers, business analysts and support engineers who work inside Pega projects often sit it too. They want to speak the same language as the build team and understand why an application behaves the way it does.
Why the CPSA Matters for Your Pega Career
For many people, the CPSA is the first Pega credential on their profile. It tells a hiring manager or project lead that you understand how Pega applications are put together, not just that you have heard of the platform.
It is also a strong base for whatever Pega study comes next. The habits you form now carry forward. If you learn to think in cases, stages and data objects today, the senior material later will feel like a next step rather than a fresh start.
There is a practical side too. Teams that build on Pega need people who can pick up a story, open the application and make a sound design choice without constant help. The topics on this exam, from routing and service levels to access groups and data transforms, are the same things you will touch in your first weeks on a real project.
Finally, the exam gives your study a clear finish line. Without a date on the calendar, learning a platform can drift for months. Booking the exam turns "I should learn Pega" into a four-week plan with a result at the end.
Pega CPSA Exam Facts at a Glance
Before you plan a single study session, get the numbers straight. These come from Pega Academy and the ProcessExam master record for this exam.
- Exam name: Certified Pega System Architect (CPSA)
- Version and code: version '25, PEGACPSA25V1
- Questions: 60
- Time: 90 minutes
- Pass mark: 65%
- Fee: USD 190
- Delivery: Pearson VUE, at a test center or online proctored
- Languages: English, Japanese, Spanish, French, German and Portuguese-Brazilian
- Level: Beginner
The online option means you can take the exam from a quiet, uninterrupted room at home or at the office. You book it through the Pearson VUE Pega testing page, where you also pick a date and check the system needs for online delivery.
The Math Behind Missing 21 Questions
Here is the simple arithmetic that shapes the whole plan. Sixty questions at a 65% pass mark means you need 39 correct answers. That leaves room for 21 wrong answers.
Ninety minutes across 60 questions gives you about 90 seconds per question. That is enough time to read a scenario carefully, but not enough to rebuild the whole case type in your head for every item.
The idea of a "miss budget" changes how you study. You are not trying to be perfect. You are trying to make sure your misses fall on the lightest topics and on the hardest edge cases, not on the core ideas that show up again and again.
A candidate who knows Case Management and Data and Integration very well has already covered close to half of the exam. A candidate who spread the same hours evenly across all eight topics may know a little of everything and not enough of anything.
The short video below from the ProcessExam channel walks through this same idea in under two minutes.
How the Eight Topic Areas Are Weighted
Pega publishes eight topic areas with a weight for each. This is the most useful table in your whole preparation, because it tells you roughly how many questions each topic will bring.
On a 60-question exam, those weights work out to about:
- Case Management, 25%: about 15 questions
- Data and Integration, 20%: about 12 questions
- Application Development, 15%: about 9 questions
- User Experience, 10%: about 6 questions
- Security, 10%: about 6 questions
- Pega GenAI, 10%: about 6 questions
- DevOps, 5%: about 3 questions
- Insights, 5%: about 3 questions
These counts are estimates from the percentages, not a promise of exact numbers on your form. Still, they show the shape of the exam clearly. The top two topics bring about 27 questions. The bottom two bring about 6.
For a full breakdown of what sits inside each area, the Pega CPSA syllabus breakdown on ProcessExam lists the subtopics for all eight areas in one place.
Case Management: Where a Quarter of Your Score Lives
Case Management is the heart of Pega, and the exam treats it that way. At 25%, it deserves more of your time than any other area.
This topic covers how a case moves from start to finish. You should be comfortable designing a case life cycle with stages and steps, setting case statuses, and adding service levels that set goals and deadlines. Routing work to the right person or queue, building approvals, and automating steps are all part of it too.
Child cases are a common source of mistakes. Know when a piece of work should become its own child case and how the parent case waits for it. Questions often describe a business situation and ask which design choice fits best.
The best way to learn this area is to build. Create a small case type in the System Architect mission, then change it. Add a stage, move a step, attach a service level, and watch what happens. When you can predict the result before you click, you are ready for scenario questions.
Data and Integration: The Second Pillar
Data and Integration carries 20% of the exam. Together with Case Management, it makes up 45% of your score.
This area covers data types and data objects, how they relate to each other, and how you validate what a user enters. It also covers data transforms, which set and copy values, and how a Pega application connects to outside systems.
Many candidates find this topic dry, so they read it once and move on. That is a costly habit. Questions here tend to test whether you know which tool fits which job, for example, when a data transform is the right choice and when you need an integration.
Practice by tracing data through your sample application. Follow one value from the screen where a user enters it, through a transform, to where it is stored or sent. That single exercise teaches more than a chapter of notes.
Application Development, UX, Security and GenAI
The next four topics sit in the middle of the table. Application Development is 15%, and User Experience, Security and Pega GenAI are 10% each. Together they make up 45% of the exam, the same share as the top two topics combined.
Application Development covers why teams choose Pega, how the platform is built, roles on a project, workspaces, debugging and managing rules. Expect questions on where to look when something breaks and how rules are organized.
User Experience covers views, templates, forms, field settings, channels, personas and localization. Know how a view is built and how the same application can serve different users.
Security covers authentication, authorization and role-based access. Understand how operators, access groups and personas decide who can see and do what.
Pega GenAI is the newest area. The syllabus names tools such as Blueprint, Autopilot, Knowledge Buddy, Coach and Connect Rules. Learn what each one is for and where it fits in the build process. You do not need deep theory, but you should not meet these names for the first time on exam day.
These topics reward steady coverage more than deep drilling. Aim to understand the main ideas in each, and make sure none of them is a blank spot.
DevOps and Insights: Small but Not Zero
DevOps and Insights are 5% each, or about three questions apiece. This is where a smart candidate spends part of the miss budget.
That does not mean skipping them. Three questions is still three questions. Learn the basics: DevOps covers continuous integration and delivery and testing a deployment, and Insights covers exploring data and building dashboards.
Give each of these one focused study session and one short review before the exam. If a question here stumps you on the day, move on without panic. You planned for it.
A 30-Day Pega CPSA Study Plan Built on Weights
This plan puts the heaviest topics first, while your energy is highest, and leaves the last week for timed practice. Adjust the days to your schedule, but keep the order.
Week 1: Case Management
Spend the first seven days on Case Management. Work through the matching parts of the System Architect mission and build one case type from start to finish. By the end of the week, you should be able to explain stages, steps, statuses, service levels, routing and child cases in your own words.
A simple day-by-day split works well. Days 1 and 2 cover the case life cycle, stages and steps. Day 3 covers statuses and service levels. Day 4 covers routing and approvals. Day 5 covers automation and child cases. Day 6 is for rebuilding your case type from memory, and day 7 is a short quiz on everything from the week.
Week 2: Data and Integration
Move to data. Build data objects, link them, add validation, and write a few data transforms. Then look at how the application talks to an outside system. End the week by tracing one value through the whole application.
Week 3: The Middle-Weight Topics
Cover Application Development, User Experience, Security and Pega GenAI, about a day and a half each. Save one day for DevOps and Insights together. Keep a short list of anything that still feels unclear.
Week 4: Timed Practice and Review
Now switch from learning to performing. Take a full timed set of 60 questions in 90 minutes. Review every miss, sort each one by topic, and restudy the weak topics. Repeat two or three times before exam day.
Keep a one-page tracker next to your desk. List the eight topics down the side and mark each one green, yellow or red after every practice set. By the end of week 4, the two heaviest topics should be green. A red mark on DevOps or Insights is not a crisis, but a red mark on Case Management is a reason to delay the exam by a week.
If you are short on time, cut days from week 3 before you cut them from weeks 1, 2 or 4. The top two topics and the timed practice are where the marks are.
Why Candidates Study the Right Material the Wrong Way
A common story goes like this. A candidate finishes the mission, reads every note, and still falls short. They studied the right material, but in the wrong order and with the wrong balance.
One LinkedIn write-up tells this story well: a CPSA candidate who studied the right material with the wrong outline. The lesson is the same one this guide is built on. The outline you follow matters as much as the content you read.
Other Pega exams show the same pattern. A post on the Pega CPCSD customer service exam makes the point that hands-on tracing and debugging beat passive reading. Another on the Pega CPDS data scientist exam shows how domain weights guide study for a very different Pega role.
Here are the most common mistakes to avoid:
- Equal hours for every topic. It feels fair, but the exam is not built that way.
- Reading without building. Scenario questions test judgment that only comes from doing.
- Skipping GenAI because it is new. At 10%, it is worth as much as Security.
- No timed practice. Knowing the answer slowly is not the same as knowing it in 90 seconds.
- Reviewing only the score. The score tells you where you are. The review tells you what to do next.
How to Read a Pega Scenario Question
Many CPSA questions are short business stories followed by a design choice. The story might describe a claims team, a loan request or a service desk. Your job is to spot which Pega feature solves the problem in the story.
Start by finding the real ask. It is usually in the last line: "What should the system architect do?" or "Which configuration meets this need?" Read that line first, then read the story with that question in mind.
Next, underline the signal words in your head. A phrase like "must be completed within two days" points to a service level. "Only managers can approve" points to routing, approvals or access. "The same details are used in several cases" points to a data object rather than fields copied into each case.
Then rule out the answers that are true but do not fit. Pega exams often list options that are real features but solve a different problem. If an option would work only with extra steps the story never mentions, it is probably not the best answer.
Last, choose the simplest option that fully meets the need. The answer that uses a built-in feature in the intended way is often the right one. Practice this four-step habit on every practice question until it runs on its own.
Exam-Day Strategy for the Pega CPSA
Good preparation can still slip on the day if you have no plan for the clock. Use these habits.
Pace in blocks. Check the clock after every 20 questions. At 90 seconds each, you should reach question 20 around the 30-minute mark and question 40 around the 60-minute mark.
Flag and move. If a question takes more than two minutes, pick your best answer, flag it and move on. A late question you never reach costs as much as a wrong one.
Read the whole scenario. Pega questions often hide the key detail in the last sentence. Look for words about who does the work, when it must be done, and what must happen if it is late.
Spend misses wisely. If a DevOps or Insights question feels unfamiliar, do not burn three minutes on it. That is exactly where your miss budget is meant to go.
Prepare the room. If you test online, clear your desk, close other programs and test your system the day before. A calm start is worth a few extra correct answers.
How Practice Tests Help You Pass
Practice tests are not a shortcut. They are a mirror. Used well, they show which topics are costing you marks and whether your pace fits the 90-minute limit.
ProcessExam offers practice exams for the Certified Pega System Architect that follow the same number of questions, time limit and pass mark as the real exam. They are independent study material, not Pega material, and no practice test can promise a pass. What they can do is give you a clear, honest read on where you stand.
Use them in three steps:
- Attempt. Sit a full set under exam conditions: 60 questions, 90 minutes, no notes.
- Review. For every miss, write down the topic and why the right answer is right.
- Retarget. Restudy the topics with the most misses, then test again within two days.
Watch how your misses spread across topics. If most of them sit in Case Management or Data and Integration, that is a warning sign, because those topics carry the most weight. If most of them sit in DevOps and Insights, you are spending your miss budget the way you planned.
This longer video from the ProcessExam channel covers how to get well prepared for the CPSA.
Pega CPSA FAQs
How many questions can I miss on the Pega CPSA exam?
The exam has 60 questions and a 65% pass mark, so you need 39 correct answers. That means you can miss up to 21 questions and still pass. Plan for those misses to fall on the lighter topics.
How long is the Certified Pega System Architect exam?
You get 90 minutes for 60 questions. That works out to about 90 seconds per question. Check your pace after every 20 questions so you do not run short at the end.
Which Pega CPSA topics carry the most weight?
Case Management is the largest at 25%, followed by Data and Integration at 20%. Together they make up 45% of the exam. Application Development is 15%, and User Experience, Security and Pega GenAI are 10% each.
Can I take the Pega CPSA exam online?
Yes. The exam is delivered by Pearson VUE, either at a test center or through online proctoring. For online delivery you need a quiet, uninterrupted room at home or at the office.
What should I study before the Pega CPSA exam?
Pega lists the System Architect mission on Pega Academy as the prerequisite. Build a sample application as you go, then use timed practice tests in the final week. Focus most of your hours on the two heaviest topics.
Your Next Step
The Pega CPSA exam does not ask you to be perfect. It asks you to get 39 of 60 right in 90 minutes. Put your hours where the weights are, build instead of only reading, and save the last week for timed practice.
Start today by opening the System Architect mission and building your first case type. Then write the eight topic weights on a sticky note and keep it where you study. Every session should move one of those numbers in your favor.