Requirements and acceptance criteria
A design should make the business outcome and the boundary of each decision testable.
Practice outputTurn an equipment-request brief into user goals, acceptance criteria and open questions.
Preparing for Pega LSA Application Design & Build? Strengthen how you analyse requirements, explain architectural decisions and practise building Pega applications.
Contact ITCertPath to discuss your preparation goals, the areas you want to improve and the guidance currently available.
Reviewed 25 October 2026 against Pega Academy · Independent preparation guidance; Pega controls assessment and certification.
This guide is for experienced Pega practitioners exploring the Lead System Architect pathway, candidates preparing for the Architecture exam and candidates planning for the later Application Design & Build assessment. These are related but different decisions: first confirm your credential prerequisites, then check the Architecture exam scope, then plan how to demonstrate design and implementation ability.
Pega lists System Architect and Senior System Architect certifications as required. It recommends substantial project experience—at least 36 months after Senior System Architect—but that recommendation should not be confused with an automatically enforced waiting period. Read the current CPLSA requirements at Pega Academy for your version and situation.
The Pega Lead System Architecture exam tests architecture and design knowledge; Pega currently identifies PEGACPLSA25V1 as its Platform ’25 Architecture exam code. The later Application Design & Build assessment asks candidates to analyse requirements, document design decisions and implement a solution. Do not use an Architecture-exam code as though it were a retail App Build voucher.
Pega Academy says the Infinity ’25 Application Design & Build assessment is now one phase and uses Pega Blueprint. It still requires human review of the generated design and the resulting application. Older descriptions of separate design and build phases should not be treated as the current format. Check Pega’s own instructions before any registration or preparation decision.
Use your own practice scenario to learn. Pega’s actual assessment scenario and assessed work are confidential; do not share them with ITCertPath or ask anyone to complete an assessed build.
The current Lead System Architect mission spans Constellation adoption, infrastructure, planning, design, implementation and deployment. The activities below turn those themes into independent learning outputs.
A design should make the business outcome and the boundary of each decision testable.
Practice outputTurn an equipment-request brief into user goals, acceptance criteria and open questions.
Case types, stages and reuse boundaries shape how the solution changes later.
Practice outputSketch the request life cycle; explain whether approval and fulfilment belong in one case or related cases.
The application must distinguish its own records from authoritative external data.
Practice outputList request, employee and inventory data objects, then mark which system owns each value.
A working flow is not enough if a requester can see or change another person’s decision.
Practice outputMake an access matrix for requester, manager and fulfiller; test denied actions as well as allowed ones.
Current Pega preparation includes reviewing generated design and modern view choices, not accepting them blindly.
Practice outputCritique a practice Blueprint’s case life cycle, personas and data model; note changes needed before implementation.
Out-of-stock items, failed integrations and delayed tasks need explicit recovery paths.
Practice outputDesign an exception route and an idempotent retry for an inventory-status update.
Architectural decisions must remain supportable when usage, data volume and teams grow.
Practice outputRecord one tradeoff between a quick local rule and a reusable component, including operational consequences.
A reviewer needs evidence that the requirement, rule and observed result agree.
Practice outputTrace each acceptance criterion to a test and explain one design decision in a short decision record.
Imagine employees requesting a laptop or monitor. A manager approves the request; inventory is checked; a fulfilment team assigns or orders the item; the requester receives an update. This is an independent ITCertPath learning example, not a Pega assessment scenario and not a prediction of one.
Write acceptance criteria for submitting, approving, rejecting and fulfilling a request. Decide whether stock replenishment is part of the same case or a related case. Capture requester, item and inventory data with clear ownership.
Define requester, manager and fulfiller access. Mark the inventory service as an external integration rather than copying its entire database. Record what happens if inventory is unavailable or an approval expires.
Review any Blueprint-generated structure with a human decision record. Test a valid request, rejection, out-of-stock route, retry and unauthorized action. Link each test back to an acceptance criterion.
For a worked method, read the Pega LSA practice-project and design-decision guide.
Check current Pega Academy prerequisites, assessment sequence and version. Note which requirements you already meet and which are recommendations.
Use the current Lead System Architect mission to revisit infrastructure, planning, implementation and Constellation topics. Make a list of decisions you cannot yet explain.
Use a self-created, non-assessment scenario. Produce requirements, a reviewed Blueprint or design outline, a small implementation and exception paths.
Ask whether each case, data, integration and security choice follows from a requirement. Test negative paths and document tradeoffs, not only happy-path screenshots.
Revise your practice project, review official guidance again and confirm the next authorized Pega step in your own account before scheduling.
See the detailed Pega LSA App Build study plan for a gap-review worksheet and practice sequence.
Tell us where you are in the Pega pathway and what you want to strengthen. We can discuss the preparation options currently available and whether they fit your goals. This page does not promise a particular instructor, mentoring package, project review, schedule or exam outcome.
Bring questions about your own practice work, not Pega’s confidential assessment scenario, submission or evaluation. Pega Academy remains the authority for official training, eligibility, assessment instructions, fees and certification decisions.
Ask About Available Preparation SupportIt involves strengthening architecture, requirements analysis, application design, implementation, testing and the ability to explain tradeoffs. For the current Infinity ’25 pathway, Pega describes one Application Design & Build assessment using Blueprint after the Architecture exam. Always confirm the version in Pega Academy.
They are separate steps in the Certified Pega Lead System Architect journey. Pega lists the Architecture exam first, followed by its Application Design & Build assessment. The current exam page identifies PEGACPLSA25V1 as the Architecture exam code; that code is not the App Build assessment code.
Practise translating requirements into case and data choices, refining a Blueprint, explaining reuse and integration boundaries, securing role-specific actions, handling exceptions and testing both successful and denied paths. Use a self-created scenario rather than official assessment material.
Use the current official mission and assessment guidance as your scope, build an original practice application, explain why you made each decision, test edge cases and revisit gaps. No practice plan or third-party guidance can guarantee a pass.
Documentation connects requirements to choices and makes tradeoffs reviewable. Tests show whether the implemented application respects the case flow, data rules, access boundaries and exception paths described in that design.
Yes. You can contact ITCertPath to discuss your own learning goals and ask about available preparation support. Do not send Pega’s confidential assessment scenario, assessed application, submission or feedback to us or anyone outside Pega’s authorized process.
Read Pega Academy’s CPLSA overview and the current Architecture exam and Application Design & Build instructions. Pega lists System Architect and Senior System Architect credentials as required; its 36-month experience recommendation is not presented as a universal hard prerequisite. Pega may update versions and eligibility.
Use the WhatsApp or call action on this page. Tell us your current certification stage and the topics you want to strengthen; we can discuss available preparation options without asking for confidential Pega assessment content.
Contact ITCertPath to discuss your experience, learning goals and available preparation support.