Pega CPBA study plan

Map the end-to-end Case Lifecycle vocabulary (stages, processes, steps, alternate stages, optional processes) and write a one-paragraph definition of each in your own words

Build a working case type from scratch with at least three primary stages, one alternate stage, and one optional process

Configure a service level agreement on a process and explain in writing how goal, deadline, and passed-deadline times differ

Demonstrate how stage transitions, dependencies, and process ordering control when a step becomes available

Configure routing at the case, stage, and step level and justify which routing target each level should use

Add conditional and optional steps, plus a multi-step approval, and verify behavior by running the case through every branch

Configure local actions, case-wide actions, and bulk actions, then explain when each is appropriate

Wire a subcase and a child case into a parent and describe how data flows between parent and child

Configure case-wide and stage-level settings that affect behavior across the lifecycle, including case locking and status values

Design and test a scenario where an alternate stage is entered and later returns control to the primary path

Implement a case dependency that blocks a step until a related case reaches a specific status

Trace a stuck or misrouted case using the audit trail and case history and document the root cause

Complete a full timed practice set on Case Management and review every missed item for the underlying concept, not just the answer

Apply the Pega Express delivery approach (kickoff, design thinking, build, and the role of a minimum lovable product) to a small scenario and explain each phase in writing

Identify which Pega Express artifacts (for example journey maps, backlog items, and user stories) would be produced at each phase of your scenario

Distinguish case data, data objects, and data pages, and configure each correctly in a working application

Configure a data page with the right scope and refresh strategy and justify the choice with a use case

Build a data transform that maps and defaults values, then test it with multiple inputs

Model a one-to-many relationship between a case type and a related data type and display it on a form

Configure a REST or SOAP connector to an external endpoint and handle both success and error responses

Explain how integration error handling, retry behavior, and queue processing interact in a failing integration

Configure role-based access with access control policies or roles and verify that a restricted user is actually blocked

Apply attribute-based and case-level access controls and describe the difference between authentication and authorization in Pega

Build a form with a layout that adapts to different screen sizes and explain how responsive breakpoints are configured

Configure a view or section with conditional visibility and dynamic behavior driven by a field value

Use application development tooling (ruleset and application structure, rule resolution, and inheritance) to explain why a rule in a specific ruleset wins

Create a reusable component and reference it from two places to demonstrate inheritance and specialization

Build a report definition with a filter, grouping, and a summary calculation, then surface it on a dashboard

Configure a mobile-ready channel or app experience and describe how offline behavior and mobile navigation differ from the desktop experience

Run a full timed mixed-domain practice exam and review every domain, weighting review time toward the lowest-scoring area

Revisit your written notes from weeks 1 through 7 and consolidate them into a single one-page-per-domain reference