1.1 Certified Pega System Architect Exam Format, Blueprint & Strategy

Certified Pega System Architect (CSA) Exam Format, Blueprint & Strategy

The Certified Pega System Architect (Pega CSA) certification represents the foundational industry benchmark for developers building enterprise solutions on the Pega Platform. Administered by Pegasystems, the CSA credential certifies that an architect understands core platform principles, knows how to model end-to-end case lifecycles, can construct reliable data models, and can implement low-code solutions adhering to Pega guardrails.

Achieving the CSA credential is also the mandatory prerequisite for advancing to senior credentials, including the Certified Senior System Architect (PCSSA) and Certified Lead System Architect (PCLSA) certifications.

---

1. Exam Parameters and Administrative Logistics

The Pega CSA exam is delivered exclusively through Pearson VUE, available either as an in-person proctored exam at an authorized Pearson VUE testing center or as an online proctored exam via Pearson VUE's OnVUE testing platform.

Core Exam Specifications

Retake Governance and Waiting Policies

Pegasystems enforces a strict global retake policy to preserve examination security and credential integrity:

1. First Retake (Attempt 2): If a candidate does not achieve the 65% threshold on their first attempt, they must wait at least three (3) full calendar days before taking the exam a second time.
2. Second Retake (Attempt 3): If the candidate does not pass on the second attempt, they must observe a mandatory fourteen (14) calendar day cooling-off period before their third attempt.
3. Annual Cap: A candidate may sit for the same exam code a maximum of three (3) times within any rolling 12-month period. If all three attempts are unsuccessful, the candidate must wait until 12 months have elapsed from their first attempt date before registering again.
4. Registration Fees: Each retake attempt requires payment of the full registration fee of $190 USD plus applicable taxes; Pegasystems does not offer discounted retake vouchers.

---

2. Examination Question Anatomy and Item Types

The 60 questions on the CSA exam assess both factual recall of platform mechanisms and scenario-based application of architecture patterns. The questions are presented in three distinct formats:

A. Standard Single-Response Multiple Choice

Candidates are given a direct technical question or brief scenario followed by four options, with exactly one correct answer. These items test definitions, rule capabilities, or direct platform behavior (e.g., identifying which class type cannot have instances).

B. Scenario-Based Multi-Response Questions

Candidates read a detailed business scenario involving enterprise requirements—such as routing a loan approval, configuring an SLA escalation, or defining data page scopes. The prompt explicitly specifies how many responses to select (e.g., "Select Two" or "Select Three"). Credit is awarded only when all correct options and no incorrect options are chosen; there is no partial credit.

C. Drag-and-Drop Matching Tasks

Interactive items require candidates to drag platform terms, rule types, or process steps into corresponding target drop zones. Common examples include:

• Matching business requirements to the correct routing strategy (Worklist vs. Work Queue).
• Mapping urgency values and action triggers to SLA intervals (Goal, Deadline, Passed Deadline).
• Categorizing rule authoring tasks between App Studio and Dev Studio.

---

3. The Official Blueprint: Two Active Exam Versions

Pega publishes a separate exam page for each platform version, and more than one version is active at once. Confirm which version your Pega Academy account and Pearson VUE booking reference before you study.

The '25 and '24 blueprints are close but not identical, and the differences are exactly where candidates lose marks.

Domain Weights Side by Side

+-----------------------------------------------------------------------+
|        PEGACPSA25V1 DOMAIN WEIGHTS (PEGA PLATFORM '25)                |
+-----------------------------------------------------------------------+
| [1] Case Management             [====================]  25%           |
| [2] Data and Integration        [================]      20%           |
| [3] Application Development     [============]          15%           |
| [4] User Experience             [========]              10%           |
| [5] Pega GenAI                  [========]              10%           |
| [6] Security                    [========]              10%           |
| [7] Insights                    [====]                   5%           |
| [8] DevOps                      [====]                   5%           |
+-----------------------------------------------------------------------+

What Changed From '24 to '25

1. Pega GenAI is new and carries 10%. Roughly six of the 60 questions cover material that did not exist on the previous version: Pega Blueprint, Autopilot, Coach, Connect Rules, Knowledge Buddy, and Agents with Tool Rules. Chapter 13 is devoted to it.
2. Mobile disappeared as a named domain. The '24 blueprint weights Mobile at 5% with two objectives (configure mobile app channels; configure swipe actions and image assets). The '25 blueprint has no Mobile domain, folding channel work into User Experience. Chapter 11 still covers mobile delivery because '24 remains active.
3. Reporting was renamed Insights and narrowed to the Insights and Explore Data material rather than classic report definitions.
4. Security doubled from 5% to 10% and now names authentication versus authorization, the Security Checklist, the relationship between operators, access groups, access roles, and personas, and role-based access control.
5. Case Management dropped from 33% to 25%, but it remains the largest single domain on both versions.

Domain Deep Dives

1. Case Management ('25: 25% | '24: 33%)

The largest domain on both versions. The published objectives cover: designing a case life cycle with stages, case statuses, and task instructions; adding a service level agreement with urgency, goals, deadlines, and passed deadlines; routing assignments to users, work groups, work queues, and by business logic; approval processes including cascading approvals and the authority matrix; identifying duplicate cases; optional actions in the case life cycle and on data objects; automating workflow decisions using conditions; the purpose of flow actions in a process; pausing and resuming case processing with wait steps; skipping a stage or process; configuring child cases; when to use automation shapes; automating decisions with decision tables and decision trees; and defining personas. The '24 version adds configuring and sending email correspondence and creating and managing teams of users.

2. Data and Integration ('25: 20% | '24: 23%)

The second cornerstone domain. Objectives cover describing the data model; configuring data types and creating data objects, data relationships, data records, and field types; identifying and creating calculated values; validating data with business-logic validation rules; manipulating application data, setting default property values, and configuring data transforms; accessing sourced data in a case, refresh strategies, and populating user interface controls; saving data to a system of record; and simulating application data. In platform terms this is the property-mode, data-page, data-transform, and connector material in Chapters 4 and 5, including value modes (Single Value, Value List, Value Group), page modes (Single Page, Page List, Page Group), data page scopes (Thread, Requestor, Node), and read-only, editable, and savable data page modes.

3. Application Development ('25: 15% | '24: 12%)

Objectives cover evaluating the benefits of using Pega Platform for digital solutions; explaining how the Situational Layer Cake, prescriptive design, studio interoperability, and the Reuse Library support modular enterprise reuse; describing the benefits of the Center-out architecture; describing the platform's accessibility features; defining the responsibilities of key roles in Pega project delivery; explaining the roles of workspaces and branches in development; managing application development with Agile Workbench including user stories, feedback, and bugs; creating and maintaining rules, rulesets, classes, inheritance, and relevant records; and debugging application errors. The '24 version also names the Estimator tool for scoping a project. Chapters 7 and 12 cover this domain.

4. User Experience ('25: 10% | '24: 12%)

Objectives cover configuring views and templates and customizing the full page view; differentiating default from hierarchical forms; configuring field settings, primary fields, and field groups; explaining how patterns, conditional expressions, and when rules control dynamic field behaviour; explaining channels and their relationship to personas and comparing portal templates; and describing landing page templates, themes, widgets, and localization best practices. The '24 version adds adding and removing fields, displaying list data with repeating dynamic layouts, and enabling accessibility features.

5. Security ('25: 10% | '24: 5%)

Objectives cover describing the relationship between authentication and authorization; identifying the benefits of the Security Checklist; explaining the relationship between operators, access groups, access roles, and personas; and describing role-based access control (RBAC). The '24 version phrases the domain as managing user and role assignments, configuring security policies, and tracking and auditing changes to data. Chapter 8 covers both framings, including access of role to object (ARO), privileges, and attribute-based access control.

6. Pega GenAI ('25: 10% | not on '24)

Objectives cover leveraging Pega GenAI Knowledge Buddy for client-specific contextual knowledge and support; the role of Pega Blueprint in transforming application design, including creating, importing, and modifying a Blueprint; analysing the role of Pega GenAI Autopilot in developing applications faster; integrating generative AI features using Pega GenAI Connect Rules; enabling custom AI-powered capabilities that guide users through complex processes with Pega GenAI Coach; and describing how Pega GenAI Agents and Tool Rules benefit application users. Chapter 13 covers all six.

7. Insights / Reporting (5% on both)

Objectives cover describing the benefits of using Insights; using the Explore Data landing page to create Insights; and, on '25, describing the relationship between Insights, dashboards, the Dashboards landing page, portal landing pages, and full page case views. Chapter 10 covers this along with the report definition mechanics that remain useful in practice.

8. DevOps (5% on both)

The '25 objectives are explaining Pega's process of continuous development, integration, delivery, and deployment (CI/CD) in application development, and describing the types of tests required to ensure a successful application deployment. The '24 objectives are narrower: recording a unit test and identifying best practices for configuring unit tests. Chapter 9 covers both, plus guardrail compliance scoring, severity levels (Severe, Moderate, Informational), and the Clipboard and Tracer diagnostic tools.

9. Mobile ('24 only: 5%)

The '24 objectives are configuring mobile app channels and configuring swipe actions and image assets. Chapter 11 covers mobile delivery, web mashup, and the channel and portal material that the '25 blueprint folds into User Experience.

---

4. Preparation Roadmap and Tactical Study Plan

To master this extensive syllabus, candidates should follow a structured 4-phase preparation methodology:

PHASE 1: Theory & Missions       PHASE 2: Hands-On Studio Labs
[Pega Academy System Architect]   [App Studio Lifecycle & UI]
               |                                |              
               v                                v              
PHASE 3: Deep Technical Rules    PHASE 4: Timed Triage & Drills
[Dev Studio, ECS, Tracer, ARO]   [60-Q Practice, 1.5 Min/Item]

Step 1: Complete the Official Pega Academy Mission

Work through the complete System Architect mission on Pega Academy. Complete every module, pass every module quiz with 100%, and review the challenge summaries. Do not merely skim the text—read the design rationale behind each architectural recommendation.

Step 2: Hands-on Low-Code Practice in App Studio

Spend significant time in a Pega Community Edition or training sandbox. Build an application from scratch:

• Model two distinct Case Types (e.g., Onboarding and EquipmentOrder).
• Configure primary stages, alternate stages, and stage transition conditions.
• Configure single-field routing and business-logic-based routing to Worklists and Work Queues.
• Implement multi-level SLAs on steps and stages with escalating urgency.

Step 3: Promote and Inspect in Dev Studio

Switch to Dev Studio to inspect the underlying rules generated by App Studio:

• Examine how Case Types appear in the Application Explorer under the Implementation layer.
• Open the generated Data Transforms and inspect property mapping syntax (.Customer.FirstName).
• Inspect the Clipboard (pyWorkPage, D_ Data Pages, and pxRequestor).
• Run the Tracer while submitting a case step to observe Rule Resolution and event sequencing.

Step 4: Time-Management & Question Pacing Triage

With 60 questions and 90 minutes, candidates have exactly 1.5 minutes (90 seconds) per question.

• The Two-Pass Method: On Pass 1, answer all short, direct factual questions immediately (aiming for 30–45 seconds each). For lengthy, multi-paragraph scenario questions, read the prompt, eliminate obviously false choices, select your best tentative answer, flag the item for review, and move on.
• Pass 2 Review: Use the remaining 20–25 minutes to revisit flagged scenario items. Re-read the scenario constraints carefully to verify that your selected answers satisfy all stated business conditions.

---

5. Common Exam Traps and Pitfalls

• Trap 1: Confusing App Studio vs. Dev Studio boundaries. Remember that App Studio handles Case Design, Data Model creation, View configuration, and Persona routing. Dev Studio is required for configuring Activities, advanced Integration connectors, custom SQL Report joins, and fine-grained Access Control (AROs).
• Trap 2: Conflating Value Lists with Page Lists. A Value List stores an ordered collection of single primitive values (e.g., a list of phone numbers: "555-0199", "555-0198"). A Page List stores an ordered collection of complex objects/pages, each containing multiple child properties (e.g., OrderLines(1).ItemName, OrderLines(1).Price).
• Trap 3: Reaching for Activities over Declarative Rules. Pegasystems strictly penalizes unnecessary Activity rules in guardrail reviews and exam questions. If a scenario requires computing a value or copying properties, the correct answer is almost always a Data Transform or a Declare Expression, never an Activity.
• Trap 4: Miscalculating SLA Urgency Accumulation. SLA urgency adjustments are additive. If initial assignment urgency is 10, reaching the Goal adds 15 (total 25), and reaching the Deadline adds 25 (total 50). Urgency cannot exceed 100 on standard Pega assignments.