Pega LSA study guide
Pega LSA · Work through your exam, one topic at a time.
The Certified Pega Lead System Architect (LSA) is described by Pega as the top level of certification, after Certified Pega Senior System Architect, and as a credential that "signifies an expert capability that an elite group of resources achieve." It is aimed at experienced architects who already hold the Certified Pega Senior System Architect credential, which Pega states is required to earn the LSA. The certification is not a single sitting. Pega describes a two-part examination process: candidates must first pass a written Architecture Exam, then demonstrate their acquired skills in a hands-on Application Exam by designing and building an application on Pega Platform. Because the two parts test different things, preparation should be split accordingly. Topics on this exam: Architecture (written exam) and Application Design and Build (hands-on exam). The Pega LSA study guide has 2 sections and about 843 words.
01Architecture (Written Exam): Enterprise Structure, Security, Deployment, and Performance
The Architecture written exam tests enterprise-level decisions: how you structure reusable applications with the Enterprise Class Structure and Situational Layer Cake, secure them, deploy them through environments, and keep performance predictable. Expect scenario questions where two answers both work but only one preserves upgradeability. Build from the top down: Organization, Division, and Unit form the enterprise layer; Framework and Application form the application layer; implementation classes hold case-type specialization. Put shared case types and data types in the framework or organization layer, and use directed inheritance plus circumstancing for local variation.
423 words, about 2 min02Application Design and Build (Hands-On Exam): Case Life Cycle, Data, UI, Integrations, and Testing
The Application Design and Build hands-on exam tests whether you can construct a working Pega application in App Studio: case life cycle, data model, views, routing, integrations, validation, and test coverage. The exam rewards solutions that use declarative, guardrail-compliant rules rather than procedural workarounds. Stages express the case's high-level states; processes contain steps and can run in parallel; steps are assignments or automations. Decide whether a process is case-wide or stage-only, and use alternate stages for exception paths rather than building parallel case types.
420 words, about 2 min