100+ Free Pega LSA Practice Questions

Pass your Certified Pega Lead System Architect (PEGACPLSA) exam on the first try — instant access, no signup required.

✓ No registration✓ No credit card✓ No hidden fees✓ Start practicing immediately

Not publicly published Pass Rate

100+ Questions

100% Free

1 / 100

Question 1

Score: 0/0

An enterprise stack uses one organization-layer application, one division-layer application, and three implementation-layer applications built on top. A property must be reusable by all three implementation apps and the division app, but not by other divisions. Where should the property's class be defined?

In the organization layer so all of Pega can reuse it

In each implementation layer so each team owns its copy

In the division layer so only that division and its implementations inherit it

In a personal ruleset of the senior architect so changes are auditable

to track

2026 Statistics

Key Facts: Pega LSA Exam

Exam Questions

Pega Academy LSA Architecture exam page

120 min

Time Limit

Pega Academy LSA Architecture exam page

65%

Passing Score

Pega Academy LSA Architecture exam page

$190

Architecture Exam Fee

Pega Academy

CPSSA

Required Prerequisite

Pega Senior System Architect certification in any version

15%

Largest Domains

Data Model Design and Security Design

$500

App Design and Build Fee

Separate 14-day, 75% hands-on assessment

3 attempts

Per 12 Months

Pega exam-attempt policy from first attempt date

The PEGACPLSA Architecture exam is 60 questions in 120 minutes with a 65% passing score and a $190 USD fee, delivered at Pearson VUE test centers or online proctored. Pegasystems requires Certified Pega Senior System Architect (CPSSA) certification in any version before you can register, and recommends 12+ months of hands-on LSA-level field experience. The blueprint is weighted toward Data Model Design (15%) and Security Design (15%), followed by Application Design (13%), Pega Platform Design (12%), Reporting Design (12%), Work Delegation Design (10%), Asynchronous Processing Design (8%), Deployment and Testing Design (8%), and User Experience Design (7%). The Architecture exam is only Phase 1: full LSA certification also requires the LSA Application Design and Build assessment, a 14-day, ~50-hour, $500 hands-on engagement scored at 75%.

Sample Pega LSA Practice Questions

Try these sample questions to test your Pega LSA exam readiness. Each question includes a detailed explanation. Start the interactive quiz above for the full 100+ question experience with AI tutoring.

1An enterprise stack uses one organization-layer application, one division-layer application, and three implementation-layer applications built on top. A property must be reusable by all three implementation apps and the division app, but not by other divisions. Where should the property's class be defined?

A.In the organization layer so all of Pega can reuse it

B.In each implementation layer so each team owns its copy

C.In the division layer so only that division and its implementations inherit it

D.In a personal ruleset of the senior architect so changes are auditable

Explanation: Pega's enterprise class structure isolates reuse to the lowest common ancestor. The division layer sits between the organization and the three implementations, so a property defined there is inherited by the division app and all implementations built on it, but not by sibling divisions.

2Two implementation teams need divergent business logic on the same case type, and the divergence is permanent and tied to the line of business. Which approach best supports long-term maintainability?

A.Add when conditions to every step in the shared flow

B.Specialize the case type in each implementation layer using class inheritance

C.Create a single flow with a privately checked-out copy in production

D.Branch the framework ruleset and never merge it back

Explanation: Permanent divergence aligned to a line of business is the textbook case for class-based specialization in the implementation layer. Each implementation inherits the framework case type and overrides only what differs, keeping shared behavior in the parent.

3A program has three teams: a component team, a framework team, and an implementation team. The component team ships reusable connectors. Which division of work most reduces release coupling?

A.Implementation team owns connectors so changes ship with the business release

B.Component team owns connectors, framework team consumes a fixed version, implementation team configures only data instances

C.Framework team owns connectors and implementation team modifies them per release

D.Each team co-owns every connector to avoid single points of failure

Explanation: Versioned ownership is what decouples release schedules. The component team publishes a frozen version, the framework consumes it, and the implementation only configures runtime data instances. This is the canonical Pega multi-team operating model.

4Several implementation applications must share a common case type that occasionally needs implementation-specific UI. What is the cleanest design?

A.Define the case type in the framework and override only the relevant sections in each implementation class

B.Copy the case type into each implementation and keep the copies in sync manually

C.Move the case type to the organization layer so every app sees the same UI

D.Embed the implementation choice in a single section using nested when conditions

Explanation: Defining the case type once in the framework and circumstancing or specializing UI sections per implementation class preserves shared logic while letting each implementation own its own presentation layer.

5An LSA must decide whether a new customer-facing portal should ship in Constellation or in the older Cosmos React UI. Which factor most strongly favors Constellation?

A.The team needs deeply customized handcoded React components

B.The team wants Pega-supported, design-token-driven UI generated from case design

C.The portal must run on Pega Platform 7.x

D.The team prefers section rules with classic harnesses

Explanation: Constellation is Pega's design-system-driven UI architecture that derives the user experience from case design and Pega-supplied components. When the team wants Pega-supported, design-token-aligned UX rather than a custom React stack, Constellation is the right choice.

6A division application must absorb a Pega Industry Foundation framework upgrade every six months without disrupting two implementation applications already in production. Which architectural rule is most important to enforce?

A.Implementations must never declare classes that override framework rule names

B.Implementations may freely save-as framework rules into their own ruleset

C.Framework rules must be locked into the implementation rulesets

D.Every framework rule must be copied into the organization layer for safety

Explanation: Pega's intended pattern is for implementations to specialize via save-as into their own ruleset and class, leaving framework rules untouched. That way framework upgrades flow through cleanly and only the deliberately specialized rules need re-validation.

7An LSA inherits an application where every business unit has its own copy of an org-wide application rule. New business units cannot reuse anything. What refactor restores reuse?

A.Promote shared rules into a higher-layer enterprise application and have each business app build on it

B.Move all rules into one giant implementation application

C.Replace the application stack with a single ruleset on the organization class

D.Use an access-of-role-to-object rule to grant each business unit access to every rule

Explanation: The canonical fix is the enterprise class structure: a higher-layer enterprise or organization application owns shared rules, and each business application builds on it. New business units inherit reuse for free.

8A program team wants to release new business behavior every two weeks without redeploying the application. Which Pega capability best enables that?

A.Branch rulesets shipped via Deployment Manager

B.Decisioning data instances and decision tables maintained in production by business users

C.Hotfix patches applied through Pega support

D.Direct rule edits in production with a private checkout

Explanation: When change is data-shaped (rates, eligibility tables, decision strategies), Pega's intended pattern is to expose it as decisioning data instances and decision tables that business users can update in production without a new release.

9A new implementation must reuse 80% of an existing case type but render a completely different mobile experience. Which is the most appropriate approach?

A.Create a new case type from scratch in the implementation layer

B.Reuse the framework case type and override only the channel-specific UI in the implementation

C.Modify the framework case type to fork by channel

D.Disable the framework case type and replace it with a Constellation-only flow

Explanation: Reusing the framework case type and overriding only the channel-specific UI keeps 80% of behavior shared and isolates the divergence to UI rules in the implementation, which is exactly what specialization is for.

10Which application stack is the most appropriate base for a multi-tenant SaaS implementation built on Pega?

A.Enterprise foundation app, then a tenant-shared app, then per-tenant implementation apps

B.One implementation app with all tenants sharing the same access groups

C.A single ruleset deployed once and copied per tenant database

D.A flat ruleset list with tenant identifiers stored on every rule

Explanation: A clean multi-tenant Pega design layers an enterprise foundation, then a tenant-shared app for cross-tenant logic, and finally per-tenant implementation applications for branding and divergence. This preserves reuse and isolates tenant-specific behavior.

About the Pega LSA Exam

The Certified Pega Lead System Architect (PEGACPLSA) Architecture exam validates senior-level judgment for designing and governing enterprise-grade Pega Platform applications. It is the written, scenario-heavy first phase of the LSA program: candidates who pass become eligible for the LSA Application Design and Build assessment. Topics span enterprise application architecture, advanced case design, data model strategy, security, reporting, asynchronous processing, deployment, and testing across complex multi-team Pega implementations.

Assessment

60 scenario, multiple-choice, and drag-and-drop items delivered through Pearson VUE

Time Limit

120 minutes

Passing Score

65%

Exam Fee

$190 per attempt (Pegasystems)

Pega LSA Exam Content Outline

15%

Data Model Design

Enterprise-class data model strategy: system of record patterns, data pages with refresh and access strategies, savable data pages, declarative chains, decision data store, materialized views, Pega-supplied Cassandra-backed Interaction History, ADM and CDH datasets, and integration class hierarchy decisions across an application stack.

15%

Security Design

Application security architecture: access control policies and policy conditions, attribute-based access control, authentication services for OAuth 2.0 and SAML, identity federation, KEK and DEK rotation for platform encryption, role and access group inheritance across built-on layers, and operator provisioning patterns.

13%

Application Design

Enterprise application stacking: framework versus implementation layers, divisions of work between component, framework, and implementation teams, Constellation versus traditional UI selection, application packaging, multi-app strategies, and reuse patterns across business units.

12%

Pega Platform Design

Cluster topology and node classification (WebUser, BackgroundProcessing, BIX, Stream, Search, RealTime, ADM, CustomerDecisionHub), platform service distribution, Pega Cloud and on-premises deployment patterns, multi-data-center considerations, and capacity planning for production-grade systems.

12%

Reporting Design

Reporting strategy at scale: optimized properties versus exposed columns, database indexes for reports, the difference between PEGAUSER and PEGADATA partitions, summary and aggregate reports, list view performance tuning, BIX extracts, and Pega Search backed by Elasticsearch for full-text and aggregation reporting.

10%

Work Delegation Design

Routing strategy across complex case workloads: skill-based and business-logic routing, work group and workbasket design, get-next-work versus pull-from-list patterns, urgency calculations, SLA design, attended versus unattended work allocation, and supervisor reassignment governance.

Asynchronous Processing Design

Background work patterns: Queue Processor (standard and dedicated), Job Scheduler, advanced agents, child case orchestration, Stream Service usage for Kafka-backed events, Event Strategy Manager for real-time processing, and resilience and ordering guarantees for asynchronous flows.

Deployment and Testing Design

DevOps strategy: Deployment Manager pipelines, branching and merging, regression and unit test suites with the PegaUnit framework, Pega Test Automation, application packaging, rolling deployments, hotfix strategy, and environment promotion across dev, QA, staging, and production.

User Experience Design

UX architecture decisions: Constellation versus Cosmos React versus traditional UI, design system selection, channel strategy across web and mobile, portal customization, accessibility, and balancing prebuilt Pega UX with custom components.

How to Pass the Pega LSA Exam

What You Need to Know

Passing score: 65%
Assessment: 60 scenario, multiple-choice, and drag-and-drop items delivered through Pearson VUE
Time limit: 120 minutes
Exam fee: $190 per attempt

Keys to Passing

Complete 500+ practice questions
Score 80%+ consistently before scheduling
Focus on highest-weighted sections
Use our AI tutor for tough concepts

Pega LSA Study Tips from Top Performers

1Front-load Data Model Design and Security Design, because together they account for 30% of the blueprint and most LSA-style scenarios depend on getting class structure, savable data pages, and access control policies right.

2Practice walking through Pega cluster topology and node classification (WebUser, BackgroundProcessing, BIX, Stream, Search, ADM, CustomerDecisionHub) so platform-design questions become procedural rather than memorized.

3Drill case and data hand-offs across framework versus implementation layers, including divisions of work between component teams, framework teams, and implementation teams on a multi-business-unit Pega stack.

4Be fluent in the difference between Queue Processor, Job Scheduler, advanced agents, Stream Service, and Event Strategy Manager so asynchronous-processing questions become a quick pattern match.

5Treat reporting as an architecture concern: optimized properties versus exposed columns, database indexes, PEGAUSER versus PEGADATA partitions, BIX extracts, and Pega Search on Elasticsearch all show up in scenario questions.

6Study Pega security beyond basic access groups: policy conditions, attribute-based access control, OAuth 2.0 and SAML authentication services, identity federation, KEK and DEK rotation, and operator provisioning across environments.

7Practice translating a multi-channel UX decision into a Constellation versus Cosmos React versus traditional UI recommendation, including which channel each design system best supports.

8Walk through a Deployment Manager pipeline end to end, including branches, merges, PegaUnit and Pega Test Automation regression, application packaging, and a rolling deployment, since the deployment-and-testing domain expects opinion, not just recall.

Frequently Asked Questions

How many questions are on the Pega Lead System Architect Architecture exam?

Pega Academy lists 60 questions delivered in 120 minutes. Items include scenario questions, multiple choice, and drag-and-drop. The exam is delivered through Pearson VUE either in a test center or online proctored.

What is the passing score for the PEGACPLSA Architecture exam?

Pega Academy states the Architecture exam passing score is 65%. The companion LSA Application Design and Build assessment uses a separate 75% benchmark and runs as a 14-day hands-on engagement worth $500 USD.

Do I need to be a Senior System Architect first?

Yes. Pega Academy requires Certified Pega Senior System Architect (CPSSA) certification in any version before you can begin the LSA program. Pega also recommends at least 12 months of hands-on field experience operating at LSA scope before you sit the exam.

How much does the PEGACPLSA Architecture exam cost?

The Architecture exam is $190 USD per attempt at Pearson VUE. Each exam may be taken up to three times in any rolling 12-month period, with the 12-month window starting on the first attempt date. The Application Design and Build assessment is a separate $500 USD per attempt.

Which exam version should I take in 2026?

Pega Academy lists PEGAPCLSA86V2 as the current Architecture exam blueprint and recommends candidates plan around the Pega Infinity 25 release. Pegasystems has stated the Pega Infinity 24.2 LSA exam will retire on 30 June 2026, and the Application Design and Build exam on Pega Infinity 25 becomes available for scheduling on 1 May 2026.

What domains carry the most weight?

Data Model Design and Security Design tie for the largest weight at 15% each, followed by Application Design (13%), then Pega Platform Design and Reporting Design at 12% each. The lighter domains are Asynchronous Processing Design (8%), Deployment and Testing Design (8%), and User Experience Design (7%).

Is the LSA Architecture exam scenario-based?

Yes. Pega Academy explicitly describes scenario questions, multiple choice, and drag-and-drop items. Expect long context stems with multiple stakeholder constraints rather than recall-only items, since the exam targets candidates who can defend architectural decisions in front of project sponsors.